WCAG 2.2 accessibility
audit checklist

Information and interface components must be presentable to users in ways they can perceive.

• 1.1.1Non-text ContentLevel AEvery image, icon and control has a text alternative that conveys its purpose. Decorative images are marked so screen readers skip them.
• 1.2.1Audio-only and Video-only (Prerecorded)Level AAudio-only content has a transcript; video-only has a transcript or audio description.
• 1.2.2Captions (Prerecorded)Level AAll prerecorded video with audio has accurate synchronised captions - auto-captions alone rarely pass.
• 1.2.3Audio Description or Media AlternativeLevel AVisual information in video that isn't in the soundtrack is available via audio description or a text alternative.
• 1.2.4Captions (Live)Level AALive audio content in synchronised media is captioned in real time.
• 1.2.5Audio Description (Prerecorded)Level AAPrerecorded video has audio description of important visual detail.
• 1.3.1Info and RelationshipsLevel AStructure is conveyed in markup, not just visually: real headings, lists, tables with headers, and programmatically associated form labels.
• 1.3.2Meaningful SequenceLevel ADOM order matches the logical reading order. Check that CSS positioning hasn't decoupled visual order from source order.
• 1.3.3Sensory CharacteristicsLevel AInstructions don't rely solely on shape, size, position, or sound ("click the round button on the right").
• 1.3.4OrientationLevel AAContent works in both portrait and landscape unless a specific orientation is essential.
• 1.3.5Identify Input PurposeLevel AAInputs collecting user data use the correct autocomplete attribute (name, email, tel, address...).
• 1.4.1Use of ColorLevel AColour is never the only way information is conveyed - errors, required fields, links in body text and chart series all need a second cue.
• 1.4.2Audio ControlLevel AAny audio playing automatically for more than 3 seconds can be paused, stopped or muted.
• 1.4.3Contrast (Minimum)Level AACompute it, don't eyeball it: 4.5:1 for normal text, 3:1 for large text (18.66px bold / 24px). Check placeholder, disabled-looking and overlay text too.
• 1.4.4Resize TextLevel AAText scales to 200% without loss of content or function. Test browser zoom, not just the OS font setting.
• 1.4.5Images of TextLevel AAReal text is used instead of pictures of text, except for logos and where a particular presentation is essential.
• 1.4.10ReflowLevel AANo horizontal scrolling at 320 CSS px wide (equivalent to 400% zoom on desktop). Remember desktop keyboard users get the mobile layout at high zoom.
• 1.4.11Non-text ContrastLevel AAUI components and meaningful graphics have 3:1 contrast against adjacent colours - including input borders and focus indicators.
• 1.4.12Text SpacingLevel AANo loss of content when users override line height to 1.5, paragraph spacing to 2x, letter spacing to 0.12em and word spacing to 0.16em.
• 1.4.13Content on Hover or FocusLevel AATooltips and popovers are dismissible, hoverable and persistent until dismissed.

Interface components and navigation must be operable - by keyboard, switch, voice and touch, not just a mouse.

• 2.1.1KeyboardLevel AEvery function is reachable and usable with the keyboard alone. Custom widgets (dropdowns, sliders, modals, carousels) are where this usually fails.
• 2.1.2No Keyboard TrapLevel AFocus can always move away from a component using the keyboard. Test modals and embedded media especially.
• 2.1.4Character Key ShortcutsLevel ASingle-character shortcuts can be turned off, remapped, or are active only on focus.
• 2.2.1Timing AdjustableLevel ATime limits can be turned off, adjusted or extended - including session timeouts.
• 2.2.2Pause, Stop, HideLevel AAuto-updating, moving, blinking or scrolling content lasting over 5 seconds can be paused. Carousels and marquees count.
• 2.3.1Three Flashes or Below ThresholdLevel ANothing flashes more than three times per second.
• 2.4.1Bypass BlocksLevel AA skip link or landmark structure lets users jump past repeated navigation.
• 2.4.2Page TitledLevel AEvery page has a unique, descriptive title element.
• 2.4.3Focus OrderLevel ATab order follows a logical, meaningful sequence - watch for positive tabindex values and DOM-order surprises.
• 2.4.4Link Purpose (In Context)Level ALink text describes its destination. Multiple "Read more" links on one page usually fail.
• 2.4.5Multiple WaysLevel AAMore than one route to each page - navigation plus search, sitemap or index.
• 2.4.6Headings and LabelsLevel AAHeadings and labels describe topic or purpose, and heading levels don't skip.
• 2.4.7Focus VisibleLevel AAThe keyboard focus indicator is always visible. Never remove outlines without an equally clear replacement.
• 2.4.11Focus Not Obscured (Minimum)Level AANew in 2.2. Focused elements aren't fully hidden behind sticky headers, footers or cookie banners.
• 2.5.1Pointer GesturesLevel AMultipoint or path-based gestures (pinch, swipe-to-delete) have a single-pointer alternative.
• 2.5.2Pointer CancellationLevel AActions fire on the up-event, so users can abort by moving away before releasing.
• 2.5.3Label in NameLevel AThe accessible name contains the visible label text - critical for voice-control users.
• 2.5.4Motion ActuationLevel AAnything triggered by device motion (shake, tilt) has a conventional control too, and motion can be disabled.
• 2.5.7Dragging MovementsLevel AANew in 2.2. Any drag-and-drop action has a single-pointer alternative such as tap-to-select then tap-to-place.
• 2.5.8Target Size (Minimum)Level AANew in 2.2. Pointer targets are at least 24x24 CSS px, or adequately spaced. Icon-only buttons commonly fail.

Information and the operation of the interface must be understandable.

• 3.1.1Language of PageLevel AThe html element has a valid lang attribute.
• 3.1.2Language of PartsLevel AAPassages in another language are marked with their own lang attribute.
• 3.2.1On FocusLevel AFocusing a component doesn't trigger an unexpected change of context.
• 3.2.2On InputLevel AChanging a setting doesn't automatically submit a form or navigate without warning.
• 3.2.3Consistent NavigationLevel AARepeated navigation appears in the same relative order on every page.
• 3.2.4Consistent IdentificationLevel AAThe same function is labelled consistently across the site.
• 3.2.6Consistent HelpLevel ANew in 2.2. Help mechanisms (contact details, chat, help link) appear in the same relative order across pages.
• 3.3.1Error IdentificationLevel AErrors are described in text, not colour alone, and are announced to screen readers.
• 3.3.2Labels or InstructionsLevel AInputs have visible labels. Placeholder text is not a label.
• 3.3.3Error SuggestionLevel AAWhere the fix is known, the error message suggests it - e.g. the expected date format.
• 3.3.4Error Prevention (Legal, Financial, Data)Level AASubmissions with legal or financial consequence are reversible, checked, or confirmed before finalising.
• 3.3.7Redundant EntryLevel ANew in 2.2. Information already entered is auto-populated or selectable, not re-typed.
• 3.3.8Accessible Authentication (Minimum)Level AANew in 2.2. No cognitive function test (puzzle, transcription, memorisation) without an alternative. Allow paste into OTP and password fields.

Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

• 4.1.2Name, Role, ValueLevel AEvery custom control exposes a correct name, role and state to assistive tech. Test with a real screen reader, not just an ARIA linter.
• 4.1.3Status MessagesLevel AADynamic status updates (validation, cart changes, search counts) are announced via a live region without moving focus.