Skip to main content
Category: Inclusive Design Practices

Easy Read

Also known as: Easy read, Easy Read format
Simply put

Easy Read is a way of presenting text and information in a simple, easy-to-understand format that pairs plain language with supporting pictures. It is often used to make content more accessible for people with learning disabilities, and it commonly follows conventions such as keeping to one idea per line. Easy Read is a distinct communication format and is not the same as meeting web technical standards such as WCAG.

Formal definition

Easy Read is a specialist communication format that combines carefully written, simplified text with meaningful images, deliberate layout, and clear design to convey information in an accessible way. Recognized guidance describes conventions such as writing one idea per line and pairing text with relevant pictures to aid comprehension, and the format is frequently cited as useful for people with learning disabilities. Easy Read addresses cognitive accessibility and plain-language presentation; it operates independently of, and is not a substitute for, technical conformance frameworks like the Web Content Accessibility Guidelines (WCAG) or legal requirements under laws such as the ADA. Practitioners should note that Easy Read practice varies by publisher and jurisdiction, and that this entry is not legal advice.

Why it matters

Easy Read addresses a form of accessibility that technical conformance frameworks do not fully capture: cognitive accessibility and comprehension. Many people, particularly those with learning disabilities, find conventional documents difficult to understand even when those documents meet web technical standards. By pairing carefully simplified text with meaningful images and a clear layout, Easy Read helps convey information to audiences who might otherwise be excluded from understanding it. This matters for organizations that need to communicate essential information, such as health, government, or service content, to the widest possible audience.

It is important to recognize that Easy Read is a distinct communication format and is not the same as meeting technical standards such as WCAG or satisfying legal requirements under laws such as the ADA. Producing an Easy Read version of content does not on its own establish WCAG conformance, and conversely, meeting WCAG success criteria does not guarantee that content is comprehensible to people who benefit from Easy Read. These are complementary but separate concerns, and organizations may need to address both.

Because Easy Read practice varies by publisher and jurisdiction, and because it is often developed alongside input from people with learning disabilities, the quality and conventions of Easy Read materials can differ. Organizations considering Easy Read should treat it as one tool within a broader accessibility and inclusive-communication strategy rather than as a substitute for technical accessibility work or legal compliance. This entry is not legal advice, and readers with compliance obligations should consult qualified counsel and current guidance.

Who it's relevant to

People with learning disabilities
Easy Read is frequently cited as useful for people with learning disabilities, who may find conventional text difficult to understand. The pairing of plain language with supporting pictures is intended to aid comprehension for this audience.
Government and public-sector communicators
Agencies and services that need to share essential information with the broadest possible audience may use Easy Read as a user-friendly way to present information using a simple layout with text and images. It can help convey content to people who might otherwise struggle with standard documents.
Content designers and accessibility practitioners
Those responsible for accessible content can use Easy Read to address cognitive accessibility and plain-language presentation. Practitioners should note that Easy Read operates independently of technical conformance frameworks like WCAG and is not a substitute for them, so both may need to be addressed.
Compliance and legal stakeholders
Teams responsible for accessibility obligations should understand that producing Easy Read content does not by itself establish WCAG conformance or satisfy legal requirements under laws such as the ADA. Because requirements and conventions vary by jurisdiction, and because this entry is not legal advice, such stakeholders should consult qualified counsel and current guidance.

Inside Easy Read

Simplified Language
Easy Read uses short sentences, plain vocabulary, and one idea per sentence to make content understandable for people with cognitive or learning disabilities and others who benefit from clearer text.
Supporting Images
Illustrations, photographs, or symbols are commonly placed alongside text to reinforce meaning and help readers understand each key point.
Clear Layout and Structure
Content is generally arranged with generous spacing, large readable text, and a logical order so that information is easy to follow and navigate.
Explanation of Difficult Words
Where complex or technical terms are unavoidable, they are typically explained in simple language so readers are not left without context.
User Involvement
Easy Read materials are often developed and reviewed with input from people with cognitive or learning disabilities to confirm the content is understandable to the intended audience.

Common questions

Answers to the questions practitioners most commonly ask about Easy Read.

Is Easy Read the same as meeting WCAG requirements for readability?
No. Easy Read is a distinct format that combines simplified language with supporting images to aid comprehension, primarily for people with intellectual or cognitive disabilities. WCAG includes success criteria related to readability and understandability, but conforming to WCAG does not automatically produce an Easy Read document, and creating an Easy Read document does not by itself guarantee WCAG conformance. The two address overlapping but not identical goals, and each should be evaluated on its own terms.
Does providing an Easy Read version make my content legally compliant?
Not necessarily. Offering an Easy Read version can support broader accessibility and inclusion goals, but it does not on its own establish compliance with any specific legal authority such as Title II or Title III of the ADA, Section 508, or Section 504 of the Rehabilitation Act. Legal obligations vary by jurisdiction and context and continue to evolve through regulation and case law. This entry is not legal advice; consult qualified legal counsel regarding specific obligations.
Who is the primary audience for Easy Read content?
Easy Read is most commonly associated with people who have intellectual or cognitive disabilities, though it may also assist people with lower literacy, people who are new to a language, or others who benefit from simplified presentation. Identifying the intended audience early helps guide vocabulary choices, sentence structure, and the selection of supporting images.
How is Easy Read typically structured on a page?
Easy Read commonly pairs short, plain sentences with a relevant supporting image, often placing text and its accompanying image close together so each idea is presented in a self-contained way. One main idea per sentence and generous spacing are frequently used conventions. The specific layout should be tested with the intended audience rather than assumed.
Should Easy Read documents still meet digital accessibility standards?
Yes. When Easy Read content is published digitally, it generally still needs to meet applicable accessibility considerations, such as providing text alternatives for images, sufficient contrast, proper structure, and compatibility with assistive technology. The simplified language does not remove the need for the document itself to be technically accessible.
How can I verify that an Easy Read version is effective?
Effectiveness is best confirmed through review and testing with people from the intended audience, ideally including people with the relevant disabilities, alongside manual review. Automated tools may detect some technical issues but cannot assess whether language and images actually improve comprehension, so human evaluation is generally required.

Common misconceptions

Easy Read is the same as meeting WCAG conformance.
Easy Read is an approach to presenting content in a more understandable form; it is distinct from WCAG, which is a technical standard published by the W3C. Producing an Easy Read version does not by itself satisfy WCAG success criteria, and conformance testing remains a separate consideration.
Easy Read is only about simplifying wording.
While plain language is central, Easy Read also commonly relies on supporting images, clear layout, and review with intended users. Reducing it to word choice alone overlooks the visual and structural elements that make the format effective.
An Easy Read version should replace the standard content for everyone.
Easy Read is generally offered as an alternative format to serve readers who benefit from it, not a wholesale replacement. Different audiences may need the standard version, and providing options is usually preferable to substituting one format for all users.

Best practices

Use short sentences and plain vocabulary, aiming for one main idea per sentence to reduce cognitive load.
Pair key points with clear, relevant images or symbols that reinforce rather than distract from the text.
Apply a consistent, uncluttered layout with generous spacing, larger text, and a logical reading order.
Explain any unavoidable complex or technical terms in simple language rather than assuming prior knowledge.
Involve people with cognitive or learning disabilities in developing and reviewing the content to confirm it is understandable.
Offer Easy Read as an alternative format alongside standard content, and treat accessibility conformance and legal compliance as separate matters that may require WCAG testing and, where appropriate, qualified legal counsel.