3.1.6 Pronunciation

1. What is the goal of this criterion?

Language can be a chameleon – the same written word can mean something completely different depending on how it’s pronounced. Take “read”: pronounced like “reed”, it’s present tense; pronounced like “red”, it’s past tense. The sentence “I read the contract” allows both – and whether you’re about to read it or already have can matter a great deal.

For people who use screen readers or have difficulty reading, this can become a real problem. If the software picks the wrong pronunciation, or there’s no hint at all, clear content suddenly turns into a puzzle.

The goal of WCAG Success Criterion 3.1.6 is clear: whenever the meaning of a word in context remains unclear without the right pronunciation, there must be a way to find out that pronunciation.

2. What exactly does it require?

This criterion covers words whose meaning depends on how they’re pronounced. It requires:

A mechanism: there must be a way to find out the correct pronunciation when it’s needed for understanding.

Only for real ambiguity: if the context makes clear how a word is meant, you don’t need to do anything. “Lead the team” is unambiguous, even though “lead” (the metal) is spelled the same way.

Different languages: the issue is especially common in languages like Japanese, where characters (kanji) can have several readings, or in languages like Hebrew and Arabic, where vowel marks are often left out.

The criterion is Level AAA – the highest level in WCAG. It only affects a few places, but in those places it makes a noticeable difference.

3. Why does it matter for accessibility?

Imagine a checklist item that just says: “Read the terms and conditions.” Is it a to-do (present tense, like “reed”) or a confirmation that it’s done (past tense, like “red”)? Sighted readers guess from the surroundings – a screen reader has to pick one pronunciation and may get it wrong.

Pronunciation help improves accessibility because it:

• helps people who rely on screen readers and miss the meaning when a word is mispronounced
• supports people with reading difficulties who “sound out” words as they read
• gives people with cognitive disabilities unambiguous information
• supports learners struggling with a foreign language or technical terms

And finally: unambiguous text is easier to understand for anyone reading quickly.

4. How to meet the criterion

The good news: pronunciation help is usually easier to implement than you’d think. And often the best solution is to rephrase the sentence so the ambiguity disappears. Here are some proven tips:

Information right in the text:

• Put the pronunciation right after the word, for example with a simple respelling: “read (past tense, pronounced like ‘red’)”.
• Or use a phonetic alphabet such as the International Phonetic Alphabet (IPA) – but use it consistently.

A glossary with pronunciation:

• Create a glossary that includes pronunciation alongside definitions.
• Link ambiguous terms directly to their glossary entries.

Technical aids:

• Audio files: link difficult words to a short audio clip.
• Ruby annotations: for East Asian languages, small characters above the main text show the pronunciation.
• Diacritics: in languages that usually omit vowel marks, they can be added for ambiguous words.

<ruby>漢字<rt>かんじ</rt></ruby>

Don’t confuse it with language markup: the lang attribute makes screen readers read foreign-language passages with the right pronunciation rules – that’s covered by Language of Parts. It doesn’t resolve ambiguity within one language.

Develop an editorial guideline:

• Decide when you provide pronunciation help.
• Define which form of pronunciation guidance you use.
• Mark critical terms consistently.

5. Why this criterion matters for businesses

3.1.6 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. For businesses, it matters most where misunderstandings have consequences.

1. Avoid misunderstandings

In instructions, contracts or event announcements, a misunderstood word can have real consequences. Unambiguous wording and pronunciation help prevent that.

2. Get names right

Beyond the criterion itself, pronunciation guidance for brand, product or personal names shows respect – and helps people talk about your brand correctly.

3. Better multilingual content

If you publish content in languages like Japanese, you can hardly avoid the topic. Pronunciation help makes that content accessible to learners, too.

This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 3.1.6 Pronunciation (Level AAA)

A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

In short: when the meaning of a word in context only becomes clear through its pronunciation, there must be a way to find out the correct pronunciation.