SERIES 01 / WEB FOR EVERYONE
Web accessibility
Standards for a web everyone can use. Understand each criterion in depth and learn how to evaluate it with AI.
Learning order
Getting started
Begin with the perspective and evaluation method.
- 01Getting Started with Web Accessibility: How to Design Evaluations with WCAG and AI
Understand accessibility issues within users’ workflows, and use WCAG 2.2 and multimodal AI to design an evaluation scope and an evidence collection plan.
A perceivable web
Perceive information visually, aurally and in other forms.
- 02Alternative Text: Conveying What an Image Does
Design alternatives that explain an image’s purpose and context rather than merely its presence.
- 03Prerecorded Audio and Silent Video: Getting the Same Information Another Way
Distinguish the alternatives needed for audio-only and video-only content.
- 04Prerecorded Captions: Conveying Dialogue and Important Sounds
Evaluate the presence, accuracy, speaker identification, and synchronization of captions.
- 05Audio Description and Media Alternatives: Explaining Information Visible Only in Video
Convey visual information in prerecorded video through description or a sufficient alternative.
- 06Live Captions: Keeping Up with Information in Live Broadcasts
Explore how to check captions for live synchronized media.
- 07Prerecorded Audio Description: Making Essential Visual Information Audible
Review the audio description of visual information required at AA.
- 08Sign Language Interpretation: Another Language Path for Prerecorded Audio
Distinguish the availability of sign language interpretation from the language expertise needed to evaluate it.
- 09Extended Audio Description: Pausing Scenes to Make Time for Explanation
Examine whether extended description is needed for videos with insufficient pauses between speech.
- 10Complete Media Alternatives: Following the Entire Video in a Document
Review complete alternatives for prerecorded synchronized media and video-only content.
- 11Live Audio Alternatives: Receiving Information Without Hearing It
Prepare equivalent alternatives for live audio-only information.
- 12Information and Relationships: Conveying Visual Structure in Code
Convey the relationships in headings, lists, tables, and forms to assistive technologies.
- 13Meaningful Sequence: Aligning Visual Order and Reading Order
Evaluate reading order that preserves the meaning of information.
- 14Sensory Instructions: Going Beyond “On the Right” or “In Red”
Improve instructions that rely on shape, color, location, or sound.
- 15Screen Orientation: Supporting Both Landscape and Portrait
Check for orientation restrictions that are not essential.
- 16Input Purpose: Creating Fields That Autocomplete Can Recognize
Make the purpose of fields collecting users’ personal information identifiable in code.
- 17Element Purpose: Enabling UI Adaptation to Users’ Needs
Explore the AAA criterion for identifying the purpose of controls, icons, and regions.
- 18Color: Not the Only Cue for Information
Convey states and distinctions through means other than color as well.
- 19Automatically Playing Audio: Making It Possible to Stop and Adjust
Check the means of controlling audio that plays automatically for more than 3 seconds.
- 20Text Contrast: Ensuring Readable Luminance Differences
Calculate contrast for normal and large text according to the applicable conditions.
- 21Resizing Text: Preserving Functionality at 200%
Check whether enlarging text causes any loss of content or functionality.
- 22Images of Text: Providing Actual Text
Provide adjustable text instead of text embedded in images.
- 23Enhanced Text Contrast: A Higher Readability Target
Apply AAA contrast targets to normal and large text.
- 24Background Audio: Keeping Speech Clear
Review background audio in prerecorded audio-only content.
- 25Text Presentation: Letting Users Choose How They Read
Address line length, line spacing, alignment, and color adjustment together.
- 26Stricter Requirements for Images of Text
Examine when images of text are permitted at AAA.
- 27Reflow: Reading and Operating Content on Narrow Screens
Reduce two-dimensional scrolling when zooming and using small viewports.
- 28Non-Text Contrast: Distinguishing Controls and Shapes
Evaluate luminance differences in controls and graphics that convey information.
- 29Text Spacing: Preserving Content When Reading Settings Change
Create interfaces that accommodate changes to letter, word, line, and paragraph spacing.
- 30Content on Hover or Focus: Making It Dismissible, Hoverable, and Readable
Check whether tooltips and popovers meet the conditions for dismissal, pointer movement, and persistence.
An operable web
Reduce barriers involving keyboards, pointers, time and navigation.
- 31Keyboard: Performing Key Functions Without a Pointer
Check whether functionality can be operated with a keyboard in actual user flows.
- 32Keyboard Traps: Being Able to Leave Where You Entered
Check the paths for moving focus out of widgets and dialogs.
- 33Keyboard Support Without Exceptions: Extending to the AAA Target
Evaluate keyboard operation of all functionality under stricter requirements.
- 34Character Key Shortcuts: Preventing Unintended Activation
Check options for disabling or remapping single-character shortcuts and restricting when they are active.
- 35Adjustable Timing: Allowing Time to Read and Enter Information
Evaluate options for turning off, adjusting, or extending time limits, along with the exceptions.
- 36Movement and Automatic Updates: Pausing to Read
Check the means of stopping automatic movement and updates.
- 37Time-Independent Tasks: Completing Them Without Rushing
Check whether functionality can be completed without time limits at AAA.
- 38Interruptions: Deferring Notifications to Stay Focused
Allow users to control interruptions except in emergencies.
- 39Re-authentication: Avoiding the Loss of Entered Content
Preserve data and progress during re-authentication after a session expires.
- 40Timeout Warnings: Explaining Limits Before Data Entry
Inform users how long they can remain inactive before their data may be lost.
- 41Flashing: Quantitatively Checking Hazardous Visual Stimuli
Distinguish flash-count evaluation from evaluation against general and red flash thresholds.
- 42Three Flashes: The Stricter AAA Requirement
Review the AAA requirement for the number of flashes per second.
- 43Animation from Interactions: Offering a Choice to Reduce Motion
Check whether motion triggered by interaction can be disabled.
- 44Bypassing Repeated Blocks: Reaching Main Content Quickly
Check the paths for bypassing repeated navigation.
- 45Page Titles: Identifying the Content Currently Open
Review whether document titles describe the topic and purpose.
- 46Focus Order: Preserving Meaning Through Interaction
Evaluate whether keyboard navigation order preserves the relationships between information and functionality.
- 47Link Purpose in Context: Knowing Where a Link Leads
Evaluate link purpose using both the link and its programmatically associated context.
- 48Multiple Ways to Navigate: Reaching the Page You Need
Check for multiple paths to find pages within a site.
- 49Headings and Labels: Accurately Describing Content and Purpose
Evaluate whether existing headings and labels use meaningful wording.
- 50Visible Focus: Showing the Current Interaction Location
Check the visual indication of keyboard focus in actual interface states.
- 51Current Location: Providing Context Within a Site
Review information that indicates where the current page belongs within the site.
- 52Conveying Purpose Through the Link Alone: The AAA Requirement
Review the means of identifying a link’s purpose without context.
- 53Section Headings: Dividing Long Content for Navigation
Explore the AAA criterion for organizing documents with headings by topic.
- 54Obscured Focus: Keeping at Least Part of the Target Visible
Evaluate whether fixed elements completely obscure the focused target at AA.
- 55Enhanced Requirements for Unobscured Focus: Showing the Entire Target
Evaluate even partial obscuring of the focused target at AAA.
- 56Focus Appearance: Providing Sufficient Area and Contrast
Measure the area and contrast between states of AAA focus indicators.
- 57Pointer Gestures: Providing Alternatives to Complex Actions
Check for simple-operation alternatives to multipoint and path-based gestures.
- 58Pointer Cancellation: Undoing Unintended Actions
Review the timing of press and release events and the means of canceling or undoing actions.
- 59Aligning Visible Labels and Accessible Names
Enable users to find targets by their on-screen labels when using voice control.
- 60Motion Actuation: Operating Without Shaking the Device
Check UI alternatives and disabling options for functionality based on device motion.
- 61Target Size: Generous Touch Areas at AAA
Review the enhanced target of 44×44 CSS px and its exceptions.
- 62Concurrent Input Methods: Using Touch and Keyboard Together
Check whether using one input method restricts the use of another.
- 63Dragging: Getting the Same Result Without Dragging
Evaluate single-pointer alternatives to dragging functionality.
- 64Target Size: AA Size and Spacing Conditions
Evaluate the 24×24 CSS px requirement and exceptions, including spacing, according to their conditions.
An understandable web
Predictable behavior, input and authentication.
- 65Page Language: The Starting Point for Correct Pronunciation
Make the document’s default language programmatically identifiable.
- 66Language of Parts: Marking Passages Where the Language Changes
Mark passages in other languages within the body text according to their meaning and the applicable exceptions.
- 67Unfamiliar Words: Providing a Way to Find Their Meaning
Review ways to explain technical terms and specialized usage.
- 68Abbreviations: Accessing Their Expanded Forms and Meanings
Make it possible to check the expanded forms or meanings of abbreviations.
- 69Reading Level: Creating Alternatives to Complex Explanations
Provide easy-to-understand supplementary options for difficult text.
- 70Pronunciation: Explaining Readings That Change Meaning
Provide a way to check expressions whose meanings differ depending on pronunciation.
- 71Avoiding Interface Changes Triggered by Focus Alone
Check whether merely entering an element causes a change of context.
- 72Input Changes: Explaining What Will Happen in Advance
Review advance notice of context changes caused by changing a setting.
- 73Consistent Navigation: The Same Paths in the Same Order
Maintain the relative order of repeated navigation structures.
- 74Consistent Identification: The Same Names for the Same Functions
Provide consistent names and representations for identical functionality.
- 75Change on Request: Predictable Changes of Context
At AAA, allow users to request changes of context or turn them off.
- 76Consistent Help: Finding Needed Help in the Same Place
Maintain the relative position of repeated help mechanisms.
- 77Error Identification: Explaining What Went Wrong and Where
Describe automatically detected input errors in text.
- 78Labels and Instructions: Providing Information Before Input
Explain the required information and format before users enter data.
- 79Error Suggestions: Guiding the Next Action
Connect known correction methods to error messages.
- 80Important Submissions: Checking Legal, Financial, and Data Changes
Review the means of reversing, checking, and confirming important actions.
- 81Context-Sensitive Help: Getting Assistance Where You Are Stuck
Provide help suited to the context of data entry and tasks.
- 82Preventing Errors in All Submissions: Extending to AAA
Review the means of reversing, checking, and confirming information submissions in general.
- 83Redundant Entry: Not Asking for the Same Information Again Within a Process
Make previously entered information available for reuse or selection.
- 84Accessible Authentication: Reducing Reliance on Memory and Puzzles
Review alternatives and assistance mechanisms for cognitive function tests in AA authentication.
- 85Enhanced Authentication Requirements: Broader Cognitive Accessibility
Review the permitted alternatives and scope of assistance in AAA authentication.
A robust web
Share names, roles and states with assistive technology.
- 86Name, Role, Value: Sharing UI State with Assistive Technologies
Programmatically convey the meaning and state changes of custom controls.
- 87Status Messages: Communicating Results Without Moving Focus
Convey task results and progress to assistive technologies.
Connecting to a service
Integrate criterion evaluations into agent workflows and operations.
- 88Connecting Accessibility Evaluation with Agents and Services
Design systems that coordinate criterion-specific prompts and connect evidence, improvements, and re-evaluation, along with structures for distributing materials and transitioning to services.