A website ADA compliance checklist starts with WCAG 2.1 Level AA: color contrast, keyboard navigation, alt text on every meaningful image, captions on video, and forms that work with a screen reader. That is the standard most Department of Justice guidance and court settlements point to when they talk about an accessible website, and it is the baseline this checklist walks through.
Get it wrong and the cost is not only legal risk, though that risk is real. It is the donor who can’t tab through your donation form, the parent using a screen reader who can’t find your program list, the volunteer who gives up on a page with no visible focus state. For a mission-driven organization, the website is often a stranger’s first contact with the work, and an inaccessible one quietly turns people away before they read a word of the mission.
By the end of this guide, you will have a working checklist to audit your own nonprofit website, know which issues a free scanner can catch and which it can’t, and understand when the fix is a few days of cleanup instead of a full redesign.
Key Takeaways
- ADA website compliance in practice means meeting WCAG 2.1 Level AA, the standard DOJ guidance and most settlements treat as the bar for “accessible.”
- A real checklist covers color contrast, keyboard navigation, alt text, captions, form labels, and heading structure, not just a scanner’s pass or fail.
- Automated accessibility checkers catch obvious issues fast but miss most problems that require a person, or real assistive technology, to test.
- Legal exposure is real, but the bigger cost is excluding the donors, volunteers, and people a nonprofit exists to serve.
- Many of the highest-impact fixes don’t require a redesign. A rebuild is one path to compliance, not the only one.
What does ADA compliance mean for a nonprofit website?
ADA compliance for a website means meeting the accessibility standard the Americans with Disabilities Act is understood to require in practice: WCAG 2.1 Level AA. The ADA predates the modern web and names no specific technical standard, but Department of Justice guidance and the overwhelming majority of court settlements treat WCAG 2.1 AA as what “accessible” means.
Most nonprofit websites fall under Title III of the ADA, which covers places of public accommodation. Courts have increasingly applied that to websites offering programs, services, or a donation page to the public, even though Title III has no website-specific regulation yet. The safest assumption for a nonprofit: if your site serves the public, treat WCAG 2.1 AA as a requirement, not a nice-to-have.
Why accessibility is more than a legal checkbox
Roughly one in four U.S. adults lives with a disability, according to the CDC, and that proportion shows up in your donor list, your volunteer pool, and the people your programs serve. An inaccessible website doesn’t just risk a complaint. It quietly excludes some of the exact people a mission-driven organization exists to reach.
WebAIM’s annual audit of the top one million home pages finds detectable accessibility failures on the large majority of them, year after year, most commonly low-contrast text, missing alt text, and form inputs with no label. A good mission doesn’t exempt a site from these patterns.
This is also where human-centered design and accessibility overlap more than most teams expect. Clear hierarchy, honest labels, and a visible focus state help a screen reader user and a stressed first-time donor on a bad connection. Build for one, and you usually build for both.
The website ADA compliance checklist: 10 things to check
Work through these on your own site before you call anyone:
- Color contrast meets at least a 4.5:1 ratio for normal text and 3:1 for large text.
- Every meaningful image has alt text; purely decorative images are marked so screen readers skip them.
- The whole site works by keyboard alone, with a visible focus indicator on every link, button, and form field.
- Forms, especially the donation form, have labeled fields, clear error messages, and never rely on color alone to flag a problem.
- Headings follow a logical order (H1, then H2, then H3) instead of being chosen for visual size.
- Videos have accurate captions; audio-only content has a transcript.
- Links and buttons use descriptive text, not “click here” repeated across the page.
- Page titles and navigation landmarks are clear enough to navigate by screen reader alone.
- Text resizes up to 200% without breaking the layout or cutting off content.
- Time-sensitive content (a countdown to a giving deadline, an auto-advancing carousel) can be paused or stopped.
A free automated scanner will catch some of this instantly: missing alt text, obvious contrast failures, unlabeled fields. It won’t catch most of it. Keyboard navigation, caption accuracy, and whether an error message actually makes sense to someone using a screen reader all require a person to test them, not just a crawler.
WCAG 2.1 AA: the standard behind the checklist
WCAG, the Web Content Accessibility Guidelines, is the technical standard the W3C maintains, and it’s what DOJ guidance and most settlements point back to. WCAG 2.1 organizes its requirements under four principles: content must be perceivable, operable, understandable, and robust enough to work with assistive technology.
“AA” is the middle of three conformance levels. Level A covers the most basic barriers; AAA is a stricter standard most organizations don’t attempt site-wide. AA is the level nearly every legal standard and public guideline settles on, which makes it the realistic target for a nonprofit website rather than a reach goal.
WCAG 2.2 has since added a handful of new success criteria, mostly around focus visibility and accessible authentication. WCAG 2.1 AA remains the baseline most guidance and litigation still cite.
Common accessibility mistakes on nonprofit websites
A few patterns show up often enough to check first:
- PDF annual reports and grant applications uploaded without a text layer, so a screen reader sees a blank page.
- Third-party donation widgets embedded from a payment processor that was never tested for accessibility.
- Image-heavy impact pages with no alt text on photos meant to carry the emotional weight of the story.
- Volunteer sign-up forms built in an old plugin with unlabeled fields and no visible error states.
- Auto-playing hero video with no caption track and no way to pause it.
None of these require rebuilding the site. They require someone going page by page and fixing what’s there.
When you need outside help, and when you don’t
Many of the checklist items above, contrast, alt text, headings, form labels, are things a comms or marketing team member can fix directly in the content management system, no developer required. Start there before assuming you need an agency.
What usually does need outside help: a site built on an old platform that can’t support keyboard navigation no matter what content changes you make, a legacy PDF library numbering in the hundreds, or a full audit against WCAG 2.1 AA with real assistive-technology testing, not just a scan.
If your site needs that deeper level of work, sector experience matters. A studio that has built product-led growth for Kiva or product work for nonprofits and NGOs has already navigated the budget and approval realities nonprofits work within, and treats accessibility as part of the design from the start, not a scan added at the end.
Frequently asked questions
Is ADA compliance legally required for nonprofit websites?
Most likely, if your site serves the public. The ADA itself doesn’t name a web standard, but courts increasingly apply Title III, which covers public accommodations, to nonprofit websites offering programs, donations, or services. Treat WCAG 2.1 AA as the practical requirement rather than wait for a case to clarify it.
What’s the difference between ADA compliance and WCAG?
The ADA is the law; WCAG is the technical standard used to judge whether a website meets it. There’s no official government website standard written into the ADA itself, so DOJ guidance and the courts have settled on WCAG 2.1 AA as the working definition of “accessible.”
How much does it cost to make a nonprofit website ADA compliant?
It depends on how far the site is from the standard today. Fixing contrast, alt text, and form labels on an existing site can often happen in-house for free. A full audit with manual testing, or rebuilding a site that can’t support keyboard navigation, runs into real design and engineering budget. Get an audit before you budget for a redesign you might not need.
Can a free accessibility checker make my site ADA compliant?
No. Automated checkers are a useful first pass that flags obvious issues quickly, but they miss most of what matters: whether the keyboard experience actually works, whether captions are accurate, whether an error message makes sense out loud. Treat a clean scanner report as a start, not a finish line.
Do small nonprofits have to comply with ADA website rules?
The ADA doesn’t carve out a size-based exemption for Title III. Enforcement and litigation risk tend to track visibility and public reach more than budget, but a small nonprofit’s donors and the people it serves are just as likely to need an accessible site as a large one’s.
The short version
A real website ADA compliance checklist goes past a scanner’s green checkmark: color contrast, keyboard access, labeled forms, captions, and a logical heading structure, all tested the way a real visitor would experience them. Most of that you can fix yourself. The rest, a platform that can’t keep up or a full audit with assistive-technology testing, is worth bringing in outside help for.
If you’ve worked through this checklist and found problems bigger than a content fix, see how we approach human-centered product design or start a conversation with Niftic. We’re a strategy-led brand and product studio that has spent over a decade building digital products for mission-driven organizations, accessibility included from the start.