Goal
Provide content that can be understood by users with lower reading ability.
Loading ...
Success Criterion · WCAG 3.1.5
When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
Goal
Provide content that can be understood by users with lower reading ability.
What to do
When text requires advanced reading ability, provide a simpler alternative or supplemental content.
Why it matters
Some users have lower literacy or cognitive disabilities; complex prose can exclude them from understanding.
Success criterion
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.
Intent
Benefits
Why it matters
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may misinterpret instructions or policies if written in complex language.
Users may abandon content that is hard to read or requires advanced literacy.
If content is written above a lower-secondary reading level, provide a simpler summary, alternative version, or supplemental explanation (e.g., plain language summary, glossary, visuals).
Reference: All summaries and highlights originate from Understanding WCAG 3.1.5 and the W3C quick reference.
Examples
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Pass
Policy includes a “Plain language summary” section with bullet points.
Fail
Only dense legal text is provided with no summary.
Pass
Guide includes “In brief” explanations and examples for complex topics.
Fail
Guide uses advanced prose and jargon with no alternative explanations.
Evidence to keep
Capture artifacts for VPATs, procurement reviews, and regression testing.
Official resources
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Testing ideas
Related success criteria