Auditing Your Site for Accessibility: Now What?
summary
Audit shows automated tools catch only about a third of problems, so the site requires manual checks like keyboard navigation, screen reader output and 400% browser zoom. A speaker form’s required-field error does not announce because hints and errors lack ARIA linking, so fixes add programmatic associations and alerts. The full audit for a small site takes about 2–3 days, using wave, axe and lighthouse to find issues and pa11y/axe-core in CI to prevent regressions.
AI-written summary · about
chapters (5)
related talks
56mAccessibility Testing 101
40mAccessibility, what, why and how?
27mAccessibility — What Do You Eat That With?
25mPrevent, Catch and Fix Accessibility Issues
22mPrioritising Accessibility to Web Development
56mQuick Start for Evaluating and Testing Web Accessibility
52mAccessibility Testing 101
44mTesting Web Accessibility