How accessible is your website?Start free check
WCAG 3.1.5Level AAAUnderstandable

Plain Language: WCAG Reading Level (3.1.5)

Also called: clear language, plain English, easy-to-read text, reading level

Definition

Plain language is writing that readers can understand the first time they read it: common words, short sentences and the most important point first. WCAG 3.1.5 Reading Level (AAA) asks for a simpler version or supplemental content when text needs more than lower secondary education reading ability.

Plain language is text that people understand the first time they read it – everyday words, short sentences and the main point up front. In WCAG it is covered by success criterion 3.1.5 Reading Level, which asks for an easier version or extra help when a text is harder to read than it needs to be. Writing in clear language is one of the most effective steps toward cognitive accessibility, and it helps every visitor who is busy, tired or reading in a second language.

What it means

The Understanding page for 3.1.5 Reading Level sets a testable threshold: when text needs reading ability more advanced than the lower secondary education level – after removing proper names and titles – you provide supplemental content or a version that does not need that level. WCAG defines lower secondary education as the two or three years of school that begin after six years of school and end nine years after primary education begins.

Part of the rule What WCAG says
Level AAA
Threshold Reading ability above lower secondary education level
Not counted Proper names and titles
Ways to meet it Supplemental content that illustrates or clarifies the text, or a simpler version

The W3C's intent is direct: content should be written as clearly and simply as possible. The criterion benefits people who have difficulty understanding and interpreting written language – for example people with reading disabilities or cognitive disabilities.

W3C lists sufficient techniques such as a text summary readable at lower secondary level (G86), illustrations and symbols that explain ideas (G103), a spoken version of the text (G79), making the text easier to read (G153) and sign language versions (G160).

Examples

A product page that explains a return policy in legal wording, followed by the same rule in plain English:

Example
<!-- Hard to read -->
<p>Notwithstanding the foregoing, the purchaser shall be entitled to
rescind the contract within a period of fourteen days commencing
upon receipt of the goods.</p>

<!-- Plain language -->
<h2>Returns</h2>
<p>You can return your order within 14 days after it arrives.
We refund the full price.</p>

The W3C's own examples include a scientific journal with readable summaries of complex research, medical information written for the public and an e-learning application. Error messages are another good place to start: a plain error suggestion such as "Enter your postcode, for example 1010" works better than "Invalid input".

Do

Put the key information first, use one idea per sentence, choose common words, explain unavoidable technical terms and use lists and headings to break up long text.

Don't

Write long nested sentences, rely on jargon or abbreviations without explanation, or hide the action people need to take at the end of a paragraph.

How to write and check plain language

    Readability formulas can give a rough signal, but WCAG names no formula. Structure also matters: real headings and short paragraphs make text easier to scan for everyone, including people using a screen reader.

    Questions

    What is the difference between plain language and easy read?

    Plain language is clear everyday writing for a general audience. Easy read (in German "Leichte Sprache") follows stricter rules – very short sentences, no abbreviations, often pictures – and is written mainly for people with learning disabilities.

    Is plain language a legal requirement?

    WCAG 3.1.5 is Level AAA, which most laws do not require. Some rules go further: Germany's BITV 2.0 asks federal public bodies to explain the main content of their homepage in easy-to-read language.

    What reading level does WCAG require?

    WCAG 3.1.5 uses the lower secondary education level as its threshold. Text above that level needs a simpler version or supplemental content such as a summary or illustrations.

    Does plain language mean dumbing down content?

    No. It keeps the full meaning but removes obstacles: unclear structure, unnecessary jargon and long sentences. Clear text also helps experts who are short on time.

    How do I find other barriers on a page besides wording?

    Automated tools cannot judge how readable a sentence is, but they find many technical barriers. The free WCAG scanner checks a page against WCAG 2.2 AA in seconds.

    • Cognitive Accessibility: Websites Easy to Understand

      Cognitive accessibility means designing websites so that people with cognitive and learning disabilities can understand and use them – including difficulties with memory, attention, language, reading and math. It covers clear content, predictable navigation, forgiving forms and processes that do not rely on memory.

      Read definition: Cognitive Accessibility: Websites Easy to Understand
    • WCAG Conformance Levels: A, AA and AAA Explained

      WCAG conformance levels are the three tiers – A, AA and AAA – at which a web page can meet WCAG. Each level includes every success criterion of the levels below it, and conformance always applies to full pages and complete processes.

      Read definition: WCAG Conformance Levels: A, AA and AAA Explained
    • Headings and Labels: Describe Topic or Purpose

      Headings and Labels is WCAG success criterion 2.4.6 (Level AA). Headings and labels describe topic or purpose, so people can tell what a section contains or what a field expects.

      Read definition: Headings and Labels: Describe Topic or Purpose
    • Error Suggestion: Help Users Fix Form Errors

      Error suggestion means that when a website detects an input error and knows how it could be corrected, it offers that correction to the user. WCAG 3.3.3 requires it at Level AA, unless it would jeopardize security or the purpose of the content.

      Read definition: Error Suggestion: Help Users Fix Form Errors

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done