W3C issues draft guidance on design system semantics and ARIA mapping

Tech · 3 min read

The draft provides recommendations for naming conventions (semantic vs. presentational), required metadata fields for tokens (purpose, intended role, accessibility priority), and examples showing how a color or spacing token should document its accessibility impact. W3C stresses that tokens should carry intent so automated tools can make better guesses about component behavior.

Included are suggested test harnesses and a minimal token manifest format that design systems can adopt to expose ARIA mappings, keyboard behaviors and suggested input modalities. The draft also addresses versioning and change notifications so downstream implementers aren't surprised by breaking accessibility changes in token updates.

W3C is seeking feedback from design system maintainers, platform vendors and assistive technology developers to iterate on the note. The community hopes the guidance will create a common vocabulary that reduces mismatches between designers' intent and runtime accessibility behavior.