Shopify and Atlassian pilot 'persona‑less' design tokens to avoid exclusionary defaults

Design · 5 min read

Shopify and Atlassian pilot 'persona‑less' design tokens to avoid exclusionary defaults

The idea behind 'persona‑less' tokens is to neutralize tokens that implicitly assume a single body, locale, or interaction pattern — for example, default control sizes that suit smaller hands, or wording baked into components using idioms unfamiliar to global audiences. Instead, teams provide an extensible base plus composable modifiers (size, reach, input modality) that are explicitly selected for each product context.

Shopify applied the model to checkout and merchant admin flows where accessibility failures have high business impact, while Atlassian focused on collaboration spaces and notification systems. Both teams reported clearer design reviews, fewer retroactive fixes, and better alignment between product and accessibility teams. They also published migration guides and coder-friendly shims for older themes.

Accessibility experts called the experiment promising because it forces teams to make explicit decisions about inclusivity rather than rely on inherited defaults. The teams plan to open-source patterns and host a joint workshop later this year to help other organizations adopt the persona‑less token approach.