WCAG 2.1, 2.2, and What the April Deadline Change Means for Associations
August 3, 2005
Short answer:
In April 2026 the Department of Justice (DOJ) extended Americans with Disabilities Act (ADA) Title II web accessibility deadlines to 2027 and 2028. Title II applies to state and local government, including public universities. Most associations and nonprofits fall under Title III, which has no deadline, meaning the accessibility requirement is already in effect. Web Content Accessibility Guidelines (WCAG) 2.2 Level AA is the practical target, since it is backward compatible with 2.1.
Accessibility comes up in almost every conversation we have with associations and nonprofits.
A client will ask whether they are compliant. A board member will raise the issue. A member will report a problem with the website. And the first real question becomes: what accessibility requirements does our organization need to meet? Local and state governments, nonprofits, and businesses need to comply with ADA guidelines. WCAG 2.1 Level AA is the accepted technical standard organizations use to achieve and demonstrate ADA-compliant web accessibility. The ADA defines the legal obligation; WCAG defines the technical standard most organizations use to meet it.
WCAG 2.1 Level AA is a reasonable starting point. It’s just no longer the place to stop.
This article explains what changed in April, which rules apply to different organizations, why the lack of a deadline does not mean the lack of risk, and why WCAG 2.2 is the better target for most member-based organizations.
We will cover:
What the DOJ changed in April
On April 20, 2026, the DOJ extended the compliance dates in its ADA Title II web accessibility rule. Large public entities now have until April 26, 2027. Smaller entities and special districts now have until April 26, 2028.
The extension shifted the dates, not the duties. The obligation, the standard, and the litigation landscape all remain the same.
Which rules apply to your organization
This is where confusion usually starts. Several laws get mentioned together, but they serve different purposes.
- Section 508 applies to federal agencies and the technology they build or buy. If you sell software to a federal agency, 508 may apply through procurement. It does not apply simply because an organization receives federal funding. The current 508 standard references WCAG 2.0 AA.
- Section 504 prohibits disability discrimination in programs that receive federal financial assistance. It does not define specific web requirements the way 508 does, but accessible digital services are part of meeting the obligation.
ADA is civil rights law.
- Title II covers state and local governments, including public universities and some quasi‑governmental entities.
- Title III covers places of public accommodation, which in practice includes most private associations, nonprofits, and businesses.
WCAG is not a law. It is a technical standard published by the World Wide Web Consortium and adopted internationally as ISO and IEC 40500. Most laws point to WCAG when they define what accessible means.
The practical takeaway:
WCAG is the standard behind all of these statutes. Building to WCAG puts your organization in a stronger position no matter which law applies. It is the most reliable way to meet your legal obligations and reduce risk.
If you are assessing your current position, our preliminary accessibility checklist is a clear place to begin.
Why no deadline does not mean no obligation
The April change applies to ADA Title II, which covers government entities. If you are a public university, a state agency, or a similar public body, that extension matters to you.
Most associations and nonprofits are not covered by Title II. They fall under Title III, which does not include a compliance deadline. That does not mean there is no obligation. It means the obligation already exists.
That distinction matters. A deadline gives a board something concrete to plan toward. Without a deadline, the responsibility is not deferred. It is immediate.
It also matters because private web accessibility litigation usually arises under Title III. According to Seyfarth Shaw’s annual tracking, plaintiffs filed 3,117 federal website accessibility lawsuits under Title III in 2025. That was a 27 percent increase over 2024 and represented 36 percent of all federal Title III filings. Industry trackers put the total number of cases, including state court filings, above 5,000.
There are two important caveats. First, most of those cases targeted e-commerce, so retail is exposed to more litigation risk than the association sector. Second, lawsuits are not the only reason to improve accessibility. But if you saw the April extension and assumed it gave your organization more time, make sure you are looking at the correct title before you rely on that assumption.
What is new in WCAG 2.2
WCAG 2.2 became the current W3C recommendation in October 2023. It adds nine success criteria and removes one.
WCAG 2.1 is not obsolete in law. Courts still reference it, and the Title II rule names it. The case for 2.2 is simpler. It is backward compatible, so if you build to 2.2 you also satisfy 2.1.
It is also the direction the field is moving. If you build to 2.1 now and move to 2.2 later, you may end up paying for the same work twice.
Several of the new requirements affect common member journeys:
- Accessible Authentication means a login cannot require a cognitive test, such as remembering a passphrase or solving a puzzle, unless there is an alternative. It also means password managers cannot be blocked.
- Redundant Entry means users should not have to enter the same information twice in one process unless there is a valid reason.
- Consistent Help means help options should appear in the same relative place across pages.
- Focus Not Obscured means the item a keyboard user is on cannot be hidden behind another element, such as a sticky header.
- Target Size requires interactive controls to be at least 24 by 24 pixels, or to have enough spacing when they are smaller.
- Dragging Movements means any action that requires dragging must have an alternative.
These are not edge cases. They show up in login, registration, renewal, help, and event workflows. Those are the paths members use most often.
Where WCAG 3.0 fits
You may also hear people talk about WCAG 3.0. It is a working draft, and it is still years from completion. The March 2026 version made progress, but it is not something to build to yet.
WCAG 3.0 is moving toward a graded conformance model, which better reflects how real sites work. It is expected to sit alongside WCAG 2.2 rather than replace it. For the next several years, WCAG 2.2 remains the practical target.
If you want to see where the standard is heading, you can read the working draft. Just do not wait for it before addressing issues you can fix now.
What to do next
If you have a Title II deadline in 2027, you still have time, but only if you start now. A serious audit takes time, and remediation usually takes longer.
If you are not covered by Title II, the same advice still applies. The obligation is current, even if the law does not give you a countdown.
Start by stopping new inaccessible content from going live. Add accessibility to your definition of done so the problem does not keep growing.
Then run automated scans, but do not stop there. Automated tools can find contrast problems, missing alt text, and some structural issues. They cannot tell you whether a tab order is logical or whether an error message is useful.
Test the pages members actually use most often. Focus on login, renewal, and event registration. Try those flows with only a keyboard. Try them with a screen reader. You will learn more from that review than from a long report of page-level issues.
Fix issues in priority order. A broken renewal form matters more than a decorative image on a low-traffic page.
Document the work. The person who manages the site in three years will need to know what changed and why.
If you need a starting point, our checklist covers the ten items we review first, and 5 Common Accessibility Mistakes and How to Fix Them covers the issues we see most often.
Frequently asked questions
Does WCAG 2.2 apply to nonprofits?
WCAG is a technical standard, not a law, so it does not apply to anyone by itself. Most nonprofits and associations fall under ADA Title III, which requires accessibility without naming a specific version. WCAG 2.2 Level AA is the practical target.
Did the ADA deadline get extended for associations?
No. The April 2026 extension applies to ADA Title II, which covers state and local government. Most associations fall under Title III, which has no compliance deadline.
Is WCAG 2.2 required if we already meet 2.1?
It is not always required, but it is the better target. WCAG 2.2 is backward compatible with 2.1, so building to 2.2 also covers 2.1.
What should associations fix first?
Start with the paths members use most, especially login, renewal, and event registration.
What is the difference between Section 508, the ADA, and WCAG?
Section 508 applies to federal agencies and the technology they procure. The ADA is civil rights law that covers government under Title II and public accommodations under Title III. WCAG is the technical standard that those laws often use to define accessibility.
Closing
If you want to know where your site stands, we can help.
We run accessibility audits that combine automated scanning with manual testing on the pages that matter most to your members. You get a prioritized list of issues and next steps written in plain language that you can share with your team or board.