My Site Is Already Online — How Do I Make It Accessible?
summary
A pragmatic process for making an existing website accessible: perform a 20‑page external WCAG audit, record each failed criterion as backlog tickets, and set a concrete 50% remediation target to stop accessibility drift. Use practical tools (Wave browser extension, axe‑core automated tests), short internal trainings and a Slack “snack” bot to spread fixes, then track progress by moving accessibility tickets into sprints and repeating audits roughly every two years.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:34Before we start...
- 1:13The initial situation
- 2:16Reviving accessibility
- 3:48Skill-building
- 5:07But that wasn’t enough...
- 5:49Setting a goal
- 6:06Preparing the audit
- 7:42Audit results
- 7:59Closing the loop with the audit
- 8:58What do we have now?
- 9:53It’s never finished!
- 12:34Takeaway: starter pack
- 13:20Takeaway: long-term pack
related talks
15mMy site is already in production and must be accessible — how do I do it?
24mWeb Accessibility Strategies for Non-Accessible Projects
26mProven ways to make your website accessible in 2023
25mBeyond Compliance: Testing for a more Accessible Web
52mAccessibility Testing 101
38mHow to set up an accessibility program in an imperfect world
50mMaking a Strong Case for Accessibility
01h 03mAccessibility: Making your websites more inclusive