Kerbly

WCAG 2.2 checklist for your website

25 checks you can do yourself, with no special tools. Switch between plain English and technical wording, tick items off as you go, then copy what is left. Free, no sign-up, saved only in your browser.

Your progress

0 of 25 checked

Tick an item when it passes, or does not apply to your site.

Images and media

0 of 3

Pictures, video and sound that some visitors cannot see or hear.

  • Hover over a photo or turn on a screen reader. It should read out what the image shows or does, such as “Front of the cafe with outdoor tables”, not “image1.jpg”.

    WCAG 1.1.1 · Level AHow to fix it

  • Look for borders, dividers and background swirls. These should have an empty description so a screen reader skips them instead of reading out file names.

    WCAG 1.1.1 · Level A

  • Play each video on your site with sound off. You should be able to follow what is said from the captions.

    WCAG 1.2.2 · Level AHow to fix it

Colour and text

0 of 5

Whether people with low vision or colour blindness can read what you wrote.

  • Paste your text and background colours into a contrast checker. Normal text needs a ratio of at least 4.5 to 1, and large text needs 3 to 1. Pale grey on white is the usual culprit.

    WCAG 1.4.3 · Level AAHow to fix itContrast checker

  • Look at the outline of a text box or the edge of a button. If you struggle to see it, someone with low vision will too. These parts need a ratio of at least 3 to 1.

    WCAG 1.4.11 · Level AAContrast checker

  • View the page in greyscale, or squint. Can you still tell links from normal text, errors from normal fields, and which option is selected? Add an underline, icon or label too.

    WCAG 1.4.1 · Level AHow to fix it

  • Try to select the words with your mouse. If you cannot, they are an image. Menus, prices and opening hours should be real text so people can resize, translate and listen to them.

    WCAG 1.4.5 · Level AA

  • Press Ctrl and + (or Cmd and +) until you reach 400%. Nothing should overlap or disappear, and you should not have to scroll sideways to read a line of text. Also check that your page does not block pinch-zoom on a phone.

    WCAG 1.4.4 / 1.4.10 · Level AAHow to fix it

Keyboard and navigation

0 of 6

Can someone use your site without a mouse?

  • Put your mouse aside and press Tab repeatedly. You should be able to reach every link, button, menu and form field, and use them with Enter or Space.

    WCAG 2.1.1 · Level A

  • Open pop-ups, chat widgets, cookie banners and date pickers using only the keyboard. You should be able to move away or close them, usually with Esc, and never get stuck.

    WCAG 2.1.2 · Level A

  • As you Tab through the page, there should be a clear outline or highlight on the current item. If it disappears, keyboard users are lost.

    WCAG 2.4.7 · Level AA

  • Tab down a long page that has a fixed header, chat bubble or cookie bar. The focused link should not be hidden underneath them.

    WCAG 2.4.11 · Level AANew in 2.2

  • Press Tab once when the page loads. A “Skip to main content” link should appear. Without it, keyboard users must tab through every menu item on every page.

    WCAG 2.4.1 · Level A

  • WCAG 2.4.4 · Level AHow to fix it

Page structure

0 of 3

The hidden labels that let screen readers describe a page.

  • Look at the browser tab. Each page should have a title that says what it is, for example “Opening hours | Corner Cafe”, not just the business name on every page.

    WCAG 2.4.2 · Level AHow to fix it

  • Each page should have one main heading, with sub-headings below it that do not skip levels. Use heading styles, not just bigger bold text.

    WCAG 1.3.1 / 2.4.6 · Level AHow to fix it

  • Ask your website builder or developer to confirm the page language (for example English or French) is set. Screen readers use it to choose the right pronunciation.

    WCAG 3.1.1 · Level AHow to fix it

Forms and buttons

0 of 4

Where visitors enquire, sign up, or buy.

  • Look at your contact and checkout forms. A label such as “Email” should stay visible above or beside each field, not only appear as grey placeholder text that vanishes when you type.

    WCAG 1.3.1 / 3.3.2 · Level AHow to fix it

  • Check icon-only buttons, such as a search magnifier, a menu icon or a close cross. A screen reader should announce “Search”, “Menu” or “Close”, not just “button”.

    WCAG 4.1.2 · Level AHow to fix it

  • Submit a form with an empty required field. The message should name the field and say how to fix it, for example “Enter an email address”. A red border alone is not enough.

    WCAG 3.3.1 · Level A

  • Go through a checkout or booking flow. If an address or name was already given earlier in the same process, it should be filled in automatically or easy to pick again.

    WCAG 3.3.7 · Level ANew in 2.2

Touch, help and sign-in

0 of 4

Newer WCAG 2.2 checks for phones, help and logging in.

  • On a phone, try tapping small links, close buttons and icons with your thumb. Targets should be at least 24 by 24 pixels, or have enough space around them, and bigger is kinder.

    WCAG 2.5.8 · Level AANew in 2.2How to fix it

  • If your site has sliders, drag-to-reorder lists or maps, check there is another way, such as buttons or typing a value, for people who cannot drag.

    WCAG 2.5.7 · Level AANew in 2.2

  • On your login page, check that people can paste a password, use a password manager, or log in with an email link. Avoid asking people to retype characters or solve puzzles with no alternative.

    WCAG 3.3.8 · Level AANew in 2.2

  • If you offer a contact link, phone number or chat button, check it appears in the same spot on every page, such as the header or footer.

    WCAG 3.2.6 · Level ANew in 2.2

This is a manual spot check based on WCAG 2.2 Level AA, not a full audit and not legal advice. Check a few different pages, such as your home page, a contact or checkout page, and a page with a lot of text.

How to use this checklist

Open your site in one window and this list in another. Work down the list one item at a time, and tick it when it passes or does not apply. For anything you cannot tick, use the “How to fix it” link, or pass it to the person who looks after your website. The contrast checker helps with colours, and the statement generator helps once you know where you stand.

A manual check finds things a scanner cannot, such as whether an image description makes sense. A scanner finds things you would never spot by eye, such as a missing label buried in the code. Use both.

Questions people ask

Is this a full WCAG audit?

No. It is a quick manual check of 25 of the most common things, based on WCAG 2.2 Level AA. A full audit tests every page type with several assistive technologies and is done by an expert. Use this list to catch the obvious problems yourself, and use an expert if you need a formal report.

What is the difference between WCAG A, AA and AAA?

They are three levels of the same standard. Level A covers the most basic barriers, AA is the target most laws and policies point to, and AAA is the strictest and is not expected for a whole site. This checklist covers items from A and AA, which together are what most people mean by "WCAG 2.2 AA".

What is new in WCAG 2.2?

WCAG 2.2 added nine success criteria. Of these, this list includes Focus Not Obscured, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication. Items from 2.2 are marked "New in 2.2".

Should I tick items that do not apply to my site?

Yes. If your site has no videos, for example, tick the captions item because there is nothing to fix. Tick an item when it passes or does not apply, and leave it open when it needs work.

Will ticking everything make my site compliant?

Not on its own. A manual spot check on one or two pages cannot prove that a whole site meets WCAG, and no automated tool can either. A finished checklist is a good sign, but it is not a guarantee or legal advice.

Are my ticks saved or sent anywhere?

They are saved only in your own browser, so you can come back later on the same device. Nothing is uploaded, and there is no sign-up. Clearing your browser data removes them.

What should I do after I finish the checklist?

Fix the items you left open, starting with the ones that affect the most visitors, such as faint text, missing image descriptions and links with no name. Then run a scan to catch problems a manual check misses, and repeat after big changes to your site.

Let a scan do the part you cannot see

A free scan checks your page against WCAG 2.2 and gives you a plain-English list of what to fix.

No account needed. Takes about 30 seconds.