WCAG 3.1.4: Abbreviations
Every industry writes in shorthand — and every reader outside it pays the price. This criterion asks that a mechanism be available to find the expanded form or meaning of every abbreviation: spell it out on first use, mark it up with <abbr>, or link it to a glossary. “SC 1.4.3 re AA conformance per EN 301 549” should never be a sentence a reader has to decode alone.
The success criterion, in full
A mechanism for identifying the expanded form or meaning of abbreviations is available.
“Abbreviation” is a defined term: a shortened form of a word, phrase, or name where the shortened form has not become part of the language. Acronyms, initialisms, and truncations are in scope; words like “laser” that outgrew their origins are not. “Expanded form or meaning” matters too — for something like “e.g.”, the useful mechanism gives the meaning (“for example”), not the Latin expansion.
Who this helps and why
An unexpanded abbreviation is a small locked box in the middle of a sentence. Some readers can force it open from context; many cannot, and for a few groups the box is effectively welded shut.
People with cognitive disabilities
Decoding an abbreviation requires recalling or reconstructing its expansion — a working-memory task that an inline expansion removes entirely.
Screen reader listeners
Synthesizers guess: some spell 'NASA' letter by letter, others pronounce 'SC' as 'sc'. Hearing an expansion once anchors every later occurrence.
Non-native speakers
Abbreviations are language- and culture-bound. 'IRS', 'NHS', and 'GEZ' each mean nothing outside their country; the expansion travels, the initials do not.
Newcomers to any field
Onboarding docs, medical results, legal notices, government forms — the reader who most needs the content is precisely the one who does not know its shorthand yet.
Conforming mechanisms, strongest first
1. Expand at first use (G97)
Write the full form with the abbreviation in parentheses the first time it appears: 'Web Content Accessibility Guidelines (WCAG)'. Visible to every user, in every browser, with every input method. This should be your default.
2. Link to a glossary or abbreviation list (G55/G62)
Each abbreviation links to its entry in a glossary on the same page or a dedicated page. Scales across a whole site, works for readers landing mid-document, and doubles as the 3.1.3 definitions mechanism.
3. The abbr element (H28)
<abbr title="…"> attaches the expansion in markup. Semantically correct and a recognized technique — but title tooltips are hover-only and inconsistently announced by screen readers, so use it to supplement the first two mechanisms rather than replace them.
Whichever you choose, consistency is part of the mechanism: after expanding “service level agreement (SLA)”, keep writing “SLA” — do not alternate between the abbreviation, the full form, and a second abbreviation for the same thing.
Code examples
First-use expansion, then abbr for later mentions
The belt-and-braces pattern: visible expansion once, semantic markup afterwards so the expansion stays attached everywhere.
<!-- ✗ Shorthand with no way in -->
<p>Your SLA guarantees 99.9% uptime. SLA credits apply below that.</p>
<!-- ✓ Expanded at first use; <abbr> carries it afterwards -->
<p>
Your service level agreement (<abbr>SLA</abbr>) guarantees
99.9% uptime.
<abbr title="service level agreement">SLA</abbr> credits
apply below that.
</p>Link abbreviations to a glossary
For document sets full of shorthand — specs, legal, medical — a linked abbreviation list is reachable from any entry point, not just the first paragraph.
<!-- ✓ In the running text -->
<p>
Public-sector sites must meet
<a href="/glossary#en301549"><abbr>EN 301 549</abbr></a>
via <a href="/glossary#wcag"><abbr>WCAG</abbr></a> 2.2 AA.
</p>
<!-- ✓ On the glossary page -->
<dl>
<dt id="wcag">WCAG</dt>
<dd>Web Content Accessibility Guidelines — the W3C standard
for accessible web content.</dd>
<dt id="en301549">EN 301 549</dt>
<dd>The European standard for ICT accessibility that
incorporates WCAG for web content.</dd>
</dl>Give the meaning when the expansion doesn’t help
The criterion says expanded form or meaning. For Latin truncations and lexicalized forms, the meaning is the useful thing — or skip the abbreviation entirely.
<!-- ✓ Meaning, not the unhelpful Latin expansion -->
<p>Bring photo ID (<abbr title="for example">e.g.</abbr>,
a passport or driving licence).</p>
<!-- ✓ Better still for plain language: no abbreviation at all -->
<p>Bring photo ID — for example, a passport or driving licence.</p>Common failures
- Abbreviations used throughout a page with no expansion, no glossary, and no abbr markup anywhere.
- Relying solely on <abbr title> tooltips — hover-only, unreachable by keyboard and touch, inconsistently announced by screen readers.
- Expanding on first use in a long document, then assuming readers who arrive mid-page via search or a fragment link saw it.
- Internal shorthand and product codenames ('the CSAT flow', 'PDP page') published to external audiences undefined.
- Inconsistent forms for the same thing — alternating 'SC', 'success criterion', and 'criterion' — so the first-use expansion never attaches to later mentions.
- A glossary that exists but is not linked from the content, or is missing the abbreviations the content actually uses.
- Ambiguous abbreviations with multiple readings ('Dr.' as Doctor or Drive, 'St.' as Saint or Street) left for the reader to disambiguate.
How to test for 3.1.4
- 1
List every abbreviation on the page
Scan for capital-letter clusters, truncations with periods, and unit-like shorthand. A regex pass (e.g. \b[A-Z]{2,}\b) over the content catches most candidates; a human pass catches 'Dr.', 'approx.', and friends.
- 2
Exclude only true dictionary words and names
Strike lexicalized forms (laser, scuba) and letters that are the actual name. Everything else — however famous — stays on the list for the mechanism check.
- 3
Verify a mechanism for each
For every remaining abbreviation confirm one of: expansion at first use, a link to a glossary entry containing it, or abbr markup — and that the expansion given is correct for this context.
- 4
Test the mechanism without a mouse
Reach every expansion by keyboard and on a touch screen. If the only route is a title-attribute hover tooltip, the mechanism fails real users even where it technically conforms — upgrade it.
- 5
Listen with a screen reader
Have NVDA or VoiceOver read the content. Note how each abbreviation is announced and confirm a user who mishears it can still reach the expansion through the visible mechanism.
Relationship to 3.1.3 and 3.1.5
Guideline 3.1 Readable builds up from 3.1.1 Language of Page (Level A — declare the language so text is pronounced correctly) to a trio of AAA comprehension criteria. 3.1.3 Unusual Words handles meaning: jargon, idioms, and restricted senses need definitions. 3.1.4 handles form: shortened forms need expansions. 3.1.5 Reading Level handles the text as a whole: unavoidably complex writing needs a supplement or simpler version.
They chain naturally: expand “ARIA” to “Accessible Rich Internet Applications” (3.1.4), and a newcomer may still need to know what that is (3.1.3), explained in words they can read (3.1.5). One well-maintained glossary, linked from content, is the cheapest way to serve all three at once.
Frequently asked questions
What does WCAG 3.1.4 Abbreviations require?
It requires that a mechanism for identifying the expanded form or meaning of abbreviations is available. Whenever content uses a shortened form — an acronym like NASA, an initialism like HTML, or a truncation like 'Dr.' — the reader must have a way to discover what it stands for or what it means: an expansion at first use, an <abbr> element, a link to a glossary, or a definition list. It is a Level AAA success criterion under Guideline 3.1 Readable, introduced in WCAG 2.0.
What counts as an abbreviation under WCAG?
WCAG defines an abbreviation as a shortened form of a word, phrase, or name where the abbreviation has not become part of the language. That includes initialisms (HTML, GDP), acronyms (NASA, WYSIWYG), and truncations (etc., approx., Dr.). It excludes shortened forms that are now ordinary words in their own right — 'laser' and 'scuba' began as acronyms but are dictionary words today — and names where the letters are the actual name rather than a shortening the organization still uses in full.
Is the abbr element with a title attribute enough to pass 3.1.4?
It is a recognized W3C technique (H28), so it can conform — but it is the weakest mechanism on its own. The title attribute's expansion is only exposed on mouse hover in most browsers: keyboard users can't trigger it, touch users can't hover, and screen readers vary in whether they announce it (many require a setting to be enabled). Treat <abbr title="…"> as a useful semantic supplement, and pair it with a robust primary mechanism: expanding the abbreviation in text at first use, or linking it to a glossary entry.
Does expanding an abbreviation the first time it appears satisfy the criterion?
Yes — providing the expanded form immediately before or after the first occurrence ('Web Content Accessibility Guidelines (WCAG)') is the classic conforming technique (G97), and it is also just good writing. Two caveats from the understanding guidance: the abbreviation should be used consistently after that, and in contexts where users may land mid-document or content is re-ordered (search results, syndicated fragments), a glossary or <abbr> on later instances makes the expansion reachable from anywhere, not only from the top of the page.
Do I need to expand extremely common abbreviations like HTML or USA?
The criterion has no popularity exception — the exemption is only for shortened forms that have become words in the language (laser, scuba) or letters that are the actual name. In practice, audience matters for risk judgment: 'HTML' unexpanded on a developer-tools site will trouble no one, while the same letters on a beginners' course page deserve expansion. Since the cost of a first-use expansion or glossary link is near zero, the safe pattern is to expand everything once and let familiar readers skim past it.
How does 3.1.4 relate to 3.1.3 Unusual Words?
They are adjacent AAA criteria under Guideline 3.1 Readable, splitting the vocabulary problem. 3.1.4 covers shortened forms: the reader needs the expansion ('SLA' → 'service level agreement'). 3.1.3 covers meaning: the reader needs a definition of jargon, idioms, and words used in restricted senses. Note they often chain: expanding 'SLA' to 'service level agreement' satisfies 3.1.4, but if the reader still doesn't know what a service level agreement is, a 3.1.3-style definition finishes the job. A single glossary that gives expansion plus definition serves both.
Related Success Criteria
The default human language of each page can be programmatically determined.
The human language of each passage can be programmatically determined.
A mechanism is available for identifying specific definitions of words.
Text requires reading ability no higher than lower secondary education level.
A mechanism is available for identifying pronunciation of words.