Accessibility in the GOV.UK Design System
summary
GOV.UK design system centralizes styles, components and patterns across 300,000 pages and 780 services so teams share a consistent UI while services still run on many stacks. Accessibility work includes automated checks with axe (automation catches ~30% of issues; their deliberately horrible test page revealed 3%), manual testing with JAWS, NVDA, VoiceOver, ZoomText and Dragon, external audits, user research with people with disabilities, and shipping experimental components to validate real-world usage.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:11Accessibility in the GOV.UK Design System
- 1:56780 services
- 3:06Users should not have to understand how Government works
- 4:2320% of people in the UK have a disability
- 7:34How do we meet these needs?
- 7:44Meet Web Content Accessibility Guidelines 2. Test with assistive technologies 3. User research with real users
- 8:041. Meet the Web Content Accessibility Guidelines
- 9:16aXe - Accessibility engine for automated Web Ul testing
- 12:30External accessibility audit
- 14:58Accessibility Empathy Lab
- 16:49Researching in a real world context can be difficult
- 17:27The best research comes from real world usage
- 18:11Design Systems can't make services accessible on their own
- 18:45This is not a unique problem to accessibility
- 18:58Design Systems are a starting point
related talks
39mAccessibility for Design Systems
26mAuditing design systems for accessibility
52mDesigning inclusive and accessible experiences
01h 05mAccessibility Testing 101
49mScaling Accessibility An Accessibility Design Manager’s Tale
59mImproving Accessibility Through Design Systems
47mFrom Parts to Whole – Beyond Design System
32mBuilding Empathy and Accessible Apps