Jun 20, 2026

Accessible Donation Forms: A Nonprofit's Guide to Not Losing Donors (or Getting a Demand Letter)

There is a comfortable myth in the nonprofit world: that accessibility lawsuits are a problem for big-box retailers and hotel chains, not for the local food bank or the arts charity running on three staff and a volunteer board. The myth is wrong, and it is wrong in a way that costs money on both ends — donations you never receive, and legal demand letters you never saw coming.

Courts in the United States have repeatedly treated nonprofit websites as “places of public accommodation” under the Americans with Disabilities Act. A charity that invites the public to donate online is, in the eyes of the law, running a public-facing service. If a blind donor using a screen reader cannot complete your donation form, that is not a minor inconvenience. It is the exact fact pattern that plaintiffs’ firms look for when they send the demand letters that have become an industry of their own. And in Europe, the European Accessibility Act has tightened the rules further for organizations that take payments online.

The good news: donation forms are one of the most fixable things on a nonprofit website. You do not need a developer to find the problems, and most of the fixes are configuration changes in tools you already use. This guide walks through the barriers that actually block donors, why each one matters, and how to fix it — in plain English.

Why donation forms are uniquely high-risk

A donation form is the single most important interactive element on most nonprofit sites. It is also, far too often, an embedded widget from a third-party fundraising platform that nobody on staff has ever tested with a keyboard or a screen reader.

That combination is dangerous. The form is the page that converts a visitor into a supporter, so any barrier there has a direct financial cost. And because it is usually an iframe or script dropped in from a vendor, the people who chose it almost never checked whether it was accessible — they checked whether it had the right payment options and a logo upload.

Roughly one in four adults lives with a disability. A meaningful share of them use assistive technology: screen readers, screen magnifiers, keyboard-only navigation, voice control. When your donation form fails these users, you are not losing a rounding error. You are losing the most loyal cohort of donors there is — people who, once they find an organization whose process actually works for them, tend to stick around for years.

The seven barriers that block donors

Here are the issues that show up again and again on nonprofit donation forms. You can check for most of them yourself in about twenty minutes.

Almost every donation form offers preset amounts: $25, $50, $100, “Other.” Visually these are obvious. But they are frequently built as plain <div> or <span> elements styled to look like buttons, with no semantic role and no indication of which one is selected.

A screen-reader user hears nothing useful — maybe just “25” with no context that it is a selectable option, and no announcement when it becomes active. To test it yourself: turn on your computer’s built-in screen reader (VoiceOver on Mac, Narrator on Windows) and try to select an amount using only the Tab and arrow keys and the spacebar. If you cannot tell which amount is selected without looking at the screen, neither can your donors.

The fix is to use real radio buttons or real <button> elements with a clear pressed or selected state. On a hosted platform, this usually means choosing a different, accessible form template — which is a conversation to have with your vendor, not a coding job.

2. Form fields with no real labels

This is the most common accessibility failure on the web, and donation forms are full of it. A field that shows “Card number” as grey placeholder text inside the box, with no actual <label>, looks fine until the donor starts typing — at which point the hint vanishes and a screen reader may announce the field as just “edit text,” giving no clue what belongs there.

Every field — name, email, card number, billing ZIP, the comment box — needs a visible, persistent label that stays put when the field has content. Placeholder text is a supplement, never a substitute. This single fix resolves a huge share of the issues that automated scanners flag, and it helps everyone, not just assistive-technology users: anyone who gets distracted mid-form and forgets what an empty box was for.

3. Errors the donor can’t find or understand

A donor enters a card number wrong. The form rejects it. What happens next decides whether you keep the gift.

The accessible version moves focus to the error, names the specific field, and says what to do: “Card number must be 16 digits.” The inaccessible version turns the field border red and does nothing else — invisible to a screen-reader user, invisible to anyone with low color vision, and confusing to a stressed donor on a phone. Color alone is never enough to communicate an error. There must be text, and a screen reader must be told about it.

To test: deliberately submit the form with a blank required field and a bad email address. Does the page tell you, in words, exactly what is wrong and where? Does keyboard focus jump to the problem? If not, you are losing donors at the most fragile moment — the moment they have already decided to give.

4. A form you can’t complete with a keyboard

Many disabled users — and plenty of nondisabled ones with a broken trackpad — never touch a mouse. They move through a page with the Tab key and activate things with Enter or the spacebar.

Put your mouse down and try to make a full donation using only the keyboard. Can you reach every field, every preset amount, the “monthly” toggle, the cover-the-fees checkbox, and the final submit button? Can you actually see where you are — is there a visible focus ring moving from element to element? If the focus indicator is missing, or if any control is unreachable, the form is broken for keyboard users. This is one of the most common and most serious failures, and it is also one of the easiest to spot once you know to look.

5. Recurring-donation toggles that announce nothing

The “make this monthly” toggle is one of the highest-value elements on the form — recurring donors are worth far more over time. It is also frequently built as a custom switch with no accessible state. A screen-reader user cannot tell whether monthly giving is on or off, so they either avoid it or abandon the form.

A proper toggle announces its label and its state (“Monthly donation, off”) and updates when changed. If your form’s toggle is silent to a screen reader, you are quietly suppressing your most valuable donations from a whole category of supporters.

6. Time limits and CAPTCHAs that lock people out

Some donation flows time out for “security” or throw a visual CAPTCHA — “select all the traffic lights” — before completing payment. Both are barriers. A donor using a screen reader or a switch device may need more than a few minutes, and a purely visual CAPTCHA is impossible for a blind user and hard for many others.

If your platform imposes a session timeout, it must warn the user and let them extend it. If it uses a CAPTCHA, there must be a non-visual alternative, or better, a modern invisible method that does not challenge legitimate users at all. Ask your vendor which they use. “We use reCAPTCHA” is not automatically safe; the visual checkbox-and-images version still blocks people.

7. A confirmation that disappears silently

The donor hits “Give.” Visually, a green “Thank you!” appears. For a screen-reader user, nothing is announced — so they do not know whether the donation went through, and some try again, getting double-charged, or give up thinking it failed.

Confirmation messages need to be announced to assistive technology (using what developers call a live region) or the page needs to move focus to the thank-you heading. Either way, success must be communicated in more than a color and a checkmark icon.

How to check your own form in twenty minutes

You do not need to be technical to do a first-pass audit:

Run a free scanner. Paste your donation page URL into a tool like WAVE (wave.webaim.org) or run Lighthouse, which is built into the Chrome browser under Developer Tools. These catch missing labels, contrast failures, and missing structure automatically. Note: scanners find roughly a third of issues, so treat a clean scan as necessary, not sufficient.
Tab through it. Click into the address bar, then press Tab repeatedly. Watch where the focus ring goes. Try to complete the whole form without a mouse.
Turn on a screen reader. VoiceOver (Cmd+F5 on Mac) or Narrator (Ctrl+Win+Enter on Windows). Close your eyes and try to donate $25. You will learn more in five minutes than any report can tell you.
Test an error. Submit with a bad email. See whether the form explains the problem in words and sends you to it.

Write down what you find. Most of what you uncover will be the seven issues above, and most of them trace back to the donation platform itself rather than your own website.

The vendor conversation

Because the form is usually a third-party widget, your most powerful move is often a single email to your fundraising platform’s support team. Ask three direct questions:

Does your donation form meet WCAG 2.1 Level AA?
Can you share a VPAT or accessibility conformance report for the embedded form?
Are there accessible form templates, and which one should we use?

A reputable platform will have an answer. A platform that goes quiet or sends marketing fluff is telling you something important: your accessibility risk is sitting inside their product, and you may need to migrate to a form that does not expose you. Keep the email — documenting that you raised the issue and acted on it is exactly the kind of good-faith record that helps if a complaint ever lands.

What this means for your nonprofit

You almost certainly have at least three of these seven barriers on your donation form right now, and you can confirm it this afternoon without hiring anyone. Start with the two that do the most damage: real labels on every field, and a keyboard-completable flow with a visible focus ring. Fix those, then work through errors, the recurring toggle, and the silent confirmation.

This is not only a legal-defense exercise, though it is that too — a documented effort to test and fix is the best protection against a demand letter, and “we did not know” has never been a defense under the ADA. It is mission alignment. An organization that exists to serve a community cannot, in good conscience, run a donation process that excludes a quarter of that community from supporting it. The donors you are currently turning away are, very often, disabled people who care most about exactly the cause you champion.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.