WCAG 2.2 checklist for small sites

Fifty-five checks.
None of them is a plugin.

To meet WCAG 2.2 at level AA, the level the EU standard EN 301 549 and most accessibility policies refer to, a website has to meet 55 success criteria: 31 at level A and 24 at level AA. WCAG 2.2 has 86 criteria in all. It added nine to WCAG 2.1, 6 of them at A or AA, and removed 4.1.1 Parsing. Below is every A and AA criterion in plain words, a quick way to check each one, and whether a tool can help or it takes a person, in a checklist that keeps your ticks in your browser.

Open the checklist Start free
55 criteria 6 new in 2.2 W3C text checked 5 Oct 2026

By the Builderify team

01 / 2.2 vs 2.1

WCAG 2.2 vs 2.1:
nine criteria in, one out.

WCAG 2.2 became a W3C Recommendation on 5 October 2023 and was republished on 12 December 2024 with corrections to some definitions and editorial fixes; no criteria were added or removed. It keeps everything in WCAG 2.1 except 4.1.1 Parsing, and adds nine success criteria for the three groups W3C set out to help: people with cognitive or learning disabilities, people with low vision, and people with disabilities using mobile devices.

So a site that meets 2.2 also meets 2.1, and W3C recommends 2.2 as the target “even if formal obligations mention previous versions”. One catch from W3C: if a policy still requires 2.0 or 2.1, you “may need to continue to test and report 4.1.1”.

Number of success criteria in WCAG 2.1 and WCAG 2.2, by level
Version Level A Level AA Level AAA Total To meet AA
WCAG 2.1 30 20 28 78 50
WCAG 2.2 31 24 31 86 55

Counted from the conformance level printed on each criterion in the W3C Recommendations. WCAG 2.1’s count includes 4.1.1 Parsing; level AA means meeting every level A and level AA criterion.

wcag-2.1 → wcag-2.2 +9 −1

New criteria were added at the end of each guideline, so existing numbers did not change. That is also why 2.4.11 comes after 2.4.7, and levels are no longer grouped in order.

Is WCAG 2.2 an ISO standard, and does EN 301 549 use it?

Yes, and yes, with a timing catch in the EU. Here is the record as of 5 October 2026, from W3C, ETSI and the European Commission’s AccessibleEU centre.

  1. 5 October 2023

    WCAG 2.2 published as a W3C Recommendation.

  2. 12 December 2024

    Republished with errata: several definitions and the formatting of 2.5.8 and 3.3.8 corrected, plus editorial fixes. No criteria added or removed.

  3. 21 October 2025

    Approved as an international standard, ISO/IEC 40500:2025, free to download from ISO. W3C says it is “exactly the same as the October 2023 version of WCAG 2.2”.

  4. 2 September 2026

    ETSI publishes EN 301 549 V4.1.1, the European ICT accessibility standard, moving its web, document and software requirements from WCAG 2.1 to WCAG 2.2.

  5. 7 September 2026

    AccessibleEU notes that V4.1.1 is not yet the legal reference for the European Accessibility Act or the Web Accessibility Directive. Until the Commission cites it in the Official Journal, the reference stays EN 301 549 V3.2.1 (2021), based on WCAG 2.1 level AA.

  6. Expected late 2026

    W3C expects the December 2024 edition to follow as ISO/IEC 40500:2026. Not published as of 5 October 2026.

What that means for the European Accessibility Act is covered in the European Accessibility Act guide for small businesses. In practice, aiming for WCAG 2.2 AA now covers the 2.1 baseline as well.

02 / Checklist

The WCAG 2.2 AA checklist:
all 55 criteria, in plain words.

Each criterion has what it means, a quick way to check it, whether a tool can flag it, and a link to W3C’s Understanding page. Filter it, tick what you have checked, and copy the result as a report. Your ticks are saved in this browser only.

This is a working checklist, not an audit, and not legal advice. Ticking every box here does not make a site conformant: W3C conformance applies to whole pages and complete processes, and the wording that counts is in the WCAG 2.2 Recommendation. Where a law or contract depends on the answer, have the site evaluated by someone who does this for a living.

A tool can flag it means at least one rule in the open-source axe-core 4.13 checker tests part of the criterion. Passing that rule is not passing the criterion. Needs a human means no automated rule covers it at all.

Principle 1 Perceivable

20 criteria at A and AA

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

  • Guideline 1.1 · Text Alternatives
  • 1.1.1
    A

    Non-text Content

    A tool can flag it
    What it means
    Every image, icon and image button that carries meaning has a text alternative that does the same job. Purely decorative images get an empty alt so screen readers skip them.
    Check
    Let a checker find images with no alt at all, then read the alt text you do have: would it replace the image for someone who cannot see it? Icon-only buttons need a name too.
    W3C: Understanding 1.1.1 Non-text Content
  • Guideline 1.2 · Time-based Media
  • 1.2.1
    A

    Audio-only and Video-only (Prerecorded)

    Needs a human
    What it means
    A recorded podcast or audio clip has a transcript. A recorded video with no sound has a text description or an audio track that tells the same story.
    Check
    List every audio-only file and every silent video on the site. Each one needs its text version on the same page or one link away.
    W3C: Understanding 1.2.1 Audio-only and Video-only (Prerecorded)
  • 1.2.2
    A

    Captions (Prerecorded)

    A tool can flag it
    What it means
    Recorded videos with sound have synchronised captions, unless the video is itself a clearly labelled alternative to text on the page.
    Check
    Play each video with the sound off. Captions should be available, accurate and in time with the speech. Automatic captions usually need correcting first.
    W3C: Understanding 1.2.2 Captions (Prerecorded)
  • 1.2.3
    A

    Audio Description or Media Alternative (Prerecorded)

    Needs a human
    What it means
    If a recorded video shows something important that the soundtrack never says, provide an audio description or a full text alternative.
    Check
    Listen to each video without watching it. If you miss anything that matters, such as on-screen text or a demonstration, it needs description or a descriptive transcript.
    W3C: Understanding 1.2.3 Audio Description or Media Alternative (Prerecorded)
  • 1.2.4
    AA

    Captions (Live)

    Needs a human
    What it means
    Live video with sound, such as a webinar or a stream on your site, has live captions.
    Check
    For each live event, confirm captions are switched on and readable before you go live, whether from a human captioner or your platform.
    W3C: Understanding 1.2.4 Captions (Live)
  • 1.2.5
    AA

    Audio Description (Prerecorded)

    Needs a human
    What it means
    At level AA, recorded video needs audio description of important visual information. A text alternative alone is no longer enough.
    Check
    Use the same listen-only test as 1.2.3. The fix is narration that already says what is shown, or a described version of the video.
    W3C: Understanding 1.2.5 Audio Description (Prerecorded)
  • Guideline 1.3 · Adaptable
  • 1.3.1
    A

    Info and Relationships

    A tool can flag it
    What it means
    Structure you can see is in the code too: headings are real headings, lists are lists, tables have header cells and form fields are tied to their labels.
    Check
    Look at the page’s heading outline and its tables. Anything that looks like a heading, a list or a table header should be marked up as one, not just styled bold.
    W3C: Understanding 1.3.1 Info and Relationships
  • 1.3.2
    A

    Meaningful Sequence

    Needs a human
    What it means
    When the order of content affects its meaning, the order in the code matches the order that makes sense on screen.
    Check
    Read the page with a screen reader, or with styles switched off. Content should still arrive in a sensible order, with prices next to their products.
    W3C: Understanding 1.3.2 Meaningful Sequence
  • 1.3.3
    A

    Sensory Characteristics

    Needs a human
    What it means
    Instructions never rely only on shape, colour, size, position or sound, such as “press the round button on the right”.
    Check
    Search your copy and form hints for words like left, right, above, below, round, green and red. Add the control’s name to each instruction.
    W3C: Understanding 1.3.3 Sensory Characteristics
  • 1.3.4
    AA

    Orientation

    Needs a human
    What it means
    The site works in portrait and in landscape, unless one orientation is essential, such as a piano app.
    Check
    Turn a phone on each key page and in checkout. Nothing should lock to one orientation or ask you to rotate the device.
    W3C: Understanding 1.3.4 Orientation
  • 1.3.5
    AA

    Identify Input Purpose

    A tool can flag it
    What it means
    Fields that ask for the visitor’s own details, such as name, email, phone and address, say what they are in code with the autocomplete attribute, so browsers can fill them in.
    Check
    Inspect your contact, sign-up and checkout fields for autocomplete values such as name, email and tel. A checker flags invalid values, but not missing ones.
    W3C: Understanding 1.3.5 Identify Input Purpose
  • Guideline 1.4 · Distinguishable
  • 1.4.1
    A

    Use of Color

    A tool can flag it
    What it means
    Colour is never the only way information is shown. Links inside text, required fields, errors and chart lines need a second cue, such as an underline, an icon or a label.
    Check
    Look at the page in greyscale. You should still be able to tell links from text, errors from normal fields and one chart line from another.
    W3C: Understanding 1.4.1 Use of Color
  • 1.4.2
    A

    Audio Control

    A tool can flag it
    What it means
    Any sound that plays on its own for more than 3 seconds can be paused or stopped, or its volume turned down separately from the device.
    Check
    Load each page with the sound on. If audio starts by itself, a pause control has to be easy to reach near the top. Simpler still: do not autoplay sound.
    W3C: Understanding 1.4.2 Audio Control
  • 1.4.3
    AA

    Contrast (Minimum)

    A tool can flag it
    What it means
    Text has a contrast ratio of at least 4.5:1 with its background, or 3:1 for large text. Logos, decoration and disabled controls are exempt.
    Check
    Run a contrast checker over body text, buttons, links and placeholder text. Text laid over photos or gradients usually needs checking by eye.
    W3C: Understanding 1.4.3 Contrast (Minimum)
  • 1.4.4
    AA

    Resize Text

    A tool can flag it
    What it means
    Text can be zoomed to 200% without anything being cut off, overlapping or stopping working.
    Check
    Zoom the browser to 200% on key pages. Read everything, open the menu and submit a form. Also check the page does not block pinch zoom on a phone.
    W3C: Understanding 1.4.4 Resize Text
  • 1.4.5
    AA

    Images of Text

    Needs a human
    What it means
    Use real text rather than pictures of text, except for logos or where a particular look is essential.
    Check
    Try to select the words on banners, buttons and promo tiles. If you cannot, it is an image; rebuild it as live text over the picture.
    W3C: Understanding 1.4.5 Images of Text
  • 1.4.10
    AA

    Reflow

    Needs a human
    What it means
    At a width of 320 CSS pixels, the same as 400% zoom on a 1,280-pixel-wide window, content fits without scrolling sideways. Maps, data tables and similar are exempt.
    Check
    Zoom a desktop browser to 400%, or set a responsive view to 320 pixels wide. You should only ever need to scroll down, never across.
    W3C: Understanding 1.4.10 Reflow
  • 1.4.11
    AA

    Non-text Contrast

    Needs a human
    What it means
    The parts you need to see to use a control, such as field borders, checkbox outlines, icon buttons and focus states, and the parts of graphics you need to understand them, have at least 3:1 contrast against what is next to them.
    Check
    Check input borders, toggles and icon-only buttons with a contrast checker. Pale grey field borders on white are the usual failure.
    W3C: Understanding 1.4.11 Non-text Contrast
  • 1.4.12
    AA

    Text Spacing

    A tool can flag it
    What it means
    If a visitor sets line height to 1.5, paragraph spacing to 2 times, letter spacing to 0.12 times and word spacing to 0.16 times the font size, nothing is cut off or overlaps.
    Check
    Apply those four values with a text-spacing bookmarklet or a user stylesheet, then look for clipped buttons, cut-off menus and fixed-height boxes.
    W3C: Understanding 1.4.12 Text Spacing
  • 1.4.13
    AA

    Content on Hover or Focus

    Needs a human
    What it means
    Tooltips and pop-outs that appear on hover or focus can be dismissed without moving away (usually with Esc), stay open while the pointer moves onto them, and do not vanish on their own.
    Check
    Hover over and tab to each tooltip and dropdown. Press Esc, then move the mouse onto the pop-out. It should behave on all three counts.
    W3C: Understanding 1.4.13 Content on Hover or Focus

Principle 2 Operable

20 criteria at A and AA

“User interface components and navigation must be operable.”

  • Guideline 2.1 · Keyboard Accessible
  • 2.1.1
    A

    Keyboard

    A tool can flag it
    What it means
    Everything works with a keyboard alone: menus, sliders, popups, forms, video players and checkout.
    Check
    Put the mouse away. Use Tab, Shift+Tab, Enter, Space and the arrow keys to complete each key task, from the menu to the order confirmation.
    W3C: Understanding 2.1.1 Keyboard
  • 2.1.2
    A

    No Keyboard Trap

    Needs a human
    What it means
    Keyboard focus never gets stuck inside something, such as an embedded video, a map or a popup.
    Check
    Tab into and back out of every embed and dialog. If leaving needs anything beyond Tab, arrows or Esc, the page must say how.
    W3C: Understanding 2.1.2 No Keyboard Trap
  • 2.1.4
    A

    Character Key Shortcuts

    Needs a human
    What it means
    If the site uses single-key shortcuts (a letter, number or symbol on its own), people can turn them off or remap them, or they only work while that component has focus.
    Check
    Most small sites have none. If a plugin adds them, such as a key that opens search, look for a setting to turn them off.
    W3C: Understanding 2.1.4 Character Key Shortcuts
  • Guideline 2.2 · Enough Time
  • 2.2.1
    A

    Timing Adjustable

    A tool can flag it
    What it means
    Time limits can be turned off, adjusted, or extended after a warning with at least 20 seconds to respond. Real-time events, essential limits and limits over 20 hours are exempt.
    Check
    Look for session timeouts, reserved-basket countdowns and pages that refresh or move on by themselves. Each needs a warning and a simple way to extend.
    W3C: Understanding 2.2.1 Timing Adjustable
  • 2.2.2
    A

    Pause, Stop, Hide

    A tool can flag it
    What it means
    Anything that moves, blinks or scrolls on its own for more than five seconds alongside other content, such as a carousel or a ticker, can be paused, stopped or hidden. Auto-updating content too.
    Check
    Find every carousel, animated banner and live feed. Each needs a visible pause or stop control that also works from the keyboard.
    W3C: Understanding 2.2.2 Pause, Stop, Hide
  • Guideline 2.3 · Seizures and Physical Reactions
  • 2.3.1
    A

    Three Flashes or Below Threshold

    Needs a human
    What it means
    Nothing flashes more than three times in any one second, unless the flash is below the general and red flash thresholds.
    Check
    Review videos, GIFs and animations for strobing or rapid flashing. When in doubt, take it out.
    W3C: Understanding 2.3.1 Three Flashes or Below Threshold
  • Guideline 2.4 · Navigable
  • 2.4.1
    A

    Bypass Blocks

    A tool can flag it
    What it means
    There is a way to skip blocks repeated on every page, such as the header menu, usually a “Skip to content” link.
    Check
    Load a page and press Tab once. A skip link should appear and move focus straight to the main content.
    W3C: Understanding 2.4.1 Bypass Blocks
  • 2.4.2
    A

    Page Titled

    A tool can flag it
    What it means
    Every page has a title that says what it is about or what it is for.
    Check
    Read the browser tab on each page type. A checker only flags missing titles; one title used everywhere, or just “Home”, still needs fixing.
    W3C: Understanding 2.4.2 Page Titled
  • 2.4.3
    A

    Focus Order

    Needs a human
    What it means
    Tabbing moves through the page in an order that keeps its meaning. A dialog takes focus when it opens and returns it when it closes.
    Check
    Tab through each page and watch where focus goes. It should not leap around the layout or land behind an open popup.
    W3C: Understanding 2.4.3 Focus Order
  • 2.4.4
    A

    Link Purpose (In Context)

    A tool can flag it
    What it means
    The purpose of every link is clear from its text, or from its text together with the sentence, list item or table cell it sits in.
    Check
    A checker flags links with no name, such as bare icons. A person has to judge the vague ones: “click here”, “read more” and “learn more”.
    W3C: Understanding 2.4.4 Link Purpose (In Context)
  • 2.4.5
    AA

    Multiple Ways

    Needs a human
    What it means
    There is more than one way to find each page, such as a menu plus search, a sitemap or links between pages. Steps in a process, like checkout, are exempt.
    Check
    For a three- or four-page site with every page linked from the home page, W3C says that may be enough. Bigger sites: add search or a sitemap page.
    W3C: Understanding 2.4.5 Multiple Ways
  • 2.4.6
    AA

    Headings and Labels

    Needs a human
    What it means
    Headings and labels describe their topic or purpose.
    Check
    Read only the headings and form labels on a page. They should tell you what each section holds and what each field wants.
    W3C: Understanding 2.4.6 Headings and Labels
  • 2.4.7
    AA

    Focus Visible

    Needs a human
    What it means
    When someone uses the keyboard, they can always see which element has focus.
    Check
    Tab through each page. If the focus outline disappears on any link, button or field, often from outline: none in a theme’s CSS, it fails.
    W3C: Understanding 2.4.7 Focus Visible
  • 2.4.11
    AA New in 2.2

    Focus Not Obscured (Minimum)

    Needs a human
    What it means
    An element with keyboard focus is never completely hidden by something you put on the page, such as a sticky header, a cookie banner or a chat widget.
    Check
    Tab through a page with the cookie banner still open and any sticky bars showing. The focused item must stay at least partly visible.
    W3C: Understanding 2.4.11 Focus Not Obscured (Minimum)
  • Guideline 2.5 · Input Modalities
  • 2.5.1
    A

    Pointer Gestures

    Needs a human
    What it means
    Anything done with a multi-finger or path-based gesture, such as pinch, swipe or tracing a shape, can also be done with simple taps or clicks.
    Check
    For swipe carousels, galleries and maps, check there are next, previous and zoom buttons as well.
    W3C: Understanding 2.5.1 Pointer Gestures
  • 2.5.2
    A

    Pointer Cancellation

    Needs a human
    What it means
    Actions happen when the click or tap is released, not the moment it is pressed, so people can slide off to cancel, or can undo.
    Check
    Press down on a button, drag off it and let go. Nothing should happen. Standard links and buttons already behave this way.
    W3C: Understanding 2.5.2 Pointer Cancellation
  • 2.5.3
    A

    Label in Name

    A tool can flag it
    What it means
    A control’s accessible name contains the words shown on it, so a voice-control user can say what they see.
    Check
    Where buttons carry an aria-label, make sure it contains the visible text, ideally at the start: a “Buy now” button should not be named “Add product”.
    W3C: Understanding 2.5.3 Label in Name
  • 2.5.4
    A

    Motion Actuation

    Needs a human
    What it means
    Anything triggered by shaking or tilting the device also has an ordinary control, and the motion response can be switched off.
    Check
    Rare on websites. If you have shake-to-undo or tilt-to-browse, add buttons for the same thing and a way to turn the motion off.
    W3C: Understanding 2.5.4 Motion Actuation
  • 2.5.7
    AA New in 2.2

    Dragging Movements

    Needs a human
    What it means
    Anything done by dragging, such as range sliders, reordering a list, a map or a before-and-after image, can also be done with single clicks or taps, unless dragging is essential.
    Check
    For every draggable thing, look for buttons, arrows, a text field or tap-to-pick. A price slider with two editable number fields passes.
    W3C: Understanding 2.5.7 Dragging Movements
  • 2.5.8
    AA New in 2.2

    Target Size (Minimum)

    A tool can flag it
    What it means
    Click and tap targets are at least 24 by 24 CSS pixels, or spaced so that a 24-pixel circle centred on each small one touches no other target or circle. Links inside sentences are exempt.
    Check
    Check icon links, close buttons, social icons and pagination. A checker can measure; on a phone, try hitting each one with your thumb.
    W3C: Understanding 2.5.8 Target Size (Minimum)

Principle 3 Understandable

13 criteria at A and AA

“Information and the operation of the user interface must be understandable.”

  • Guideline 3.1 · Readable
  • 3.1.1
    A

    Language of Page

    A tool can flag it
    What it means
    Each page says in code which language it is in, such as lang="en" on the html element.
    Check
    A checker flags a missing or invalid language. You still need to confirm it is the right one, especially on translated pages.
    W3C: Understanding 3.1.1 Language of Page
  • 3.1.2
    AA

    Language of Parts

    A tool can flag it
    What it means
    Passages in another language are marked with their own lang attribute, so screen readers pronounce them properly. Proper names and borrowed words are exempt.
    Check
    Find quotes, product descriptions or whole sections in a second language, and mark each one with its language.
    W3C: Understanding 3.1.2 Language of Parts
  • Guideline 3.2 · Predictable
  • 3.2.1
    A

    On Focus

    Needs a human
    What it means
    Moving focus onto something never triggers a big change, such as opening a new window, submitting a form or jumping elsewhere on the page.
    Check
    Tab through forms and menus. Nothing should happen until you press Enter or Space.
    W3C: Understanding 3.2.1 On Focus
  • 3.2.2
    A

    On Input

    Needs a human
    What it means
    Changing a setting, such as a dropdown, radio button or checkbox, does not cause a change of context on its own unless people are told beforehand.
    Check
    Use every select and radio group with the keyboard. A country or language picker that reloads the page on change needs a Go button or a warning.
    W3C: Understanding 3.2.2 On Input
  • 3.2.3
    AA

    Consistent Navigation

    Needs a human
    What it means
    Menus and navigation repeated across pages appear in the same relative order each time.
    Check
    Compare the header and footer on a few page types. Links should not swap places from one template to the next.
    W3C: Understanding 3.2.3 Consistent Navigation
  • 3.2.4
    AA

    Consistent Identification

    Needs a human
    What it means
    Things that do the same job are identified the same way across pages: the same search icon, the same “Basket” label.
    Check
    Compare icons, button labels and link text for the same action on different templates.
    W3C: Understanding 3.2.4 Consistent Identification
  • 3.2.6
    A New in 2.2

    Consistent Help

    Needs a human
    What it means
    If you offer help on several pages, such as a phone number, an email address, a contact form, a chat or an FAQ, it comes in the same order relative to the rest of the page each time. You do not have to offer help; if you do, keep it in one place.
    Check
    Compare where the contact link, phone number and chat sit on your home, product and checkout pages. They should not move about in the page order.
    W3C: Understanding 3.2.6 Consistent Help
  • Guideline 3.3 · Input Assistance
  • 3.3.1
    A

    Error Identification

    Needs a human
    What it means
    When a form detects a mistake, it says which field is wrong and describes the problem in text, not just with a red border.
    Check
    Submit each form empty, then with a bad email address. Read every message you get, and check it names the field.
    W3C: Understanding 3.3.1 Error Identification
  • 3.3.2
    A

    Labels or Instructions

    A tool can flag it
    What it means
    Fields have labels or instructions when input is needed, including formats such as dates and which fields are required.
    Check
    Look for placeholder-only fields whose hint disappears once you start typing. A checker flags some labelling faults; read the rest yourself.
    W3C: Understanding 3.3.2 Labels or Instructions
  • 3.3.3
    AA

    Error Suggestion

    Needs a human
    What it means
    If you know how to fix a mistake, say so: “Enter a date like 31/12/2026”, not just “Invalid”, unless it would weaken security.
    Check
    Trigger each error message and check it tells the visitor what to do next.
    W3C: Understanding 3.3.3 Error Suggestion
  • 3.3.4
    AA

    Error Prevention (Legal, Financial, Data)

    Needs a human
    What it means
    For purchases, legal commitments, or changing or deleting stored data, submissions can be reversed, are checked for mistakes, or have a review step before they are final.
    Check
    Walk through checkout, bookings and account deletion. Look for a review page, a confirmation step or an undo.
    W3C: Understanding 3.3.4 Error Prevention (Legal, Financial, Data)
  • 3.3.7
    A New in 2.2

    Redundant Entry

    Needs a human
    What it means
    Do not make people type the same thing twice in one process. Fill it in for them or let them pick it, as with “Billing address same as delivery”. Security re-entry, such as passwords, is exempt.
    Check
    Go through checkout and any multi-step form looking for questions you already answered a step earlier. Browser autofill does not count.
    W3C: Understanding 3.3.7 Redundant Entry
  • 3.3.8
    AA New in 2.2

    Accessible Authentication (Minimum)

    Needs a human
    What it means
    Logging in does not depend on remembering, transcribing or solving something unless there is an alternative or help, such as letting password managers fill the field, allowing paste, or an email sign-in link. Object-recognition tests are allowed at AA.
    Check
    Log in with a password manager, then paste the password and any one-time code by hand. Any puzzle CAPTCHA needs a route that is not a puzzle.
    W3C: Understanding 3.3.8 Accessible Authentication (Minimum)

Principle 4 Robust

2 criteria at A and AA

“Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.”

  • Guideline 4.1 · Compatible
  • 4.1.2
    A

    Name, Role, Value

    A tool can flag it
    What it means
    Every control, including buttons, links, fields, toggles and menus, tells assistive technology its name, what it is and its current state. Standard HTML elements do this for you.
    Check
    A checker flags unnamed buttons and fields. For custom widgets such as accordions, tabs and toggles, check with a screen reader that “expanded” or “checked” is announced.
    W3C: Understanding 4.1.2 Name, Role, Value
  • 4.1.3
    AA

    Status Messages

    Needs a human
    What it means
    Messages such as “Added to basket”, “3 results” or “Message sent” are announced by screen readers without moving focus to them.
    Check
    Turn on a screen reader and trigger each message. You should hear it without having to go and find it.
    W3C: Understanding 4.1.3 Status Messages
  • 4.1.1

    Parsing Removed in 2.2

    Not part of WCAG 2.2, so not counted here. W3C’s note: assistive technology “no longer has any need to directly parse HTML”, so the problems it covered no longer exist or are handled by other criteria. Duplicate IDs that break labels or names still fail under 1.3.1 or 4.1.2.

    W3C: Understanding 4.1.1 Parsing (obsolete and removed)

No criteria match these filters. Try “A and AA” and “All”.

03 / New criteria

The WCAG 2.2 new success criteria,
drawn as a fail and a pass.

If your site already met WCAG 2.1 AA, these 6 are the new work. Most small sites trip on the same three: a cookie banner over the focused link, tiny social icons, and a checkout that asks for the address twice.

2.4.11 Level AA

Focus Not Obscured (Minimum)

A sticky cookie banner or chat bar must not completely cover the element that has keyboard focus.

In the checklist W3C Understanding 2.4.11
2.5.7 Level AA

Dragging Movements

If something can be dragged, it can also be done with single clicks or taps.

In the checklist W3C Understanding 2.5.7
2.5.8 Level AA

Target Size (Minimum)

Targets are 24 by 24 CSS pixels, or spaced so 24-pixel circles centred on them do not overlap.

In the checklist W3C Understanding 2.5.8
3.3.7 Level A

Redundant Entry

Information already given in a process is filled in or offered, not asked for again.

In the checklist W3C Understanding 3.3.7
3.3.8 Level AA

Accessible Authentication (Minimum)

Logging in does not rest on memory or a puzzle alone: let password managers and paste work.

In the checklist W3C Understanding 3.3.8
2.4.12 · New in 2.2Level AAA

Focus Not Obscured (Enhanced)

No part of the focused element is hidden by author-created content. The stricter form of 2.4.11.

W3C Understanding 2.4.12
2.4.13 · New in 2.2Level AAA

Focus Appearance

The focus indicator is at least as large as a 2 CSS pixel thick perimeter of the component, with 3:1 contrast between its focused and unfocused states.

W3C Understanding 2.4.13
3.3.9 · New in 2.2Level AAA

Accessible Authentication (Enhanced)

As 3.3.8, but object recognition and identifying your own uploaded content no longer count as exceptions.

W3C Understanding 3.3.9

AAA criteria are not part of level AA, which is why the checklist leaves them out. W3C does not recommend AAA as a general policy for whole sites, because some content cannot meet all of it.

04 / How to check

A WCAG checklist for small business websites,
in the order to test.

Start with a scan, then make eight passes by hand. Each pass covers a group of criteria, and between them they cover all 55. Pick your key templates first: the home page, one content page, a product or service page, the contact form and checkout.

“Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so.”
  1. 01

    Run an automated checker

    Free browser extensions built on engines such as axe-core, or W3C’s list of evaluation tools, find the mechanical faults fast: missing alt text, empty buttons, low text contrast, a missing language. They have rules touching 21 of the 55 criteria and none for the other 34. Fix what they find, then do the passes below for everything they cannot judge.

    1.1.1 1.2.2 1.3.1 1.3.5 1.4.1 1.4.2 1.4.3 1.4.4 1.4.12 2.1.1 2.2.1 2.2.2 2.4.1 2.4.2 2.4.4 2.5.3 2.5.8 3.1.1 3.1.2 3.3.2 4.1.2
  2. 02

    Put the mouse away

    9 criteria

    Work through your key pages and tasks using only Tab, Shift+Tab, Enter, Space, the arrow keys and Esc. Watch where focus goes, whether you can always see it, and whether anything gets in its way.

  3. 03

    Zoom and squeeze

    3 criteria

    Zoom the browser to 200%, then 400%, and apply the four text-spacing values. Content should reflow into one column and nothing should be clipped.

  4. 04

    Look again, without colour

    5 criteria

    Check contrast with a contrast checker, look at the page in greyscale, try to select the words on images, and reread your instructions for “the green button on the left”.

  5. 05

    Pick up a phone

    6 criteria

    Tap the small things, rotate the screen, try every swipe and drag with taps instead, and press a button then slide off it.

  6. 06

    Break your own forms

    9 criteria

    Submit every form empty and then wrong. Go through checkout and log in with a password manager. Read every error message as if you had never seen the form.

  7. 07
  8. 08

    Compare page types

    7 criteria

    Open your home page, a content page, a product or service page and the contact page side by side. Titles, menus, labels and help links should be consistent.

  9. 09

    Listen with a screen reader

    8 criteria

    Use the screen reader already on your device: VoiceOver on Apple devices, Narrator on Windows, TalkBack on Android. Move through headings, links, images and forms.

What an automated scan can and cannot reach, by principle
Principle A and AA criteria A tool can flag part of it Needs a human New in 2.2
1. Perceivable 20 9 11 0
2. Operable 20 8 12 3
3. Understandable 13 3 10 3
4. Robust 2 1 1 0
All 55 21 34 6

Counted from the WCAG tags on axe-core 4.13.0’s WCAG 2.0, 2.1 and 2.2 A and AA rules, leaving out experimental and deprecated ones. Other checkers test different things; the point holds for all of them.

05 / With Builderify

An accessibility menu ticks none of the 55.
It helps the people who visit anyway.

Builderify’s accessibility widget is a menu of 13 adjustments in five groups that each visitor switches on for themselves. It acts on your page as it already is and does not change your markup, so it does not meet any success criterion on your behalf, and Builderify does not claim it makes a site compliant.

Each tool in Builderify's accessibility menu, the WCAG criterion it is often mistaken for, and what that criterion asks of your site instead
Menu tool, for the visitor Often mistaken for What the criterion asks of your site
Font Size 1.4.4 Resize Text Your own text survives 200% browser zoom, with no menu involved.
Text Spacing 1.4.12 Text Spacing Your layout does not break when a visitor overrides spacing by any means, to the four values in the criterion.
Dyslexia Friendly Nothing No criterion asks for a particular typeface. This one is simply extra help.
Underline Links 1.4.1 Use of Color Links inside text are distinguishable without colour by default, for everyone.
Underline Titles 1.3.1 Info and Relationships 2.4.6 Headings and Labels Headings are real headings in your code and say what each section is about.
Disable Animations 2.2.2 Pause, Stop, Hide Anything that moves for more than five seconds has your own pause, stop or hide control.
Increase Contrast, Black & White, Invert Colors 1.4.3 Contrast (Minimum) 1.4.11 Non-text Contrast Your default colours already meet 4.5:1 for text and 3:1 for controls and graphics.
Large Cursor Nothing No criterion covers cursor size. Extra help.
Highlight Focus 2.4.7 Focus Visible Your site shows a visible focus indicator itself, on every focusable element.
Read Aloud 1.1.1 Non-text Content 4.1.2 Name, Role, Value Screen readers rely on your alt text and control names. Reading text aloud does not supply them.
Reading Guide Nothing No criterion asks for one. Extra help for long pages.

That is the honest place for any toolbar, Builderify’s included: extra help for visitors, alongside fixing the site against the checklist above. The guide to accessibility overlays and compliance goes into why no widget can do the fixing for you, and the accessibility statement template shows how to mention a menu like this without making a compliance claim.

A route for accessibility reports

Let people tell you what your checklist missed

A support ticket form in the website widget can be the feedback route your accessibility statement points to. Each report gets a reference number, a status from open to closed and a priority, and the visitor can look it up again with their email and that number.

And 3.2.6 Consistent Help

Help in the same place, if you show it everywhere

3.2.6 asks that help repeated across pages comes in the same order relative to the rest of the page. Builderify’s widget is added after your page’s own content wherever it loads, so a help block shown on every page keeps the same place in that order. It is one help mechanism; your phone number, contact link and FAQ still need checking against the criterion, and a person still has to answer the tickets.

10 credits
per 1,000 page loads with the widget on them
1 credit
per support ticket a visitor opens
250 free
credits every month, with no monthly fee

The accessibility menu is included in every account. If you outgrow the free credits, one-time packs start at $9 and never expire; the full rate card is on the pricing page, alongside the rest of the 20 modules.

Start free
Questions

WCAG 2.2, before you ask.

To meet level AA you have to meet 55 success criteria: 31 at level A and 24 at level AA. WCAG 2.2 has 86 criteria in total, and the other 31 are level AAA, which is not part of AA. WCAG 2.1 asked for 50 at the same level.

WCAG 2.2 adds nine success criteria and removes one, 4.1.1 Parsing. Six of the new ones are at level A or AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum). A site that meets WCAG 2.2 also meets WCAG 2.1.

Yes. W3C announced on 21 October 2025 that WCAG 2.2 had been approved as ISO/IEC 40500:2025, which is free to download from ISO. W3C says it is the same text as the October 2023 version, and it expects the December 2024 edition to follow as ISO/IEC 40500:2026.

Only part of it. In the open-source axe-core 4.13 checker, rules touch 21 of the 55 level A and AA criteria and none of the other 34, such as focus order, captions or error messages. W3C says evaluation tools cannot determine accessibility; they can only help a person do it.

No. A menu of visitor adjustments, Builderify's included, does not change your markup, so it does not meet any success criterion on your behalf. Builderify does not claim its accessibility menu makes a site compliant; treat it as extra help for visitors alongside fixing the site against the checklist.

Sources

Standards, Understanding pages and tool rules checked on 5 October 2026. ← All guides

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.

Start free See what it does