Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Make accordions keyboard navigable. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -22% | 0% |
| case-02 | ✓→✗ | ▼ Worse | -23% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -41% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -32% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -27% | 0% |
Poorly implemented accordions trap keyboard users and leave screen reader users unable to understand or navigate collapsed content sections.
Verify accordions use button triggers with aria-expanded, aria-controls, and proper keyboard navigation (Enter, Space, arrows).
Implement accordions with button elements, aria-expanded state, aria-controls linking to content panels, and keyboard support.
Explain the ARIA pattern for accessible accordions and how they enable keyboard and screen reader users to navigate collapsible content.
Review templates, server-rendered HTML, and shared components that output markup related to Make accordions keyboard navigable. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/accordion-accessibility
Other measured skills in the registry, with their headline benchmark lift.