WCAG 2.2 Is Not a Checkbox — It's a Liability Ladder
Web accessibility lawsuits against small businesses hit a record pace in 2024 and have continued climbing into 2026, yet most small business owners still treat WCAG as something only enterprise teams worry about. That gap is exactly where litigation lives. This guide skips the generic awareness lecture and goes straight to what WCAG 2.2 specifically added, which failures generate the most legal exposure, and the handful of fixes that resolve the vast majority of real-world compliance gaps without requiring you to tear your site down and start over.
What Changed in WCAG 2.2 (Compared to 2.1)
WCAG 2.2 became the official W3C recommendation in October 2023, and by 2026 it is the version courts and demand letters reference. If your developer or agency says your site was "built to WCAG 2.1," that is no longer good enough as a defense. Here are the criteria that are new or meaningfully changed:
2.4.11 — Focus Appearance (Minimum) — Level AA
This is the big one for most small business sites. WCAG 2.2 now requires that keyboard focus indicators meet minimum size and contrast thresholds — not just that they exist. The focus indicator must have an area of at least the perimeter of the component times 2 CSS pixels, and the focused state must have a contrast ratio of at least 3:1 against the unfocused state.
In plain English: that thin blue dotted line browsers add by default often fails. If your CSS resets focus styles (a very common practice from the 2010s), you are almost certainly non-compliant. This is also one of the most frequently cited issues in accessibility demand letters because it is trivially easy for plaintiffs' attorneys to verify with keyboard testing.
2.5.7 — Dragging Movements — Level AA
Any functionality that uses a dragging gesture — think sliders, sortable lists, drag-to-reorder — must also be achievable with a single pointer action that does not require dragging. If you have a price range slider, a drag-to-upload zone, or a sortable photo gallery, you need an alternative path.
2.5.8 — Target Size (Minimum) — Level AA
Interactive targets (buttons, links, form controls) must be at least 24×24 CSS pixels — or have sufficient spacing around smaller targets so that the spacing brings the total area to 24×24. This is a softer version of the AAA criterion that required 44×44, but it still catches a lot of small icon buttons, close icons on modals, and footer links that designers shrink for aesthetic reasons.
3.2.6 — Consistent Help — Level A
If you offer a help mechanism (a phone number, a contact form, a chat widget) on more than one page, it must appear in the same relative location on every page where it appears. Moving your phone number from the header on the homepage to the footer on your contact page violates this criterion.
3.3.7 — Redundant Entry — Level A
Within a single session, users should not have to re-enter information they already provided. Multi-step forms that ask for a billing address and then ask for it again on the confirmation step are non-compliant. Auto-populate or show the previously entered value for confirmation.
The Pareto Fix List: 20% of the Work, 80% of the Coverage
A full WCAG 2.2 Level AA audit can surface dozens of issues. But from a litigation-risk and user-impact perspective, the following fixes are where the leverage is. Address these first and you dramatically reduce your exposure before you spend a dollar on a comprehensive audit.
Fix 1: Restore and Upgrade Focus Styles (High Priority)
Search your CSS for outline: none or outline: 0 and remove those declarations on interactive elements. Then add an explicit focus style that meets 2.4.11's contrast and size requirements. A safe starting point:
- Use
:focus-visible(not just:focus) so the indicator appears for keyboard users but not on mouse click. - Set
outline: 3px solid #005FCC; outline-offset: 2px;— a high-contrast blue that passes 3:1 against most backgrounds. - Test with the Tab key on every interactive element in your navigation, forms, and modals.
This single fix addresses the most commonly cited WCAG 2.2 failure in demand letters and costs under an hour of developer time on most sites.
Fix 2: Audit and Enlarge Small Touch Targets
Open your site on a mobile device and look for any tap target that feels cramped. Common offenders: social media icon links in footers, close (×) buttons on popups, and navigation hamburger icons. Use your browser's DevTools to inspect their computed size. Anything under 24×24 CSS pixels needs either padding added or the element enlarged. On most sites this affects 5–10 elements and takes under two hours.
Fix 3: Add Alternative Inputs for Any Drag Interaction
Audit your site for drag-dependent UI. If you have a price slider, add text inputs where the user can type the minimum and maximum values. If you have a drag-to-reorder list, add up/down arrow buttons. Most small business sites do not have heavy drag interactions — but if you do, this is a new AA requirement as of WCAG 2.2 and it will be in any demand letter that a plaintiff generates by testing your site with a switch device.
Fix 4: Pin Your Help Mechanism to a Consistent Location
Decide where your primary contact option lives — header, footer, or a sticky element — and make sure it appears in that same position on every page. This also happens to be a good UX decision independent of compliance: users should never have to hunt for how to reach you.
The Fictional Plumbing Demo is a good example of this done right — the contact form CTA appears consistently in the same position across every section, so there is no ambiguity about how to get in touch.
Fix 5: Audit Image Alt Text (Still the #1 Cited Failure Across All WCAG Versions)
This predates WCAG 2.2 but remains the most commonly cited issue in ADA website compliance demand letters in 2026. Every <img> tag needs an alt attribute. Decorative images get alt="". Informational images get a meaningful description. Images that are links describe the destination, not the image. Run your site through the free WAVE tool (wave.webaim.org) right now — missing alt text will show up as red flags immediately.
Fix 6: Check Color Contrast on Body Text and UI Components
WCAG 1.4.3 (Level AA) requires 4.5:1 contrast for normal text and 3:1 for large text. WCAG 1.4.11 extends the 3:1 requirement to UI components and focus indicators. Use the WebAIM Contrast Checker to test your primary text color against your background. Gray-on-white text is the most common failure on small business sites — a design choice that looks clean but fails compliance and alienates low-vision users.
Fix 7: Ensure Form Labels Are Programmatically Associated
Every form input needs a <label> element with a matching for attribute that corresponds to the input's id. Placeholder text alone is not a label — it disappears when the user starts typing and is not consistently announced by screen readers. This fix is critical for contact forms, booking forms, and any lead capture on your site.
What a Compliance-Baseline Site Actually Looks Like
Understanding these requirements abstractly is useful, but seeing them implemented in a real site is better. The Fictional Law Firm Demo shows what a professionally structured small business site looks like when accessibility fundamentals are baked into the design from the start — semantic heading hierarchy, sufficient contrast, clearly labeled navigation, and a consistent help mechanism in the header on every page.
These are not heroic engineering achievements. They are design decisions made at build time that cost nothing extra when done from the beginning and cost real money to retrofit later. That is the argument for getting accessibility right the first time rather than patching it after a demand letter arrives.
The Practical Reality of ADA Website Compliance for Small Businesses in 2026
There is no "safe harbor" threshold in U.S. law that says "if you hit X% of WCAG criteria, you are protected." The ADA requires "effective communication" and "equal access," and courts have increasingly interpreted that to mean WCAG 2.2 Level AA is the operative standard. That said, courts and plaintiffs also respond to good-faith effort. A site with documented remediation work in progress is treated very differently from a site with zero accessibility consideration.
The practical guidance for small business owners in 2026:
- Do the Pareto fixes above now. They cost little, reduce the most common failure points, and demonstrate intent.
- Get a basic audit annually. The free WAVE tool and axe browser extension catch automated failures. A human tester with a screen reader catches the rest.
- Publish an accessibility statement. A simple page at
/accessibilitythat describes your commitment, lists known issues, and provides a contact method for users who encounter barriers is not legally required but is consistently viewed favorably in legal proceedings. - Document your fixes. Keep a changelog of accessibility improvements with dates. If you ever receive a demand letter, evidence of ongoing remediation changes the conversation.
When You Are Rebuilding: Start With an Accessible Foundation
If your current site is deeply non-compliant — broken heading structure, no landmark regions, no focus styles at all — retrofitting may cost more than rebuilding. Services like SiteGlowUp generate redesigned sites that include structured semantic HTML, LocalBusiness schema, and proper heading hierarchy out of the box, giving you a cleaner foundation to apply the accessibility fixes above rather than fighting against years of accumulated technical debt. The $299 one-time publish fee and $10/month hosting makes that baseline accessible to businesses that cannot afford a five-figure rebuild.
The Bottom Line on WCAG 2.2 Small Business Compliance
WCAG 2.2 added three new Level AA requirements — focus appearance, dragging movement alternatives, and minimum target size — on top of the existing criteria that small business sites already commonly fail. You do not need to solve all of them simultaneously. Fix your focus styles, enlarge small targets, audit your alt text, check your contrast, and label your form inputs. Those five categories cover the vast majority of issues cited in real accessibility demand letters and represent a realistic weekend of remediation work on most small business sites.
Accessibility is not a compliance burden to minimize. It is a usability investment that benefits keyboard users, screen reader users, mobile users, and aging users — which together represent a significant portion of every small business's customer base. The fixes that protect you legally are the same fixes that make your site better for everyone.
