Skip to content
Barrierefrei²

Success criterion 3.1.3

3.1.3 Unusual Words

Level AAAUnderstandable

When jargon becomes a barrier.

1. What is the goal of this criterion?

Imagine reading this on a company website: “Our agile framework implements a scalable DevOps pipeline with KPIs that optimize ROI and time to market.” Clear to insiders – a puzzle of jargon to everyone else.

People with cognitive disabilities, learning difficulties or no background in the field quickly hit their limits with jargon, idioms and words used in unusual ways. The goal of WCAG Success Criterion 3.1.3 is that the specific meaning of such terms can be looked up.

In short: every term used in an unusual or restricted sense needs an explanation people can find.

2. What exactly does it require?

This criterion covers words and phrases used in an unusual or restricted way. There are three groups:

Jargon and technical language: terms from particular professions or groups that are hardly understood outside them – such as “stakeholder”, “benchmarking” or “proof of concept”.

Idioms: expressions whose meaning can’t be worked out from the individual words – such as “hit the nail on the head” or “beat around the bush”.

Words with a special meaning: terms that have a specific definition in a text that differs from everyday usage – in WCAG, for example, “text” has its own precisely defined meaning.

The requirement: there must be a mechanism to identify the specific meaning – for example a glossary, a link to an explanation, a definition right in the text, or an explanation that can be expanded with a click.

Important: this criterion is Level AAA – the highest level in WCAG. Abbreviations are covered by the related criterion Abbreviations.

3. Why does it matter for accessibility?

Imagine reading an article about “liquid democracy” or “tokenization”, and nobody explains the terms. You give up in frustration – even though the topic actually interests you.

Explanations for unusual terms improve accessibility because they:

  • help people with cognitive disabilities or learning difficulties understand text
  • support people who find it hard to infer meaning from context
  • help people reading in a language that isn’t their first – idioms are often taken literally
  • support people with low vision who zoom in a lot and can more easily lose track of context
  • make specialist knowledge more accessible to beginners and people from other fields

And finally: they make content easier to understand for anyone curious about a new topic.

4. How to meet the criterion

The good news: explaining terms is usually easier than it sounds. Here are some proven methods:

Explain directly in the text: “Onboarding – the structured process of bringing new employees up to speed – involves …”. This is the simplest and most robust solution.

A glossary with links: create a glossary and link technical terms to it, at least the first time they appear on a page.

Mark up definitions: the HTML element <dfn> marks the place where a term is defined. Glossaries work well as description lists:

<dl>
  <dt><dfn id="onboarding">Onboarding</dfn></dt>
  <dd>The structured process of bringing new employees up to speed.</dd>
</dl>

<p>Our <a href="/glossary#onboarding">onboarding</a> takes four weeks.</p>

Expandable explanations: short explanations that open with a click work well – as long as they’re reachable by keyboard and touch and available to screen readers. Plain tooltips via the title attribute are not suitable. Content that appears on hover or focus is also covered by Content on Hover or Focus.

Structured approaches:

  • Mark explained terms consistently – and not by color alone.
  • Offer different levels of detail: a short explanation in the text plus a link to the full definition.
  • Skip jargon where you don’t need it – the best-explained term is often the one you can do without.

You’ll find more on writing understandable content in the article Easy-to-read and plain language.

5. Why this criterion matters for businesses

3.1.3 is a Level AAA criterion and not legally required under the European Accessibility Act or its German implementation, the BFSG – the underlying standard EN 301 549 requires WCAG 2.1 Level AA. Being understood is still a real advantage.

1. Reach more people

When you explain technical terms, your content becomes accessible to more people. A specialist blog with clear explanations reaches not only experts but also interested readers, students and career changers.

2. Indirectly easier to find

Accessibility isn’t a direct ranking factor. But many people search precisely for explanations – “What does … mean?”. A good glossary answers those questions and can bring in new visitors.

3. Build trust

People don’t buy what they don’t understand. A shop or service provider that clearly explains terms like “cloud-native” or “GDPR-compliant” removes uncertainty and builds trust.

This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.1.3 Unusual Words (Level AAA)

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

In short: for words and phrases used in an unusual or restricted way – including idioms and jargon – it must be possible to look up their specific meaning.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 3.1.3 (opens in a new tab)