WCAG 3.2 draft adds component-level semantics for design systems, easing compliance

Tech · 6 min read

WCAG's 3.2 draft introduces component-focused guidance recognizing that many accessibility issues stem from how shared components are implemented and composed. The draft defines semantic profiles for common design-system components like accordions, modal dialogs, comboboxes, and virtualized lists — specifying required roles, properties, and expected keyboard behaviors for each profile.

The update responds to years of implementer feedback arguing that page-level checks don't capture the nuanced accessibility obligations of reusable UI building blocks. Under the proposal, conformance can be demonstrated by validating a design system's component library against these component profiles, which then reduces repetitive page-level remediation across products that reuse the library.

Industry reaction is mixed: design-system maintainers welcome clearer rules and testable criteria, while some accessibility auditors warn that component conformance shouldn't replace whole-page evaluation. The W3C plans further public testing and interoperability trials with major component frameworks before finalizing the specification.