Review collapsible accordion sections for keyboard and screen reader access. Check button triggers, expanded-state attributes, panel links, and heading structure, then guide fixes using the HTML actually delivered to the browser.
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.
Review and fix collapsible accordions so people can use them with a keyboard or screen reader. This skill checks whether each control uses a button element, whether aria-expanded communicates its expanded or collapsed state, and whether aria-controls connects it to the corresponding content panel. It also checks operation with Enter, Space, and arrow keys, along with a heading structure that fits the document.
Use it when keyboard users get stuck in collapsible content, or when screen reader output makes the state and relationship between controls and content hard to understand. It also helps review shared components used across multiple screens and HTML generated from templates. Alongside framework source, it inspects the final HTML delivered to the browser and identifies the specific elements, attributes, and pages with problems.
There are no special notes.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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/rules/html/accordion-accessibility
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.