Yes! Your site can (and should) be accessible
summary
The Financial Times ships a rebuilt site in 2016 then discovers accessibility was never measured so accessibility becomes a measurable goal, calculating 26% of users could be affected, running automated checks in CI and surfacing hundreds of issues per branch, using a temporary threshold to avoid breaking all builds while cleaning the backlog, commissioning external audits and real user testing, fixing contrast, alt text and form labels, earning accessibility accreditation and preventing new automated errors via CI integration so regressions no longer reach production.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:05Our story
- 2:32What is accessibility
- 5:15Demographics
- 6:33Poly Police
- 12:23Contrast
- 13:22Missing alt text
- 14:20Missing required fields
- 15:47Duplicate content
- 16:36Online courses
- 17:43External audit
- 20:55Why you should do this
- 21:29We got an accreditation
- 22:34Customer research
- 22:52Dont get it wrong
- 23:02Learn to use assistive technology
- 23:23Keyboard only
- 24:03Trackpad only
- 24:18Throw away your mouse
- 25:23Have your say
- 26:19roadshows
- 28:03conclusion
- 28:19cost money
- 29:32how this all started
- 30:54what you can do
- 32:11the web is behind in space
related talks
43mYes, your site can (and should) be accessible: Lessons learned building FT.com
26mYES, your site too can (and should) be accessible. Lessons learned from building FT.com
31mYES, your site can (and should) be accessible too
53mAccessing Accessible Accessibility
14mAccessible Accessibility
54mAccessibility by everyone (and for everyone)
49mMeasuring and Benchmarking Accessibility
50mAccessibility by Everyone (and for Everyone)