Readability and Accessibility: WCAG Compliance, Screen Readers, and Readability Formulas

Readability formulas measure surface-level text characteristics—sentence length, syllable count, word frequency—but readability and accessibility WCAG compliance demands much more: structured navigation, cognitive load management, screen-reader compatibility, and non-text alternatives. Passing both requires understanding where formulas succeed and where they fail.

Introduction

Many writers and compliance teams treat readability scores and WCAG accessibility as interchangeable targets. They are not. A document can score well on the Flesch-Kincaid Grade Level scale and still fail WCAG 2.1 AA because it lacks proper heading hierarchy, has poor color contrast, includes inaccessible charts, or uses complex sentence structures that confuse screen-reader users even if the syllable count is low.

Conversely, a document can meet WCAG structural requirements and still be difficult to parse for readers with cognitive disabilities, dyslexia, or low vision if the underlying prose is convoluted.

This guide bridges that gap. It explains what WCAG actually mandates about readability, how screen readers interact with text formatting and punctuation, and which readability formulas—like Flesch-Kincaid and the Gunning Fog Index—correlate with real accessibility outcomes. You'll learn concrete compliance targets for each WCAG level, see why cognitive accessibility extends beyond grade-level scores, and walk through a healthcare example that passes both formula benchmarks and accessibility audits.

Whether you're writing patient information, compliance documentation, or public-facing content, understanding the relationship between readability metrics and WCAG requirements ensures your content works for humans and machines.

The Gap Between Readability Formulas and True Accessibility

Readability formulas were designed in the 1940s and 1950s to predict how easily humans can understand prose. The Flesch-Kincaid Grade Level, created by Rudolf Flesch and J. Peter Kincaid for the U.S. Navy, estimates the U.S. grade level required to understand a text on first reading. Gunning Fog Index, created by Robert Gunning in 1952, focuses on complex words. These metrics work by counting syllables, sentence length, and word frequency—mechanical operations that take seconds to compute.

WCAG (Web Content Accessibility Guidelines), published by the W3C and updated most recently in 2023–2024 with WCAG 3.0 drafts in progress, addresses a broader mandate: ensuring content is perceivable, operable, understandable, and robust for all users, including those with disabilities. WCAG does reference readability, but it does so alongside requirements for color contrast, keyboard navigation, alt text, form labeling, and heading structure.

The critical difference: a readability formula cannot detect that a long sentence lacks proper punctuation breaks for screen readers, that a numbered list lacks semantic markup, that a table has no header row, or that colored text conveys meaning without a text alternative.

Additionally, why grade level isn't reading level explores why a 6th-grade Flesch-Kincaid score does not guarantee a 6th-grader can understand the content. Domain vocabulary, prior knowledge, conceptual density, and layout all matter. WCAG addresses many of these factors; readability formulas largely ignore them.

WCAG 2.1 and 3.0 Readability Requirements: What the Standards Actually Say

WCAG 2.1—the current stable standard as of 2026—does not mandate a specific readability score. Instead, it offers guidance at three conformance levels: A (minimum), AA (recommended), and AAA (enhanced).

WCAG 2.1 Level A includes no explicit readability criterion. Compliance focuses on alt text, keyboard access, and color contrast.

WCAG 2.1 Level AA includes Guideline 3.1.5: "Reading Level." The criterion states: "When text requires reading ability more advanced than the lower secondary education level after removal of proper nouns and titles, supplemental content or a version that does not require reading ability more advanced than the lower secondary education level, is available."

Translation: if your prose requires an 8th-grade reading level or higher (U.S. standard for "lower secondary"), you must provide a simplified version, glossary, or supplemental explanation. This is not about banning complex writing—it is about ensuring users with cognitive disabilities or language barriers can access equivalent information.

WCAG 2.1 Level AAA includes Guideline 3.1.6: "Pronunciation." When word pronunciation affects meaning (homographs, acronyms), markup or inline explanation is required. This is separate from readability but highlights WCAG's focus on semantic clarity.

WCAG 3.0 (emerging, draft status through 2026) introduces more nuanced cognitive accessibility language. Early drafts emphasize "cognitive load," "task load," and "memory load"—concepts that go far beyond syllable counting. WCAG 3.0 is expected to move toward outcome-based conformance rather than prescriptive checkboxes, though the final version remains in development.

For practical 2026 compliance, treat WCAG 2.1 AA as the industry standard: target a lower-secondary (6th–8th grade) readability level, provide plain-language summaries for specialized content, and ensure proper semantic structure.

How Screen Readers Interact With Sentence Length and Punctuation

Screen readers parse text character-by-character and phrase-by-phrase, converting it to synthesized speech. Long sentences without punctuation breaks create distinct accessibility problems:

Run-on sentences and ambiguous boundaries. A screen-reader user hears: "The patient should take the medication with food which can reduce nausea and also improves absorption so do not take on an empty stomach." Where does one clause end? Where does advice change? A human reader's eye can scan and parse; a screen-reader user cannot pause and re-read mid-sentence easily.

Semantic punctuation. Periods, commas, colons, and hyphens are not merely visual—they signal grammatical boundaries. Screen readers pause briefly at periods, slightly longer at semicolons. Removing or misusing punctuation degrades comprehension for both sighted and screen-reader users.

Conjunction overload. Sentences strung together with "and," "but," "however," and "therefore" without structural markers (headings, lists, line breaks) force screen-reader users to hold multiple concepts in working memory. A sentence like "Patients with hypertension and diabetes and a family history of stroke should monitor blood pressure weekly and report readings above 140/90 and seek immediate care if experiencing chest pain or dizziness" is hard to parse by ear.

Optimal structure for screen readers: Keep sentences under 20 words on average. Use lists instead of prose for multiple conditions or steps. Use active voice. Break complex thoughts into separate sentences. Ensure each sentence stands alone or connects clearly to the prior one.

Readability formulas explained can detect long sentences, but they cannot evaluate whether punctuation and conjunctions are placed optimally for audio consumption.

Grade Level Targeting for WCAG Level AA Compliance

WCAG 2.1 AA requires lower-secondary (6th–8th grade) readability. In U.S. terms, this typically means:

• Flesch-Kincaid Grade Level: 6–8
• Gunning Fog Index: 8–10
• Flesch Reading Ease: 60–70 (higher is easier)
• SMOG Index: 6–8

These are target ranges, not hard cutoffs. A score of 7.2 on Flesch-Kincaid is compliant; 8.5 is borderline; 10+ is non-compliant without supplemental plain-language content.

In practice:

• Healthcare content (patient information, discharge instructions): aim for Flesch-Kincaid 5–7. Patients under stress retain less; lower is better.
• Government forms and public notices: WCAG 2.1 AA compliance requires Flesch-Kincaid 6–8; plain language compliance standards often push for 5–6.
• Legal and compliance documents: Flesch-Kincaid 8 is acceptable at AA level, but larger font, chunking, and glossaries become more important.

For WCAG Level AAA (enhanced) — if you pursue it — aim for Flesch-Kincaid 5–6 across the board. This is not mandated by WCAG 3.0 (still in draft), but accessibility best practices recommend it for users with cognitive disabilities or dyslexia.

Why multiple formulas? Because they measure different aspects. Flesch-Kincaid emphasizes syllables and sentence length. Gunning Fog counts complex words (3+ syllables) but ignores syllables in common words. SMOG, designed for health communication, tends to run 0.5–1.0 grade levels higher than Flesch-Kincaid. Use all three; if they agree, your text is predictably readable. If they diverge, investigate: complex words? Long sentences? Unfamiliar domain terms?

Cognitive Accessibility: Beyond Grade-Level Scores

Grade-level readability scores cannot measure cognitive load—the mental effort required to parse, hold, and act on information. Two pieces of content can both score Flesch-Kincaid 7.0 and present vastly different cognitive burdens.

Consider:

Version A (Flesch-Kincaid 7.1): "Patients with a history of myocardial infarction, hypertension, hypercholesterolemia, or diabetes mellitus should be screened for atrial fibrillation using 24-hour Holter monitoring or event monitoring based on symptom frequency."

Version B (Flesch-Kincaid 7.0): "Your doctor will check your heart rhythm if you have had a heart attack, high blood pressure, high cholesterol, or diabetes. We use a 24-hour heart monitor or a portable device you carry. Your doctor picks the right test based on how often you feel symptoms."

Both score near 7.0 on Flesch-Kincaid, but Version B is cognitively easier: it uses familiar words ("doctor," "heart attack" rather than "myocardial infarction"), shorter sentences, and logical chunking. Version B also uses the second person ("your"), which engages users better than passive voice.

Cognitive accessibility strategies that readability formulas miss:

• Consistent terminology. Use "blood pressure" throughout; do not alternate with "BP" or "hypertension measurement." Synonyms force working memory to map equivalences.
• One idea per sentence. Even if a sentence scores low on Flesch-Kincaid, multiple clauses buried in it overload cognitive load.
• Visual hierarchy and whitespace. Lists, subheadings, and margins are not readability metrics, but they cut cognitive load by 15–30% (cited in cognitive-load theory research). WCAG addresses structure; readability formulas do not.
• Concrete language. "Take your medicine every morning after breakfast" is easier to execute than "Administer medication following a morning meal." Both may score similarly on grade level, but one is actionable.

For patient information readability, cognitive accessibility means testing with actual users, not just scoring. A document that passes Flesch-Kincaid 5.0 and WCAG AA but confuses users with dense medical terminology is not truly accessible.

Real Example: Healthcare Form Optimized for WCAG and Readability Scores

Original version (non-compliant):

"All patients presenting with complaints related to cardiovascular dysfunction, including but not limited to chest discomfort, dyspnea, arrhythmias, or syncope, must complete a comprehensive health history questionnaire prior to examination and provide documentation of prior diagnostic studies, pharmaceutical interventions, and familial disease states."

Metrics: Flesch-Kincaid 14.2 (way above AA), Flesch Reading Ease 28 (very difficult), SMOG 13.5.

Revised version (WCAG AA + readability compliant):

"Please tell us about your heart health. Have you had any of these?

• Chest pain or pressure
• Shortness of breath
• Heart racing or skipping
• Fainting or dizziness

Bring any test results or medication lists from previous visits."

Metrics: Flesch-Kincaid 5.8 (AA compliant), Flesch Reading Ease 72 (easy to read), SMOG 5.2.

What changed:

1. Replaced medical jargon ("cardiovascular dysfunction," "dyspnea," "syncope") with plain language ("heart racing," "shortness of breath," "fainting").
2. Broke a 41-word sentence into a heading, a list, and a 15-word instruction.
3. Used second person ("Have you had") instead of passive ("patients presenting").
4. Removed "prior diagnostic studies" and "pharmaceutical interventions"—replaced with "test results" and "medication lists."

The revised version also benefits from WCAG structure: headings are proper <h3> tags, the list is semantic (bulleted), and the instruction is clear and scannable. A screen-reader user hears a logical, pausable sequence. A user with dyslexia can read short sentences without losing place. A low-vision user benefits from increased whitespace and larger font (which is enabled by shorter lines).

This revision passes WCAG 2.1 AA on readability and structure. It also scores well on accessibility testing tools, which check for alt text (if images are present), form labeling, color contrast, and keyboard navigation.

Heading Structure, Chunking, and Why Formula Metrics Miss Half the Picture

Readability formulas analyze running text. They ignore headers, lists, subheadings, and white space—all critical to accessibility and actual readability.

A document with:

• Poor heading hierarchy (missing <h2>, jumping from <h1> to <h4>)
• Long paragraphs (400+ words)
• No bulleted or numbered lists
• No visual breaks

…will score well on Flesch-Kincaid if individual sentences are short, but it will fail accessibility audits and frustrate users because the structure is inaccessible.

WCAG requires:

• Proper heading hierarchy (no skipped levels).
• Semantic markup (<h1>, <h2>, not styled <p> tags).
• Lists marked as <ul> or <ol>, not prose with commas.
• Form fields with labels (<label> tags, not placeholder text).
• Tables with header rows (<th> tags).

A screen reader depends on this structure to orient users and allow navigation. "Jump to next heading" is a standard screen-reader command; if headings are not marked, the command fails.

Best practice: Use WCAG's heading and list guidelines to break text into digestible chunks. Then measure readability of each chunk. A section with a subheading, a 2-3 sentence intro, a bulleted list, and a concluding sentence is far more accessible than the same information in a 6-sentence paragraph—even if both score Flesch-Kincaid 6.0.

Testing Tools: Which Readability Formulas Correlate With Accessibility Compliance

Not all readability tools are built equally. Some integrate accessibility checks; most do not.

Readability-only tools (detect formula scores but not WCAG compliance):

• Hemingway Editor: Highlights long sentences, passive voice, and complex words. Good for drafting. Does not check heading structure or semantic markup.
• Flesch-Kincaid (Microsoft Word, Google Docs plugins): Fast, familiar. Limited to grade-level estimates. No color contrast or alt-text checking.
• Grammarly: Offers readability and tone suggestions. Accessibility features are limited and often require premium tiers.

Accessibility + readability integrated tools:

• WAVE (WebAIM): Checks WCAG contrast, alt text, heading hierarchy, and form labels. Includes Flesch-Kincaid integration. Best for web content.
• Axe DevTools (Deque): Comprehensive WCAG 2.1 AA and AAA auditing. Integrates readability checks. Requires browser extension or API access.
• AccessiBe and similar platforms: Automated scanning plus remediation suggestions. Integrates readability formulas with WCAG checks. Cost-dependent.

Most relevant for balanced compliance: Use a combination approach. Run your text through Hemingway Editor or Microsoft Word for grade-level scores and sentence-length detection. Then run the final HTML/web content through WAVE or Axe DevTools to ensure heading structure, contrast, alt text, and form labeling are WCAG-compliant.

For plain-language writers focused on government and public communication, the plain language compliance standards page outlines both readability benchmarks and regulatory accessibility requirements.

Frequently Asked Questions

Do readability scores guarantee WCAG compliance?

No. A document can score Flesch-Kincaid 6.0 and still fail WCAG 2.1 AA if it lacks proper heading hierarchy, has color-only instructions, includes inaccessible tables, or uses images without alt text. Readability formulas measure only sentence structure and word choice. WCAG addresses structure, non-text content, color contrast, keyboard navigation, and more.

What reading level is WCAG Level AA?

WCAG 2.1 Level AA requires lower-secondary education reading level (6th–8th grade in the U.S.). This typically translates to Flesch-Kincaid Grade 6–8. If your content scores higher, you must provide a plain-language summary, glossary, or simplified version. WCAG 2.1 Level A has no readability requirement; Level AAA expects 5th–6th grade.

Can dyslexia-friendly writing also meet readability formulas?

Yes. Dyslexia-friendly techniques—short sentences, sans-serif fonts, increased line spacing, consistent terminology—typically improve readability scores as well. However, readability formulas do not detect font choice or spacing. Use formulas to validate sentence and word complexity; use WCAG guidelines and dyslexia-accessibility research to guide layout and typography.

Why do my screen-reader tests fail even though my Flesch-Kincaid score is good?

Likely causes: missing alt text on images, improper heading hierarchy, form fields without labels, tables without header rows, color-only instructions, or poor list markup. Screen readers depend on semantic HTML structure, which readability formulas cannot evaluate. Run an accessibility audit tool like WAVE to identify structural issues.

Should I always target the lowest possible reading level?

Not necessarily. A 5th-grade reading level is not always appropriate for specialized audiences (e.g., clinical researchers, engineers). However, WCAG 2.1 AA compliance mandates lower-secondary level for general audiences. If your primary audience is specialized, document this decision and ensure non-specialist sections (e.g., executive summaries, patient-facing materials) meet grade-level targets.

How does cognitive accessibility differ from readability formulas?

Cognitive accessibility addresses mental load: working memory, attention span, conceptual density, and task complexity. Readability formulas count syllables and sentence length. A 7th-grade-level sentence listing ten conditions and five actions is cognitively harder than a 9th-grade sentence describing one concept clearly. Use formulas as a baseline; supplement with user testing and cognitive-load best practices.

Can WCAG 3.0 change readability compliance targets?

WCAG 3.0 is expected to focus more heavily on outcome-based conformance and cognitive accessibility, but as of mid-2026, it remains in draft. For current compliance, follow WCAG 2.1 (lower-secondary level for AA). Monitor WCAG 3.0 updates; early signals suggest cognitive accessibility will receive more explicit attention.

Bottom Line

Readability formulas and WCAG compliance are complementary but distinct. Readability formulas predict how easily humans parse prose and are essential for meeting WCAG 2.1 Level AA (6th–8th grade) and AAA (5th–6th grade) targets. WCAG, however, demands semantic structure, cognitive clarity, alternative content, and navigation accessibility—dimensions formulas cannot measure. To optimize for both, target a Flesch-Kincaid score of 5–8 depending on your audience and WCAG level, ensure proper heading hierarchy and list markup, test with accessibility tools like WAVE or Axe DevTools, and—for healthcare, legal, and other high-stakes domains—validate your work with real users, including those with dyslexia, low vision, and cognitive disabilities. The goal is not a perfect formula score; it is content that works for everyone.