The Americans with Disabilities Act turned thirty-six years old in 2026, and it has never been more relevant to your website. The Department of Justice finalized its first-ever rule setting specific technical standards for web accessibility under ADA Title II in April 2024. Lawsuits under ADA Title III continue to climb, with plaintiffs filing more than 5,100 federal website accessibility cases in 2025 alone, a twenty percent increase over the previous year. And in April 2026, the DOJ extended the original Title II compliance deadline by one year, creating both confusion and a false sense of security for organizations that assume the extension means they can wait.
If you run an association or nonprofit, you are likely hearing about ADA web accessibility for the first time or wondering whether the new rules apply to you. The short answer is that some version of ADA web accessibility requirements almost certainly applies to your organization. The longer answer depends on who you are, who you serve, and how your website functions.
This post breaks down what ADA Title II and Title III actually require, which one applies to your association, what the current deadlines are, and what you should be doing about it right now.
Title II vs. Title III: Which One Applies to You
The ADA has two titles that are relevant to website accessibility, and they cover different types of organizations.
ADA Title II covers state and local government entities. This includes cities, counties, states, school districts, public universities, transit authorities, and special purpose districts. If your organization is a government body or a department of one, Title II applies to you. The DOJ finalized specific web accessibility requirements under Title II in April 2024, mandating compliance with WCAG 2.1 Level AA.
ADA Title III covers private entities that operate "places of public accommodation." This is the section that applies to most associations, trade organizations, professional societies, and nonprofits. Title III has covered physical accessibility since 1990 and has been interpreted by the DOJ and most federal courts to extend to websites and digital services operated by covered entities.
The critical distinction for associations: Title II has a specific, published rule with defined technical standards and deadlines. Title III does not yet have a comparable published rule. But that does not mean Title III has no requirements. Courts across the country have been ruling on Title III website accessibility cases for over a decade, and the DOJ has consistently maintained that Title III obligations extend to websites.
How Title II Affects Associations Indirectly
Even if your association is a private organization covered by Title III rather than Title II, the Title II rule matters to you for three reasons.
First, if your association contracts with state or local governments to deliver services, programs, or activities, you may be covered by Title II through that relationship. A professional association that administers a state-mandated licensing exam online, a trade association that manages a government-funded workforce development portal, or a nonprofit that operates a public health resource directory on behalf of a county agency could all be subject to Title II requirements because they are delivering government services.
Second, the Title II rule establishes WCAG 2.1 Level AA as the definitive technical standard. While Title III does not reference a specific WCAG version, courts increasingly look to WCAG 2.1 AA as the benchmark when evaluating Title III claims. The Title II rule reinforces this as the accepted standard, making it harder for any organization to argue that a lower standard of accessibility is acceptable.
Third, the Title II rule signals regulatory momentum. The DOJ has stated publicly that a Title III web accessibility rule is under consideration. When that rule arrives, it will almost certainly adopt WCAG 2.1 AA or higher. Organizations that wait for a Title III rule before acting on accessibility will find themselves scrambling to retrofit years of inaccessible content under a deadline.
What Title III Requires Today
Unlike Title II, there is no published federal regulation that specifies exact technical standards for website accessibility under Title III. That might sound like it gives associations a pass. It does not.
Title III requires that places of public accommodation provide equal access to their goods, services, privileges, and activities. The DOJ has consistently taken the position that this requirement extends to websites and digital services. In March 2022, the DOJ published guidance stating directly that the ADA applies to web content and that organizations should follow WCAG guidelines to ensure accessibility.
Federal courts have broadly agreed, though the legal landscape varies by circuit. Some circuits require a "nexus" between the website and a physical place of business. Others have ruled that websites are independently places of public accommodation. Regardless of the circuit-level differences, the trend is overwhelmingly toward treating websites as covered by Title III.
For associations specifically, the analysis is usually straightforward. Your association likely holds conferences, maintains offices, and operates facilities that qualify as places of public accommodation. Your website is how members and the public access your services, register for events, apply for membership, download resources, and engage with your programming. That website is an extension of your services and is covered by the same accessibility requirements.
The Current Deadlines
Here is where the timeline stands as of May 2026:
Title II (Government Entities): The DOJ published an Interim Final Rule on April 20, 2026, extending the original compliance deadlines by one year. State and local government entities with populations of 50,000 or more now have until April 26, 2027. Entities with populations under 50,000 and special district governments have until April 26, 2028. The technical standard remains WCAG 2.1 Level AA. The extension changed the timeline, not the requirements.
Title III (Private Organizations, Including Associations): There is no specific compliance deadline because there is no published Title III web accessibility rule. However, the absence of a deadline does not mean the absence of obligation. Lawsuits under Title III are filed based on the existing statutory requirement of equal access. More than 5,100 federal web accessibility lawsuits were filed in 2025. You do not need a deadline to be sued.
Section 508 (Federal Agencies and Federal Funding Recipients): If your association receives federal grants or contracts, Section 508 of the Rehabilitation Act may independently require that your digital content meet accessibility standards. This is a separate requirement from the ADA and has its own enforcement mechanisms.
What WCAG 2.1 Level AA Requires
Whether you are covered by Title II, Title III, or both, WCAG 2.1 Level AA is the standard you should be working toward. It is organized around four principles, often remembered by the acronym POUR:
Perceivable: All content must be presentable to users in ways they can perceive. This includes providing text alternatives for images, captions for video, sufficient color contrast, and the ability to resize text without breaking the layout. If a blind user cannot perceive your membership benefits through a screen reader, that content fails this principle.
Operable: All interactive elements must be operable by all users. This means full keyboard navigation (no mouse required), no content that flashes in ways that could trigger seizures, enough time to read and interact with content, and clear navigation mechanisms. If a user with limited mobility cannot tab through your event registration form and submit it using only a keyboard, that form fails this principle.
Understandable: Content and interface operation must be understandable. This includes readable text, predictable navigation behavior, consistent interface elements, and helpful error messages on forms. If your membership application returns a cryptic error without explaining what the user did wrong or how to fix it, that form fails this principle.
Robust: Content must be robust enough to be reliably interpreted by a wide variety of user agents, including assistive technologies. This means using proper HTML semantics, valid markup, and standard interface components. If your member portal uses custom JavaScript widgets that screen readers cannot interpret, those widgets fail this principle.
WCAG 2.1 Level AA includes 50 specific success criteria across these four principles. Some are straightforward (minimum color contrast ratios). Others require careful implementation (accessible drag-and-drop interactions, keyboard-accessible functionality for all features).
Where Association Websites Typically Fail
After auditing dozens of association websites, the same accessibility issues appear repeatedly:
Member login and portal: Custom-built member portals are among the worst offenders. Login forms without proper labels, CAPTCHA challenges without audio alternatives, session timeout warnings that disappear before users can respond, and portal dashboards built with div elements instead of semantic HTML.
Event registration: Multi-step registration forms with poor focus management, dynamic price calculators that update without notifying screen readers, date pickers that only work with a mouse, and confirmation pages that rely entirely on color to communicate status.
Resource libraries: PDFs uploaded without text layers (scanned images that screen readers cannot read), filtering interfaces that use custom dropdowns with no keyboard support, and download links that do not identify the file type or size.
Video content: Conference recordings, webinars, and educational videos without captions or transcripts. Auto-generated captions from platforms like YouTube are better than nothing but are not sufficient for compliance because they contain too many errors.
Navigation: Mega menus that trap keyboard focus, mobile navigation that cannot be operated with screen readers, and breadcrumb trails implemented as styled text rather than semantic navigation elements.
Third-party embeds: Embedded forms from services like WPForms or Gravity Forms, social media feeds, chat widgets, and analytics consent banners that are inaccessible. You are responsible for the accessibility of everything on your page, including third-party content.
The Lawsuit Landscape
The risk is not theoretical. Website accessibility lawsuits under Title III have increased every year since 2017. In 2025, plaintiffs filed more than 5,100 federal cases, and that number does not include state-level filings or pre-litigation demand letters, which are far more common.
Several trends are making the litigation environment more aggressive. Plaintiffs are increasingly using automated scanning tools and AI to identify violations and draft complaints at scale. Approximately forty percent of 2025 federal ADA Title III filings were filed pro se, meaning without attorney representation, which lowers the barrier to filing. And serial plaintiffs who file dozens or hundreds of cases per year continue to target organizations across every sector.
Associations are not immune. Any organization that operates a public-facing website where people can register for events, apply for membership, purchase products, or access resources is a potential target. The settlement costs for a single demand letter typically range from $5,000 to $25,000. A full lawsuit can cost $50,000 to $150,000 or more in legal fees alone, before any remediation costs.
The cheapest lawsuit is the one you prevent by making your website accessible before someone files.
Overlay Tools Are Not the Answer
You may have seen products that promise instant ADA compliance by adding a JavaScript widget to your website. These overlay tools typically place a small icon on the page that opens an accessibility menu allowing users to adjust font sizes, contrast, and other settings.
Overlays do not make your website compliant. The National Federation of the Blind and other disability advocacy organizations have publicly opposed overlay products. Multiple lawsuits have been filed against websites that used overlays, with courts finding that the presence of an overlay did not constitute compliance. In several cases, the overlay itself introduced new accessibility barriers.
True accessibility requires changes to your underlying code, content, and design. There is no shortcut. An overlay on top of an inaccessible website is like painting over a cracked foundation. The cracks are still there.
What Your Association Should Do Right Now
Regardless of whether a Title III rule is published next month or three years from now, the practical steps are the same:
Step 1: Audit your website. Conduct a professional accessibility audit against WCAG 2.1 Level AA. Automated scanning tools like WAVE, axe, or Lighthouse can catch some issues, but they typically identify only thirty to forty percent of accessibility barriers. A comprehensive audit requires manual testing by someone who understands assistive technology, including keyboard-only navigation and screen reader testing.
Step 2: Prioritize and remediate. You will not fix everything at once. Prioritize based on impact: fix the issues that affect the most users on the most critical pages first. Your membership application, event registration, member login, and primary navigation are the highest-priority targets.
Step 3: Publish an accessibility statement. An accessibility statement on your website demonstrates good faith. It should describe your commitment to accessibility, reference the standard you are working toward (WCAG 2.1 AA), provide a way for users to report accessibility barriers, and offer alternative methods of accessing services while you work on remediation.
Step 4: Train your content team. Accessibility is not a one-time fix. Every new page, blog post, PDF, and video your team creates must meet accessibility standards going forward. Train your content editors on writing alt text, using heading hierarchy, creating accessible documents, and captioning video.
Step 5: Build accessibility into your vendor contracts. If your website is built or maintained by a vendor, your contract should require WCAG 2.1 AA compliance for all deliverables. If you use third-party tools embedded on your site, verify their accessibility or find alternatives. You are responsible for the accessibility of everything that appears on your pages.
Step 6: Monitor continuously. Accessibility is not a project with an end date. It is an ongoing practice. Run automated scans monthly. Conduct manual audits annually. Test major updates before deployment. Assign someone on your team as the accessibility point person.
The Business Case Beyond Compliance
Legal risk is the most common motivator for accessibility work, but it is not the only one. Accessible websites perform better across multiple dimensions.
Accessible websites rank higher in search engines because the same semantic HTML and structured content that screen readers need is also what search engine crawlers need. They convert better because clear navigation, logical form design, and readable content improve the experience for all users, not just users with disabilities. They reach a larger audience, given that the CDC estimates that 28.7 percent of American adults live with some form of disability.
For associations specifically, accessible websites improve member retention by ensuring that members with disabilities can fully participate in the benefits they pay for. They reduce support burden by preventing the "I cannot use this" calls and emails. And they demonstrate the inclusive values that most associations claim in their mission statements.
The Bottom Line
ADA web accessibility is not a future concern. It is a current legal obligation under Title III for private organizations including associations. The Title II rule and its WCAG 2.1 AA standard reinforce the direction that courts, regulators, and the DOJ are moving. The extended Title II deadline changes nothing about your Title III exposure. And the lawsuit volume makes clear that enforcement is not waiting for a rule.
Your association website either serves all of your members or it does not. Accessibility is what closes that gap. Start with an audit, prioritize the highest-impact fixes, train your team, and build accessibility into every future decision about your digital presence. The organizations that do this now will spend less, face less risk, and serve their members better than those that wait.
Thinking about a redesign or a new digital strategy? We would love to hear from you.