WCAG 2.2 SC 3.1.5 Reading Level (AAA) Accessibility & Plain-Summary Playbook

W3C WCAG 2.1 and 2.2 Success Criterion 3.1.5 (Reading Level — Level AAA) requires that when text demands reading ability more advanced than the lower secondary education level (UNESCO ISCED Level 2, corresponding to US Grade 7–9 / roughly 9 years of total schooling) after removing proper names and titles, either the primary text is simplified OR supplemental content—such as a Grade 6–8 Plain-Language Summary—is provided.
Key Compliance & Engineering Takeaways
- Lower Secondary Education (UNESCO ISCED Level 2) maps to roughly US 7th–9th Grade (CheckReadability enforces ≤ Grade 9.0 as the primary gate).
- WCAG 3.1.5 explicitly does NOT force you to strip technical precision from API docs, legal terms, or research papers—adding a concise Grade ≤ 8 'Plain-Language Summary' callout box completely satisfies Technique G86!
- Per W3C guidance, strip proper nouns, company/product titles, and code blocks before measuring reading grade so capitalized names don't artificially inflate syllable counts.
- Cognitive accessibility benefits users with dyslexia, ADHD, aphasia, traumatic brain injury, screen-fatigue, and non-native English proficiency alike.
- Use our WCAG 3.1.5 Auditor's 1-click 'Prepend WCAG Plain Summary' tool (via Rule Engine or Local AI) to generate compliant lower-secondary summaries offline.
W3C WCAG 3.1.5 Techniques & Cognitive Accessibility Gates
| W3C Technique / Standard | Compliance Requirement | Measured Readability Gate | Implementation Pattern |
|---|---|---|---|
| Technique G153 (Primary Text) | Consensus Grade ≤ 9.0 | Lower Secondary (ISCED 2) | Write main body copy directly at Grade 7–9 with active verbs |
| Technique G86 (Text Summary) | Summary at Grade 6.0–8.0 | Supplemental Plain Box | Add a <section aria-label='Plain-language summary'> above dense text |
| Technique G103 (Visual Aid) | Diagram / Flowchart + Alt | Visual Supplement | Pair complex multi-step workflows with clear visual diagrams |
| Technique G79 (Spoken Version) | TTS / Audio Read-Aloud | Auditory Supplement | Helps dyslexic & low-vision users process complex terminology |
| W3C COGA Usable Content | 0 Sentences ≥ 30 Words | Dale-Chall ≤ 7.5 | Avoid double negatives, metaphors, idioms & walls of text |
Real-World Before vs. After Plain-Language Rewrites
Measured directly using CheckReadability's 12-formula consensus & POS engine.
Case Study: Satisfying WCAG Technique G86 on a Dense Banking Security Policy
“Cryptographic passkey authentication credentials generated via WebAuthn asymmetric public-key infrastructure remain hardware-bound within your device's Trusted Platform Module, precluding phishing-induced credential exfiltration across cross-origin federated sessions.”
“Plain-Language Summary: Passkeys let you sign in safely with your fingerprint or face instead of a password. Your secret key stays locked inside your phone or laptop, so fake phishing websites cannot steal it.”
Why this passes: Keeps the exact WebAuthn technical specification below for security engineers while prepending a Grade 6.9 summary so every customer understands why passkeys protect their account.
Step-by-Step Zero-Upload Compliance Audit Workflow
- 1
Strip Code Blocks, Markdown & Proper Titles First
WCAG 3.1.5 specifies measuring reading level 'after removal of proper names and titles.' Use /clean-text-extractor to strip HTML/Markdown tags and code blocks before scoring technical documentation.
- 2
Run the 3-Gate WCAG 2.2 SC 3.1.5 Accessibility Check
Paste your prose into /wcag-reading-level-checker to test Consensus Grade ≤ 9.0, Run-On Sentences = 0, and New Dale-Chall Familiar Vocabulary ≤ 7.5.
- 3
Generate & Prepend a Supplemental Plain-Language Summary (Technique G86)
If domain-critical terminology pushes your article above Grade 9.0, click 'WCAG 3.1.5 Summary' right above the editor to generate a Grade 7–8 summary locally and place it in a semantic callout at the top of your page.
- 4
Batch-Audit Help Center & Public Portal Pages via CSV
Export your CMS or documentation pages to CSV and drop them into /bulk-readability-checker to flag every help article exceeding Grade 9 before your VPAT / ACR accessibility audit.
Why Cognitive Accessibility Is Essential Web Engineering
Most automated accessibility linters (like Lighthouse or axe-core) catch missing `alt` attributes, color contrast ratios, and ARIA roles—yet completely miss whether a human with a reading or cognitive disability can actually comprehend the page.
Roughly 15–20% of the global population experiences some form of language-based learning difference, dyslexia, ADHD, post-concussion cognitive fatigue, or age-related working-memory decline. In addition, millions of deaf users whose primary language is American Sign Language (ASL) or British Sign Language (BSL)—which have distinct spatial grammar rather than English syntax—process written English as a second language.
Under WCAG 2.2 Guideline 3.1 ('Make text content readable and understandable'), Success Criterion 3.1.5 establishes an objective, testable benchmark grounded in UNESCO's International Standard Classification of Education (ISCED Level 2: completion of roughly 9 years of primary and lower-secondary schooling).
How the 'Supplemental Plain Summary' Rule Works (W3C Technique G86)
A common misconception among legal, medical, and engineering teams is that WCAG 3.1.5 requires rewriting PhD research papers, securities disclosures, or API specifications in 7th-grade vocabulary.
In fact, the W3C standard explicitly anticipates specialized prose. When primary content requires advanced reading skill, providing a concise, accurate Plain-Language Summary written at the lower-secondary level (Grade 6–8) right at the top of the page (or inside an accessible `<details>` / `<aside aria-label='Plain-language summary'>` region) fully satisfies Success Criterion 3.1.5!
This dual-layer pattern—popularized as 'Layered Disclosure'—helps every user: novices and cognitively fatigued readers get the clear TL;DR immediately, while domain specialists still get the unabridged specification underneath.
- Keep supplemental summaries between 50 and 120 words (2–4 short paragraphs or bullets).
- State what the page means for the user's actions ('What you need to do', 'Who qualifies', 'Deadlines').
- Avoid idioms ('ballpark figure', 'grandfathered in'), double negatives, and nested parentheticals.
Why Proper Names & Titles Must Be Excluded from Accessibility Audits
Readability formulas estimate word difficulty mechanically using character length, syllable count, or unfamiliar word lists.
If a public-transit alert repeats 'Massachusetts Department of Transportation' (13 syllables across 4 words) six times, Flesch-Kincaid and SMOG will artificially jump by 3 grade levels even if every sentence is crystal clear ('Buses replace Red Line trains this weekend'). W3C Understanding SC 3.1.5 explicitly instructs auditors to remove proper names, street names, and formal document titles when testing prose against the lower-secondary threshold.
Preparing for the European Accessibility Act (EAA) & VPAT Audits
While SC 3.1.5 sits at Level AAA in WCAG 2.2, plain-language accessibility is rapidly moving from voluntary best practice into enforceable consumer regulation.
The EU European Accessibility Act (Directive 2019/882) explicitly requires consumer banking, e-commerce, telecommunications, and transport providers to supply service terms and user instructions in 'understandable' language not exceeding upper-intermediate complexity (CEFR B2, roughly US Grade 8–10). Auditing both WCAG Grade ≤ 9.0 and CEFR bands locally in CheckReadability lets global product teams document compliance across US VPATs and EU EAA filings simultaneously.
Run These Offline Readability & Compliance Tools Now
100% browser-local execution with built-in sample documents — 0 bytes uploaded
HTML, Markdown & Zero-Width LLM Character Sanitizer
Strips HTML tags, Markdown syntax, [1] citations, smart quotes & invisible zero-width chars.
New Dale-Chall Readability Calculator (3,000 Familiar Words)
Compares every word against the 3,000 words known by 80% of 4th-grade students.
Live Readability Studio
Live 12-formula consensus + inline highlights for hard sentences, passive voice & jargon.
Frequently Asked Questions
What US school grade corresponds to WCAG 3.1.5 'Lower Secondary Education'?
UNESCO ISCED Level 2 (Lower Secondary Education) corresponds to roughly 7 to 9 years of formal schooling—US 7th, 8th, or 9th Grade. Aiming for Consensus Grade ≤ 8.5 gives you a comfortable pass margin.
Does WCAG 3.1.5 ban technical, scientific, or legal terms?
No. Essential domain terminology can remain in your main body text; if that pushes the primary text above Grade 9, adding a Grade 6–8 Plain-Language Summary at the top of the page satisfies W3C Technique G86.
Do automated accessibility scanners like Lighthouse test WCAG 3.1.5?
No—DOM linters like Lighthouse and axe-core only test markup attributes and contrast, not prose reading level. You must run a dedicated readability audit on extracted page text.
Which readability formulas work best for WCAG cognitive accessibility?
Pair Consensus Grade (sentence length + syllable load) with New Dale-Chall (/formulas/new-dale-chall-readability-formula), which tests every word against 3,000 familiar everyday words.
How does WCAG 3.1.5 relate to the EU European Accessibility Act (EAA)?
Annex I of the European Accessibility Act mandates that consumer product and banking information be understandable and not exceed CEFR Level B2—which closely aligns with US Grade 8–10.
More Compliance Playbooks & Readability Benchmarks

NIH, AMA & HIPAA Patient Informed Consent Readability Playbook (SMOG & Grade 6–8)
Complete clinical playbook for IRB reviewers, medical writers, and hospital teams: meet NIH Grade 6–7, AMA Grade 6, FDA 45 CFR 46.116, and SMOG readability gates locally with zero PHI uploads.

US Plain Writing Act of 2010 & Federal PlainLanguage.gov Compliance Playbook
Complete compliance playbook for federal, state, and municipal agencies under the US Plain Writing Act of 2010 (Public Law 111-274), OMB M-11-15, and PlainLanguage.gov.

Consumer Contract & Insurance Flesch Reading Ease Statutes (45–60 Legal Floors)
Statutory guide to US state insurance and consumer contract plain-language laws (NAIC Model Act, NY § 5-702, CT § 42-152, MA c. 175 § 2B, FL § 627.4145) requiring Flesch Reading Ease ≥ 45–50.

GOV.UK Service Manual, NHS Digital & Crystal Mark Plain-English Playbook
Apply UK Government Digital Service (GDS) GOV.UK Service Manual, NHS Digital Content Style Guide, and Plain English Campaign Crystal Mark rules—reading age 9, ≤25-word sentences, and front-loaded headings.

ISO 24495-1:2023 International Plain Language Standard Implementation Playbook
Operationalize ISO 24495-1:2023 (Plain language — Part 1: Governing principles and guidelines) and Part 2 (Legal communication) with measurable readability, structure, and multilingual LIX gates.

GDPR Article 12 & CCPA Privacy Policy Readability Audit Playbook
How DPOs, privacy counsel, and product teams audit Privacy Policies and Cookie Notices to satisfy EU GDPR Article 12(1) ('clear and plain language') and CCPA/CPRA readability rules.