YES, your site too can (and should) be accessible. Lessons learned from building FT.com

on YouTube ↗26m

" summary

FT.com adds automated pa11y checks into CircleCI using pa11y‑ci, raises a high threshold, then tightens it until branches fail on new accessibility errors, cutting detectable issues to zero per app. Manual audit by the Digital Accessibility Center produces a ~200‑page report, fixes take months, and FT.com earns conformance accreditation. About 20% of users factor into the accessibility case, keyboard‑only and VoiceOver testing expose gaps, and a roadshow with screenreader exercises spreads practical knowledge across teams.

AI-written summary · about

" chapters (14)

1. 0:00Intro
2. 0:43Accessibility
3. 2:51What is accessibility
4. 4:15Disability categories
5. 5:22Demographics
6. 6:49Starting small
7. 7:27Palli
8. 11:49Other steps
9. 16:54assistive tech
10. 17:40keyboard only
11. 18:59shortcuts
12. 19:34throw your mouse
13. 21:01spread the word
14. 23:11recap

" related talks

• 43mYes, your site can (and should) be accessible: Lessons learned building FT.comLaura Carvajal · Codemotion Rome 2018
• 31mYES, your site can (and should) be accessible tooLaura Carvajal · JSConf Budapest 2017
• 33mYes! Your site can (and should) be accessibleLaura Carvajal · NodeConf EU 2017
• 40mAccessibility, what, why and how?Marjorie Figueroa · angularday 2020
• 14mAccessible AccessibilityRon Au · OZeWAI 2020
• 43mLucky Nkosi: A11y Beyond the Theory: Integrating Accessibility Testing into Your WorkflowLucky Nkosi · TestCon Europe 2024
• 53mAccessing Accessible AccessibilityJennifer Wong · NDC Sydney 2017
• 26mHow (Not) to Fail at AccessibilityTrish Ang · JSConf Hawai 2019