Resource
2027–2028 Website Accessibility Deadlines: What Nonprofits and Public Agencies Need to Know
ADA Title II and HHS Section 504 name different organizations, different dates, and the same technical standard: WCAG 2.1 Level AA. This guide separates them.
Last reviewed November 9, 2026.
People use the website to reach the service.
For a housing program, a clinic, a city office, or a food pantry, the website is often the front door. If a form, a PDF, or a video does not work with a keyboard, a screen reader, or captions, some of the people the organization exists to serve cannot get through.
Two federal rules now name a technical standard for that problem, and they do not apply to the same organizations. The Department of Justice rule under ADA Title II covers state and local governments. The Department of Health and Human Services rule under Section 504 covers recipients of HHS financial assistance. A private nonprofit is not automatically in either group.
In 2026 both departments extended the dates for meeting WCAG 2.1 Level AA. The extensions changed the calendar. They did not erase older duties to avoid disability discrimination. HHS, for example, still tells recipients that programs and activities offered through the web have to be accessible to people with disabilities. HHS announcement (opens in a new tab) · DOJ Federal Register (opens in a new tab)
What is WCAG 2.1 AA?
WCAG — the Web Content Accessibility Guidelines — is the W3C standard for making web content work for people with disabilities. The DOJ and HHS rules require the Level A and Level AA success criteria in version 2.1, which is usually shortened to WCAG 2.1 AA. Read WCAG 2.1 (opens in a new tab) · W3C overview (opens in a new tab)
In practice, that means attention to things like:
- Keyboard navigation, including a visible focus indicator and no traps
- Screen reader compatibility: names, roles, and states for controls
- Color contrast for text and essential graphics
- Alternative text for images that carry information
- Form labels, instructions, and errors that are tied to the fields
- Captions for prerecorded video
- Headings, landmarks, and a content structure people can follow
- Interactive components — menus, dialogs, tabs — that work without a mouse
The guidelines sit under four ideas:
- Perceivable. People can take in the content. That includes text alternatives, captions, and contrast.
- Operable. People can use the interface. Keyboard access is the clearest example.
- Understandable. The page behaves in a predictable way, and forms explain themselves.
- Robust. Assistive technology can interpret the content, which depends on proper names, roles, and structure.
W3C's current recommendation is WCAG 2.2, which adds criteria and does not replace 2.1. W3C describes 2.2 as backwards compatible with 2.1, with a note that one older criterion, 4.1.1 Parsing, is obsolete in 2.2. These two federal rules name 2.1. Using 2.2 as a build target can be a project choice. It is not what the rules require.
What are the actual deadlines?
The original rules, published in 2024, used earlier dates. DOJ extended them by one year in an interim final rule effective April 20, 2026. HHS did the same in a rule effective May 7, 2026. The table uses the extended dates. 28 CFR 35.200 (opens in a new tab) · 45 CFR 84.84 (opens in a new tab)
| Rule | Who | Date |
|---|---|---|
| ADA Title II | State and local governments with a total population of 50,000 or more | April 26, 2027 |
| ADA Title II | State and local governments with a total population under 50,000 | April 26, 2028 |
| ADA Title II | Special district governments | April 26, 2028 |
| HHS Section 504 | Recipients of HHS financial assistance with 15 or more employees | May 11, 2027 |
| HHS Section 504 | Recipients of HHS financial assistance with fewer than 15 employees | May 10, 2028 |
Title II applies to web content and mobile apps that a public entity provides or makes available, directly or through contractual, licensing, or other arrangements. The rule has exceptions, and it allows a limit where compliance would fundamentally alter a service or cause an undue burden. Those limits are specific. They are not a general opt-out. DOJ fact sheet (opens in a new tab)
Population is "total population," as DOJ defines it. For most governments that is the 2020 Census figure. A library, police department, or parks office uses the population of the city or county it belongs to, not its patron count or its staff size. A state university uses the state's population, not enrollment. Independent school districts are not special districts; DOJ points them to Small Area Income and Poverty Estimates. Special district governments — DOJ's examples include utility districts, transit authorities, and water and sewer boards — use the later date. A school district is not in that category. How DOJ explains the calculation (opens in a new tab)
The HHS dates apply to recipients of HHS financial assistance. The department has pointed to community health centers, hospitals, and primary care practices as examples, and the rule can also reach other health and human services organizations that receive HHS funds. It does not reach a nonprofit simply because the nonprofit receives some other kind of funding. Recipients with 15 or more employees are on May 11, 2027. Recipients with fewer than 15 employees are on May 10, 2028. HHS announcement (opens in a new tab)
An organization can be covered by both rules at once. A county health department is a Title II entity and may also receive HHS funds. The dates are not interchangeable. Read both, and do not pick the later one without checking which content each rule covers.
The rules have exceptions. They are narrow.
DOJ describes limited exceptions, including archived web content, some preexisting conventional documents, content posted by a third party who is not posting because of a contract or similar arrangement with the government, certain individualized password-protected documents, and preexisting social media posts. Each exception has conditions. Moving a file into a folder named Archive is not enough, and a document people still use to apply for a service generally stays in scope. Exceptions also do not, on their own, remove the duty to communicate effectively when someone asks. DOJ's explanation of the exceptions (opens in a new tab)
The HHS rule has its own regulatory limits, including fundamental alteration and undue burden. This page is not a catalog of every exception. Use the regulation and the agency guides, and ask counsel before you rely on one.
Do these deadlines apply to my nonprofit?
Not every nonprofit is directly covered by the ADA Title II web rule. Title II is about state and local government.
Some nonprofits that receive HHS financial assistance — including healthcare and human services organizations — may be subject to Section 504's web requirements. Funding that has nothing to do with HHS does not, by itself, put an organization on the HHS calendar.
If you provide services through a government contract, the public entity may have to make sure the web content it offers through that arrangement conforms. The regulation names the public entity. The contract may still assign the work, and the cost, to you.
Other accessibility obligations can apply under ADA Title III, Section 504 programs run by other federal agencies, state law, and contractual requirements. DOJ has not set a Title III website date that matches this Title II schedule. The absence of an April 2027 or May 2027 date is not a finding that a nonprofit has no accessibility duties.
Choose the closest description. The note that follows is general guidance, not a legal determination.
What happens if a website isn't accessible?
The first consequence is practical. People cannot apply, donate, register, or understand a service. Participation drops in ways a traffic report will not explain.
Inaccessible content can also lead to complaints and disputes. Public entities and funding recipients can face administrative or legal processes. Remediation done in a hurry, after a complaint, is usually more disruptive than work planned against a real inventory.
None of that means every inaccessible page automatically violates every rule. Coverage, exceptions, and the particular barrier all matter. This page does not estimate lawsuit counts, and it is not a prediction of what will happen to a specific organization.
How to evaluate your website
An automated scan is a flashlight, not a verdict. It can surface missing labels, some contrast failures, and some structural problems. It cannot establish full WCAG conformance. W3C on evaluating accessibility (opens in a new tab)
A useful evaluation also includes:
- Manual keyboard testing. Tab through the real tasks. Watch where focus goes, and whether you can see it.
- Screen reader evaluation. Listen to the names of buttons, the order of headings, and the errors on a form.
- Forms and interactive elements. Menus, dialogs, date pickers, and multi-step applications fail in ways scanners shrug at.
- Important user journeys. Apply, donate, find a location, register for a program. Test the path, not only the homepage.
- PDFs and other documents. If the information lives in a file, the file is part of the service.
- Third-party donation and application tools. A vendor's embed is still the experience on your site.
CauseHouse also publishes a separate readiness check for organizational habits — ownership, procurement, documents, vendors. It does not scan a website and it does not test WCAG conformance.
A preparation checklist
Useful whether or not you hire anyone. Nothing here is submitted.
- 01
Identify the applicable accessibility requirements.
Separate Title II, HHS Section 504, contracts, and any other duties. Do not assume one date covers every nonprofit.
- 02
Inventory important pages, forms, documents, and third-party systems.
Start with the journeys that enroll, apply, donate, register, or explain eligibility.
- 03
Run an initial accessibility assessment.
Use an automated check as a map, then read the results. A score is not a finding list.
- 04
Conduct manual testing.
Keyboard, focus order, screen reader, forms, and video. Include at least one real task from start to finish.
- 05
Prioritize barriers affecting essential services.
A broken application matters more than a decorative image on a blog post from 2014.
- 06
Develop a remediation roadmap.
Group work by template, document library, and vendor. Assign owners and a sequence.
- 07
Retest completed work.
A fix that is not checked has a way of shipping the same barrier in a new component.
- 08
Establish ongoing review procedures.
New pages, new PDFs, and new vendors are how accessible sites become inaccessible again.
Questions people ask first
Does every nonprofit need to comply by April 2027?
No. The April 26, 2027 date in the Department of Justice rule is for state and local government entities with a total population of 50,000 or more. A private nonprofit is not assigned that date merely because it is a nonprofit. A nonprofit that receives financial assistance from the U.S. Department of Health and Human Services may instead be looking at May 11, 2027 if it has 15 or more employees, or May 10, 2028 if it has fewer. Other accessibility duties can still exist under ADA Title III, another agency's Section 504 rules, state law, or a contract.
Does federal funding automatically mean my nonprofit is covered?
No. The HHS web rule applies to recipients of federal financial assistance from HHS. A grant from a different department, a foundation award, or a state contract is not the same thing. Check the notice of award, and ask counsel if you are a recipient under 45 CFR Part 84.
What is WCAG 2.1 AA?
WCAG is the Web Content Accessibility Guidelines, published by the W3C. Level AA is the middle conformance level. The DOJ and HHS rules require the Level A and Level AA success criteria in WCAG 2.1, often shortened to WCAG 2.1 AA. That includes keyboard access, names for controls, contrast, text alternatives, captions, form labels, and a structure people can follow. It is a technical standard. Meeting it is not, by itself, a legal opinion.
Do donation forms need to be accessible?
When the form is part of web content covered by one of these rules, yes. A donation or application form that a government or an HHS funding recipient places on its site is generally that organization's content, including when a vendor supplies the tool. The exception for third-party posts is narrow. It is not a waiver for a payment form the organization chose. People who cannot finish a gift or an application are blocked from the service whether or not a deadline has arrived.
Does accessibility apply to PDFs?
Often, yes. Both rules address web content, and conventional documents such as PDFs are part of that. Some preexisting documents can fall under an exception, and the exception has conditions. A PDF people still use to apply for a benefit usually does not qualify just because it was uploaded years ago. The DOJ fact sheet sets out the conditions.
Can an accessibility widget make my website compliant?
No. An overlay or widget does not make a website conform to WCAG 2.1 AA, and it can add barriers of its own. The work is in the templates, the content, the documents, and the third-party tools.
Is a free automated scan enough?
No. Automated tools catch a subset of issues. They miss keyboard traps, confusing focus order, many screen-reader problems, and a lot of what goes wrong in forms and documents. A scan cannot establish WCAG conformance. It can be a useful first pass before a person tests the journeys that matter.
Does a website redesign guarantee compliance?
No. A new website can launch with the same unlabeled controls, the same inaccessible PDFs, and the same third-party form. Conformance depends on the design, the build, the content, and the testing, and then on what the team publishes afterward.
What if a third-party tool is inaccessible?
If your organization selected the tool and presents it as part of the site — a donation form, an application portal, a calendar, a map — the exception for content posted by an outside party usually does not apply. You may need a fix from the vendor, a different tool, or another way for people to finish the same task. Put that requirement in the contract before you renew.
What should our organization do first?
Name an owner. List the pages, forms, documents, and third-party tools people use to get help, give, or apply. Sort out which of these rules might apply, with counsel if the funding is complicated. Test those journeys with a keyboard and, where you can, a screen reader. Fix the barriers that block essential tasks before you work through a long list of smaller ones.
Official resources
- DOJ fact sheet on the web rule (opens in a new tab)
- DOJ first steps for state and local governments (opens in a new tab)
- DOJ small entity compliance guide (opens in a new tab)
- DOJ 2026 interim final rule (PDF) (opens in a new tab)
- DOJ 2026 interim final rule, Federal Register (opens in a new tab)
- 28 CFR 35.200, current Title II web requirements (opens in a new tab)
- HHS announcement of the Section 504 extension (opens in a new tab)
- HHS 2026 interim final rule, Federal Register (opens in a new tab)
- 45 CFR 84.84, current HHS web requirements (opens in a new tab)
- W3C: WCAG overview (opens in a new tab)
- W3C: WCAG 2.1 (opens in a new tab)
- W3C: evaluating accessibility (opens in a new tab)
Last reviewed November 9, 2026. This page is general information about public rules. It is not legal advice, and it is not a determination that any specific organization is covered. Rules change. Check the sources above before you rely on a date.
Not sure where your website stands?
Start with a free preliminary accessibility review from CauseHouse.
Get my free review →