Missing explanation of unusual words (AAA)
manual/unusual-words
- WCAG success criterion
- 3.1.3 (level AAA)
- Outcome class
- Manual. A tool cannot decide this check. The audit only points a person at it; it is never counted as automatically verified.
- Area
- Accessibility, Language & Clarity
- Default severity
- low
- axe-core rule
unusual-words
Why we flag this
Users with cognitive impairments or non-native speakers do not understand the text.
Missing glossary linkage or in-text explanation.
What the rule checks
Scope. Pages with any visible text (text outside title, script, style, noscript).
Expectation. One needs_review (UNTESTED) note per page, at the root, on every page with text; never pass or violation. A page without any text (an image with alt only) gets no note.
Why a person has to decide. Whether a word is jargon or an idiom, and whether it is explained, is a judgement about language no detector makes.
Source. WCAG 2.2 SC 3.1.3 Unusual Words (AAA)
Detection: shared; needs dom.
Failing example
The check flags this for review. Corpus case interaction_static_text. The page may contain further findings for other rules.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Club rules</title>
<style>
body { font-family: sans-serif; margin: 0; padding: 16px; color: #111; background: #fff; }
a, button, input { display: inline-block; min-width: 44px; min-height: 44px; padding: 12px; box-sizing: border-box; margin: 4px; }
.skip { position: absolute; left: -9999px; }
.skip:focus { left: 16px; }
</style>
</head>
<body>
<header><p>Example Club</p></header>
<main>
<h1>Club rules</h1>
<p>Members pay their fee by the end of January.</p>
<p>Guests are welcome on Sundays.</p>
<p>The clubhouse closes at ten in the evening.</p>
</main>
<footer><p>Example Club footer</p></footer>
</body>
</html>This page is generated from the rule catalogue and the rule contracts; see therule overview for how the outcome classes are derived.