WCAG 2.2 Quick Reference

Every WCAG 2.2 success criterion translated into plain English, with a concrete example of how it typically fails, who it affects, and the ExceedAbility tools and services that address it. Australian-aligned. No signup, no paywall.

Use this page as the one-stop look-up when a criterion comes up in an audit, a design review, a procurement spec or a piece of writing. Each criterion has a stable URL anchor. Link to /wcag-quick-reference.html#sc-1-4-3 from anywhere on the site.

5 of 86 criteria fully populated. Remaining 81 coming soon.
Level
Principle
1.1.1

Non-text Content

Level A Perceivable Since WCAG 2.0
Plain English
Every image, icon, chart or other non-text element must have a text alternative that describes its purpose, so people who cannot see it (or whose tools cannot render it) still get the meaning.
Typical failure
Images uploaded to a CMS with no alt attribute, alt="image", alt="picture123.jpg", or decorative graphics that screen readers announce as "graphic, graphic, graphic" because alt="" was never set.
Affects
Visual Cognitive
At ExceedAbility

Authoritative source: W3C Understanding 1.1.1 ↗

1.4.3

Contrast (Minimum)

Level AA Perceivable Since WCAG 2.0
Plain English
Text and images of text must have a contrast ratio of at least 4.5:1 against their background (3:1 for large text). This lets people with low vision, colour-vision differences or older screens still read your content.
Typical failure
Light grey body text (#999) on white; pale brand-colour buttons with white labels; placeholder text in form fields rendered at 30% opacity.
Affects
Visual Cognitive
At ExceedAbility

Authoritative source: W3C Understanding 1.4.3 ↗

2.1.1

Keyboard

Level A Operable Since WCAG 2.0
Plain English
Everything a user can do with a mouse must also be possible using only a keyboard. Many people with physical, visual or temporary mobility issues navigate exclusively by keyboard, switch device or voice control that maps to keyboard input.
Typical failure
Custom dropdown menus that only open on hover; modal dialogs you can open by clicking but cannot close without the mouse; drag-and-drop interfaces with no keyboard equivalent.
Affects
Visual Physical
At ExceedAbility

Authoritative source: W3C Understanding 2.1.1 ↗

2.4.7

Focus Visible

Level AA Operable Since WCAG 2.0
Plain English
When something on the page receives keyboard focus, there must be a clear visual indicator showing which element is focused. Without it, keyboard users have no way to track where they are.
Typical failure
CSS that strips the default browser focus ring (outline: none) without providing a replacement; designer-supplied focus styles that meet the brand palette but disappear against busy backgrounds.
Affects
Visual Physical Cognitive
At ExceedAbility

Authoritative source: W3C Understanding 2.4.7 ↗

3.3.2

Labels or Instructions

Level A Understandable Since WCAG 2.0
Plain English
Form fields that need user input must have visible labels or instructions explaining what is expected. Placeholder text alone is not a label. It vanishes as soon as the user starts typing.
Typical failure
Search boxes labelled only with a magnifying-glass icon; checkout forms using placeholder text in lieu of labels; required-field markers shown only by red asterisks with no legend.
Affects
Visual Cognitive
At ExceedAbility

Authoritative source: W3C Understanding 3.3.2 ↗