Plain language vs easy language: when is it required?

“Do I need easy language or plain language on my website?” – this question is often answered wrongly, because the two terms get confused and because a rule from the public sector is mistakenly applied to private companies. This article explains the difference, what is actually required and for whom, and when simpler language is worth it anyway. It is part of our guide on how to make your website accessible.

Easy language and plain language – not the same thing

The two terms mean different things:

Easy Language (also called Easy Read) is a strongly regulated, simplified form of language with a fixed rule set: very short sentences, only one statement per sentence, no subordinate clauses, the explanation of difficult words, often supported by images and large type. It was developed above all for people with cognitive impairments or learning difficulties.

Plain language is a more flexible simplification: clear standard language with shorter sentences and common vocabulary, but without the strict rule set. It addresses a broad audience – people with lower reading literacy, non-native speakers, or simply readers in a hurry.

The two are often confused, but they serve different purposes and follow a different degree of strictness.

When easy language is required

Easy language is an obligation in the public sector. In several countries, public-sector bodies must provide certain content in easy language – such as basic information about the content, the navigation and the explanation of accessibility – sometimes alongside a sign-language version.

This is exactly where a common source of confusion lies: this duty comes from public-sector rules and is wrongly understood as if it applied to everyone.

What the EAA requires of the private sector

The decisive point: for private companies, the EAA requires neither easy language nor plain language. The EAA points to EN 301 549 and the WCAG, and while these do call for “understandable” content, that is not the same as an obligation to use easy or plain language. The WCAG success criterion that explicitly concerns reading level sits at Level AAA and is therefore not required. The legal framework is set out in our European Accessibility Act guide.

So a private company has no EAA obligation to offer easy or plain language. Anyone who claims otherwise – especially as something you must buy in order to be “compliant” – is misrepresenting the legal position.

Why plain language can still make sense

The fact that something is not required does not mean it brings no benefit – quite the opposite. Clearer, simpler language reaches more people: those with lower reading literacy, non-native speakers, people under cognitive load, and everyone who quickly looks something up on the move. As a rule this improves comprehension – and with it the success of your site.

So the honest framing is this: plain language is a value-add and a choice – a way to serve more visitors better – not a compliance tick-box.

How to write more understandably

A few principles count as “understandable” content and are simply good writing anyway: short sentences, common words, active phrasing, one idea per paragraph, a clear structure with headings, and the explanation of unavoidable technical terms. This improves your content for everyone – without committing to the full rule set of easy language.

This guide is not legal advice. For a binding assessment of your specific case, consult a qualified professional.