accessibility
/accessibility
Buduje i testuje strony i aplikacje dostępne dla osób z niepełnosprawnościami wg WCAG 2.2 AA, zgodnie z EAA, ADA i RPwD.
- Autor
- devpilotX ↗
- Repozytorium
- ai-skill-ai ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 31.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 31.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/a11y_check.py
Co robi i kiedy
Buduje i testuje strony i aplikacje dostępne dla osób z niepełnosprawnościami wg WCAG 2.2 AA, zgodnie z EAA, ADA i RPwD.
Oryginalny opis (EN)
Build and test websites and apps that disabled people can actually use, to WCAG 2.2 level AA, the way professional auditors test. Use when a build must meet an accessibility law (European Accessibility Act, ADA Title II, Section 508, India RPwD Act and GIGW), when fixing audit findings, when adding a dialog, menu, tab set, combobox or carousel, or when checking keyboard, screen reader, zoom, contrast, forms or motion. Runs a static markup check, then names the manual tests a script cannot do. Triggers on accessibility, a11y, WCAG, WCAG 2.2 AA, screen reader, keyboard navigation, alt text, colo
Jak działa
- When to use and when to stay off
- Non-negotiables
- Procedure
- Self-audit
- What this cannot do
Podgląd SKILL.md
--- name: accessibility description: Build and test websites and apps that disabled people can actually use, to WCAG 2.2 level AA, the way professional auditors test. Use when a build must meet an accessibility law (European Accessibility Act, ADA Title II, Section 508, India RPwD Act and GIGW), when fixing audit findings, when adding a dialog, menu, tab set, combobox or carousel, or when checking keyboard, screen reader, zoom, contrast, forms or motion. Runs a static markup check, then names the manual tests a script cannot do. Triggers on accessibility, a11y, WCAG, WCAG 2.2 AA, screen reader, keyboard navigation, alt text, colour contrast, ARIA, focus order, EAA, ADA, Section 508, GIGW, accessible name, VPAT. For colour and type use visual-design. For motion use motion-design. For label and error wording use ux-writing. For component kits use ui-compose. For component code use frontend-build. For the CI gate use quality-gates. For the pre-launch sweep use ship-audit. For a native app use mobile-build. For the whole site plan use website-build. license: MIT metadata: version: 1.0.0 suite: ai-skill --- # Accessibility to WCAG 2.2 AA The common failure is a page that looks finished and locks out a real group of people: an icon button a screen reader announces as "button", a form field with no programmatic label, a modal that does not trap focus so the keyboard wanders behind it, a colour pair no low-vision reader can tell apart, a carousel that cannot be paused. None of these show in a design review on a mouse and a good monitor. They show when a blind user hits the page with NVDA, when a motor-impaired user has only a keyboard, when a regulator audits it. This skill builds accessibility in from the markup out, then tests it the way an auditor does: a static check first, then the keyboard, the screen reader, zoom, contrast and the real content. It never confuses a clean automated scan with an accessible product. ## When to use and when to stay off Run when the work decides whether a disabled person can use the thing: building an interactive component, fixing audit findings, meeting an accessibility law, or testing a build before release. Stay off, and route instead, when: - The work is colour palettes, type scale or visual hierarchy. Use `visual-design`, and bring the contrast numbers back here. - The work is animation, transitions or `prefers-reduced-motion`. Use `motion-design`; this skill only checks that motion is reducible. - The work is the wording of labels, buttons, error messages or instructions. Use `ux-writing`; this skill checks the label exists and is associated, not how it reads. - The work is finding an open-source component kit to start from. Use `ui-compose`; confirm the kit's accessibility claims here. - The work is writing the component's framework code. Use `frontend-build`; this skill supplies the pattern it must implement. - The work is wiring the check into a pipeline as a gate. Use `quality-gates`. - The work is the final pre-launch sweep across everything. Use `ship-audit`. - The target is a native mobile app, not a web view. Use `mobile-build`; the manual tests here still apply through TalkBack and VoiceOver. - The work is the whole-site architecture and page plan. Use `website-build`. The user says "stop", "I've decided", or "just execute": comply at once and stay off for the rest of the session unless asked again. ## Non-negotiables These override everything else in this file. 1. Semantic HTML before ARIA. A native `button`, `a`, `label`, `input`, `nav`, `main` or heading carries its role, its name and its keyboard behaviour for free. Reach for ARIA only to fill a gap the platform leaves, and never put a role on an element that already has it. The first rule of ARIA is to use a native element instead where one exists (W3C ARIA Authoring Practices, verified October 2026). 2. An automated pass is not a pass. A tool finds a minority of WCAG failures; the rest need a human. Never report a build as accessible or compliant on a green scan alone. State what the script checked, then what the keyboard, screen reader, zoom and content review found, with dates. 3. Every interactive thing works with the keyboard alone, in a visible, logical order, with no trap. Tab reaches it, Enter or Space operates it, Escape closes it, focus is always visible and never lost behind an overlay. A control that only responds to a mouse or a pointer is a failure (WCAG 2.1.1, 2.4.3, 2.4.7, 2.4.11). 4. Every non-text element that carries meaning has a text alternative, and every decorative one is hidden from assistive technology. An informative image has descriptive `alt`; a decorative image has `alt=""`; an icon-only control has an accessible name; a chart or canvas has an equivalent in text or a data table (WCAG 1.1.1). 5. Target the current law for the jurisdiction, and name it. WCAG 2.2 level AA is the technical bar this skill builds to. Which law applies, and its date, is a legal question: a lawyer confirms legal compliance, not this skill and not a tool. 6. Every version, date, licence and legal deadline in this file carries its "verified" or "as of" date, because they move. A fact without a date is treated as stale. ## Procedure Depth is in the reference files: WCAG 2.2 AA criteria and the six new ones in `references/wcag22-aa.md`; the law table with dates in `references/law.md`; the manual test scripts in `references/manual-tests.md`; the ARIA component patterns in `references/aria-patterns.md`; the findings report format in `references/report-format.md`. ### Step 1, fix the target and the law Write down the standard (WCAG 2.2 level AA) and, for each market, the law that makes it binding and its compliance date. The headline laws, each checked against its official source in `references/law.md`: - European Union: the European Accessibility Act (Directive 2019/882) applies from 28 June 2025, with the technical requirements in EN 301 549 (which references WCAG). Verified against the European Commission EAA page, October 2026. - United States, state and local government: the ADA Title II web rule adopts WCAG 2.1 level AA. An Interim Final Rule published 20 April 2026 extended the compliance dates to 26 April 2027 for entities serving a population of 50,000 or more, and 26 April 2028 for smaller entities and special district governments. Verified against ada.gov, October 2026. - United States, federal: Section 508 requires EN 301 549 / WCAG 2.0 level AA conformance for federal ICT. - India: the Rights of Persons with Disabilities Act 2016 (Sections 40 to 46) mandates accessibility; GIGW 3.0 (February 2025) aligns government sites to WCAG 2.1 level AA, and IS 17802 (harmonised with EN 301 549) covers ICT products and services. Verified October 2026. Building to WCAG 2.2 AA satisfies the technical bar of all of these, because 2.2 is a superset of 2.1 and 2.0. It does not by itself make the product legally compliant: that is the lawyer's call, phrased in "What this cannot do". ### Step 2, build with semantic HTML, add ARIA only to fill gaps Start every component from the native element. A link navigates, a button acts, a `label` is tied to its control with `for`/`id` or by wrapping it, a `fieldset`/`legend` groups related controls, one `main` holds the primary content, headings nest without skipping a level, and landmarks (`nav`, `header`, `footer`, `aside`) mark the regions. Add a visible skip link to `main` as the first focusable element. Only when no native element gives the behaviour (a disclosure, a tab set, a combobox) reach for the ARIA pattern, and implement it whole: the roles, the states, the keyboard interaction and the focus management together. Read `references/aria-patterns.md` for dialog, menu, tabs, combobox and carousel, each traced to the W3C ARIA Authoring Practices Guide. A half-built ARIA widget (a `role` with no keyboard code behind it, an `aria-expanded` that never changes) is worse than the plain element it replaced. ### Step 3, handle the hard cases: names, live regions, focus, data and canvas - Accessible names: an icon-only control gets `aria-label` or visually hidden text, never a bare glyph. Decorative images get `alt=""`; informative images get descriptive `alt`; complex images (a chart) get a short `alt` plus a longer description or an adjacent data table. - Live regions: content that updates without a reload (a search result count, a form error summary, a toast) sits in an `aria-live` region so a screen reader announces it. Use `polite` for status, `assertive` only for genuine interruptions. - Focus management in single-page apps: on a route change, move focus to the new view's heading and update the page title, or the screen reader user is stranded on a stale element. On opening a dialog, move focus in and trap it; on closing, return focus to the trigger. - Data tables: real `table`, `th` with `scope`, a `caption`. Do not fake a table with `div`s. - Charts, 3D and canvas: a `canvas` or WebGL scene is opaque to assistive technology. Provide a text equivalent, a data table, or an accessible DOM overlay. Respect `prefers-reduced-motion` for anything that animates. ### Step 4, run the static check Run the bundled script against the built HTML before any manual testing, so the cheap, certain defects are gone first: ``` py -3 scripts/a11y_check.py ./dist py -3 scripts/a11y_check.py ./dist --strict --json a11y.json ``` It checks page language, title, image `alt`, labelled form controls, named buttons and links, vague link text, heading order, a single `main`, duplicate ids, positive `tabindex`, focusable elements inside `aria-hidden`, autoplaying media, a zoom-blocking viewport, and inline colour contrast where both colours are literal. Fix every error, confirm each warning. This is a static reader: it proves what the markup proves and nothing about the rendered page. For rendered pages, add a browser engine. `axe-core` (Deque, MPL-2.0, verified October 2026) is the standard; run it through Playwright, or `npx @axe-core/cli <url>`, or Lighthouse's accessibility category (Lighthouse is Apache-2.0). Pa11y (LGPL-3.0) wraps the same engines from the command line, and the W3C Nu Html Checker (MIT) validates the markup. `references/manual-tests.md` gives the exact commands. ### Step 5, test the way an auditor does, by hand No tool catches these. Work through `references/manual-tests.md`: - Keyboard only: unplug the mouse. Tab through the whole page. Every control is reachable, operable, in a sensible order, with a focus indicator you can see, and no trap. Modals trap and release focus correctly. - Screen reader: NVDA (free, Windows) with Firefox or Chrome, VoiceOver on macOS and iOS, TalkBack on Android, JAWS where it is the user's reality. Confirm names, roles, states and announcements match what is on screen. - Zoom and reflow: 200 percent zoom with no loss of content or function, and 400 percent (reflow, WCAG 1.4.10) with no two-dimensional scrolling for a single-column read. - Reduced motion: with `prefers-reduced-motion: reduce` set, non-essential animation stops. - Contrast: text at least 4.5:1 (3:1 for large text), and UI components and focus indicators at least 3:1 (WCAG 1.4.3, 1.4.11). - Forms and errors: errors are identified in text, tied to their field, and suggest a fix; nothing relies on colour alone. - Media: captions on video, a transcript for audio, no content that flashes more than three times a second. - Timeouts: a user can turn off, adjust or extend any time limit. ### Step 6, write the findings report Record every issue in the format in `references/report-format.md`: the WCAG success criterion and level, the severity, the users it affects, where it is, and the fix. Separate what the script found from what a human found, and date the run. Hand the report to the fix owner and, where law is in play, to the lawyer. ## Self-audit - The target standard (WCAG 2.2 AA) and the governing law with its date are written down, and legal compliance is left to a named lawyer. - Every component starts from a native element; ARIA appears only where no native element fits, implemented whole with roles, states, keyboard and focus. - `scripts/a11y_check.py` was run against the built output, its date recorded, every error fixed and every warning resolved. - A rendered-page engine (axe-core, Lighthouse or Pa11y) was run, with its licence noted, or its absence is stated. - The manual battery was done: keyboard only, a screen reader, 200 and 400 percent zoom, reduced motion, contrast, forms and errors, media, timeouts, each with a result. - Every image, icon control, chart and canvas has a text alternative or is correctly hidden. - No claim of "accessible" or "compliant" rests on an automated scan alone. - Every version, licence, date and legal deadline in the deliverable carries its date. ## What this cannot do It cannot certify legal compliance. WCAG conformance is a technical result; whether a specific product in a specific market meets the law is a legal judgement that turns on the entity, the jurisdiction and the date. Ask a lawyer qualified in disability and digital-accessibility law in the relevant country: "Given this product, this market and today's date, does it fall under the European Accessibility Act, ADA Title II or III, Section 508, or the RPwD Act, and does WCAG 2.2 AA conformance satisfy that obligation?" It cannot replace testing by disabled people. An automated check and an expert manual pass catch most defects, but only real users of screen readers, switch access, voice control and magnification find the problems that make a page pass a checklist and still fail a human. Budget for usability testing with disabled participants where the stakes warrant it. It cannot prove the rendered experience from markup alone. The static script reads HTML; visible focus, keyboard operation, reflow, screen reader output and stylesheet-driven contrast need a browser and a person, which is why steps 4 and 5 exist.
Pliki w paczce (7)
- SKILL.md 14 KB
- references/aria-patterns.md 4 KB
- references/law.md 4 KB
- references/manual-tests.md 5 KB
- references/report-format.md 4 KB
- references/wcag22-aa.md 5 KB
- scripts/a11y_check.py 27 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · devpilotX/ai-skill-ai | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| evanca/flutter-ai-rules | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| xobotyi/cc-foundry | 100 | MIT |
| krzysztofsurdy/code-virtuoso | 100 | MIT |
| andreibesleaga/gabbe | 100 | CC-BY-4.0 |
Migawka bazy z 13.11.2026 · wersja paczki f27ef9a0ae1d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100web-accessibility
Buduje i audytuje interfejsy webowe zgodnie z WCAG 2.2 AA: semantyczny HTML, klawiatura, formularze, kontrast i dialogi. - 100accessibility-auditor
Audytuje strony i komponenty pod kątem zgodności z WCAG 2.2: problemy czytników ekranu, kontrast kolorów i nawigację klawiaturą. - 100accessibility-audit
Audytuje interfejsy web pod kątem WCAG 2.2 AA narzędziami axe i Lighthouse oraz ręcznie: klawiatura, czytnik i kontrast. - 100site-accessibility
Sprawdza stronę, ekran lub komponent pod kątem WCAG 2.2 AA: kontrast, skan axe lub Lighthouse, obsługę klawiaturą i czytnik ekranu. - 100a11y-audit
Sprawdza stronę lub aplikację pod kątem WCAG 2.2 A/AA w przeglądarce, poprawia kod i weryfikuje każdą poprawkę ponownym audytem. - 100accessibility-compliance-audit
Audytuje interfejsy HTML, React, Vue i Angular pod kątem WCAG 2.2 AA i generuje gotowy kod poprawek.