Your website is the front door to your mission. For the millions of Californians living with disabilities, that door needs to open every time, on every device, without friction. Yet most nonprofits discover their accessibility gaps only after a complaint, a legal notice, or a frustrated donor who simply gives up. A solid nonprofit website accessibility checklist helps you get ahead of that. It maps the technical standards you must meet under federal and California law, the manual checks that automated tools miss, and the organizational policies that keep your site accessible as it grows.
Table of Contents
- Understanding accessibility criteria for nonprofit websites
- Core checklist items for nonprofit website accessibility
- Effective methods to evaluate website accessibility
- Prioritizing and managing accessibility improvements for nonprofits
- Accessibility checklist comparison: key components at a glance
- Our perspective: accessibility is a mission statement, not a legal task
- Build a site that serves every member of your community
- Frequently asked questions
Key Takeaways
| Point | Details |
|---|---|
| WCAG 2.1 Level AA is baseline | California nonprofits must target WCAG 2.1 Level AA for ADA and state accessibility compliance. |
| Alt text and captions critical | Descriptive alt text and accurate captions make media accessible to a wider audience. |
| Combine automated and manual checks | Automated tools alone can’t confirm accessibility; manual reviews and assistive tech tests are essential. |
| Prioritize high-impact pages | Focus audits and fixes on donation, registration, and frequently used site functions first. |
| Maintain ongoing policies | Accessibility is continuous; train staff and establish clear policies to sustain compliance. |
Understanding accessibility criteria for nonprofit websites
Before you can check anything off a list, you need to know what standard you are checking against. For nonprofits in California, the baseline is WCAG 2.1 Level AA, the required technical standard under the ADA Title II rule for state and local governments’ web content, and the benchmark most courts and regulators look to when evaluating private nonprofits as well. WCAG stands for Web Content Accessibility Guidelines. Level AA is the middle tier, stricter than Level A but realistic for most organizations to achieve without a full rebuild.
California adds another layer through AB 434, which requires state agency websites to certify compliance with WCAG 2.1 Level AA. While AB 434 applies directly to state entities, it sets a clear signal for how California regulators interpret “accessible” for any publicly serving organization. If you follow best practices for nonprofit websites and aim for WCAG 2.1 Level AA, you are aligned with both federal and state expectations.
Accessibility under these standards covers four major disability categories, and your checklist must address all of them:
- Visual impairments: Users who are blind or have low vision rely on screen readers, high-contrast modes, and text alternatives for images.
- Auditory impairments: Deaf or hard-of-hearing visitors need captions on videos and transcripts for audio content.
- Cognitive and learning differences: Clear language, consistent navigation, and predictable layouts reduce barriers for users with dyslexia, ADHD, or cognitive disabilities.
- Physical and motor impairments: Users who cannot operate a mouse depend entirely on keyboard navigation and voice-control software.
Compliance is not a single switch you flip. It is a combination of technical implementation and genuine accommodation for individual user needs. Publishing an accessibility statement on your site is one signal that your organization takes this seriously and provides users a clear path to request accommodations.
With a clear understanding of the standards nonprofits must meet, let’s examine the key checklist items that embody these criteria.
Core checklist items for nonprofit website accessibility
This is where the work happens. A practical checklist for website compliance covers six core areas, each tied directly to WCAG 2.1 Level AA criteria. Common technical gaps include missing alt text, video captions, and semantic headings, all of which map directly to WCAG evaluation techniques reviewers will check first.
Alt text for images
Every image that communicates meaning needs a short, descriptive alt attribute. “Photo1234.jpg” tells a screen reader nothing. “Volunteer handing food boxes to families at our Sacramento distribution event” tells the full story. Decorative images, like background textures, should carry an empty alt attribute (“alt=”"`) so screen readers skip them entirely.
Video captions and audio descriptions
All video content must have synchronized, accurate captions. Auto-generated captions from video platforms are a starting point, not a finish line. They regularly misidentify speakers, mangle proper names, and miss background audio. Review your captions manually, or use a service that specializes in audio description and video captioning for content that also includes visual-only information. Speaker identification matters too, especially in interview or panel videos.
Semantic headings
Headings are not just visual formatting tools. Screen readers use heading levels (H1 through H6) to let users jump directly to sections. A page that uses bold text styled to look like headings, but is not actually tagged as headings in the HTML, is completely unnavigable for screen reader users. Correct SEO content and semantic markup serves both search engines and assistive technology at once.
Form accessibility
Every input field on your donation form, event registration page, or contact form needs a programmatic label, not just placeholder text that disappears when someone starts typing. Error messages must be specific and tell users exactly what to fix. “Please enter a valid value” fails the test. “Please enter a valid email address, for example: name@domain.com” passes it.
Keyboard navigation
Tab through your entire website using only a keyboard and no mouse. Can you reach every link, button, and form field? Is the focus indicator (the visible outline that shows where you are on the page) clearly visible at all times? If it disappears, keyboard users are lost.
- All interactive elements must receive keyboard focus in a logical order.
- No content should trap keyboard focus in a loop with no exit.
- Dropdown menus must be operable without a mouse.
Pro Tip: Test keyboard navigation starting from your donation page. If a donor cannot complete a gift using only the keyboard, you are losing contributions and failing a critical compliance requirement at the same time.
After reviewing these key checklist elements, the next step is to understand how to verify them effectively.
Effective methods to evaluate website accessibility
Knowing what to check is half the battle. Knowing how to check it accurately is the other half. Most nonprofits start with automated tools, which is fine as a first pass, but automated reports alone can miss real barriers or flag non-blocking issues, making a combination of automated and manual review the only reliable approach.
Here is a practical evaluation sequence:
- Run an automated scan using a tool like WAVE or axe. This surfaces obvious issues quickly: missing alt text, empty links, low color contrast. Log every flagged issue before moving on.
- Conduct keyboard-only navigation through your five most critical user flows: making a donation, registering for an event, submitting a contact form, finding your service locations, and accessing your resources page.
- Test with a screen reader. NVDA (free, Windows) and VoiceOver (built into Mac and iOS) are the most common. Read through your homepage and at least one form page. Listen for how headings, images, and buttons are announced.
- Check color contrast using a tool like the WebAIM Contrast Checker. Body text requires a minimum 4.5:1 contrast ratio against its background. Large text (18pt or 14pt bold) requires 3:1.
- Review on mobile devices across at least two browsers. California donors and volunteers increasingly access nonprofit sites from phones, and touch targets need to be large enough to activate without precision tapping.
The biggest mistake nonprofits make in accessibility evaluation is treating a clean automated report as proof of compliance. An automated scan might catch 30 to 40 percent of real barriers. The rest requires a human to navigate the site the way a person with a disability actually would.
Pro Tip: Ask a colleague to navigate your donation form using only VoiceOver or NVDA with the screen off. Their experience in real time will show you more than any report.
Check your accessibility evaluation best practices regularly, not just when you redesign. Content editors adding new pages, images, or videos introduce new gaps every day.
Prioritizing and managing accessibility improvements for nonprofits
A complete audit will almost always surface more issues than you can fix at once. The goal is not perfection overnight. It is a clear, prioritized plan that addresses the highest-risk barriers first and builds a culture of ongoing compliance. Organizations should prioritize high-risk user journeys and audit content and applications accordingly.
Focus your first round of fixes on the areas that affect the most users or carry the highest legal risk:
- Donation and payment flows: Any barrier here directly blocks financial support and represents a significant compliance risk.
- Event registration and program sign-ups: If community members cannot register for your services, the mission impact is immediate.
- Contact and intake forms: These are often how people request help, making inaccessibility here especially harmful.
- Navigation and site-wide elements: Header menus, footers, and search functions affect every page.
Beyond web pages, your checklist must include documents. PDFs and Word files linked from your site are covered under federal accessibility scoping rules. An inaccessible PDF annual report or program flyer is a compliance gap. Review documents for tagged structure, reading order, and alt text on embedded images.
Third-party tools require attention as well. Embedded donation platforms, event ticketing systems, and chatbots are part of your user experience. Review contracts to confirm vendors are required to deliver accessible tools. If a vendor cannot meet WCAG 2.1 Level AA, that is a business decision you need to make consciously, not a gap to overlook. Support for ongoing accessibility through a dedicated accessibility support and care plan can help you manage this continuously.
Finally, embed accessibility into your organization’s operations. Train content editors to write descriptive alt text, use proper heading levels, and caption new videos before publishing. A one-time audit without follow-through training is a short-term fix, not a solution. Consider creating an accessibility statement that documents your current compliance level, your remediation timeline, and your contact for accommodations.
Accessibility checklist comparison: key components at a glance
WCAG 2.1 Level AA criteria organize accessibility into four principles: Perceivable, Operable, Understandable, and Robust. The table below maps your checklist items to these principles and notes where automated tools help versus where manual review is essential.
| Checklist item | WCAG principle | Automated detection | Manual review needed | Regulatory priority |
|---|---|---|---|---|
| Alt text for images | Perceivable | Partial (flags missing, not poor quality) | Yes, for descriptive accuracy | High |
| Video captions | Perceivable | No | Yes, for accuracy and sync | High |
| Color contrast | Perceivable | Yes | Yes, for complex backgrounds | High |
| Keyboard navigation | Operable | Partial | Yes, full flow testing | High |
| Focus indicator visibility | Operable | Partial | Yes | Medium |
| Semantic heading structure | Understandable | Yes | Yes, for logical order | High |
| Form labels and error messages | Understandable | Partial | Yes | High |
| PDF and document accessibility | Perceivable / Understandable | Limited | Yes | Medium |
| Third-party tool compliance | Robust | No | Yes, vendor audit | Medium |
| Accessibility statement | Policy | No | Yes | Medium |
A few patterns stand out from this table. Items in the Perceivable and Understandable categories tend to carry the highest regulatory risk and the most direct impact on users with visual or cognitive disabilities. Operable items like keyboard navigation and focus indicators are often invisible to sighted users, which is exactly why they get missed. And the Robust category, particularly third-party tool compatibility, is where even well-intentioned nonprofits leave gaps because the responsibility feels shared but goes unverified.
For SEO and accessibility integration, note that most high-priority checklist items, semantic headings, descriptive alt text, clear link text, also directly improve how search engines read and rank your content. Accessibility and discoverability reinforce each other.
Our perspective: accessibility is a mission statement, not a legal task
Most accessibility guides frame this entirely as a compliance exercise. Fix the violations, avoid the lawsuit, move on. That framing misses what is actually at stake for nonprofits specifically.
Your organization exists to serve a community. In many cases, the people most likely to be disabled are also the people most likely to need your services. When your website is inaccessible, you are not just risking legal exposure. You are telling a portion of your community that the front door is closed to them. That is a direct contradiction of your mission, regardless of how your programs work in person.
We have worked with nonprofit web projects since 2005, and the organizations that treat accessibility as a mission value rather than a compliance checkbox make better websites overall. Their content is clearer, their forms are simpler, their navigation is more logical. That is not a coincidence. Designing for people with the widest range of needs forces you to simplify and clarify in ways that benefit every visitor.
The practical implication is this: build your accessibility checklist into your content workflow, not just your annual audit. When you publish a new program page, ask if it has proper headings. When you upload a video, ask if it has reviewed captions. When you add a form, test it with the keyboard before it goes live. These habits cost almost nothing and prevent the accumulation of barriers that makes remediation so expensive later.
Build a site that serves every member of your community
If your current website is not yet meeting WCAG 2.1 Level AA, you are not alone, and the path forward is clearer than it might feel right now. At Nonprofit Web Design, we have been building purpose-driven websites for nonprofits since 2005, and accessibility is built into how we work, not added as an afterthought.
Whether you need a new site built to current web accessibility standards from the ground up, a focused accessibility audit of your existing site, or an ongoing care plan to maintain compliance as your content grows, we can help. Our team understands the specific pressures California nonprofits face, from mission alignment to limited budgets, and we design solutions that reflect your values. Reach out to learn how we can support your accessibility goals and help you serve your full community.
Frequently asked questions
What is the minimum accessibility standard nonprofits must meet in California?
Nonprofits in California should meet WCAG 2.1 Level AA, aligning with ADA Title II requirements and state certification standards to ensure effective communication and equal access for all users.
Can automated web accessibility checkers confirm full compliance?
No. Automated tools are useful for initial scans but cannot identify all barriers or assess real usability. Manual reviews and assistive technology testing are essential to verify true accessibility.
Which website content should nonprofits test for accessibility besides web pages?
Accessibility testing should include PDFs, Word documents, videos, interactive forms, and embedded third-party tools. Many teams overlook PDFs and attachments even though they fall under federal accessibility scoping rules.
How should nonprofits handle inaccessible third-party content on their sites?
Nonprofits must ensure vendors provide accessible content and may need to update contracts accordingly, since organizations are responsible for the accessibility of all public-facing content on their sites, including embedded tools.