Inclusive Token Conventions: Industry Forum Reaches Consensus on Naming and Semantics

Design · 4 min read

Representatives from several large design systems, independent libraries, and tooling vendors met to resolve common pain points around token naming, semantics, and accessibility metadata. The consensus was simple: tokens should describe purpose and behavior (e.g., color-interactive-primary, motion-reduce) rather than brand hues (e.g., blue-500), and systems should carry accessibility intent alongside values.

Proposed conventions include standardized suffixes and categories for contrast tiers, motion preferences, time-based tokens (durations for animations), and focus styles. Attendees also recommended embedding accessibility metadata directly into token files — such as WCAG contrast level, recommended use cases, and examples of disabled/hover states — so that both designers and automated tooling can make safer decisions.

Tooling already started aligning: several Figma community plugins and tokenizers pledged updates to export the new naming schema, and a Storybook addon prototype now reads token metadata to flag mismatches. Organizers stressed that the conventions are optional but urged teams to adopt them incrementally, starting with new components and high-risk interactive patterns.