Menu

Content

Readability Testing

A practical UX content method for measuring and improving how easily users can read, understand, and act on written information.

How to run readability testing to reduce complexity, improve comprehension, and support better task completion.

4 min read

What it is

testing is a UX method used to evaluate how easily users can read and understand content.

It involves measuring factors such as sentence length, word choice, structure, and complexity.

Tools and metrics like Flesch-Kincaid or SMOG can be used alongside real user testing.

The focus is on , speed, and rather than grammar alone.

The goal is to ensure content is accessible, understandable, and actionable for the target audience.

Readability testing is most useful when content performance is measured by understanding, not just correctness.

When to use it

Use this method when is critical.

It is most useful when:

your content is dense, technical, or lengthy
users are struggling to complete tasks due to language
you want to meet accessibility and plain language standards
the product is public-facing or widely used
you need evidence to guide content simplification

It is less useful when:

content is very simple or already validated
the audience is highly specialised
Readability testing is often used alongside plain language reviews and content audits.

Key takeaway

Use readability testing when unclear language is creating friction in key journeys.

How to run it

Set up properly

Be clear on the content you are evaluating, the audience it is for, and what you need. A grade level is a proxy, not a goal.

Include real and tasks where possible. Reading in isolation is a different activity from reading to get something done.

Run the method

testing is evaluative and iterative. Formulas give you a number quickly; people give you the truth slowly, and you need both.

  1. Measure with a formula to get a baseline, understanding what it does and does not see. scores count syllables and sentence length, not whether the sentence makes sense.
  2. Observe real users reading and then acting. is demonstrated by doing the right thing, not by saying it was clear.
  3. Identify the specific words, phrases or structures that cause hesitation, rather than judging the passage as a whole.
  4. Collect on , but weight above opinion. People routinely report understanding content they then act on incorrectly.
  5. Adjust and retest. A rewrite that has not been retested is an assumption with better formatting.

Focus on and together. Content can be understood perfectly well and still take three times longer than it should.

Capture and make sense of it

The value comes from measurable . After testing, document:

  • Passages that were too complex, with what made them so
  • Simpler alternatives, tested rather than assumed
  • Changes prioritised by user impact rather than by score improvement
  • The gap between reported and actual

Use this to optimise content for and . Where score and disagree, behaviour is right.

What to look for

Focus on:

Comprehension: do users understand the content quickly
Speed: how long it takes to read and act
Complexity: sentence length, jargon, word choice
Clarity: are instructions or explanations clear
Errors: misinterpretation or confusion

Where it goes wrong

Most issues come from:

If users can’t understand, the content fails.

Treating a readability score as the goal, when it counts syllables and not sense
Trusting reported clarity over observed behaviour, which routinely disagree
Rewriting to hit a grade level and losing the precision that mattered
Changing style in one place and leaving the rest inconsistent
Shipping the rewrite without retesting it

What you get from it

Done properly, this method gives you:

Evidence about comprehension rather than an opinion about tone
The specific words and structures that stopped people
Content people can act on, not merely read
An argument about writing that is settled with data

Key takeaway

It helps users understand and act on content without struggle.

Get in touch

If this sounds like something you need, we can test your content for readability and help make it clear, concise, and actionable for all users.

No guesswork. No assumptions. Just content that works.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is readability testing in UX?

It is a method for evaluating how easy it is to read and understand content.

When should you use readability testing?

When you need evidence rather than opinion about whether content lands. It is most useful on high-traffic or high-stakes pages, and on anything written by specialists for a general audience. The gap between those two is where readability usually fails.

What can you measure?

Comprehension, reading speed, complexity, and clarity.

Why test readability rather than judge it?

Because writers are the worst judges of their own clarity. Testing replaces the author's confidence with evidence of whether real readers take away the right meaning, which is frequently not the meaning that was intended.

Does readability testing improve UX?

Yes. Clear content increases usability and reduces errors.

Quick take

If users struggle to read your content, they won’t engage. Test how readable it really is.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer