Your executive director asks the obvious question: how much of that work do we have to redo? The answer is much simpler than you are probably imagining.
The Short Answer: Most of Your 2.1 Work Still Counts
WCAG 2.2 adds 9 new success criteria on top of 2.1. It does not replace anything — it extends. If you are already 2.1 AA compliant, you are looking at an incremental update, not a rebuild. Your color contrast fixes still work. Your keyboard navigation improvements still work. Your form label improvements still work. The new criteria address gaps that emerged since 2.1 was published in 2018, or edge cases that the earlier guidelines did not anticipate. You are not starting from zero.
What WCAG 2.2 Actually Adds (The Criteria That Matter for Associations)
Not all 9 new criteria matter equally to association websites. Here are the ones that do:
Focus Appearance (2.4.11, AA): When a member tabs through your event registration form, the focused element must have a visible indicator. Not a thin outline. Not a subtle highlight. A 3px minimum border or clear visual change. This matters because keyboard-only users need to know where they are in a form. Many association sites use browser defaults that do not meet the new minimum. You might have been compliant under 2.1, but 2.2 raises the standard. Some sites that use light gray outlines now need darker or thicker indicators. If your site uses custom form elements (common in member portals), the focus styles need to be custom-coded to meet the new specification.
Dragging Movements (2.5.7, AA): Any functionality that requires dragging must have a click or tap alternative. This affects drag-and-drop event scheduling, sortable committee member lists, interactive dashboards, or calendar builders. If your portal has drag-to-reorder features without keyboard alternatives, they violate 2.2. A member using only a keyboard cannot accomplish the same task. The fix is to add a context menu or buttons: "Move Up", "Move Down", "Remove" next to each item. It adds complexity to the UI, but it is required.
Target Size (2.5.8, AA): Interactive elements (buttons, links, form fields) must be at least 24×24 CSS pixels. Mobile navigation, footer links, densely packed event calendars, and volunteer sign-up buttons often fail this. A 24px minimum is larger than most sites use for secondary actions. Your site might have small icons for social media links or a condensed event list. Those now need to be larger or have a larger clickable area around them. This is particularly important for association sites where volunteer recruitment or event attendance relies on easy-to-click buttons.
Consistent Help (3.2.6, A): If your site has help mechanisms (chat widget, FAQ link, phone number), they must appear in the same location across pages. Many association sites move the help link between the header, footer, and sidebar depending on the template. This consistency requirement means you need to standardize where help is available. If your home page has a chat widget in the bottom right and your member portal has the FAQ link in the top right, you are violating 2.2. The fix is simple but requires discipline: decide on one location and enforce it everywhere.
Redundant Entry (3.3.7, A): If a member already entered information in a previous step (name, email, member ID), do not ask them to re-enter it. Multi-step event registration forms and renewal workflows frequently violate this. A member provides their email in step 1 and you ask for it again in step 2? That violates 2.2. The fix requires form architecture planning: you need to carry form data through all steps and use it to pre-fill fields in later steps. This is straightforward in modern web development, but it requires intentional design.
Accessible Authentication (3.3.8, AA): Login processes must not require cognitive function tests without alternatives. CAPTCHAs on member login pages are the most common violation. If you use a CAPTCHA to verify that it is a real person logging in, you need a phone call or email alternative. A member with vision impairment cannot pass a visual CAPTCHA. A member with dyslexia might struggle with distorted text recognition. Accessible authentication means offering multiple verification methods, not just the CAPTCHA.
Testing WCAG 2.2 Compliance: What the Audit Actually Involves
A WCAG 2.2 compliance audit for an association website typically covers 50-100 pages across the public site and any member portal. The audit involves manual testing and automated tool scanning. For the new 2.2 criteria specifically, testing focuses on these areas: keyboard navigation throughout the entire site, focus indicator visibility on every interactive element, target size measurement on buttons and links, help feature location consistency, form field pre-filling and data persistence, and authentication method alternatives.
An automated scanner can find about 40% of compliance issues. The remaining 60% require human testing — a person using only a keyboard, a screen reader user, a mobile user, and a designer checking visual contrast and focus indicators. For 2.2-specific criteria, the testing is more thorough because the criteria target subtle user experience issues that tools cannot detect reliably. That is why 2.2 compliance typically requires both automated scanning and manual testing. A tool alone will miss problems.
What It Costs to Update from 2.1 to 2.2
Most association sites can update in four to eight weeks for $5,000 to $15,000. If your site is already well-coded and well-structured, you are looking at the lower end. Most of the work is focus indicator updates (CSS modifications), target size adjustments on mobile navigation (mostly CSS and layout adjustments), and authentication flow changes (backend work if you need to add alternative verification). If you are already using a good CMS (WordPress, Drupal) with semantic HTML, the changes are straightforward. The CMS likely already handles many accessibility requirements, and the 2.2 updates are refinements to what is already there.
If your portal has custom interactive elements — drag-and-drop components, complex member dashboards, multi-step workflows — you are closer to $15,000. Those custom elements need alternative workflows coded specifically for keyboard and mouse navigation. A custom event scheduling dashboard that lets members drag events between days needs keyboard shortcuts and buttons for the same workflow. That is developer work, and it is more expensive than CSS updates.
Timeline: Four to eight weeks for audit and remediation on a typical association site (50-100 pages, one member portal, a few custom components). The audit takes one to two weeks. Remediation takes three to six weeks depending on complexity. If your site has custom integrations or unusual functionality, add more time. A site with standard WordPress plus a basic member portal? Four weeks. A site with custom-built everything? Eight weeks.
Do You Need to Rush to 2.2 Compliance?
Not every association needs to rush to 2.2 compliance. If you completed your 2.1 AA audit within the last year and your site does not have complex interactive components, the 2.2 gaps are likely minor. A quick internal review of focus indicators and target sizes may be sufficient before investing in a full audit. Many of your existing accessibility investments remain valid, and incremental updates beat reactive overhauls.
The Overlay Tool Warning (Still Applies to 2.2)
WCAG 2.2 does not change the reality that overlay tools (AccessiBe, UserWay, AudioEye) do not make your site compliant. They add a toolbar. They do not fix the underlying code. The changes required for 2.2 require actual code modifications — focus indicators, target sizing, authentication alternatives, form field pre-filling. A toolbar cannot provide those. The FTC and DOJ have issued guidance that overlay tools are not sufficient for WCAG compliance. Courts have rejected them as adequate remediation. If WCAG compliance matters for your organization (and it should — the stakes are legal liability and member access), you need code-level fixes, not an overlay. An overlay might improve the experience for some users, but it cannot meet the specific requirements of 2.2.
What You Walk Away With
If you are already 2.1 AA compliant, the 2.2 update is incremental, not a rebuild. We will run a WCAG 2.2 gap assessment against your current site — specifically the new criteria that 2.1 compliance did not cover — and give you a prioritized remediation list with realistic costs.
Link: WCAG 2.1 Compliance: The Foundation → /blog/association-website-accessibility-wcag-compliance
Link: The Most Common Mistakes in Association Website Redesigns → /blog/what-trade-associations-get-wrong-website-redesign
Link: How Much Should Your Association Website Cost? → /blog/how-much-trade-association-website-cost-2026
You will know exactly what needs to change and what it will cost.