Website Accessibility for Nonprofits: What Compliance Means and Where to Start

A donor who uses a screen reader lands on your donation page and hears "button, button, button." A parent with low vision cannot read gray text on white. A volunteer who cannot use a mouse tries to tab through your sign-up form and gets stuck. None of them tell you. They leave.

Website accessibility is the practice of building a site that people with disabilities can use, and for a nonprofit it is both the mission and, increasingly, the law. Here is what compliance means in plain terms, what the rules are in 2026, and where a small organization starts without a budget for a rebuild.

What the standard is

The standard nearly everyone uses is the Web Content Accessibility Guidelines, WCAG, published by the organization that sets web standards. Version 2.1 at Level AA is the benchmark written into United States regulations; version 2.2 exists and adds a few requirements. In plain terms, WCAG asks that content be perceivable, operable, understandable, and robust: text alternatives for images, captions for video, enough color contrast, everything reachable by keyboard, forms with labels, headings in order, text that can be enlarged, and pages that work with assistive technology. It is a long document; the handful of requirements below cover most of what a small nonprofit's site gets wrong.

What the law says in 2026

This is not legal advice, and the rules differ by who you are and who funds you.

• State and local governments are covered by a Department of Justice rule adopting WCAG 2.1 AA for their websites and apps, with compliance deadlines the Department extended in April 2026 to April 26, 2027 for larger entities and April 26, 2028 for smaller ones. A nonprofit that provides services on a government's behalf can find those obligations flowing through its contract.
• Recipients of federal funds are covered by Section 504 of the Rehabilitation Act, and the Department of Health and Human Services has adopted WCAG 2.1 AA for its funding recipients with its own deadlines beginning in 2026. If your organization receives federal health or human services money, confirm your date.
• Nonprofits that serve the public are generally treated as public accommodations under Title III of the Americans with Disabilities Act. There is no regulation setting a technical standard for private websites, but courts have increasingly treated WCAG 2.1 AA as the measure, and thousands of website accessibility lawsuits are filed in federal court each year.

The practical reading for a small nonprofit: WCAG 2.1 AA is the target whether or not a deadline applies to you, and the risk of doing nothing is rising. Our article on the compliance deadlines nonprofits quietly miss covers the others.

Accessibility is not a feature for some visitors. It is whether the door opens for everyone who comes to it.

The fixes that matter most

• Alt text on every meaningful image, describing what it shows. Decorative images marked as decorative.
• Color contrast between text and background that meets the standard's ratio. Light gray on white fails; so does white on a pale photo.
• Keyboard navigation: every link, button, menu, and form reachable and usable with the Tab key alone, with a visible indicator of where the focus is.
• Labeled forms, so a screen reader announces "email address" rather than "edit text." The donation form is the one to fix first.
• Headings in order, one main heading per page and sections nested beneath it, which is also what search engines and AI systems read.
• Captions on video and transcripts for audio. Most short video is watched with sound off anyway.
• Text that can be enlarged without breaking the layout, and no content that only works on hover.
• Links that make sense out of context. "Read our annual report," not "click here."
• Documents: PDFs are often the least accessible content on a nonprofit site. Publish the content as a web page where you can, and tag the PDFs you must keep.

Where to start

• Run an automated scan. Several checkers, including one built into common browsers, list the problems a machine can find, usually a third to half of the total.
• Do the keyboard test. Unplug the mouse and try to donate, sign up, and find the phone number. Where you get stuck, others get stuck.
• Do the screen reader test. Every phone and computer has one built in. Listen to your homepage and your donation page.
• Fix the templates first. Menus, headers, footers, and forms appear on every page; fixing them once fixes the site.
• Then the top ten pages, by traffic, starting with the donation and contact pages.
• Publish an accessibility statement with a way to report problems and a person who answers.
• Make it a habit: alt text and headings on every new page, captions on every new video, and the keyboard test after any change.

Adding the alt text, fixing the contrast and forms, captioning the video, and keeping every new page to the standard is part of what our Marketing department maintains for organizations without a web team. See how our staff keep your site open to everyone.

What does not fix it

Overlay widgets, the toolbars that promise one-line compliance, do not make a site accessible and have not protected organizations from complaints. Accessibility lives in the site's own code and content. Neither does a statement of good intentions substitute for the fixes. And a redesign does not guarantee it either, unless accessibility is in the requirements from the first day; our article on nonprofit website redesign shows where to put it.

Why it is also good for everyone else

Accessible sites load faster, read better on phones, rank better in search, and are easier for AI systems to summarize correctly, because the same structure that helps a screen reader helps a machine. Captions help people watching in a waiting room. Clear headings help a donor skimming on a lunch break. The work serves the mission twice.

Questions nonprofits ask about accessibility

Are small nonprofits really being sued over websites?

Most suits target businesses, but nonprofits are not exempt, and demand letters cost time and money whether or not they go anywhere. The better reason is the people you exclude, who never write to tell you.

Do we need to meet the standard perfectly?

Aim for WCAG 2.1 AA and fix the highest-impact problems first. Progress that is visible and ongoing is what both regulators and courts have looked for.

Does our donation processor's page have to be accessible too?

Yes, in practice, since it is part of your site to the person using it. Ask the vendor for its accessibility statement before choosing or renewing.

How much does it cost?

For most small sites, the fixes above are hours of work on templates and top pages rather than a rebuild. The cost of a rebuild is the cost of ignoring it until the site cannot be fixed.

Your mission is bigger than the visitors you can see

The people who cannot use your site are among the people your mission exists for, and the fixes are known and finite. You do not need to become an accessibility specialist on top of everything else. You need a staff that is already writing the alt text, already fixing the forms, and already captioning the video while you lead the mission only you can lead. Find out what our staff can do for you.

Zoya Syal is Content and Production Manager at Nonprofits Engine, where she leads the content and testimonial work for a team that helps small nonprofits get set up and funded.