Overview
Accessibility fails in design systems when it is treated as a checklist applied after components are built. A component that passes an automated accessibility scan can still be unusable with a keyboard, confusing to a screen reader, and invisible to a user with low vision — because automated tools catch 30% of accessibility issues and miss the 70% that require understanding how the component behaves in context.
The Accessibility in Design Systems Prompt builds accessibility into the component contract — so the default behavior of every component is the accessible behavior, and teams have to actively work to make a component inaccessible rather than accidentally doing so.
What you get: - ARIA implementation standard: the role, state, and property requirements for every component category - Keyboard interaction model: the complete keyboard behavior specification for interactive components - Focus management system: how focus moves within and between components in complex interactions - Color and contrast token standard: the token structure that enforces WCAG AA contrast ratios at the design layer - Automated testing integration: the axe-core and Playwright configuration that catches regressions at CI - Manual testing protocol: the screen reader and keyboard testing procedure that catches what automation misses
Built for: design engineers, accessibility specialists, and design system leads building WCAG AA-compliant component libraries.