A11Y Wars: The Accessibility Interpretation Problem
summary
Claim: WCAG leaves room for multiple valid interpretations, with success criteria are the only normative, testable parts and confusion between normative vs informative text causing more than 50% of disagreements. Offer: the Accessibility Peace Model sorts interpretations into minimal / optimized / idealized, maps them to roles and goals, and recommends documenting, communicating and harmonizing test procedures. Practical steps: use the white paper (bit.ly/a11ypiece), ask tool developers how they interpret WCAG, and publish which level a given test targets — document and communicate interpretations.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 4:05Defining the problem
- 7:41The interpretation gap
- 14:47Normative vs. informative
- 19:41Roles and goals
- 27:06The accessibility piece model
- 37:55Applying the model
- 40:53Q&A and conclusion
related talks
45mAccessibility: Why You Should Learn About WCAG
50mAccessibility in the Enterprise: The Relationship of A11y and ROI
01h 03mAccessibility: Making your websites more inclusive
56mAccessibility Testing or: How I Learned to Stop Worrying and Ignore WCAG
22mAccessibility in Practice
37mAccessibility Matters: Creating a Better Web
38mHow to set up an accessibility program in an imperfect world
15mRapid Introduction to Web Accessibility