8 Free Personas Spot Accessibility Issues in Design
8 free accessibility personas shift designer burden from memorizing WCAG to recognizing exclusion during work. Applying Nielsen's heuristic #6 to creators means fewer bad websites from good designers. Add them to your design critiques this sprint.
WHY IT MATTERS: Accessibility failures rarely stem from bad intentions. The article argues that designers want to include everyone but are drowning in guidance spanning visual design, interaction patterns, content strategy, and WCAG compliance. When cognitive load exceeds capacity, exclusion happens not by malice but by omission. The stakes are high. A poorly designed bus timetable can cause someone to miss a dying grandmother's final moments or a child's birthday. Every interface you ship is a life event for someone.
WHAT CHANGED: The proposal reframes Jakob Nielsen's sixth usability heuristic, recognition rather than recall, for the people building interfaces instead of the people using them. Rather than expecting designers to memorize vast accessibility rules, the author suggests embedding recognition cues directly into the design process. The concrete tool is a set of eight free personas from the companion site to What Every Engineer Should Know About Digital Accessibility by Sarah Horton and David Sloan. These personas include Vishnu, an engineer with low vision who needs adjustable screens and simple sentences; Trevor, a high school student with autism who needs consistent patterns; Steven, a deaf graphic artist who needs captions; Maria, a bilingual health worker who leaves confusing sites; Lea, an editor with fatigue who cannot handle dense drop-down lists; Jacob, a blind paralegal who relies on technology; Emily, who has cerebral palsy and needs simpler screens; and Carol, a grandmother with macular degeneration who struggles with screen text. Using these personas during critiques makes accessibility tangible instead of abstract.
WHAT TO WATCH: Whether design tools integrate these personas natively or through plugins. The article essentially asks for accessibility guardrails that surface the right persona at the right time, similar to how spell check surfaces errors without requiring writers to memorize dictionaries. If your team does not have accessibility specialists, assign one persona per design review round robin style. The goal is to make recognizing exclusion as routine as checking contrast ratios.
Read the original → alistapart.com
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.