Review component accessibility with AI
Review the states of a reusable component, from its accessible name and focus order to the way it behaves in a real page.
Review component accessibility with AI when a shared control behaves differently across a product. A menu that opens correctly from a toolbar may put focus somewhere unexpected when the same menu appears in a dialog. The accessible-component-review skill starts by listing supported variants, states and ways of interacting.
The review checks the native element, its name and role, keyboard behaviour and the visual conditions that change what a user can perceive. Findings can lead back to the shared component or to the way one page uses it. Trying representative consumers helps the team distinguish those cases.
What it does
- Check a tab set with a keyboard as well as a pointer.
- Compare an icon-only button with the version that has a visible label.
- Review the messages announced when a control changes state.
- Try zoom, forced colours and reduced motion on supported variants.
- Confirm that a component-level change still works in representative screens.
Install and use
- Provide component source or a working example and a browser. Use the project's regular tests if available and list the variants you support.
- Work through the interaction with a keyboard and inspect how each state is exposed to assistive technology.
- Review the smallest appropriate change at its source, then recheck affected examples.
FAQ
Source
Made by a11y-agent-skills contributors (smukh). Original skill: accessible-component-review, published on GitHub under the MIT licence.
View on GitHub