← All guides

Nonprofit website accessibility: where to start

November 12, 2026 · 4 min read

A donor who uses a screen reader opens your donate page, tabs through the form, and reaches a field with no label. They hear "edit text" and nothing else. They don't know whether it wants a name, an amount, or a card number, so they leave. You never learn they were there. Nonprofit website accessibility is mostly this kind of small, fixable failure, and you can find most of it in an afternoon without hiring anyone.

This is a plan for a small nonprofit with a volunteer or a part-time person looking after the site.

Start with the pages that take something from people

Check the donate page first, then the volunteer sign-up, then any event registration. These are the pages where a barrier costs a gift or a helper. The home page can wait.

If your donate page lives on a payment platform, the platform's form is part of your site as far as a donor is concerned. Ask the vendor whether it has been tested with a keyboard and a screen reader, and ask them to show you how. A reply that says "yes, we care about accessibility" is not an answer. Your donate page needs to load and work on a phone before any of this matters, so fix that first.

Run the keyboard test

This takes ten minutes and needs no software. Put the mouse out of reach. Open your donate page and use only the Tab key to move forward, Shift and Tab to move back, Enter to press a button, and the arrow keys to choose among options.

Watch for four things:

  1. You can see where you are. Each stop should show a visible outline or highlight. If the cursor vanishes, a keyboard user is lost.
  2. The order makes sense. Focus should move down the page the way you'd read it, not jump from the footer back to the top.
  3. You can finish. Choose an amount, enter details, and submit the gift using the keyboard alone.
  4. Menus open. Dropdown menus should open with the keyboard, not only when a mouse hovers over them.

Frank Lakatos, writing for Candid in 2020, recommends testing with a screen reader and walking through the site using only the keyboard, and lists free automated checkers such as WAVE and the audit tab in Chrome's developer tools. He is clear that automated tools are one part of the work and not the whole of it.

Small fixes for nonprofit website accessibility

Candid's article offers a few changes that a non-technical person can usually make or ask for:

  • Don't use color alone to mark a required field. Add the word "required" next to it.
  • Declare the page language, so a screen reader pronounces the words correctly.
  • Provide a transcript for any audio or video, so people who can't hear it still get the content.
  • Check heading order and color contrast, which an automated checker will flag for you.

Say your volunteer sign-up form marks required fields in red and nothing else. One person in the room is color blind, another is using a phone in bright sun, and both guess. Adding the word "required" to those fields fixes it in five minutes.

Know what you don't know

Accessibility has legal dimensions that differ by organization. Lakatos notes in the same Candid article that some organizations, for example those receiving federal funding, may be legally required to meet accessibility standards, and he advises consulting legal counsel. The standard usually cited is the Web Content Accessibility Guidelines from the W3C, which has levels A, AA, and AAA. If you want a target to give a web vendor, ask for conformance to the AA level and ask to see the testing.

You don't have to settle the legal question to start. Fixing the donate page, the sign-up form, and the labels is useful whatever the answer turns out to be.

Check the basics from outside

Some of what a visitor meets is outside the site's design: whether the page loads over HTTPS, whether the title and headings make sense, whether the donate and volunteer links work at all. The website scan checks those from the outside in a few seconds. It's free, and there's no paid version of it. It doesn't test accessibility, so the keyboard test above is still yours to do.

Write down what you find, fix the donate page first, and run the keyboard test again after any change to the form or the payment provider.

Website scan

See what your website tells a stranger

Enter your address and in a few seconds you'll see how your site looks to search engines, AI assistants, and email providers, and whether your donate link works. Free, with nothing to set up.

Related guides