A nonprofit website accessibility audit is a structured review of your site against WCAG 2.2 AA, combining automated scans with expert manual testing using keyboards and screen readers. Cost depends on how many unique page types and interactive components your site has, not raw page count, and the deliverable is a prioritized findings report your team or your developer can act on.
If you’re collecting quotes for an audit right now, you’ve probably noticed they vary wildly — and it’s rarely clear why. Usually it’s because vendors are quoting different things: one is selling an automated scan with a logo on it, another is scoping days of expert testing. This guide walks through what a real audit includes, what actually drives the price, and how to tell the difference before you sign anything.
What does a nonprofit website accessibility audit actually cover?
A thorough audit measures your site against the Web Content Accessibility Guidelines (WCAG), the standard published by the W3C. Most audits use version 2.1 at the AA level, because that’s the benchmark courts, regulators, and funders most often point to. In practice, the work breaks into layers:
- Automated scanning across the site to flag machine-detectable issues like missing alternative text, low color contrast, and unlabeled form fields.
- Manual keyboard testing: can someone navigate every menu, form, and modal without touching a mouse, and can they always see where focus is?
- Assistive technology testing with screen readers such as JAWS, NVDA, and VoiceOver, checking what’s actually announced, not just what the code says.
- Key journey walkthroughs (donating, registering for an event, signing up to volunteer), because those are the paths where a barrier costs you the most.
- Document review for PDFs and downloadable reports, often scoped separately because each file takes specialized time to evaluate.
Why isn’t an automated scan enough?
Automated tools are genuinely useful, and any decent audit starts with one. But they can only detect the presence or absence of code patterns. A scanner can confirm an image has alt text; it can’t tell you the alt text says “IMG_4032.jpg.” It can confirm a form field has a label; it can’t tell you the error message never gets announced to a screen reader user who submits the form incorrectly.
The judgment calls (reading order, focus management, whether instructions make sense without visual context) require a human tester. That’s why an audit quote dramatically cheaper than the others is usually a scan wearing an audit’s clothes. If budget is tight, start with a self-check instead: our guide to auditing your nonprofit website’s accessibility walks through what you can test yourself in an afternoon, at no cost.
What drives the cost of an accessibility audit?
Here’s the part that surprises most nonprofit teams: total page count barely matters. A 900-page site built from ten templates costs about the same to audit as a 40-page site built from ten templates, because auditors test unique patterns, not duplicates. What actually moves the price:
| Cost driver | Why it affects the price |
|---|---|
| Unique page templates | Each distinct layout needs its own full pass of manual testing. |
| Interactive components | Donation forms, calendars, filters, carousels, and maps each need keyboard and screen reader testing across their states. |
| Third-party embeds | Donation processors and ticketing widgets add testing surface you don’t control. |
| Assistive technology matrix | Testing across more screen reader and browser combinations takes more hours. |
| Documents in scope | PDFs and downloadable reports are evaluated one by one. |
| Depth of remediation guidance | Code-level fix recommendations take longer to write than a list of problems. |
When you request quotes, share a list of your templates and interactive features rather than your page count. You’ll get more accurate numbers, and you’ll be comparing like with like.
Audit, monitoring, remediation — which do you need?
These three get bundled and confused constantly, so it’s worth separating them:
- An audit is a point-in-time expert assessment. It tells you where you stand today and what to fix first.
- Monitoring is ongoing automated scanning that catches regressions between audits. It’s useful, but it inherits every limitation of automated tools.
- Remediation is the actual fixing, whether your developer works from the report or the auditing team handles it directly.
Most organizations end up needing all three, but in that order. Paying for monitoring before you’ve had a manual audit means automatically watching a site you’ve never actually evaluated.
What should a good findings report include?
The report is the product, so hold it to a high bar. A useful one includes:
- Every issue mapped to the specific WCAG success criterion it fails
- A severity rating that separates blockers (someone cannot donate) from minor friction
- Where each issue lives: the template or component, with screenshots and steps to reproduce
- A recommended fix, specific enough for a developer to act on without guessing
- A plain-language summary your leadership or board can read in five minutes
Ask for a sample report before you hire anyone. If the sample turns out to be a raw scanner export with a cover page, keep looking.
How do you choose an accessibility auditor?
Credentials and methods matter more than portfolio polish. Look for:
- IAAP certification. The International Association of Accessibility Professionals certifies individual practitioners; CPACC and WAS are the common credentials. It’s the clearest signal that a human on the team has verified expertise, not just a subscription to a scanning tool.
- Manual testing, described specifically. Ask which screen readers and browsers they test with. Vague answers are an answer.
- Nonprofit context. An auditor who has tested donation flows, event plugins, and CRM-embedded forms before will find issues in yours faster.
- A retest plan. Fixing issues and verifying fixes are separate steps; ask how validation works after remediation.
Elevation’s Accessibility Services team includes IAAP-certified professionals, and because we’ve worked exclusively with nonprofits since 2007, the donation forms and event calendars in your stack are ones we’ve tested many times before. If you’d like to talk through scope before committing to anything, you can book a free accessibility consultation.
Will one audit make you compliant for good?
No — and any vendor who implies otherwise is selling something other than an audit. An audit is a snapshot. The day after it’s delivered, someone on your team publishes a blog post without alt text, uploads a PDF, or installs a new plugin, and your compliance picture shifts. Accessibility holds up when it becomes part of how the site is run:
- Train content editors on headings, alt text, and descriptive link text
- Re-audit after redesigns, platform migrations, or major new features
- Use monitoring between audits to catch machine-detectable regressions early
- Build accessibility into design decisions from the start; our roundup of nonprofit website best practices covers how it fits alongside everything else your site needs to do
And if an audit reveals problems too structural to patch (templates built without semantic markup, a theme that fights keyboard users), remediation can cost more than rebuilding accessibly. That’s a conversation for a Web Design & Development team; for what it’s worth, every site Elevation builds meets WCAG 2.2 AA by default.
For the day-to-day checklist behind the audit, see our nonprofit accessibility best practices.
Nonprofit website accessibility audit FAQs
Is an automated scan enough to protect us from ADA risk?
No. Courts have increasingly applied the ADA to websites, and disputes turn on whether real users with disabilities can complete real tasks, something automated tools can’t fully evaluate. Scans are a useful layer, not a defense.
How long does an accessibility audit take?
It depends on the same factors that drive cost: templates, components, and how many assistive technology combinations are in scope. A credible auditor will give you a timeline after seeing your site, not before.
Do small nonprofits really need an accessibility audit?
Size doesn’t exempt you from the ADA, and if your organization receives federal funding, Section 508 obligations may apply as well. The stronger argument is the mission one: barriers on a donation form or a services page shut out the very people many nonprofits exist to serve.
Should we audit against WCAG 2.1 or WCAG 2.2?
WCAG 2.2 is the W3C’s newer release and builds on 2.1 with additional success criteria. Version 2.1 AA remains the benchmark most legal and funding language references, but we audit against WCAG 2.2 AA as the default. Testing against 2.2 puts you slightly ahead of the curve.
How often should we re-audit?
After any redesign, migration, or significant new functionality, and periodically even without them, since small content changes accumulate. Between full audits, monitoring plus a trained content team keeps most regressions from piling up.
If you’re weighing an audit, the most useful next step is a conversation about your site’s actual templates and components. That’s what determines scope, and it’s a short discussion. You can see how Elevation approaches audits, remediation, and ongoing accessibility work on our Accessibility Services page, and when you’re ready, we’re happy to help you figure out what your site actually needs.
