WCAG 2.2 AA for Small Business Websites: Softix Audit–Fix–Prove

Status: Draft only — do not publish until Salman confirms.

Published (planned): September 10, 2026 · Last updated: September 10, 2026 · Author: Softix

Category: Web Design and Development

If your marketing site, booking flow, or WordPress storefront still targets WCAG 2.1, you are one release behind the W3C’s current recommendation. Web Content Accessibility Guidelines (WCAG) 2.2 became a W3C Recommendation on 12 December 2024. It extends WCAG 2.1 with new success criteria—especially around keyboard focus, target size, authentication, and drag alternatives—while remaining backwards compatible: content that conforms to 2.2 also conforms to 2.0 and 2.1.

WCAG 2.2 AA small business website work is not a badge Softix stamps on your homepage. It is engineering remediation Softix implements and retests: find what fails on real pages, fix the highest-impact gaps (starting with WCAG 2.2 deltas), and keep retest evidence your team can reuse when a buyer, agency partner, or counsel asks what you did.

This guide is for U.S. SMB founders, marketing ops, and product owners who ship on WordPress or custom web stacks. Softix’s Audit–Fix–Prove sequence keeps the work scoped—and honest about what WCAG can and cannot claim.

What WCAG 2.2 AA means for an SMB site

WCAG 2.2 organizes guidance under four principles—perceivable, operable, understandable, robust—with testable success criteria at levels A, AA, and AAA. Most U.S. commercial and public-sector contracts that mention WCAG still land on Level AA: every Level A and Level AA criterion for the pages (and complete processes) in scope.

What is new in 2.2 (normative additions called out by W3C):

WCAG 2.2 also removes obsolete criterion 4.1.1 Parsing. If a policy still cites WCAG 2.0/2.1 Parsing, keep testing it for that policy—but W3C advises adopting 2.2 as the current target.

What Softix will not claim: Softix does not certify legal compliance with the ADA, Section 508, state laws, or any plaintiff’s demand letter. WCAG is a technical standard; legal exposure depends on facts, jurisdiction, and counsel. Softix delivers engineering remediation and retest evidence—not a guarantee that a court or regulator will accept your claim.

Softix Audit–Fix–Prove (why three steps beat a one-shot audit PDF)

Vendors love “accessibility audits” that dump 200 axe issues with no shipping plan. Softix sequences the work the way SMB web teams actually release:

Use Softix for sequencing. Use W3C WCAG 2.2 and the How to Meet WCAG 2.2 quick reference for normative detail.

Step 1 — Audit: axe/WAVE plus a real keyboard pass

Automation finds a lot; it does not replace a human keyboard and focus review. Softix’s baseline Audit:

1. Scope pages and processes. Home, landing, service, contact, checkout/booking, login, multi-step forms. Conformance covers full pages and complete processes.
2. Run axe and/or WAVE per template. Export dated reports; “0 issues” is not AA.
3. Keyboard-only pass. Tab nav, skip links, forms, modals, sticky/cookie/chat. Check focus order, visible focus (2.4.7), and focus not entirely covered (2.4.11).
4. Pointer/mobile spot-checks. Measure targets vs 24×24 (2.5.8); verify drag alternatives (2.5.7).
5. Auth and wizards. Flag puzzle CAPTCHAs and re-asked fields (3.3.8, 3.3.7).
6. Residual risk. Inventory third-party embeds (maps, chat, booking iframes) you do not control.

Softix judgment

If you only have one afternoon, Audit the conversion path first—not the blog archive. Softix pairs this with UX/UI design reviews when the issue is layout density (targets, sticky layers) rather than a missing alt.

Step 2 — Fix: prioritize WCAG 2.2 deltas on WordPress and custom sites

Fix order matters. Softix usually ships 2.2 Level AA deltas and keyboard blockers before polishing every decorative SVG.

Focus not obscured (2.4.11)

Sticky announcement bars, fixed CTAs, and cookie consent layers routinely cover the focused link at the top of the next section. Fixes Softix implements:

• Reserve space or offset scroll-margin so focused items clear fixed chrome.
• Ensure dismissible overlays do not trap or fully cover focus without a keyboard path.
• Retest with Tab after every marketing widget install—WordPress plugin updates reintroduce this weekly.

Target size minimum 24×24 (2.5.8)

Tiny social icons, pagination dots, and “×” closes fail on phones. Enlarge hit areas (padding counts), or space undersized targets so 24px-diameter circles do not intersect. Prefer visible 44px-class targets on primary CTAs even though AA’s minimum is 24px.

Accessible authentication (3.3.8)

Cognitive function tests—remember a password without paste, solve a distorted character CAPTCHA, type a one-time code without an assist—conflict with AA unless you provide an alternative or mechanism (password managers, copy/paste, passkeys, object recognition / personal content patterns W3C allows). Softix remediates login themes and plugins so password managers and paste work, and replaces puzzle-only gates where product risk allows.

Dragging alternatives (2.5.7)

Price range sliders, drag-to-reorder menus, and map pin drags need a non-drag path: number inputs, buttons, or select lists. Essential user-agent behavior is exempt; author-built drag UIs are not.

Redundant entry (3.3.7)

Checkout that retypes shipping after billing, or wizard steps that blank prior answers, fail Level A. Autofill or “same as previous” controls are the usual Softix fix on custom WordPress and custom form stacks.

Baseline AA hygiene still required

2.2 does not retire contrast (1.4.3), resize/reflow (1.4.4, 1.4.10), labels (3.3.2), name/role/value (4.1.2), or status messages (4.1.3). Softix folds those into the same Fix backlog when Audit surfaces them—especially on custom web design rebuilds where color systems and component libraries can fix dozens of pages at once.

Softix judgment

Prefer theme and component fixes over per-page Elementor patches. Coordinate with Core Web Vitals for small business websites so sticky/consent widgets are not “fixed” for LCP while re-breaking focus obscurity.

Step 3 — Prove: retest evidence, not a certificate

Prove is the folder Softix leaves you after remediation:

• Scope statement — URLs, templates, user agents, and date.
• Methods — automated tools used, keyboard procedure, sample assistive-tech spot checks if performed.
• Before/after — issue IDs closed, screenshots or short clips of focus paths, residual open items with owners.
• Third-party exceptions — embeds not under Softix control, with mitigation notes.
• Retest cadence — re-run Audit after major plugin, theme, or checkout changes (website maintenance & support is where this usually lives).

Optional public or contractual conformance claims have required components in WCAG 2.2 §5.3 (date, guidelines URI https://www.w3.org/TR/WCAG22/, level, page set, technologies relied upon). Softix can help you assemble accurate technical evidence; Softix does not sell a “WCAG certified” seal, and a Softix report is not a legal opinion.

SMB checklist — Audit–Fix–Prove

Audit

• [ ] Critical templates and full conversion processes listed
• [ ] axe and/or WAVE exports dated per template
• [ ] Keyboard pass: nav, forms, modals, sticky/cookie/chat
• [ ] Target-size and drag-alternative spot checks on mobile
• [ ] Login and multi-step forms reviewed for 3.3.8 / 3.3.7
• [ ] Third-party embeds inventoried

Fix

• [ ] Focus not entirely obscured by author UI (2.4.11)
• [ ] Primary pointer targets meet 24×24 or spacing exception (2.5.8)
• [ ] Drag widgets have single-pointer alternatives (2.5.7)
• [ ] Auth allows assist/alternative; paste and password managers work (3.3.8)
• [ ] Processes avoid needless re-entry (3.3.7)
• [ ] Contrast, labels, and visible focus regressions closed

Prove

• [ ] Retest pack saved (scope, methods, before/after, residuals)
• [ ] Owners assigned for open third-party gaps
• [ ] Retest scheduled after next theme/plugin release train

30-day plan for a typical WordPress SMB site

Limits and honesty checks

• WCAG is not the whole law. ADA Title III case law, state statutes, and federal procurement rules may impose different or additional expectations—talk to counsel for legal strategy.
• AAA is rarely a whole-site policy target. W3C notes AAA is not recommended as a general requirement for entire sites.
• Conformance is page- and process-scoped. A fixed homepage does not make checkout conforming.
• No fabricated scores. Softix does not invent “100% AA” claims, traffic lifts, or lawsuit statistics in this article.
• Tools change. Always verify current axe/WAVE rule packs against the WCAG 2.2 Recommendation.

FAQ

Is WCAG 2.2 required for every U.S. small business website?

No universal federal statute says “every SMB must meet WCAG 2.2 AA tomorrow.” Many contracts, education/government buyers, and risk programs reference WCAG AA. Softix treats 2.2 AA as the practical engineering target for new remediation work.

Does conforming to WCAG 2.2 also satisfy 2.1?

Yes for the WCAG model: W3C states content that conforms to 2.2 also conforms to 2.0 and 2.1. Policies that still name 2.1 can usually accept 2.2 as an alternate means—confirm with your contract language.

Can Softix “certify” my site as ADA compliant?

No. Softix provides remediation and retest evidence against WCAG success criteria. Legal compliance determinations belong with qualified counsel—not a web vendor badge.

Where should a five-page brochure site start?

Audit the contact and quote forms, then sticky header/cookie focus issues, then icon target sizes. Skip AAA experiments until AA on the conversion path is boringly solid.

What to do next

Read the WCAG 2.2 Recommendation, then run Softix’s Audit checklist on your highest-revenue templates. Fold Fix into the same release train as design-system and performance work—not a once-a-year PDF.

Softix helps U.S. SMB teams turn accessibility work into maintainable custom web design, WordPress development, UX/UI, and maintenance. For a scoped Audit–Fix–Prove engagement—not certification theater—let’s talk.

Before you commit runway, pressure-test Build vs Buy vs Customize with Softix’s SMB software TCO calculator.

---

Primary source cited: W3C Recommendation — Web Content Accessibility Guidelines (WCAG) 2.2 (12 December 2024), https://www.w3.org/TR/WCAG22/. Softix analysis is interpretive engineering guidance and not a W3C or legal certification.