YES, your site can (and should) be accessible too
summary
A major site launch initially ignores accessibility then discovers 26% of users may be excluded and a quick run of pa11y reveals hundreds of failures. Integration via poly CI into CircleCI/Heroku with a growing threshold lets teams get reports without breaking everything, then remove the threshold to block regressions. Automated checks cover ~20–30% of issues, manual audits and user testing with the Digital Accessibility Centre produce a 200‑page remediation list, months of fixes, and an eventual accreditation.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:46Accessibility doesn't just happen You make it happen
- 2:34Web accessibility means that people with disabilities can use the Web
- 11:07Before setting the build on fire train people
- 18:361. External Audit 2. Customer Research 3. DIY
- 23:20Don't take it all on yourself
- 25:42Talk about it A lot
- 25:571. External Audit & 2. Customer Research & 3. DIY
- 26:40"It's the right thing to do" doesn't get you a budget
- 28:16Diversity improves your product your team your life
related talks
26mYES, your site too can (and should) be accessible. Lessons learned from building FT.com
43mYes, your site can (and should) be accessible: Lessons learned building FT.com
33mYes! Your site can (and should) be accessible
43mLucky Nkosi: A11y Beyond the Theory: Integrating Accessibility Testing into Your Workflow
15mMy Site Is Already Online — How Do I Make It Accessible?
56mAccessibility Testing 101
26mProven ways to make your website accessible in 2023
14mAccessible Accessibility