WCAG 3.1.4 — Abbreviations

What this requires

A mechanism is available for identifying the expanded form or meaning of abbreviations. The mechanism can be inline (an <abbr> element with title, an in-text expansion on first use), or external (a glossary listing the abbreviations used).

How AI coding tools fail this

When asked to "write the docs page", AI tools use abbreviations freely — SDK, CLI, MFA, API, SSR — without ever expanding them. The content reads naturally to a developer audience and is unparseable to anyone outside it.

The second pattern: <abbr> with no title attribute. The semantic element is in place; the expansion isn't there to be revealed.

The third: expanding on first use but then using the abbreviation inconsistently. Some readers arrive on page 3 of the docs without ever seeing page 1 where the expansion lives.

Failing examples

Industry abbreviations with no expansion:

<p>
  Configure your SSO IdP to point at the IAM endpoint exposed by the SDK.
</p>

<abbr> with no expansion:

<p>
  Configure your <abbr>SSO</abbr> provider.
</p>

Passing examples

Expand on first use:

<p>
  Configure your <abbr title="Single Sign-On">SSO</abbr> identity
  provider (<abbr title="Identity Provider">IdP</abbr>) to point at
  the <abbr title="Identity and Access Management">IAM</abbr>{" "}
  endpoint exposed by the{" "}
  <abbr title="Software Development Kit">SDK</abbr>.
</p>

Or inline expansion without <abbr>:

<p>
  Configure your Single Sign-On (SSO) identity provider to point at
  the Identity and Access Management (IAM) endpoint exposed by the
  Software Development Kit (SDK).
</p>

Edge cases

<abbr title="..."> is the markup; the title attribute carries the expansion. Screen readers handle this well.
First-use expansion + linked glossary covers most cases without cluttering subsequent uses.
Common abbreviations (HTML, USA, NASA) generally don't need expansion — they're treated as words.
Mobile and keyboard users don't get the title tooltip. The in-text expansion is more reliable.
Internal jargon abbreviations (a company's own acronyms) need the most aggressive expansion — readers won't know them at all.

How Jeikin handles this

The scanner finds candidate abbreviations (all-caps tokens of 2-5 characters) and surfaces them to the reviewer with a note about whether they're expanded elsewhere on the page. The dashboard tracks abbreviation usage and glossary coverage. The decision per term is editorial.