WCAG 2.1 SC 3.1.4: Abbreviations (Level AAA)
3.1.4 Abbreviations (Level AAA) — what it requires, a common failure example, and how to fix it. Part of WCAG 2.1's 3.1 Readable guideline under the Understandable principle.
WCAG 2.1 guidelines hub → Understandable → 3.1 Readable
3.1.4 Abbreviations (Level AAA)
Readable is about making the language of your content programmatically identifiable, so screen readers pronounce it correctly and translation/reading tools work as intended. Most sites clear the Level A bar here with a single HTML attribute; the AAA criteria go further, into content clarity, that most sites won’t target.
This page is educational technical reference material, not legal advice. Meeting WCAG 2.1 does not by itself determine legal compliance with the ADA or any other law — consult qualified counsel for legal risk questions.
Plain-language explanation: Similar to 3.1.3, but specifically for abbreviations and acronyms — there should be a mechanism to find out what they stand for.
Common failure: Product pages are full of unexplained abbreviations (“OEM,” “UPC,” “MOQ”) with no expansion available anywhere.
Remediation: Use the HTML <abbr title="..."> element on first use, or link to a glossary that expands each abbreviation.
In this guideline — 3.1 Readable: 3.1.1 Language of Page (A) · 3.1.2 Language of Parts (AA) · 3.1.3 Unusual Words (AAA) · 3.1.4 Abbreviations (AAA) · 3.1.5 Reading Level (AAA) · 3.1.6 Pronunciation (AAA)
← Previous: 3.1.3 Unusual Words (AAA) · Next: 3.1.5 Reading Level (AAA) →
↑ Back to the Understandable overview · Full WCAG 2.1 wiki
See a sample report or check pricing — $890 one-time, $99/month for ongoing re-checks after fixes ship.
This page is educational content about technical accessibility practice, not legal advice. Meeting WCAG 2.1 does not guarantee legal compliance with the ADA or any other law. Consult qualified counsel for legal risk questions.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.