WCAG 2.2 Compliance for Small Business Websites: A 2026 Practical Guide
A practical guide to WCAG 2.2 compliance for small business websites in 2026 — covering the nine new success criteria, legal requirements, testing tools, and a prioritized checklist to achieve Level AA.
What WCAG 2.2 actually is
Web Content Accessibility Guidelines, maintained by the W3C, published as a formal recommendation. Version 2.2 landed in October 2023. It is additive: a site that conforms to 2.2 also conforms to 2.1 and 2.0.
It added nine success criteria, and removed one. That removed one is worth knowing about, because it's the criterion most developers spent years obsessing over: 4.1.1 Parsing, the requirement for perfectly valid markup, is obsolete. Modern browsers and assistive technology cope with imperfect HTML, so it was retired. If an audit flags it as a failure, the audit is out of date.
The nine additions lean toward cognitive accessibility and mobile use, which is where the largest share of unaddressed barriers actually sit.
The four principles, unchanged, are remembered as POUR: Perceivable, Operable, Understandable, Robust. They're a useful sanity check; they're not a checklist.
The legal position, corrected
This is where most small business guides are loose, and the looseness leads people to spend money on the wrong things.
Europe: the European Accessibility Act applies from 28 June 2025 to a defined list of products and services, including e-commerce, banking, transport, and ebooks, for businesses above a small-enterprise size threshold. It references a harmonised standard based on WCAG 2.1 AA. If you sell into the EU above the threshold, this is now a live obligation rather than a forecast.
United States, public sector: the Department of Justice finalised a rule in 2024 requiring state and local government entities to meet WCAG 2.1 AA. If you supply or work with a public body, expect accessibility in the procurement requirements.
United States, private businesses: there is no federal regulation specifying a technical standard for private websites. The DOJ never issued one for Title III after withdrawing its rulemaking in 2017. What exists instead is litigation: thousands of lawsuits and demand letters a year, in which settlements consistently reference WCAG 2.1 or 2.2 AA as the benchmark, plus a growing set of state laws.
That distinction matters. It means for a private US business the risk is being sued, not being inspected, and the practical defence is conformance to WCAG AA plus a documented effort. Anyone telling you a specific federal law requires your website to be WCAG 2.2 compliant right now is overselling.
The numbers, hedged appropriately. Industry trackers have counted roughly four thousand web accessibility lawsuits a year in the US federal courts in recent years, concentrated in e-commerce and in a handful of states. Settlements vary enormously; the small ones run to a few thousand dollars plus legal fees and remediation, and a demand letter is cheaper still for the claimant to send. I'd treat any specific average as indicative rather than reliable.
Why small businesses get targeted
Not because they're unlucky. Because:
- They have forms and checkouts that are hard to operate, which is where complaints originate.
- They rarely have anyone responsible for accessibility.
- They respond to a letter quickly because they have no legal team, which makes them attractive targets.
The pattern is unglamorous: a demand letter citing specific failures on a specific flow, typically a booking or payment form.
The nine new criteria, and which ones apply to you
Most of the additions are relevant to a small business site. Here's the practical subset.
3.2.6 Consistent Help (Level A)
If you offer help, such as a phone number, a chat link, or a contact route, it must appear in the same relative place on every page.
Easy win: put the phone number in the same header position site-wide.
3.3.7 Redundant Entry (Level A)
Don't ask for the same information twice in one process. If someone enters their address on step one, don't ask again on step three.
This one fails constantly in multi-step forms and checkouts, and it costs completions from everybody, not only disabled users.
3.3.8 Accessible Authentication (Level AA)
No cognitive function test for logging in, unless an alternative or a mechanism to assist exists. In practice:
- Allow paste into password fields. Blocking paste breaks password managers and is a failure.
- Allow password managers to work.
- Don't require solving a puzzle to log in.
- Support copying a one-time code, and don't time it out aggressively.
This matters for every site with a customer account.
2.4.11 Focus Not Obscured (Level AA)
The element with keyboard focus must not be entirely hidden by sticky headers, footers, cookie banners, or chat widgets.
Very common in modern layouts, and trivially fixed: add scroll padding so focused elements land below the sticky header.
2.5.7 Dragging Movements (Level AA)
Anything requiring a drag needs a single-pointer alternative. Sliders, sortable lists, carousels, image croppers.
2.5.8 Target Size Minimum (Level AA)
Interactive targets at least 24 by 24 CSS pixels, with exceptions for inline links and where an equivalent control exists elsewhere.
Small close buttons on modals and tightly packed footer links are the usual failures.
The others
2.4.12 Focus Not Obscured (Enhanced) and 2.4.13 Focus Appearance are AAA, so they're optional unless you're targeting AAA. The criteria above cover the practical ground.
The practical path to AA
You're probably aiming at WCAG 2.1 AA or 2.2 AA. AA is what settlements reference, what procurement asks for, and what's achievable without a specialist budget.
Step 1: Get a real baseline
Run an automated scan on your templates. It will find the mechanical failures: missing labels, contrast, missing language, empty links. It will also miss most usability failures, so treat its output as a starting list, not a verdict.
Step 2: Fix the top twenty by hand
Across nearly every small business site the same twenty issues appear:
- Form inputs without labels.
- Placeholder-only fields.
- Insufficient body text contrast.
- Missing focus indicators.
- No skip link.
- Heading levels skipped or duplicated h1s.
- Images without alt, or with useless alt like "image1.jpg".
- Link text like "read more" repeated.
- Empty links and buttons.
- Custom dropdowns that don't work with a keyboard.
- Modals that don't trap or return focus.
- Error messages that are colour only.
- Error messages that clear the form.
- Video without captions.
- Tables without header cells.
- Page language not declared.
- Sticky headers covering focused elements.
- Touch targets under 24px.
- Carousels that auto-advance with no pause.
- No accessibility statement or contact route.
Twenty fixes, mostly in shared components, which is why they multiply.
Step 3: Test the money flow manually
Keyboard only, then with a screen reader, through your enquiry or booking or checkout flow. This is the flow that produces complaints, and it's the one automated tools judge worst.
Step 4: Write a statement that's true
What standard you target, what's known to be non-conforming and when you'll fix it, how to report a problem, and who replies. A generated badge from an overlay vendor is not this.
Step 5: Keep it in the build
Add accessibility checks to your design and development process, not as a one-off project. The failures return with every new component otherwise.
What not to buy
An overlay. It doesn't make you compliant, and in the US the FTC has already settled with a major vendor over marketing claims to that effect. The article on overlays covers this in detail.
A "certification". There's no accredited body that certifies websites. An audit by a reputable firm is a professional assessment, not a certificate.
A generated accessibility statement that claims full conformance when the site has a dozen known failures. A false statement is worse than none.
Where to start
Keyboard-test your enquiry form this week, then fix labels, focus, and contrast. That's three changes, all in shared components, and it moves you meaningfully toward AA.
A free digital presence audit on Webcheckhub covers accessibility basics within website health, which shows which of the twenty items above are present on your own site. When you want a documented audit and the remediation done, Solutions Elites handles WCAG conformance work for small businesses.
Sources and further reading
These references were used to check the facts in this article. Quoted or adapted material is used under the licence shown beside each source, with credit to the original publisher.
Watch the explainer
Videos are embedded with YouTube's official player and credited to their creators. We never re-host third-party video; playback and reuse follow the licence stated by the owner.
Credited to its creator and original publisher; playback follows the creator's own terms.
5
Core Areas Audited
28+
Checkpoints Scanned
100
Free — No Credit Card
Run your free digital presence audit
See exactly where your business stands across Google, website, social media, SEO, and conversion — with a client-ready report.
Check Your Digital Presence — Free
Webcheckhub Editorial Team
PublisherPublished by Webcheckhub, a digital presence audit platform. Our articles are researched and produced by our editorial team, with AI assistance for drafting, and reviewed for accuracy against current industry standards and Google's official guidelines.
© 2026 Webcheckhub. All rights reserved. This article is original content and may not be reproduced without written permission.
Digital growth partner for Webcheckhub
Contact us
Questions about this guide, or want your website, Google profile or automations handled by specialists? Reach out to the Solutions Elites team and we'll reply with a straight answer.
