Level AAA

Abbreviations without an expansion mechanism break comprehension for readers who do not already know the term -- screen readers may pronounce acronyms as words, hiding the meaning entirely

3.1.4 Abbreviations

In Plain Language

WCAG 2.2 Success Criterion 3.1.4 Abbreviations (Level AAA) requires a mechanism for identifying the expanded form or meaning of every abbreviation -- acronyms like WCAG, initialisms like HTML, and shortened forms of longer words[1]. Without that mechanism, readers who do not already know the term have no way to recover the meaning from the page alone.

The HTML mechanism is <abbr title="Hypertext Markup Language">HTML</abbr>: the title attribute exposes the expansion programmatically, screen readers can announce it on demand, and browsers render it as a tooltip on mouse hover. Equivalent mechanisms: expand the abbreviation in parentheses on first use ("Web Content Accessibility Guidelines (WCAG)..."), link the abbreviation to a glossary entry, or mark the defining instance with <dfn>.

Why It Matters

  • Readers with cognitive and learning disabilities, non-native readers, and users new to a domain hit an unfamiliar acronym and have no in-page path to its meaning -- comprehension stops until they search elsewhere or give up.
  • Screen readers pronounce short acronyms as words when the letter sequence is pronounceable: WCAG becomes "wuh-cag", ARIA becomes "ar-ee-uh", SCOTUS becomes "skoh-tus". Without an <abbr title> or a parenthetical expansion, the expanded form is never available to the assistive technology.
  • Initialisms that are not pronounceable get spelled out letter by letter -- V-P-A-T, I-C-T, S-C -- which is phonetically correct but semantically empty for a reader who does not already know the acronym.
  • Government, legal, and technical content is dense with domain abbreviations. When none are expanded, the page is readable only by insiders; everyone else must keep a second tab open to a dictionary or glossary.

Examples

Do: Expand abbreviation on first use with abbr element

The WCAG (Web Content Accessibility Guidelines) define how to make web content more accessible.

✔ Abbreviation expanded on first use and marked with abbr element

<p>The <abbr title="Web Content Accessibility
  Guidelines">WCAG</abbr> (Web Content Accessibility
  Guidelines) define how to make web content
  more accessible.</p>
Don't: Abbreviations with no expansion mechanism

Check the VPAT for SC conformance before the ICT deadline.

✘ VPAT, SC, and ICT are never expanded -- readers must already know these abbreviations

<!-- FAILS: no mechanism to identify VPAT, SC, or ICT -->
<p>Check the VPAT for SC conformance before
  the ICT deadline.</p>
Do: Link abbreviations to a definitions section

Submit your VPAT to demonstrate ICT conformance.

VPAT
Voluntary Product Accessibility Template
ICT
Information and Communications Technology

✔ Each abbreviation links to its definition -- users can look up any term

<p>Submit your <a href="#def-vpat">VPAT</a>
  to demonstrate <a href="#def-ict">ICT</a>
  conformance.</p>

<dl>
  <dt id="def-vpat">VPAT</dt>
  <dd>Voluntary Product Accessibility Template</dd>
  <dt id="def-ict">ICT</dt>
  <dd>Information and Communications Technology</dd>
</dl>
Do: Parenthetical expansion on first use

The Americans with Disabilities Act (ADA) applies to state and local government websites. The ADA requires nondiscriminatory access to services delivered online.

✔ ADA is expanded on first use -- subsequent uses can use the abbreviation alone

<p>The Americans with Disabilities Act (ADA)
  applies to state and local government websites.
  The ADA requires nondiscriminatory access to services
  delivered online.</p>

How to Fix It

  1. Expand on first use. Write the full term followed by the abbreviation in parentheses the first time it appears on a page -- "Web Content Accessibility Guidelines (WCAG)" -- then use the short form for the rest of the page. This mechanism is keyboard-, touch-, and screen-reader-accessible with no extra markup.
  2. Use <abbr title="..."> to expose the expansion programmatically. The title attribute makes the expanded form available to assistive technology on demand and to mouse users as a tooltip. Do not rely on <abbr> alone: the title tooltip is mouse-only by default, so pair it with a first-use parenthetical expansion so keyboard and touch users also see the full term.
  3. Link abbreviations to a glossary. For pages with many domain-specific acronyms, build a definitions list (<dl> with <dt>/<dd>) and link each acronym to its entry. One definition, many references -- this scales better than inline expansion on a page with dozens of terms.
  4. Mark the defining instance with <dfn>. When a page introduces a term, wrap the defining occurrence in <dfn> so the relationship between the term and its definition is exposed in the accessibility tree.
  5. Be consistent across the page. Pick a mechanism (inline expansion, <abbr title>, or glossary link) and apply it to every abbreviation. Expanding some and leaving others unexplained is the most common 3.1.4 failure mode -- the reader who needed help on the expanded ones will be stuck on the skipped ones.
  6. Do not assume insider knowledge. HTML, CSS, API, and URL look obvious to a developer and opaque to a policy analyst or content author reviewing the same page. Expand them on first use anyway -- the cost is a few words; the benefit is a page that works for readers outside your discipline.

References

  1. [1] W3C (2023). Understanding Success Criterion 3.1.4: Abbreviations. W3C, Accessed 2026-04-07. https://www.w3.org/WAI/WCAG22/Understanding/abbreviations.html ↩