Readability for Government and Plain-Language Compliance: Meeting Federal and Accessibility Standards

Readability for government audiences isn't optional—it's a compliance mandate. The Plain Writing Act of 2010, accessibility standards under WCAG 2.1, and Section 508 requirements create a binding framework that federal agencies must follow. Yet most government writers work with scattered guidance: an outdated training module here, an agency memo there, no unified standard for what "plain language" actually means in measurable terms.

This guide consolidates that scattered guidance into actionable compliance targets, shows you which formulas agencies actually use (with real target scores), and gives you an auditable checklist to prove compliance.

The Plain Writing Act: What Government Agencies Are Actually Required to Do

The Plain Writing Act (PWA), signed in 2010, requires federal agencies to write "clear, concise, well-organized" material. But what does that mean in practice?

The law mandates:

• Clear communication of information the public must use or understand
• Measurable clarity—agencies must use readability metrics to validate compliance
• Audience-centered design—content aimed at the audience's actual needs and literacy level, not bureaucratic custom
• Written compliance certification—agencies must document that they've applied plain language standards during document creation

For a government benefits application, plain language compliance means a 9th-grade reader can understand eligibility rules without a lawyer. For health alerts, it means a 6th-grader can follow instructions. For tax forms, it means clarity at or below the 8th-grade level.

The PWA applies to "significant" documents—anything that affects public benefit, legal obligation, or health/safety. It does not apply to classified material, internal agency memos, or purely procedural guidance. But if the public must read it to obtain a benefit or follow a regulation, the Plain Writing Act covers it.

Compliance isn't aspirational. Agencies risk federal review and public criticism for non-compliance. The Office of Management and Budget (OMB) and the Plain Language Action and Information Network (PLAIN) audit agency websites and major publications quarterly.

Which Readability Formula Do Federal Agencies Use? (And Why Flesch-Kincaid Dominates)

Not all readability formulas are equal in government contexts. The Flesch-Kincaid Grade Level formula became the de facto federal standard because:

1. It's built into Microsoft Word, which dominates government writing workflows
2. It produces results consistent with Plain Writing Act guidance—the OMB and PLAIN explicitly cite it
3. It's legally defensible—agencies can cite it in compliance documentation without challenge
4. It correlates measurably with audience comprehension across diverse literacy levels

The Flesch-Kincaid Grade Level formula weights sentence length and syllable count:

Grade = 0.39 × (words/sentences) + 11.8 × (syllables/words) − 15.59

In plain terms: longer sentences and longer words raise the grade level. A 9th-grade text requires roughly 15–17 words per sentence and single-syllable or two-syllable words.

Other formulas—Flesch Reading Ease, SMOG, Gunning Fog, Dale-Chall—get used in healthcare and accessibility contexts, but they're secondary in government compliance audits. Flesch-Kincaid is the standard.

Why not just use the simpler Flesch Reading Ease score (0–100 scale, higher = easier)? Because the grade-level output is more intuitive for compliance reporting. Saying "this document meets 7th-grade readability" means more to a government writer than "this document scored 75 on Reading Ease."

Target Grade Levels by Agency Type: IRS vs HHS vs VA vs GSA

Federal agencies don't have one universal readability target. The Plain Writing Act requires agencies to match grade level to audience and purpose. Here's what major agencies actually target:

Internal Revenue Service (IRS)

• Target: 8th grade
• Rationale: Tax forms and instructions must reach the broadest possible taxpayer base; many filers have limited education or English as a second language
• Real benchmark: IRS Publication 17 (tax guide for individuals) aims for 8th-grade Flesch-Kincaid; recent audits show it lands at 8.2–8.9
• Application: Every instruction, every form note, must test below 8.5 grade level

Department of Veterans Affairs (VA)

• Target: 6th–8th grade
• Rationale: Benefits language must be accessible to disabled veterans, many of whom face cognitive, TBI, or literacy challenges; plain language is a veteran service
• Real benchmark: VA claims forms and eligibility guides target 7th grade; internal compliance reviews flag text above 8th grade for rewrite
• Application: Simplified vocabulary; no conditional clauses; active voice mandatory

Department of Health and Human Services (HHS)

• Target: 6th–9th grade (varies by program)
• Rationale: Medicare beneficiaries (avg. age 73) have mixed literacy; public health guidance must reach non-native speakers
• Real benchmark: Medicare.gov content targets 8th grade; vaccine safety guides and adverse-event forms target 6th grade
• Application: Healthcare content is higher-risk; lower grades = safer compliance margin

General Services Administration (GSA)

• Target: 8th–9th grade
• Rationale: Procurement and benefits information for federal employees; audience is diverse but assumes basic work literacy
• Real benchmark: eForms and personnel guidance test at 8.5–9.2
• Application: Internal government communications have slightly higher tolerance; public-facing benefits info drops to 7th–8th

Social Security Administration (SSA)

• Target: 8th grade
• Rationale: Beneficiary communications reach retirees, disabled workers, and families; audience spans all education levels
• Real benchmark: SSA benefit letters and eligibility notices target 7th–8th grade; recent overhauls reduced grade levels from 10–11 range
• Application: Consistent use of conversational tone; "your benefit will start on [date]" instead of "commencement of remuneration shall occur upon…"

The pattern: If the audience includes vulnerable populations (elderly, disabled, non-native English speakers, low-income), the target drops to 6th–7th grade. If the audience is federal employees or educated professionals, 8th–9th is acceptable.

Flesch Reading Ease Thresholds for Government Compliance

While Flesch-Kincaid Grade Level dominates federal reporting, the Flesch Reading Ease score (0–100, higher = easier) offers a secondary validation layer. Here are the government thresholds:

Score Range	Grade Equivalent	Government Use	Compliance Margin
90–100	5th grade or below	Children's health materials, simplified forms	Safe (surplus clarity)
80–89	6th–7th grade	Veteran benefits, public health alerts, Medicare info	Recommended for vulnerable audiences
70–79	8th–9th grade	IRS forms, federal benefits, standard compliance target	Acceptable for most federal writing
60–69	10th–12th grade	Technical guidance, agency procedures (internal)	Non-compliant for public-facing documents
Below 60	College+	Academic papers, legal analysis	Violates Plain Writing Act for public documents

A Flesch Reading Ease score of 65–75 often means a Flesch-Kincaid grade of 8–9. The two formulas are correlated but not identical; use both to validate.

Government audit practice: If your Flesch-Kincaid score is 8.5 and your Flesch Reading Ease is 72, you're compliant with most federal targets but should flag it for editorial review if your audience includes non-native English speakers.

WCAG 2.1 and Readability: Beyond Grade Level to Accessibility

The Plain Writing Act focuses on grade level, but WCAG 2.1 (Web Content Accessibility Guidelines) and Section 508 compliance add a second layer: structural readability for screen readers and cognitive accessibility.

WCAG 2.1 Success Criterion 3.1.5 (Reading Level) requires that "text shall remain clear and understandable" after removing headers, form labels, and other scaffolding. This is tighter than grade-level alone.

Practical implications for government writers:

1. Headings must be semantic and scannable, not just bold text

   • Don't: Important note: Your form expires after 30 days.
   • Do: Use a proper H3, and lead with the deadline: "Your form expires after 30 days."

2. Lists break up dense text and lower cognitive load

   • Dense: "You must provide your Social Security number, date of birth, and state of residence in order to verify your identity."
   • Accessible: "To verify your identity, provide: Your Social Security number; Your date of birth; Your state of residence."

3. Acronyms must be expanded on first use

   • Don't: "File your 1040-NR form with the IRS by April 15."
   • Do: "File your 1040-NR form with the Internal Revenue Service (IRS) by April 15."

4. Avoid abbreviations for months and states

   • Don't: "Your benefit started 03/15/2024 in NY."
   • Do: "Your benefit started March 15, 2024 in New York."

These changes don't directly lower a grade-level score, but they dramatically improve comprehension for screen readers, dyslexic readers, and non-native speakers. A document can score 7th-grade Flesch-Kincaid and still fail WCAG 2.1 if it's a wall of dense paragraphs.

Real Example: Rewriting IRS Instructions to Meet Plain Language Standards

Here's a redacted real-world case: an IRS instruction note on child tax credit eligibility, pre- and post-revision.

Original (Pre-Plain Language Audit)

"In the event that a taxpayer has received or is entitled to receive dependent-care benefits through a cafeteria plan maintained by an employer, the taxpayer shall exclude from the definition of 'qualifying person' any child for whom such benefits were provided if the child's age exceeded 12 years at the close of the relevant taxable year, and furthermore shall not take into account such benefits in the computation of employment-related dependent care expenses for the purposes of this section."

• Flesch-Kincaid: 16.3 (graduate level)
• Flesch Reading Ease: 28 (very difficult)
• Compliance: Failed (target is 8th grade)

Revised (Post-Plain Language Audit)

"If your employer gave you dependent-care benefits for your child, don't claim the child tax credit if your child was older than 12 at the end of the year. Also, don't include those benefits when you calculate dependent-care expenses."

• Flesch-Kincaid: 7.8 (7th–8th grade)
• Flesch Reading Ease: 74 (fairly easy)
• Compliance: Passed

Changes made:

1. Removed "shall," "in the event that," "entitled to receive"—replaced with direct address ("your")
2. Broke one 48-word sentence into two 12–15 word sentences
3. Cut passive voice; converted to active ("don't claim" vs. "shall not take into account")
4. Removed subordinate clauses; made relationships explicit with "Also" and "don't"
5. Replaced "qualifying person" and "relevant taxable year" with "your child" and "the end of the year"

The revision removed zero regulatory content—it's still legally accurate and complete. It just made it readable.

You can test this yourself using a Flesch-Kincaid calculator for compliance testing, which will show you grade level and Reading Ease simultaneously.

Conducting a Readability Audit: Compliance Checklist for Government Writers

Use this checklist to audit a government document for Plain Writing Act and WCAG 2.1 compliance:

Grade-Level Validation

• Run the document through Word's readability stats or an external tool
• Record the Flesch-Kincaid Grade Level and Flesch Reading Ease
• Verify the grade level matches your target audience (6th–9th grade for most federal public-facing content)
• Flag any paragraph above 9th grade for rewrite
• Spot-check compliance; don't rely on tool averages alone

Sentence and Word Checks

• Average sentence length: aim for 15–17 words
• Flag sentences over 25 words; break them into two
• Scan for Latinate or technical terms; replace with common synonyms where possible
• Replace "utilize" with "use," "subsequent" with "next," "terminate" with "end"
• Check what is a good readability score for your specific agency or audience type

Accessibility and Structure

• All headings are semantic (HTML H2, H3, etc., not just bold text)
• Lists are used instead of dense paragraphs
• Acronyms are expanded on first mention
• No abbreviations for months or states
• Active voice dominates (spot-check at least 10 sentences)
• Conditional phrases ("if…then") are broken into separate short sentences

Compliance Documentation

• Document is dated with readability score at sign-off
• Grade-level target and achieved score are noted in the metadata or certification memo
• Any exceptions (technical terms that can't be simplified) are justified in writing
• Multiple readers (including non-experts) have reviewed for clarity

Real Audit Red Flags

• Document tests above 10th grade on any section
• Sentences average over 20 words
• Passive voice appears in more than 10% of sentences
• Acronyms are used without expansion
• Tables or forms lack clear labeling

Tools and Training: Microsoft Word, Grammarly, and Plain Language Validation

Microsoft Word (Built-In, No Cost)

• Enable readability stats: File > Options > Proofing > Show readability statistics
• Pros: Integrated, free, legally defensible (OMB recognizes it)
• Cons: Accuracy varies; can miss structural accessibility issues
• Government use: Standard for federal agencies; most compliance audits accept Word output
• Limitation: Microsoft Word readability score accuracy can drift on documents with heavy formatting or embedded tables

Grammarly (Subscription, ~$10–15/month)

• Flags long sentences, passive voice, and readability in real-time
• Pros: Catches more patterns than Word; integrates with browsers and Office
• Cons: Privacy concerns in some federal networks; requires IT approval
• Government use: Growing adoption, but check your agency's cloud-security policy first
• Note: Grammarly's readability scores correlate with Flesch-Kincaid but don't always match Word exactly

Flesch-Kincaid Specialist Tools

• Readability Check, Hemingway Editor, ProWritingAid offer dedicated Flesch-Kincaid calculation
• Pros: Precise scoring; batch processing for large documents
• Cons: Some require web upload (check FISMA compliance)
• Government use: Useful for validation but not standard for official compliance certification

Plain Language Training

• The Plain Language Action and Information Network (PLAIN) offers free federal training on its website
• GSA's plainlanguage.gov provides templates, checklists, and before/after examples
• Many agencies (VA, HHS, IRS, SSA) run internal plain language workshops; check your agency's learning portal
• Consider improving readability scores with concrete editing tactics specific to your document type

Validation Without Tools

• Read-aloud test: Read the text aloud to a peer. If you pause for breath more than once per sentence, it's too long.
• Audience proxy: Have someone outside your field read a section silently and summarize it back to you. If they misunderstand, revise.
• Grade-level estimation: Compare your writing to 7th-grade newspaper articles (local news, not opinion). If yours is more complex, it's above your target.

Conclusion

Government readability compliance is measurable, auditable, and non-negotiable. The Plain Writing Act requires federal agencies to prove clarity through Flesch-Kincaid Grade Level scoring, with targets between 6th and 9th grade depending on audience vulnerability. The IRS, VA, HHS, and SSA all publish internal compliance targets—8th grade is the standard for public-facing benefits and regulatory content.

Beyond grade level, WCAG 2.1 and Section 508 standards require structural accessibility: semantic headings, lists, expanded acronyms, and active voice. A document that scores 8th-grade Flesch-Kincaid but lacks these structural elements will still fail federal accessibility review.

Use the audit checklist above before sign-off. Record your baseline readability score. Validate with a second tool (Word + an external calculator). Document the score in your compliance memo. This creates an auditable trail that protects your agency in case of OMB review or public challenge.

Your writing doesn't need to be simplified or dumbed down. It needs to be clear and direct—which is harder than it sounds, because clarity requires work. But that work is the job. Plain language compliance isn't a box to check; it's the standard.