Accessibility
Every part aims to meet WCAG 2.2 level AA, in the code you take home as well as on this site.
How parts are tested
- axe accessibility rules for WCAG 2.0, 2.1 and 2.2, levels A and AA, with each part closed and open.
- Keyboard-only flows: open, move, pick and close without a mouse, with focus returned where it came from.
- Target sizes of at least 24 by 24 CSS pixels, and no sideways scrolling at phone widths.
- Chromium, WebKit (the engine behind Safari) and an emulated iPhone 15.
- The same tests run on every exported output (React + Tailwind, HTML/CSS/JS, and the Vue, Svelte, Astro, Angular, Solid and Web Component files built from it, the Vue and Svelte ones server-rendered too) for every variant of the options.
Patterns followed
Interactive parts follow the WAI-ARIA Authoring Practices Guide: combobox, dialog, menu button, tabs, accordion, disclosure, carousel and tooltip. Each part's page lists its pattern and the keys it answers to.
Known limits
- Automated tests cannot judge what a screen reader actually says. Each part has a manual checklist on its page, including what a screen reader should announce, to run with the one you use.
- WebKit in the test runner is close to Safari but not identical; a real-device check stays on the checklist.
- Colours you choose in the editor can lower contrast. Accent colours used as text are corrected automatically, but check your final palette.
- Once the code is in your project, what you change is yours to test.
Report a problem
If something on this site or in an exported part does not work with your assistive technology, please tell Adesh Shukla through devstash.me, with the part, the browser and the tool you used.