Abbreviations
Summary:
WCAG 3.1.4, "Abbreviations," focuses on helping users understand abbreviations commonly found in web content. This guideline is particularly useful for people who are not familiar with these shortened forms, including those with cognitive disabilities or users who are non-native speakers of the page's language.
What:
This criterion requires that a mechanism is provided for identifying the expanded form or meaning of abbreviations.
Why:
Abbreviations can be confusing or misleading for many users. Providing their full forms or explanations ensures that all users, regardless of their background or abilities, can comprehend the content.
Examples and Scenarios:
- Academic Texts: Expanding abbreviations like 'e.g.' to 'for example' aids understanding.
- Technical Articles: Explaining industry-specific abbreviations, such as 'UI' for 'User Interface.'
- Medical Content: Providing meanings for medical abbreviations like 'BP' for 'Blood Pressure.'
How to Comply:
- Websites: Use HTML techniques to provide the expanded form of abbreviations or include a glossary.
- Mobile Apps: Offer tooltips or links to explanations for abbreviations.
- Software Applications: Ensure that any abbreviations used within the interface are accompanied by their full forms or definitions, accessible to the user.
Exceptions:
- Commonly Known Abbreviations: If an abbreviation is widely known and understood by the target audience, like 'USA' for 'United States of America.'
- Technical Constraints: In some cases, technical constraints might limit the ability to provide expansions for all abbreviations, especially in dynamically generated content.