Loading...
Loading content...
Loading content...
Provide pronunciation for ambiguous words (e.g., 'desert' vs 'desert').
Why it matters: Screen readers may mispronounce words, changing the meaning.
A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
What This Means: This success criterion requires that words with ambiguous pronunciation (words that can be pronounced differently with different meanings, like 'desert' vs 'desert', 'record' vs 'record') have pronunciation guidance available. This helps screen readers pronounce them correctly and prevents misunderstanding.
Why It's Important: Screen readers may mispronounce words with multiple possible pronunciations, which can change the meaning and make content confusing or incorrect. For example, 'I live in the desert' could be misunderstood if 'desert' is pronounced as 'de-ZERT' (to abandon) instead of 'DEZ-ert' (dry area). Providing pronunciation guidance ensures screen readers pronounce words correctly.
Use title attributes, phonetic spelling, or IPA (International Phonetic Alphabet) notation to provide pronunciation. For example: <span title='pronounced: DEZ-ert'>desert</span> or using IPA: <span title='IPA: /ˈdezərt/'>desert</span>. Only words where meaning is ambiguous without pronunciation need guidance. Common words with clear pronunciation don't require it.
This criterion ensures that screen reader users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
A word with multiple pronunciations is used without guidance.
<p>I live in the desert.</p>Pronunciation is provided using phonetic spelling or IPA.
<p>I live in the <span title="pronounced: DEZ-ert">desert</span>.</p>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.1.6 Pronunciation are met. Check off items as you complete them.
To meet this success criterion, ensure the following requirements are met:
While meeting the minimum requirements ensures compliance, consider these enhancements for a better user experience:
Screen readers will figure out the pronunciation from context.
Screen readers may mispronounce ambiguous words, changing the meaning. Provide explicit pronunciation guidance for clarity.
I need to provide pronunciation for every word.
Only words where meaning is ambiguous without pronunciation need guidance. Common words with clear pronunciation don't need it.
Ambiguous words without pronunciation guidance.
Add pronunciation using title attributes, phonetic spelling, or IPA notation. Example: <span title='pronounced: DEZ-ert'>desert</span>.
Pronunciation guidance that's not accessible to screen readers.
Use title attributes or visible text for pronunciation. Ensure screen readers can access the guidance.
Inconsistent or unclear pronunciation notation.
Use standard notation consistently. Consider using phonetic spelling (DEZ-ert) or IPA notation (/ˈdezərt/).
Note: These are official W3C resources for 3.1.6. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.1.6 Pronunciation correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Understandable PrincipleGuideline
3.1 Readable