This article explains accessibility standards in plain terms and is not a substitute for legal advice. If your business faces a compliance complaint or operates across multiple jurisdictions, consult a qualified accessibility professional.
Quick answer: A practical WCAG 2.2 compliance checklist for small businesses covers color contrast, keyboard navigation, image alt text, form labeling, and four new 2026-relevant criteria: focus visibility, touch target size, dragging alternatives, and accessible authentication. Most sites fail on a handful of fixable, recurring issues rather than obscure edge cases.
I’ll be direct about something most accessibility guides avoid saying plainly: nearly every small business website has accessibility problems right now, and that’s not a judgment on any one business owner. It’s the industry-wide norm.
Why This Matters More Than the Statistics Suggest
According to WebAIM’s 2026 Million report, 95.9% of the top one million homepages had detectable WCAG 2 failures, an increase from the previous year. Low-contrast text alone appeared on 83.9% of homepages tested, making it the single most common accessibility issue found.
That’s not a niche problem affecting a handful of poorly built sites. It’s the default state of the modern web, which means your competitors likely have the same gaps you do. However, that doesn’t make fixing them optional, since accessibility requirements increasingly carry legal weight, not just good practice value.
What Is WCAG 2.2, and Why Does the Version Number Matter?
The W3C’s official WCAG 2.2 standard is the current international benchmark for web accessibility, published in October 2023. It builds on WCAG 2.1 by adding nine new success criteria and removing one obsolete one, bringing the total to 87 testable criteria across four principles: perceivable, operable, understandable, and robust.
If your last accessibility audit referenced WCAG 2.1, you’re working from an outdated checklist. Regulations including the European Accessibility Act and updated U.S. Section 508 guidance now reference WCAG 2.2 specifically, so an older audit may miss requirements regulators actually check for today.
The Practical Checklist: What to Check First
Color Contrast
Text needs a contrast ratio of at least 4.5:1 against its background for normal text, and 3:1 for large text, to meet Level AA. Since low contrast is the single most common failure found across homepages, this is worth checking first, before anything else on this list.
Image Alt Text
Every meaningful image needs a text description explaining what it shows, not filler text like “image1.jpg.” Decorative images that add nothing informative can be marked to skip screen readers entirely, but genuinely informative images need real, specific descriptions.
Keyboard Navigation
Every interactive element, links, buttons, forms, needs to work without a mouse. Try tabbing through your entire site using only your keyboard. If you get stuck anywhere, or can’t tell where focus currently sits, that’s a real barrier for keyboard and screen reader users.
Form Labels and Error Messages
Every form field needs a properly associated label, not just placeholder text that disappears once someone starts typing. Error messages should clearly state what went wrong and how to fix it, not just flash a red border with no explanation.
What’s New in WCAG 2.2 That You Probably Haven’t Checked Yet
Focus Not Obscured
If a sticky header, cookie banner, or chat widget covers the currently focused element when someone tabs through your site, that’s a new 2.2 failure. This specifically targets a problem that’s become more common as sites add more overlapping UI elements.
Target Size (Minimum)
Clickable elements, buttons, links, form controls, need to be large enough for users with motor impairments to tap accurately, generally at least 24×24 pixels. Small, tightly packed navigation icons or social media links often fail this criterion without anyone noticing.
Dragging Movements
Any interaction requiring a drag gesture, a slider, a reorderable list, needs a non-dragging alternative available. That means a simple click-based option alongside any drag-and-drop feature, not drag-only functionality.
Accessible Authentication
Login processes can’t rely solely on cognitive tests, like solving a puzzle or transcribing distorted text, without an accessible alternative. This specifically targets users with cognitive disabilities who may struggle with certain CAPTCHA styles.
The Nuance Most Checklists Skip: You Don’t Need Level AAA
Here’s something worth saying plainly, because plenty of accessibility vendors imply otherwise. WCAG defines three conformance levels: A, AA, and AAA. Nearly every regulation that actually matters, the European Accessibility Act, U.S. Section 508, EN 301 549, requires Level AA, not the more demanding AAA tier.
Chasing AAA conformance for a small business site usually means spending disproportionate time and money on requirements that aren’t legally required and may not meaningfully improve usability for most visitors. Target AA thoroughly and correctly. Treat AAA as optional polish, not a compliance requirement.
This overlaps directly with obligations under the European Accessibility Act, which specifically references WCAG 2.1 AA as its current benchmark, with WCAG 2.2 increasingly cited as the practical standard regulators expect going forward.
The Mistake I See Most: Fixing Contrast and Alt Text, Then Stopping
Here’s my honest take. Businesses that do address accessibility often stop after the two most visible fixes, contrast and alt text, and assume they’re done. Keyboard navigation and form accessibility get skipped because they’re harder to notice without actually testing them.
A genuinely useful audit tests all four categories above, not just the two easiest to spot visually. If your developer only mentions contrast and alt text when discussing accessibility, ask specifically about keyboard navigation and the new 2.2 criteria too.
This kind of thorough audit often overlaps with general site health work I cover in 10 website mistakes costing small businesses thousands, since accessibility gaps frequently show up alongside other maintenance issues on sites that haven’t had a technical review in a while.
How Does This Connect to Other Compliance Requirements?
Accessibility rarely sits alone as a compliance concern anymore. If you’re auditing your site for WCAG 2.2, it’s worth checking your cookie consent setup at the same time, since UK and EU privacy rules have also changed significantly. I’ve covered the current requirements in UK cookie consent rules 2026, worth reviewing alongside this checklist if your site serves UK or EU visitors.
Frequently Asked Questions
What is WCAG 2.2, and how is it different from 2.1?
WCAG 2.2 is the current W3C accessibility standard, adding nine new success criteria to WCAG 2.1, including focus visibility, touch target size, dragging alternatives, and accessible authentication requirements.
Do small businesses need to meet WCAG 2.2 Level AAA?
No. Nearly every regulation requiring WCAG compliance specifies Level AA, not AAA. Targeting AA thoroughly satisfies most legal requirements without the disproportionate cost of pursuing AAA conformance.
What’s the most common accessibility failure on business websites?
Low contrast text is the most common issue, found on the vast majority of tested homepages according to WebAIM’s ongoing research, making it a good first check for any audit.
Can I check WCAG 2.2 compliance without hiring a specialist?
Basic checks, contrast ratios, alt text, keyboard navigation, can be done manually or with free tools. However, a thorough audit covering all criteria, including newer 2.2 requirements, benefits from professional review.
Does an automated accessibility scanner catch everything?
No. Automated tools catch many issues but miss context-dependent problems like whether alt text is actually meaningful or whether keyboard navigation genuinely works end to end. Manual testing remains necessary.
Is WCAG 2.2 legally required for my website?
It depends on your jurisdiction and business type. Regulations like the European Accessibility Act and U.S. Section 508 reference WCAG standards directly, so legal requirements often apply even without explicit mention of “WCAG 2.2” itself.
Want Your Site Checked Against This Checklist?
If you’re not sure how your website measures up against WCAG 2.2, message me on WhatsApp and send me your link. I’ll give you a straight technical read on what actually needs fixing.