The executive director of a county food bank once told me she had looked into web accessibility and concluded it did not apply to her: the ADA was for businesses and government, her organization was neither, and with eleven employees she was too small to be on anyone's radar anyway. She was wrong on all three counts, and the specific way she was wrong is the reason this article exists.
Here is the sentence that changes the conversation. The ADA's definition of a place of public accommodation, at 42 U.S.C. §12181(7)(K), lists “a day care center, senior citizen center, homeless shelter, food bank, adoption agency, or other social service center establishment.” Congress did not write the nonprofit sector out of the statute. It wrote the nonprofit sector into the statute, by name, in its own subsection. And Title III applies regardless of headcount — there is no small-organization exemption of the kind that exists under some employment laws.
Three separate laws can reach your organization, and they stack
Nonprofits get confused here because they go looking for “the nonprofit accessibility law” and there is not one. There are three independent legal hooks, and most organizations are caught by at least two at once. They do not override each other; you have to satisfy whichever ones apply.
1. ADA Title III — because you serve the public
Title III covers private entities operating places of public accommodation. The twelve statutory categories sweep in far more of the sector than most boards realize: subsection (J) covers private schools and “other place of education,” (H) covers museums, libraries, and galleries, (I) covers parks and places of recreation, and (K) covers the social-service establishments named above. A legal-aid clinic, a community health center, a youth program, a private preschool, a historical society, an animal shelter with a public adoption floor — these are public accommodations.
One honest caveat, because you will hear it argued both ways: there is currently no federal regulation establishing a single technical web standard under Title III. DOJ finalized a rule setting WCAG 2.1 Level AA for state and local government under Title II in April 2024, but no parallel Title III web rule exists. What that absence is not is a safe harbor. DOJ's longstanding enforcement position is that Title III's effective-communication and equal-access obligations reach the goods and services a covered entity offers online, and courts, DOJ settlements, and private demand letters all reach for WCAG as the working yardstick. The practical effect of “no rule” is not “no obligation” — it is uncertainty, and uncertainty favors whoever files first.
2. Section 504 — because you take federal money
This is the hook nonprofits most often miss, and it is the one with an actual date attached. Section 504 of the Rehabilitation Act prohibits disability discrimination by recipients of federal financial assistance — not only by federal agencies. If you hold an HHS grant, run a program funded through one, or receive pass-through dollars as a subrecipient of a state or county award, you are a recipient. Plenty of organizations that would never describe themselves as federally funded are subrecipients three layers down a funding chain and have never traced it.
The HHS Section 504 rule makes this concrete for digital content: covered web content and mobile applications must conform to WCAG 2.1 Level AA. Following the May 2026 interim final rule extending the original dates, compliance is due May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for recipients with fewer than 15. Note that the tier turns on employee count, not budget — which is why a small nonprofit's deadline may be the later one while its fiscal sponsor's is the earlier one. Both are still ahead of us; the work to do now is to get in front of them.
The rule carves out five limited exceptions rather than a general small-entity escape: archived web content, certain preexisting conventional electronic documents, certain third-party posted content, individualized password-protected conventional electronic documents, and preexisting social media posts. Those are narrow, and none of them covers the pages that actually matter — your program descriptions, eligibility criteria, intake forms, and application portals.
3. Title II by contract — because you run somebody else's program
If your organization delivers a program on behalf of a city, county, school district, or state agency, that public entity's Title II obligations frequently flow down to you through the contract or grant agreement. A public entity cannot discharge its accessibility duty by handing the program to a contractor. Read your agreements: the accessibility clause is usually there, often buried alongside the nondiscrimination boilerplate, and it typically references WCAG 2.1 AA and the Title II deadlines of April 26, 2027 for public entities serving 50,000 or more and April 26, 2028 for smaller entities and special districts. Some states, California and New York among them, layer additional accessibility mandates on top.
| What triggers it | Law | Working standard | Timing |
|---|---|---|---|
| You serve the public — food bank, shelter, clinic, private school, museum | ADA Title III | WCAG, in practice, via enforcement and settlements | Already in effect; no phase-in |
| You receive federal financial assistance, including as a subrecipient | Section 504, 45 CFR Part 84 | WCAG 2.1 Level AA, by regulation | May 11, 2027 (15+ employees) · May 10, 2028 (under 15) |
| You run a program for a public entity under contract | ADA Title II, flowed down by agreement | WCAG 2.1 Level AA, by regulation | April 26, 2027 · April 26, 2028 |
| You are a religious organization or an entity it controls | Exempt from ADA Title III under 42 U.S.C. §12187 | — | The ADA exemption does not carry over to Section 504 if you take federal funds |
That last row deserves a sentence of its own, because it is the most commonly over-claimed exemption in the sector. Section 12187 exempts “private clubs or establishments” and “religious organizations or entities controlled by religious organizations, including places of worship.” It does not exempt every charity with a faith-inspired mission, a denominational founding, or a board seat reserved for clergy. And an ADA exemption is not a Section 504 exemption — a faith-based organization that accepts federal grant dollars still answers to Section 504 as a recipient.
Not sure which hooks apply to you? Tracing the funding and establishing the employee-count tier takes about an afternoon, and it determines everything downstream. We run that assessment for nonprofits as the first step of every engagement.
The overlay widget is not a fix, and the FTC has said so
When a nonprofit with no IT staff and no budget line for this discovers it has an obligation, the accessibility overlay looks like the obvious escape hatch: one line of JavaScript, a monthly fee smaller than a single audit, and a badge in the footer announcing compliance. It is among the worst uses of restricted program dollars in this sector.
In January 2025, the Federal Trade Commission ordered overlay vendor accessiBe to pay $1 million to settle allegations that it misrepresented its AI-powered widget's ability to make any website WCAG-conformant; the Commission approved the order as final in April 2025. The order bars the company from representing that its automated products can make a website WCAG-compliant, or keep it compliant over time, without evidence to support the claim. The FTC also alleged the company had formatted third-party articles and reviews to look like independent, impartial endorsements.
An overlay cannot write meaningful alt text, cannot fix a form with no programmatic labels, cannot repair a heading structure that was never there, and cannot remediate an untagged PDF grant application. It changes what a scanner reports, not what a screen-reader user experiences. Regulators and plaintiffs both look at the second thing.
There is a second trap specific to organizations serving multilingual communities, and it catches people who did everything else right. Accessibility does not carry over between language versions. Remediating your English intake form does nothing for the Spanish one. A translated PDF comes back from most vendors as an untagged export, with reading order, alt text, and language attributes stripped out — so a bilingual program ends up with an accessible English document and an inaccessible Spanish one serving the households least able to escalate about it. If you translate anything you have remediated, the accessibility work has to be redone per language, or specified up front so it is done once.
A three-step plan that fits a nonprofit's reality
You do not need a compliance department. You need to do three things in order.
- Trace the money and count the heads. Pull every active award letter, contract, and subgrant agreement and mark anything with a federal source, including pass-through dollars from a state or county. Then count employees. Those two facts tell you which laws reach you and which deadline is yours, and nothing else can be planned until you know.
- Audit against WCAG 2.1 AA — including the documents, and every language. Most nonprofit accessibility failures are not on the homepage. They are in the PDF eligibility packet, the scanned intake form, the fillable application, the Form 990 posted for donors, and the event-registration widget embedded from a third-party platform. Inventory all of it, in every language you publish, and test with real assistive technology rather than an automated scan alone.
- Remediate worst-first, then build it into the workflow. Prioritize anything that gates program access — eligibility, intake, application, appointment scheduling — ahead of marketing pages. Then set the rule that nothing new publishes untested, and that translation requests specify accessible output as a deliverable rather than an afterthought.
Do this and the picture is straightforward: a documented conformance posture, a client who can actually complete an intake form with a screen reader, and a grant monitor who finds accessibility addressed rather than absent. Skip it and the failure modes are all expensive in ways nonprofits absorb badly — a demand letter that costs more to answer than the remediation would have cost, an OCR complaint, a finding in grant monitoring, or the quieter version: someone who needed your program and could not get through the door you built online.
Why work with Taika
Language Access Hub, powered by Taika Translations, is a veteran-owned (VOSB), SAM-registered, GSA- and NASPO ValuePoint-contracted language access provider working with nonprofits, school districts, healthcare organizations, and government agencies. We handle ADA and Section 508 compliance — WCAG 2.1 AA audits, remediation, and accessible document production — alongside certified translation by ATA-certified linguists and interpretation, which means the multilingual accessibility gap gets closed once instead of twice. Our nonprofit language access services are built for organizations that have to make restricted dollars go a long way, and our PDF remediation guide walks through the documents most audits flag first.