WCAG 2.2 Example Library

Equivalent text lets screen reader users understand non-text content.

Users who cannot hear or see the media still need access to the same information.

Captions make prerecorded audio content available to deaf and hard-of-hearing users.

Critical visual information must be available to people who cannot see the video.

Live captions are needed for real-time access to spoken information.

Users who cannot see the video need access to important visual-only content.

Some users rely on sign language rather than captions for full comprehension.

Some visuals require more time to describe than natural pauses allow.

A full text alternative provides equivalent access without requiring video playback.

Users need another way to access live audio-only content.

Relationships shown visually must also be exposed in the markup.

Meaningful sequence must survive CSS changes and assistive technology reading order.

Users may not perceive color, shape, or spatial references the same way.

Users may mount devices or depend on a fixed orientation.

Identifying input purpose supports personalization and autofill tools.

AAA asks for programmatic identification of broader UI purpose, not just input purpose.

Color alone cannot be the only cue for meaning or status.

Unexpected audio interferes with screen readers and concentration.

Minimum contrast supports readability for many low-vision users.

Users must be able to resize text without losing access or meaning.

Text in images is harder to resize, translate, and adapt.

AAA enhanced contrast further improves readability for low-vision users.

Competing background audio makes speech harder to understand.

AAA visual presentation supports sustained reading comfort and comprehension.

AAA removes most exceptions for images of text.

Users should not need two-dimensional scrolling for ordinary content.

Non-text UI components still need sufficient visual distinction.

Users often override spacing to improve readability.

Users need enough control to read and interact with revealed content.

Keyboard access is foundational for many assistive technology users.

Keyboard users must never get trapped inside a control.

AAA removes exceptions for keyboard operation.

Character shortcuts often conflict with speech input and assistive tech.

People need different amounts of time to read, understand, and respond.

Moving content can distract users and interfere with reading.

AAA expects timing to be unnecessary unless it is essential to the activity.

Unexpected interruptions can derail users with cognitive or attention-related disabilities.

Re-authentication should not force users to redo their work.

Users need notice when inactivity could cause data loss.

Rapid flashing can trigger seizures in susceptible users.

AAA requires stricter avoidance of flashing content.

Motion can cause dizziness or nausea for vestibular disorders.

Repeated blocks should be easy to bypass.

Descriptive titles help users orient and navigate browser tabs and history.

Predictable focus order preserves meaning and usability.

Users should understand link purpose before activating it.

Multiple ways help users locate content efficiently.

Good labels reduce ambiguity and scanning effort.

Users need to know where keyboard focus currently is.

AAA location cues help users stay oriented in complex systems.

AAA expects link meaning to stand on its own without surrounding context.

Section headings support scanning, navigation, and comprehension.

Focused controls must remain at least partially visible.

Enhanced focus visibility requires the whole focused component to remain visible.

AAA defines stronger focus appearance requirements to improve detectability.

Complex gestures need a simpler alternative.

Pointer cancellation helps users avoid accidental activation.

Speech input users rely on visible labels matching spoken commands.

Motion-based input needs a conventional alternative.

Larger targets reduce accidental activation and improve motor accessibility.

Content should not block available input methods without an essential reason.

Dragging motions need a simpler single-pointer alternative.

Minimum target size improves touch and pointer accuracy.

Language metadata helps assistive technologies choose pronunciation rules.

Language changes within content should be programmatically identified.

AAA helps users understand uncommon terminology.

Users should be able to identify the full meaning of abbreviations.

AAA supports users who benefit from easier reading levels.

Pronunciation cues can prevent misunderstanding when meaning depends on spoken form.

Focus should not surprise users by changing the interface.

Input changes should not unexpectedly shift context.

Consistency reduces relearning and navigation cost.

Consistent identification helps users build reliable expectations.

AAA favors user-initiated changes over automatic ones.

WCAG 2.2 adds consistency requirements for repeated help mechanisms.

Users need explicit text describing what went wrong.

Users need persistent guidance on what information is required.

Helpful correction suggestions reduce frustration and rework.

Important commitments and data changes need error prevention.

AAA help supports users during data entry and decision-making.

AAA extends submission error prevention to all user-provided information.

WCAG 2.2 reduces unnecessary memory and typing burden.

Authentication should not depend on memory, transcription, or puzzle solving alone.

AAA further reduces cognitive barriers during authentication.

Assistive technologies rely on machine-readable control semantics.

Users need important status updates even when focus stays put.