Most nonprofit websites fail basic accessibility checks that quietly cost donations. You can catch the biggest offenders yourself in about 30 minutes: color contrast, missing image descriptions, and unlabeled form fields. Those three cover most of the legal and revenue risk without hiring anyone.
The short version
- In 2026, 95.9% of the top one million home pages had detectable Web Content Accessibility Guidelines (WCAG) failures, per the WebAIM Million report.
- The three most common failures, low-contrast text, missing image alt text, and unlabeled form fields, are also the three that hurt donation forms most.
- The U.S. Department of Justice (DOJ) now requires WCAG 2.1 Level AA for state and local governments, which cements the benchmark nonprofits get measured against.
- You can audit your highest-risk pages yourself in 30 minutes with free browser tools, no consultant required.
Why this matters more right now
Your year-end giving traffic is about to arrive, and accessibility failures convert worst exactly when volume is highest. September through November is when most nonprofits earn the bulk of their annual online revenue, with GivingTuesday landing on December 1 this year. A donor who uses a screen reader or navigates by keyboard and hits an amount field with no label does not file a complaint. They leave. Every accessibility defect on a donation page is also a conversion defect, and right now is the last clean window to fix them before the traffic shows up.
The problem is the norm, not the exception
Accessibility failures are standard across the web, and they have not improved in seven years. The 2026 WebAIM Million report, an automated analysis of the top one million home pages, found detectable WCAG failures on 95.9% of them, up from 94.8% in 2025, with an average of 56.1 errors per page. The six most common issues have been the same for seven straight years. Low-contrast text appeared on 83.9% of pages, missing alternative text on 53.1%, missing form input labels on 51%, empty links on 46.3%, and empty buttons on 30.6%. The takeaway is not that your site is uniquely bad. It is that the common failures are predictable, which is exactly why you can catch most of them in a fixed, repeatable check.
Check 1: Color contrast (10 minutes)
Low-contrast text is the single most common failure and the easiest to catch. It affects 83.9% of pages, and it is the one your design team most often creates on purpose in the name of a lighter look. WCAG success criterion 1.4.3, Contrast (Minimum), Level AA, requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, where large means 18 point or 14 point bold. Open your donation page and run the built-in contrast checker in your browser's developer tools, or a free tool like WebAIM's Contrast Checker. Test body copy, muted gray captions, button labels, placeholder text, and footer links. The repeat offenders are always the same: light gray on white, white text on a pale brand color, and any text sitting over a photo. In Webflow you fix most of these in the style panel in minutes. In WordPress it is usually a theme setting or a few lines of CSS. This is same-day work.
Check 2: Image alt text (10 minutes)
Missing alternative text hides your images from screen readers and from search engines at the same time. It affects 53.1% of pages and maps to WCAG 1.1.1, Non-text Content, Level A, the most basic tier of the standard. Use a free browser extension to list every image on the page without an alt attribute, or open the page source and scan for image tags. Meaningful images, a photo of a program participant or an infographic with a statistic, need descriptive alt text. Purely decorative images should carry an empty alt attribute so assistive technology skips them. There is a direct marketing payoff here too, because the same alt text feeds Google Image search, so this check pays for itself twice.
Check 3: Form labels (10 minutes)
Unlabeled form fields break your donation form for anyone using assistive technology, and the donation form is a form. This failure affects 51% of pages and maps to WCAG 3.3.2, Labels or Instructions, and 4.1.2, Name, Role, Value. This is the check that costs you money most directly. Put your mouse down and tab through the entire donation flow with the keyboard only. Every field, the email input, the gift amount, the recurring-gift toggle, should announce a clear label as you land on it. A gray placeholder that disappears when you start typing is not a label. It vanishes the moment a donor needs it, and screen readers do not reliably read it. If you cannot tab to a field at all, or the focus outline disappears, that is a bigger keyboard problem worth flagging for a developer.
What this does not cover
This is a triage, not a full WCAG 2.2 conformance audit. It catches the three highest-frequency, highest-impact failures and deliberately ignores the rest. It does not test keyboard focus order across a full page, the correctness of your ARIA attributes, motion and animation controls, video captions, heading structure, or dynamically loaded content. Those matter, and a complete audit covers them.
Two limits worth naming. First, the payment fields inside your processor's embedded frame, a Stripe element or a hosted donation platform, are the vendor's responsibility, and you cannot fix them from your own code. What you can do is choose a vendor that documents WCAG conformance. Second, this is not legal advice. The DOJ's 2024 rule requiring WCAG 2.1 Level AA applies to state and local governments under Title II of the Americans with Disabilities Act (ADA), not to nonprofits directly. Nonprofits generally fall under Title III as places of public accommodation, where the exposure comes from demand letters and private suits, and WCAG is the standard courts and plaintiffs reference. Talk to counsel about your specific risk rather than treating a passing triage as a clean bill of health.
What to do with what you find
Fix in order of effort and impact, not in the order you found the problems. Contrast issues are usually CSS-only and can ship the same day. Alt text is a content task your team can knock out without a developer. Form label fixes may need a nonprofit web developer if your form is hand-coded. Sequence the work by starting with the donation path end to end, then the top landing pages by traffic. To find those quickly, open GA4 and go to Reports, then Engagement, then Pages and screens, and sort by views. Fix the pages that actually carry your year-end traffic first.
When I ran this triage on a legal-services nonprofit's donation page last fall, the entire gift form used a pale gray placeholder as its only field label and failed 1.4.3 on every button. Both were fixable in an afternoon of CSS and template edits, and they were the difference between a form a screen-reader user could complete and one they could not. Nothing exotic. Just the same three failures that show up on nearly every site.
Frequently asked questions
Does the ADA legally require my nonprofit's website to be accessible?
There is no single statute that names a WCAG version for nonprofits the way the DOJ's Title II rule does for governments. Most nonprofits are covered as public accommodations under Title III of the ADA, and courts have increasingly treated websites as covered. The practical answer is that WCAG 2.1 Level AA is the standard you will be measured against, and demand letters citing it are common. Confirm your specific obligations with a lawyer.
What WCAG version and level should a nonprofit aim for?
Target WCAG 2.2 Level AA. It is the current published version and is backward-compatible with the 2.1 Level AA that the DOJ rule references, so building to 2.2 AA covers you against the benchmark everyone cites while keeping you current.
Can an accessibility overlay widget fix all of this for me?
No. Overlay widgets that promise instant compliance do not reliably achieve conformance, and sites using them have still been named in accessibility suits. The three failures above live in your source code and content, and the durable fix is to correct them there, not to paint over them with a script.
How often should I re-run this check?
Run it before any high-traffic season and after any redesign or template change. A contrast tweak or a new donation form can reintroduce a failure you already fixed, so a 30-minute pass each quarter, and always before year-end, keeps the highest-risk pages clean.
If you want me to run this triage on your nonprofit's donation flow and hand you a prioritized fix list before year-end giving starts, book a 20-minute read-out and I will walk you through exactly what to fix first.