Design Tokens 2.0 Proposal Adds ARIA Mapping to Close the Assistive Tech Gap

Design · 4 min read

The proposal suggests token metadata keys like aria-role, aria-live, and semantic-purpose that travel with tokens into component libraries. For example, a token governing a “status-pill” could include recommended aria-live settings and a semantic-purpose tag so implementers know whether the component should announce changes.

Advocates argue this reduces ambiguity between designers and engineers: instead of ad-hoc ARIA decisions during implementation, semantic intent is specified upfront and versioned alongside visual tokens. Tooling vendors are already experimenting with token transforms that produce both CSS/Swift code and accessibility manifests consumed by platform accessibility APIs.

Critics caution against overloading design tokens with behavioral responsibilities and recommend the proposal remain optional and vetted by accessibility experts. The working group plans a pilot with three major design systems to test real-world workflows before seeking broader adoption.