wcag-checklist-builder
Builds a per-component WCAG 2.2 accessibility checklist from a component spec - covers focus management, color contrast, ARIA roles & states, keyboard interaction, error handling, and live-region announcements - emitting a markdown checklist or YAML test plan that pairs with screen-reader-test-author for manual verification and the violation gate for automated scans. Use during component-spec review or pre-implementation acceptance.
Install with skills.sh (any agent)
npx skills add testland/qa --skill wcag-checklist-builderwcag-checklist-builder
Overview
A component-level a11y checklist makes acceptance criteria explicit before implementation. Without one, "is this accessible?" becomes a vague handoff between design, eng, and QA. This skill takes the component's spec (props, states, interaction model) and emits the matching WCAG 2.2 checklist.
The checklist pairs with:
When to use
Step 1 - Identify the component archetype
The skill maps to one of these archetypes; each has its own checklist pattern:
| Archetype | Examples |
|---|---|
| Static text / display | Heading, badge, banner, blockquote. |
| Interactive - single trigger | Button, link, icon button. |
| Interactive - form input | Text input, checkbox, radio, select, switch. |
| Interactive - multi-state | Disclosure, accordion, tabs, popover. |
| Interactive - overlay | Modal, drawer, dropdown menu, command palette. |
| Composite | Combobox, date picker, multi-select, tree. |
| Live region | Toast, alert, in-page status, error banner. |
| Layout / navigation | Header, footer, breadcrumb, pagination. |
For each archetype, the matching checklist sections are below.
Step 2 - Apply the per-archetype checklist
Static text / display
Interactive - single trigger
Interactive - form input
Interactive - multi-state (disclosure / accordion / tabs)
Interactive - overlay (modal / drawer / popover)
(See wcag-focus-trap for the 6-step pattern.)
Composite (combobox, date picker, multi-select)
(See aria-authoring-patterns.)
Live region
Layout / navigation
Step 3 - Add per-component customization
Beyond the archetype defaults, the spec may declare:
Step 4 - Emit the artifact
The skill produces two outputs:
Manual-verification items must be emitted as concrete keystrokes and expected announcements - never as a bare skill name. The artifact ships into the user's repo and has to be runnable by a tester holding only that file. Baseline commands (per the NVDA user guide (opens in new window) and Apple VoiceOver (opens in new window); same set as screen-reader-test-author):
| Action | NVDA + Firefox (Windows) | VoiceOver + Safari (macOS) |
|---|---|---|
| Next heading | H | VO (Ctrl+Option) + Cmd + H |
| Next form field | F | VO + Cmd + J |
| Read next / previous item | Down / Up arrow | VO + Right / Left arrow |
| Enter focus mode on a field | Enter | (automatic) |
| Activate the focused control | Enter | VO + Space |
| Element list overlay | - | VO + U (web rotor) |
A step passes when the announcement identifies the element type, reads the visible label verbatim, and conveys state and position-in-set where applicable.
Markdown checklist (for spec / PR review)
## A11y Checklist - `<ComponentName>`
**Archetype:** Interactive - overlay (modal)
### Required (must pass before merge)
- [ ] Modal has `role="dialog"` and `aria-modal="true"`.
- [ ] Modal title is `aria-labelledby`-referenced.
- [ ] On open: focus moves to first focusable inside modal.
- [ ] Tab cycles within modal; outside content is `inert`.
- [ ] Escape closes; focus returns to trigger.
- [ ] Close button has accessible name "Close" or "Dismiss".
- [ ] Focus indicator on close button at ≥3:1 contrast.
### Per-component (this design adds)
- [ ] Confirmation modal's "Delete" button has `aria-describedby`
linking to the warning text.
- [ ] On confirm: live region announces "Deleted" via
`aria-live="polite"`.
### Verification
- Automated: axe-core scan with `dialog` rule enabled.
- Manual (NVDA + Firefox, Windows): press `Enter` on the trigger -
NVDA announces "Confirm delete, dialog"; `Tab` cycles inside the
dialog and never reaches page content; `Escape` closes and focus
returns to the trigger, announced as "Delete, button".
- Manual (VoiceOver + Safari, macOS): `VO`+`Space` on the trigger,
`VO`+`Right arrow` to walk the dialog contents, `Escape` to
close - same expected announcements.
- Code review: against the checklist above.YAML test plan (for test-management tools)
component: ConfirmModal
archetype: overlay-modal
checks:
- id: AC-MODAL-1
description: Modal has role and aria-modal
severity: blocker
method: automated
rule: axe::role-modal
- id: AC-MODAL-2
description: Focus moves to first focusable on open
severity: blocker
method: e2e-test
framework: playwright
- id: AC-MODAL-3
description: Escape closes; focus restored
severity: blocker
method: e2e-test
- id: AC-MODAL-4
description: Live region announces "Deleted" on confirm
severity: blocker
method: manual
tester_role: a11y-specialist
instructions: >-
NVDA + Firefox (Windows): Tab to "Delete", press Enter.
NVDA must speak "Deleted" from the aria-live="polite" region
without focus moving. VoiceOver + Safari (macOS): VO+Space on
"Delete"; same announcement expected.Anti-patterns
| Anti-pattern | Why it fails | Fix |
|---|---|---|
| Generic checklist for all components | Static text doesn't need keyboard checks; modal does. | Per-archetype checklist; pick once. |
| Checklist created post-implementation | A11y becomes a retrofit; bugs found late. | Run this skill on the spec, before implementation. |
| Marking items "won't fix" without rationale | Loss of institutional knowledge; same item resurfaces next quarter. | Document each waiver with a date + reviewer initials. |
| One mega-checklist per component (50+ items) | Reviewer fatigue; rubber-stamping. | Per-archetype defaults; only add custom items the design demands. |
References
Related skills
a11y-violation-gate
Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.
aria-authoring-patterns
Reference for the W3C ARIA Authoring Practices Guide (APG) - covers the 31 canonical interactive-widget patterns (Combobox, Dialog, Menu, Tabs, Tree, etc.), their required ARIA roles and states, the keyboard-interaction model per pattern, and the canonical-violations to watch for. Use when authoring a custom interactive widget that doesn't have a native HTML equivalent, or when reviewing one for ARIA correctness.
axe-a11y
Authors and runs axe-core accessibility scans - the most-deployed open-source a11y engine - via the `axe.run()` JavaScript API or the @axe-core/playwright / @axe-core/cli wrappers, parses the `violations[]` results into per-rule severity (critical / serious / moderate / minor), configures rule disable / disable-by-tag patterns, and emits JUnit-shaped output for CI gating. Use when the project ships UI tests in JavaScript / TypeScript and wants automated a11y coverage on every PR.
ibm-equal-access-a11y
Authors and runs IBM Equal Access accessibility-checker scans - IBM's open-source a11y engine with WCAG 2.0 / 2.1 / 2.2 + US Section 508 rule sets, integrating with Node / Selenium / Puppeteer / Playwright / Karma / Cypress test runners. Distinguished by IBM's enterprise-tier rule coverage and Section 508 specificity. Use when the project ships to US federal / public-sector customers (Section 508 mandate) or when the team values IBM-branded a11y reporting.
lighthouse-a11y
Configures Lighthouse CI's Accessibility category for automated accessibility testing (a11y / WCAG coverage) - `categories:accessibility` audits backed by axe-core (axe) - with per-URL minimum-score assertions (fail a build when a page's score drops below a threshold) and per-audit overrides, distinct from the Performance category that `lighthouse-perf` covers. Use when the project already runs Lighthouse CI for Web Vitals and the team wants to add accessibility coverage in the same pipeline rather than spinning up a separate scanner.
pa11y-a11y
Authors and runs pa11y accessibility scans - a CLI / Node.js tool that wraps HTML CodeSniffer (htmlcs) and / or axe-core engines - with `pa11y {url}` invocation, reporter selection (cli / csv / json / html / tsv), WCAG standard selection (WCAG2A / WCAG2AA / WCAG2AAA), and rule ignoring. Use when the project needs scriptable a11y scans without a full test framework, or when a Node-stack project wants an alternative to direct axe-core use.
screen-reader-test-author
Builds a screen-reader test narrative - a step-by-step manual test script for NVDA (Windows), JAWS (Windows), VoiceOver (macOS / iOS), or TalkBack (Android) - that exercises a specific user flow through a component or page and captures the expected announcement at each step. Use when authoring an accessibility-acceptance test the team will run before sign-off, OR when scripting a manual a11y audit.
wave-a11y
Runs WebAIM WAVE accessibility scans via the WAVE API or the browser-extension UI - produces visual overlay of errors / alerts / structural elements directly on the page, plus categorized JSON output for CI use. Use when the team values manual-review-friendly visual feedback (the WAVE overlay) alongside automated CI scans, or when a regulatory audit requires WebAIM-branded reports.
wcag-color-contrast
Reference for WCAG 2.2 color-contrast conformance - covers SC 1.4.3 Contrast (Minimum, AA), 1.4.6 Contrast (Enhanced, AAA), 1.4.11 Non-text Contrast (AA), and 1.4.13 Content on Hover or Focus (AA) - with the canonical contrast ratios (4.5:1 normal text, 3:1 large text and UI components), measurement formula references, and bulk design-token checking patterns. Use when designing a color palette, reviewing a component for accessibility, or auditing existing CSS for contrast violations.
wcag-compliance-reporter
Builds a per-page WCAG 2.2 compliance score report by aggregating output from one or more accessibility scanners (axe-core / pa11y / lighthouse / WAVE / IBM Equal Access), pivoting violations by Success Criterion (1.4.3 contrast, 2.4.7 focus visible, etc.), grouping by conformance level (A / AA / AAA), reporting per-page coverage gaps explicitly (the "this page wasn't scanned" failure mode), and emitting both an executive summary and a per-page drill-down. Use after a multi-page accessibility scan - pa11y-ci, axe across a sitemap, lighthouse-batch - when the team needs a shareable conformance report rather than a per-page tool dump.
wcag-focus-trap
Reference for **intentional** focus management in modal / dialog / drawer / popover components - the canonical pattern that satisfies WCAG SC 2.4.3 (Focus Order) without violating SC 2.1.2 (No Keyboard Trap). Covers focus-on-open, focus-cycle-within-container, Escape-closes-and-restores, return-to-trigger, and inert-the-rest-of-the-page. Use when authoring or reviewing any component that displays content over the page (modals, drawers, popovers, command palettes).
wcag-keyboard-navigation
Reference catalog for WCAG 2.2 keyboard-navigation conformance - covers SC 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), 2.1.4 (Character Key Shortcuts), 2.4.3 (Focus Order), 2.4.7 (Focus Visible), 2.4.11/2.4.12 (Focus Not Obscured) - with conformance levels (A/AA), test scripts, and per-criterion failure patterns. Use when authoring or reviewing keyboard-only interaction support.
widget-a11y-test-matrix
Per-widget manual accessibility test matrices where every row pairs one keystroke with the expected focus behavior, the expected NVDA announcement, the expected VoiceOver announcement, and the WCAG 2.2 success criterion that row verifies. Covers button, toggle button, checkbox, text input, modal dialog, menu button, and combobox archetypes, plus universal Tab traversal. Use when a rendered widget has cleared automated scanning and a tester needs a fill-in pass/fail sheet to run by hand against NVDA and VoiceOver.