Hi everyone!
Today we're talking about a WCAG criterion that goes beyond the technical aspects of code and focuses on language clarity: WCAG 3.1.5 Reading Level. This is a Level AAA criterion, meaning it's a more advanced goal, but its importance for inclusivity is immense.
What is WCAG Success Criterion 3.1.5?
This criterion states that:
"When text requires reading ability more advanced than the lower secondary education level (approximately 9 years of education), a supplementary version of the content is available that does not require reading ability more advanced than the lower secondary education level."
In other words, if your content is complex and requires higher education to be understood, you must provide a simpler version or a summary that is comprehensible to a wider audience.
Why is Plain Language So Important for Accessibility?
Clear and concise language is fundamental for:
- Individuals with Cognitive Disabilities: They may have difficulty processing complex information.
- Individuals with Learning Difficulties: Overly dense texts or specialized jargon can be an insurmountable barrier.
- Individuals with Low Literacy: Not everyone has the same level of education.
- Non-Native English Speakers: Simple language facilitates comprehension.
- Everyone: In a fast-paced world, everyone benefits from information presented directly and easy to digest. It reduces cognitive effort and increases efficiency.
Even though 3.1.5 is AAA, applying plain language principles is a good practice for all content:
- Use Short, Simple Sentences: Avoid long and complex sentences.
- Common Vocabulary: Prefer commonly used words over specialized terms, unless strictly necessary (and if so, explain them).
- Clear Structure: Use headings, subheadings, bullet points, and short paragraphs to organize information.
- Avoid Jargon: If you must use technical terms, explain their meaning.
- Active Voice: Prefer active voice over passive.
- Highlight Key Points: Use bold text to emphasize important information.
- Explain Acronyms and Abbreviations: Always spell out the full meaning the first time you use them.
- Complex: "The paradigmatic interaction between the user interface and the underlying system architecture may induce a heuristic dysfunction in the end-user's cognitive engagement."
- Simple: "The way you use the software can make it hard to understand."
What are your strategies for making content easier to read? Do you have examples of texts you've had to simplify? What tools do you use to assess readability (e.g., readability indexes)?
Warm regards,
Michele (wcgadmfrm)
WCAG Plus Forum Team