From personas to people: making research-driven inclusivity part of design systems

Design · 5 min read

Teams are discovering that static personas in a design kit don't capture accessibility nuances, so they're attaching research artifacts directly to components. A button story might link to a short vignette showing a user with low vision accessing that pattern on a noisy train, while a date-picker points to transcripts from users with motor impairments who prefer voice input.

This practice makes inclusivity discoverable: engineers can see the real-world scenarios that motivated a particular affordance or keyboard shortcut, and designers can prioritize features that reduce known failure points. The artifacts often include test scripts and sample data sets used to validate changes — for example, locale-specific date strings that reveal parsing errors.

Embedding research into the system also helps governance. When product teams request exceptions for an accessible pattern because it 'looks heavy,' it's easier to defend the choice with linked data. Over time, the design system becomes both a UI library and a living repository of user needs, reducing the chance that accessibility becomes decoupled from product decisions.