OS-Level Accessibility Tokens: Industry Working Group Proposes Shared Spec

Tech · 4 min read

The draft specification defines a small set of accessibility tokens — reduced-motion, high-contrast-scale, focus-visibility, and text-scale-preference — that platforms and design systems can consume consistently. By mapping system preferences to token values, component libraries can react without bespoke bridging code for each platform.\n\nIf adopted, the proposal would reduce edge-case behaviors where a web app honors reduced-motion but not text scaling, or a native app adapts contrast while embedded webviews do not. The spec also includes recommendations for token fallbacks and semantic token aliases (for example 'control-border-contrast' rather than a raw color) so designers can reason about intent rather than pigments.\n\nPlatform vendors and design tool vendors are being asked to implement a runtime API and an editor-time mapping that syncs a user's OS-level preferences into the design system tokens. Accessibility advocates welcomed the move but cautioned that a tokens-first approach must be paired with clear testing guidance to avoid token misuse (for example, treating 'reduced-motion' as a binary switch when users expect degrees of motion reduction).