The Accordion component renders its header as
but never makes that element focusable and never listens for keyboard events. The Alpine binding for the header registers @click only.
As a result:
• The accordion header cannot receive keyboard focus (no tabindex).
• Even if focus could be forced onto it, nothing would happen, because there is no keydown handler for Enter or Space.
• The panel content is hidden with x-show (display: none), so there is no alternative path to the content on the page.
As a result:
• The accordion header cannot receive keyboard focus (no tabindex).
• Even if focus could be forced onto it, nothing would happen, because there is no keydown handler for Enter or Space.
• The panel content is hidden with x-show (display: none), so there is no alternative path to the content on the page.
Net effect: a keyboard-only user cannot open any accordion panel and therefore cannot read any of the content inside it. On the page linked above, that is six FAQ answers — a substantial part of the page — that are entirely inaccessible.
This is a failure of WCAG 2.2 Success Criterion 2.1.1 Keyboard (Level A): “All functionality of the content is operable through a keyboard interface.”
Please see the attached bug report.
Thank you,
Jan
bugreport-accordion-realmac.md (17.5 KB)
