Readability Score – Glossary

Scores estimate how easy text is to read” could be “Readability scores estimate how easy text is to read.

Why it matters

• Scores reveal dense wording and long sentences, useful for quick QA.
• They help match content to audience knowledge, especially for help docs and forms.
• They provide a simple baseline to compare drafts and track improvements.

Common scales

• Flesch Reading Ease: 0 to 100, higher is easier.
• Flesch-Kincaid Grade Level: school grade, lower is easier.
• Gunning Fog: years of formal education needed.
• SMOG: focuses on polysyllabic words, good for health content.

Target ranges

• General web pages: Flesch 60 to 80, FK grade 6 to 8.
• Technical docs for mixed audiences: Flesch 50 to 70, FK grade 8 to 10.
• Legal and policy pages: aim for clarity, explain jargon, provide summaries. Do not rely on a single score.

Best practices

• Use plain language, choose familiar words.
• Shorten sentences, one idea per sentence.
• Cut filler, remove hedging and redundancies.
• Prefer active voice, concrete verbs.
• Explain unavoidable jargon with short definitions.

Quick example

Before: “Utilize streamlined methodologies to expedite operational efficiencies across cross functional teams.” After: “Use simple processes to help teams work faster.”

Workflow

1. Draft normally, focus on clear intent and structure.
2. Run a readability check in your editor or CI, record the score.
3. Fix the obvious issues, long sentences and jargon.
4. Recheck scores, then read aloud and test with a colleague.
5. Publish, update scores only when you edit content.

Limitations

• Scores can be gamed, they ignore meaning and tone.
• Short words can still be unclear, context matters.
• Use scores as a compass, not a mandate.
• Pair scores with user testing, read-aloud, and task completion checks.