Frontend Accessibility Check

When To Use

Use this skill for frontend work under src/frontend when the change affects:

• UI components, primitives, pages, routes, dialogs, drawers, popovers, dropdowns, tabs, accordions, tables, forms, navigation, or canvas controls.
• ARIA attributes, labels, roles, focus management, tab order, keyboard interaction, disabled states, loading states, or error states.
• A new route or existing route surface that should be scanned.
• A request to add, fix, run, or review accessibility tests.

Use alongside:

• frontend-testing for Jest/React Testing Library patterns.
• e2e-testing for Playwright patterns.
• frontend-i18n when adding or changing user-facing labels, accessible names, aria-label, tooltips, or visible strings.
• ibm-a11y-automation to run the Python IBM route scanner and produce Markdown/HTML reports.
• ibm-a11y-level1-audit for a full IBM Level 1 audit → report → fix → verify loop against Equal Access Level 1 criteria.