Most webpages contain a significant amount of textual content. Beyond the visible text, there is often content that should be accompanied by text alternatives, such as descriptions for images or transcripts for video or audio. In this post, we’re not focusing on the technical implementation of accessible text, like how to ensure text alternatives are read correctly by screen readers, but rather on the text itself: the words you choose and how you use them. Because how something is written has a profound impact on how easily it can be understood.

If textual content can be perceived, but not understood, it cannot be considered accessible.

Why accessible language matters

Everyone benefits from clear, simple language. But for many users, including those with cognitive disabilities, learning differences, non-native language backgrounds, or limited literacy, accessible text is not just helpful but essential. Dense, overly complex writing increases cognitive load, making it harder to process information, navigate content, and act on it.

Inaccessible language creates unnecessary barriers. It can lead to misunderstandings, frustration, and even exclusion from critical information or services. Making your writing more accessible is one of the simplest and most effective ways to improve the user experience for everyone.

Accessible language helps your website reach its audience and achieve its goals, whether that involves providing important information, increasing engagement, or driving sales.

There are also legal obligations to consider. While accessible language is addressed to some extent in WCAG, several other laws specifically emphasize the importance of clear communication. In the European Union, the Consumer Rights Directive requires that consumer information and contracts be written in a clear and understandable way. In Sweden, the Language Act states that public language must be “cultivated, simple, and comprehensible,” and public authorities are expected to use plain language in their communication with the public. In the United States, the Plain Writing Act of 2010 mandates that federal agencies use plain language in documents intended for the general public.

These regulations reflect a shared principle: important information must be accessible and easy to understand.

Writing clearly is not just best practice, but often a legal requirement, and a key part of inclusive communication.

How to improve text accessibility

There are many good resources on accessible writing and plain language on the web. A few examples include:

Federal plain language guidelines (in English)

Klarspråk (in Swedish)

Leichte Sprache (in German)

Some of the most important things to have in mind are:

• Structure for readability
  • Use headings and subheadings to break content into clear sections.
  • Keep sentences concise (ideally under 20 words) and paragraphs short (2-4 sentences) to avoid overwhelming the reader.
  • Use bullet points to make complex information easier to take in.
• Reduce perceived density
  • Avoid walls of text! In addition to short paragraphs with concise sentences, visual breaks such as images, spacing and graphs* help users get an overview.
  • Use active voice and direct phrasing.
• Choose familiar words
  • Use common words over academic or formal ones.
  • Replace idioms or cultural references with more universal expressions.
  • Avoid slang, unless your audience specifically expects it.
• Explain complex concepts
  • If complex terms or concepts are not possible to avoid, explain them in clear language.
  • Use examples or analogies to clarify abstract ideas.
  • Expand and/or explain abbreviations.

Relevant WCAG criteria

While the most directly relevant WCAG (Web Content Accessibility Guidelines) success criteria for readable text are at the AAA level, meaning they’re not required for legal compliance, they still offer valuable guidance.

3.1.5 Reading Level (Level AAA)

This criterion encourages content to be written at a lower secondary education level (roughly age 15–16) or below, unless the content is complex for a valid reason (such as legal or technical documentation). This doesn’t mean “dumbing down” your content, but making it as clear as possible for as many people as possible. Achieve this by using short sentences, familiar vocabulary, and straightforward structure.

3.1.3 Unusual Words (Level AAA)

If you need to use jargon, technical terms, or uncommon words, make sure to explain them. You can do this inline, through a glossary, or using accessible help features. This is especially important in domains like healthcare, finance, or government services, where specialized language can be a major obstacle to understanding.

3.1.4 Abbreviations (Level AAA)

Abbreviations and acronyms should be expanded or explained the first time they’re used. While common abbreviations might be obvious to some users, they can confuse others, especially if they’re non-native speakers or using assistive technology.

Other related WCAG criteria

While other criteria typically focus on the technical aspects of text, such as how texts are coded and presented, compliance with these criteria are only truly effective if the text itself is written in an accessible, understandable manner.

• Criteria under 1.1 Text Alternatives and 1.2 Time-based Media
• 1.3.1 Info and Relationships (Level A)
• 2.4.4 Link Purpose (In Context) (Level A)
• 2.4.6 Headings and Labels (Level AA)
• 3.2.4 Consistent Identification (Level AA)
• Criteria under 3.3. Input Assistance

* Note: Accessible graphs is a big topic in itself! I can recommend the recent webinar from Funka, No barriers, just bar charts: Chart accessibility made easy (13 June 2025).