Here's a sentence that has never once appeared in the Americans with Disabilities Act: "unless you're a nonprofit."
Search the statute. Search Title III. It isn't there. And yet, ask ten executive directors at small nonprofits whether ADA website rules apply to them, and a striking number will tell you, with total confidence, that they don't — because they're mission-driven, not profit-driven, and surely the law was written with big companies in mind.
The Five-Person Team That Assumed It Was Exempt
Picture a small nonprofit — five staff, a volunteer board, a WordPress site built by a supporter's cousin four years ago. They run a food-security program, take donations online, and recruit volunteers through a sign-up form on their homepage.
One afternoon, a supporter using a screen reader tries to make a recurring monthly gift. The donation form's amount field has no visible label, the "custom amount" input isn't announced at all, and after a failed submission, nothing tells them what went wrong. They give up and email the organization instead — and mention, gently but clearly, that the site is hard to use with assistive technology.
The staff's first instinct is relief: at least it was a friendly email, not a demand letter. Their second instinct, once they look into it, is surprise. Nonprofit status was never a shield to begin with.
Nonprofit Status Doesn't Change Your ADA Category
Under ADA Title III, most organizations that operate a public-facing website — selling something, taking donations, registering volunteers, publishing services to the public — function as places of public accommodation in the same broad sense that retailers, banks, and service businesses do. Being a 501(c)(3) doesn't remove an organization from that category. It changes your tax treatment, not your accessibility obligations.
This matters because the mental model many nonprofits carry — ADA lawsuits are a for-profit company problem, we're doing good work, we're the good guys — has nothing to do with how the law actually draws its lines. A donation form is still a transaction. A volunteer sign-up is still a service offered to the public. The legal exposure follows the function of the page, not the tax status of the organization running it.
The Extra Layer: Section 504 and Federal Funding
For nonprofits that receive federal grants or other federal financial assistance, there's a second, more specific obligation stacked on top of general ADA exposure: Section 504 of the Rehabilitation Act. Section 504 applies directly to recipients of federal funding, which means a nonprofit that receives even partial federal grant dollars can carry a Section 504 accessibility obligation tied specifically to that funding relationship — separate from, and in addition to, its general public-accommodation exposure.
If your nonprofit applies for or holds federal grants, that's not a detail to skim past. It's a direct, funding-linked reason to treat digital accessibility as a compliance requirement rather than a someday-nice-to-have.
The Stat: WebAIM's annual "WebAIM Million" evaluation of the top 1,000,000 home pages has repeatedly found that the vast majority — in recent years around 95-96% — have detectable WCAG 2 failures, with low-contrast text and missing alt text among the most common. A four-person nonprofit web team is not an outlier for having accessibility gaps; it's the norm, and that's exactly why it's worth fixing early rather than waiting for someone to point it out. (WebAIM: The WebAIM Million)
Where the Real Risk — and the Real Mission Impact — Lives
Not every page on a nonprofit site carries equal weight. Two pages matter more than the rest combined, because they're where accessibility failure and mission failure are literally the same event.
The donation form. This is the highest-stakes page on most nonprofit sites, financially and legally. The same foundational form-accessibility work that applies to any e-commerce checkout — proper labels tied to inputs, clear error identification, sensible focus management when validation fails — applies directly here. A donor who can't complete a gift because of a missing label or an unannounced error isn't a compliance statistic. They're a lost gift, in real time, from someone who wanted to give you money and couldn't.
Event registration and volunteer sign-up forms. These carry exactly the same stakes as the donation form, just measured in time instead of dollars. An unlabeled date picker on a volunteer sign-up form, or a required-field error that isn't announced to a screen reader, blocks someone from contributing their time in precisely the way a broken donation form blocks a financial gift. If your organization runs on volunteer labor, a form failure here is a direct hit to your operating capacity.
Grant applications and annual reports as PDFs. This is a nonprofit-specific blind spot worth naming directly. Impact reports, financial disclosures, and grant materials are routinely published as PDFs — and just as routinely built without accessible structure, tags, or reading order. The same PDF remediation work that applies to any organization's document library applies here, and nonprofits often have double motivation to fix it: legal exposure on one hand, and genuine mission alignment on the other, since most nonprofits want their impact reported as widely and readably as possible.
Do This / Not This: Nonprofit Accessibility Priorities
| Area | Not This | Do This |
|---|---|---|
| Donation form | Unlabeled amount fields, silent validation failures | Proper <label>/input association, clear error identification per 3.3.1 Error Identification (Level A) |
| Volunteer/event sign-up | Unlabeled date pickers, generic "error" text with no context | Descriptive, programmatically associated error messages and visible focus states |
| Impact reports & grant PDFs | Scanned images or untagged PDFs with no reading order | Tagged, structured, screen-reader-navigable PDF exports |
| Overall approach | "We'll do a full enterprise remediation eventually" | Prioritize donation + volunteer forms first, scale remediation to actual budget |
| Federal grant recipients | Treating accessibility as optional | Treating Section 504 obligations as directly tied to the funding relationship |
What "Sized to a Nonprofit Budget" Actually Means
You don't need an enterprise remediation program to make meaningful progress, and treating "full-scale fix" as the only acceptable starting point is itself a reason many nonprofits never start. The practical path looks different:
Start with the donation form. Fix labels, error identification, and focus management — the same core issues covered in true form-accessibility work — because this single page carries the most combined financial and legal risk on the site.
Move to volunteer and event registration forms next. Same underlying issues, same fixes, and just as central to whether your organization can actually run its programs.
Then work through the PDF library — grant applications, annual reports, financial disclosures — prioritizing whichever documents get the most public traffic or are tied to active federal funding relationships.
None of this requires rebuilding your website. It requires an audit that tells you, specifically, which of these items are broken on your actual site, and a remediation plan scoped to what a small team can realistically execute.
Get an Audit Sized to Your Actual Budget
You don't need to guess whether your donation form, your volunteer sign-up, or your grant PDFs are creating real risk — legal or missional. WCAG.World builds accessibility audits and remediation plans specifically scaled to nonprofit budgets, prioritized around the pages that matter most: the ones where a broken form means a lost gift or a lost volunteer hour, not just a failed compliance check.
Get an accessibility audit sized and priced for a nonprofit budget →