WCAG 2.2 for Small Business Websites: The Checks That Matter Most
Accessibility can feel like a huge, technical subject, and the Web Content Accessibility Guidelines (WCAG) do run to dozens of success criteria. But most small business websites are a handful of page types: a homepage, service pages, a contact or quote form, maybe a booking or checkout flow. On those pages, a short list of checks catches the majority of the barriers real visitors run into.
This guide focuses on WCAG 2.2, the current version published by the W3C in October 2023. It covers what changed in 2.2, the checks worth doing first (contrast, keyboard focus, forms, alt text and tap targets), and quick tests you can run yourself without special software. It is practical guidance, not legal advice.
Key facts
- 4.5:1 — Minimum contrast for normal text under WCAG 1.4.3 (3:1 for large text)
- 24×24 px — Minimum pointer target size in WCAG 2.2's new 2.5.8, with spacing exceptions
- 9 new — Success criteria added in WCAG 2.2; 4.1.1 Parsing was removed
- Oct 2023 — When WCAG 2.2 became a W3C Recommendation
What WCAG 2.2 Is and Why It Matters
WCAG is the W3C's set of testable success criteria for making web content usable by people with disabilities, including people who are blind or have low vision, people who use a keyboard instead of a mouse, and people with cognitive or motor impairments. Each criterion has a level: A (the basics), AA (the level most policies point to) and AAA (stricter, not usually required for whole sites).
WCAG 2.2 builds on 2.1 rather than replacing it. The W3C says the 2.0 and 2.1 criteria are essentially the same in 2.2, apart from 4.1.1 Parsing, which was removed as obsolete. So if you meet WCAG 2.2 AA, you also cover what 2.1 AA asks for.
Where the law fits in
In the US, the Department of Justice's web guidance says businesses open to the public must make the goods and services they offer online accessible. It also says DOJ has no regulation setting detailed technical standards for those businesses, and it points to WCAG and Section 508 as helpful guidance. A separate 2024 DOJ rule for state and local governments adopts WCAG 2.1 Level AA. If you have specific legal questions, talk to a lawyer; for building and fixing a site, WCAG 2.2 AA is a sensible, well-documented target.
The Nine New Criteria in WCAG 2.2
WCAG 2.2 added nine success criteria. Six are at levels A or AA, which are the ones most small sites should plan for:
- 2.4.11 Focus Not Obscured (Minimum), AA. When something receives keyboard focus, it must not be completely hidden by content you added, such as a sticky header, cookie banner or chat widget.
- 2.5.7 Dragging Movements, AA. Anything that works by dragging (a slider, a sortable list, a map) must also work with a single click or tap, unless dragging is essential.
- 2.5.8 Target Size (Minimum), AA. Buttons and other pointer targets should be at least 24 by 24 CSS pixels, or have enough space around them.
- 3.2.6 Consistent Help, A. If you repeat help options on several pages (phone number, contact link, chat, FAQ), keep them in the same relative order.
- 3.3.7 Redundant Entry, A. Don't make people type the same information twice in one process. Fill it in for them or let them select it.
- 3.3.8 Accessible Authentication (Minimum), AA. Logging in must not depend on a memory or puzzle test unless there is an alternative or help, such as allowing password managers and paste.
The other three (2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance and 3.3.9 Accessible Authentication (Enhanced)) are AAA. They are good practice, especially a clear, thick focus outline, but not usually a requirement.
Check 1: Colour Contrast
Low contrast is one of the most common problems, and one of the easiest to fix. WCAG 1.4.3 asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. WCAG defines large text as at least 18 point, or 14 point bold.
WCAG 1.4.11 Non-text Contrast adds a 3:1 minimum for the parts of controls you need to see, such as input borders, icon buttons and focus indicators, against the colours next to them.
How to check
- Use a contrast checker or your browser's developer tools on body text, links, button labels, placeholder text and text over images.
- Watch for light grey text on white, white text on pale brand colours, and text laid over photos.
- Don't use colour alone to carry meaning. A red border on an error field needs a text message too. DOJ's guidance lists colour-only information as a common barrier.
Check 2: Keyboard Access and Visible Focus
WCAG 2.1.1 requires that all functionality works from a keyboard, and 2.4.7 requires a visible keyboard focus indicator. Many people navigate with a keyboard or a device that acts like one, and screen reader users rely on the same focus order.
The five-minute keyboard test
- Click in the browser's address bar, then put the mouse aside.
- Press
Tabto move forward andShift+Tabto move back through the page. - Check that you can reach every link, button, menu item and form field, and that you can always see where you are.
- Check the order makes sense and that you never get stuck inside a widget, video player or pop-up.
- Open the mobile menu, any dropdowns and the cookie banner with the keyboard, and close them again.
The new 2.2 part: focus that hides
Sticky headers, sticky footers, cookie banners and chat bubbles can sit on top of the element that has focus. Under 2.4.11, the focused item must not be entirely hidden. The W3C's suggested fix for sticky headers and footers is the CSS scroll-padding property, which keeps focused items clear of fixed overlays as the page scrolls. Never remove the browser's focus outline with outline: none unless you replace it with something at least as visible.
Check 3: Forms That Everyone Can Complete
For a small business, the contact or quote form is usually the most valuable thing on the site, so it deserves the most care.
- Real labels. WCAG 3.3.2 requires labels or instructions when content needs input. Use a visible
<label>tied to each field withforandid. Placeholder text alone disappears as soon as someone starts typing. - Clear errors. WCAG 3.3.1 says that when an error is detected, the field in error is identified and the error is described in text. "Please enter a phone number with area code" helps; a red outline alone does not. Keep what the person already typed.
- Required fields marked in text, not just with colour.
- Autocomplete. WCAG 1.3.5 asks that fields collecting personal information have a purpose that can be determined by software. In practice, add
autocompletevalues such asname,emailandtel, which also lets browsers fill the form for people. - No retyping (3.3.7). In multi-step forms or checkouts, offer a "same as billing address" option instead of asking twice.
- Spam protection that doesn't block people. A puzzle CAPTCHA can be a cognitive test. Honeypot fields and low-friction checks are kinder to every visitor.
Check 4: Images, Headings and Tap Targets
Alt text
WCAG 1.1.1 requires a text alternative that serves the same purpose for non-text content. Describe what the image means in context: a team photo might be "Our three technicians outside the workshop". A purely decorative image should have an empty alt="" so screen readers skip it. The W3C's Easy Checks also advise against starting alt text with "image of", because screen readers already announce it as an image. A logo that links home can simply use the business name.
Headings and page titles
Give every page one clear <h1> and use <h2> and <h3> in a logical order instead of picking heading tags for their size. Make each page title unique and descriptive, with the key words first. Screen reader users often jump between headings to scan a page, much like sighted visitors skim.
Tap targets (new in 2.2)
Under 2.5.8, pointer targets should be at least 24 by 24 CSS pixels. Smaller targets can still pass if there is enough space around them: the W3C's test places a 24 px circle on each small target, and the circles must not overlap another target or each other's circles. Links inside a sentence are exempt. Check social icons in the footer, close buttons on pop-ups, carousel dots and tightly packed mobile menus.
A Practical Order of Work
If you are reviewing an existing site, this order gets the most value for the time spent:
- Run the keyboard test on the homepage, one service page and the contact form.
- Fix contrast in your global styles first (body text, links, buttons), so every page improves at once.
- Fix the main form: labels, error messages, autocomplete and a keyboard-friendly submit.
- Review alt text on key images and set decorative images to empty alt.
- Check the 2.2 items: focus under sticky elements, footer icon sizes, consistent placement of contact options and any login or multi-step flow.
- Run an automated checker to catch what you missed, such as missing labels or alt attributes.
Automated tools are useful, but the W3C is clear that they can't judge everything. A tool can tell you alt text is missing; it can't tell you whether the alt text makes sense. Passing quick checks does not mean a page is fully accessible, so for a thorough review use the W3C's evaluation methodology or an expert, and ideally test with people who use assistive technology.
Write it down
Keep a short note of what you checked, when, and what you fixed. It helps the next person who works on the site, and it keeps accessibility part of routine maintenance rather than a one-off project.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- W3C WAI: What's New in WCAG 2.2
- W3C WAI: Understanding Target Size (Minimum)
- W3C WAI: Understanding Focus Not Obscured (Minimum)
- W3C WAI: Easy Checks, A First Review of Web Accessibility
- ADA.gov: Guidance on Web Accessibility and the ADA
- ADA.gov: Fact Sheet on the 2024 Web and Mobile App Accessibility Rule for State and Local Governments
Related reading
Frequently asked questions
Is WCAG 2.2 a legal requirement for my small business website?
WCAG itself is a technical standard, not a law. In the US, DOJ guidance says businesses open to the public must make their online goods and services accessible but does not set a detailed technical standard for them, and it points to WCAG as helpful guidance. A 2024 DOJ rule for state and local governments adopts WCAG 2.1 AA. For legal questions about your business, speak to a lawyer.
If my site meets WCAG 2.1 AA, what else do I need for 2.2?
Mostly the new A and AA criteria: focus not hidden by sticky elements, alternatives to dragging, 24 by 24 pixel targets or enough spacing, consistent placement of help, no redundant entry in processes, and login that does not rely on a memory or puzzle test. 4.1.1 Parsing was removed, so it no longer applies.
Can an accessibility overlay or plugin make my site compliant?
Automated tools can find some issues, such as missing alt attributes or labels, but the W3C notes they cannot judge everything, like whether alt text is meaningful. Fixing the underlying HTML, colours and forms, and testing with a keyboard and real users, is the reliable route.
Want a site that works for every visitor?
BuiltToWinWeb builds custom small business websites with clean, accessible HTML and can review your current site against these checks. Get a free quote.
Get a free quote