ADA website compliance means making your nonprofit’s website usable by people with disabilities, and courts have increasingly treated websites as covered by the Americans with Disabilities Act. For most nonprofits there is no single federal technical standard to point to, but WCAG conformance, the W3C’s accessibility guideline set, is the accepted benchmark and the most practical way to reduce legal risk.
Most people searching for this topic have just had a scare. A board member forwarded an article about website lawsuits, or a demand letter landed at a peer organization, and suddenly “is our site compliant?” is the question of the week. The fear is understandable. It is also a bad planning tool. This guide walks through what the law actually says, where the real risk sits, and what a sensible nonprofit response looks like.
One thing before we start: Elevation is a web agency that has worked exclusively with nonprofits since 2007. We are not a law firm, and nothing in this article is legal advice. If you have questions about your organization’s specific legal exposure, talk to your counsel.
Does the ADA apply to nonprofit websites?
The Americans with Disabilities Act was signed in 1990, before websites were part of daily life, so the law never mentions them. Title III of the ADA prohibits discrimination by “places of public accommodation,” and many nonprofits (clinics, museums, food banks, schools, service providers) clearly fit that description in their physical operations. The long-running question has been whether a website counts as a place of public accommodation too.
Courts in different parts of the country have answered that question differently, but the overall direction has been consistent: judges increasingly apply the ADA to websites, particularly when the site is how people access an organization’s services. A few signals that your website deserves attention:
- You serve the general public, and your site is how people find and use your programs
- You accept donations, registrations, or applications online
- You receive federal funding, which brings additional obligations (more on that below)
- Your programs have digital front doors: intake forms, event signups, resource libraries
If several of those describe your organization, the useful question is no longer “does this apply to us?” It is “how do we get ahead of it?”
How do the ADA, Section 508, WCAG, and EN 301 549 fit together?
These four names come up constantly in accessibility conversations, and they do different jobs:
| Standard | What it is | Who it matters for |
|---|---|---|
| ADA | A U.S. civil rights law prohibiting disability discrimination | Organizations that serve the public, which includes most nonprofits |
| Section 508 | A U.S. law requiring accessible technology in federal contexts | Federal agencies and organizations that receive federal funding |
| WCAG | The W3C’s technical guidelines for accessible web content | Everyone; it is the benchmark courts and regulators reference |
| EN 301 549 | The European accessibility standard, which incorporates WCAG | Organizations working with or serving audiences in the EU |
The key relationship: the ADA states the right, and WCAG describes the practice. When a court, regulator, or funder asks whether a website is accessible, WCAG conformance is almost always the measuring stick. And if your nonprofit receives federal funding, read your grant agreements closely: Section 508 and related requirements can reach you directly, not just the agency that funds you. Your counsel can tell you exactly where you stand.
What does the legal risk actually look like?
This is where fear-based marketing thrives, so let’s stay measured. Web accessibility lawsuits and demand letters are real, and nonprofits are not exempt from them. But the shape of the risk matters more than any scary headline:
- Most matters begin with a demand letter, not a courtroom
- Outcomes usually center on remediation (fixing the site) plus legal costs, rather than dramatic damages
- The organizations most exposed are typically the ones that ignored accessibility entirely, not the ones with an imperfect but active program
- A documented, good-faith effort (an audit, a remediation plan, visible progress) changes the conversation if a complaint ever arrives
You will notice we are not quoting lawsuit counts. Those numbers get repeated out of context and shift year to year. The principle underneath them is stable: doing nothing is the risky position, and demonstrable progress is the defensible one.
Why is WCAG conformance the practical answer?
The Web Content Accessibility Guidelines are the W3C’s guideline set for accessible web content, organized around four principles: content should be perceivable, operable, understandable, and robust. At the commonly targeted AA level, conformance covers things like:
- Text alternatives for images, so screen readers can describe them
- Sufficient color contrast between text and backgrounds
- Full keyboard operability for people who cannot use a mouse
- Properly labeled forms, donation forms especially
- Captions for video content
- A logical heading structure that assistive technology can navigate
WCAG 2.2 Level AA is the target we point most nonprofits toward, and it is the default on every site Elevation builds. Our accessibility work is led by IAAP-certified professionals, because checklists only go so far — judgment about how real people use assistive technology matters just as much.
Do accessibility overlays and widgets solve the problem?
You have probably seen the pitch: add one line of JavaScript and your compliance worries disappear. It is worth being direct here. Overlays can adjust some surface-level presentation, such as font size and contrast toggles, but they sit on top of your code rather than fixing it. Many assistive-technology users report that overlays get in their way rather than help. And overlays have not proven to be reliable protection: organizations that rely on them have still faced accessibility complaints.
Treat an overlay, at best, as a supplement. It is never a substitute for accessible code, structure, and content.
What should your nonprofit actually do?
A calm, ordered response beats a panicked one. Here is the sequence we recommend:
- Start with an audit. You cannot prioritize what you have not measured. Our guide to running a nonprofit website accessibility audit walks through what to test and how.
- Fix the highest-impact issues first. Donation forms, navigation, color contrast, and alt text usually top the list. Our walkthrough on how to make your nonprofit website accessible covers the practical fixes.
- Publish an accessibility statement. Say what standard you target, acknowledge known gaps, and give people a way to report problems.
- Build accessibility into your process, not just your to-do list. If a redesign is on the horizon, accessibility is far cheaper to build in than to bolt on. It is baked into our Web Design & Development work from the first wireframe.
- Re-check on a schedule. Websites drift. Every new page, plugin, and PDF is a chance to regress, so pair periodic reviews with checks after major updates.
What is the better reason to do this?
Legal risk gets the attention, but it is the least interesting reason to act. Every community a nonprofit serves includes people with disabilities: aging donors with low vision, veterans, program participants, volunteers who navigate by keyboard or screen reader. When your website is inaccessible, it quietly turns away the very people your organization exists to reach — and their families, and their advocates.
Accessibility is not a defensive expense. It is mission delivery. And the side effects are all positive: clearer navigation, better-structured content, forms that work for everyone. Compliance is the floor. Reaching the people you set out to serve is the point.
The practical prevention lives in our accessibility best practices checklist.
ADA website compliance FAQs
Is WCAG legally required under the ADA?
Not by name for most nonprofits. The ADA does not spell out a technical web standard for private organizations, but WCAG is the benchmark courts and regulators consistently reference. Treating WCAG 2.2 Level AA as your working requirement is the practical position.
We receive federal funding. Does Section 508 apply to us?
Possibly. Section 508 requires accessible technology in federal contexts, and federally funded organizations often carry related obligations through their grant agreements. Review your agreements and ask your counsel rather than assuming the requirement stops at the agency that funds you.
Will an accessibility overlay protect us from lawsuits?
No tool can guarantee protection, and overlays in particular have not proven reliable. They adjust surface presentation without fixing the underlying code, and organizations using them have still faced complaints. Treat overlays as a supplement at most, never a substitute for accessible development.
What WCAG version and level should we target?
WCAG 2.2 Level AA is the target we recommend and the standard we build to by default. It is the current version of the guidelines and adds newer success criteria. If your site was built to an older version, a redesign is the natural moment to move up.
How often should we check our website for accessibility?
Accessibility drifts as content changes, so treat it as maintenance rather than a one-time project. A sensible rhythm for many organizations is a periodic review (annually works well as a baseline) plus a check after any major redesign, new form, or significant content addition.
If you would rather not carry this alone, that is a reasonable choice too. Elevation has worked only with nonprofits since 2007 (more than 1,000 of them), and accessibility is part of how we build, not an add-on. Take a look at our Accessibility Services, or request an accessibility consultation if you want a clear, honest picture of where your site stands. No pressure either way — the important thing is that you start.
