UI Collective on YouTube · Open on YouTube
Systems and research depth · Proficient · Lesson 74 of 99 · 26 min video, then about 3 hours of practice
Auditing accessibility across a product and a system
After this you can run an accessibility audit of a design system or product area, prioritise findings, and build accessibility into components so teams get it by default.
Why it matters
One accessible screen is a junior skill; making a whole product accessible is a systems problem. The leverage is in components (if the button, form field and dialog are right, every team inherits it) and in a repeatable audit: automated checks, keyboard and screen-reader passes, contrast and target-size reviews, and annotation of focus order and semantics in design files. Focus on prioritising by user impact and frequency. Trap: treating accessibility as a launch checklist. Retrofitting is many times more expensive than designing it into the system.
How to use this resource
Accessible design in Figma past the contrast basics (focus order, annotations, semantics and states) on the current tool. The design-side half of an audit.