Loading...
Loading content...
Loading content...
Explain idioms, jargon, and unusual words.
Why it matters: Helps users with cognitive disabilities understand complex language.
A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.
What This Means: This success criterion requires that words or phrases used in unusual or restricted ways (including idioms, jargon, and technical terms) have definitions or explanations available. Users should be able to access these definitions to understand the content.
Why It's Important: Users with cognitive disabilities, non-native speakers, and those unfamiliar with specialized terminology may struggle to understand content that uses unusual words, idioms, or jargon. Providing definitions helps ensure that all users can understand the content, regardless of their background or cognitive abilities.
Use <dfn> elements for defined terms, <abbr> elements with title attributes for abbreviations, tooltips for inline definitions, or links to glossaries. Provide definitions on first use of unusual terms. Idioms should be explained or rephrased in plain language. Technical terms should have clear explanations accessible to users.
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.
This criterion ensures that non-native speakers 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.
Technical jargon is used without explanation, making content hard to understand.
<p>The API uses RESTful endpoints for CRUD operations.</p>Technical terms are linked to definitions or explained inline.
<p>The API uses <dfn>RESTful</dfn> endpoints for <abbr title="Create, Read, Update, Delete">CRUD</abbr> operations.</p>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.1.3 Unusual Words 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:
If it's a common technical term in my field, I don't need to explain it.
What's common in your field may not be common to your users. Explain technical terms or provide definitions.
Idioms are fine - everyone understands them.
Idioms can be confusing for non-native speakers and users with cognitive disabilities. Explain or rephrase them.
Technical jargon without explanations.
Provide definitions using <dfn> elements, tooltips, or glossary links. Explain terms on first use.
Idioms used without explanation.
Rephrase idioms in plain language, or provide explanations. Example: Instead of 'hit the nail on the head', use 'exactly right'.
Definitions that are hidden or hard to find.
Make definitions easily accessible. Use visible tooltips, inline explanations, or clearly labeled glossary links.
Note: These are official W3C resources for 3.1.3. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.1.3 Unusual Words 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