WCAG 2.1 AA is the internationally recognized standard for making a website usable by people with disabilities, and it is the level most organizations aim for. In practice, it means your site can be seen, heard, navigated and understood by people who use screen readers, keyboards, magnification, captions and other assistive tools.
The short answer: what WCAG 2.1 AA requires
WCAG stands for Web Content Accessibility Guidelines. They are published by the World Wide Web Consortium (W3C), the international body that develops standards for the web. Version 2.1 was released in 2018 and added guidance for mobile devices, low vision and cognitive disabilities.
The guidelines are organized into three levels of conformance: A, AA and AAA. Level A covers the most basic barriers. Level AA builds on it and addresses the issues that most often block people in everyday use. Level AAA is the most demanding and is generally not expected for entire websites.
When people say a site “meets WCAG 2.1 AA,” they mean it passes every Level A and Level AA success criterion in the guidelines. That is the benchmark referenced most often in accessibility policies, procurement requirements and legal discussions.
How the accessibility standard works in practice
Every guideline traces back to four principles. Content must be:
- Perceivable: People can take in the information, whether they see it, hear it or read it through a screen reader. Images need text alternatives, videos need captions, and text needs enough contrast against its background.
- Operable: People can use the site with a keyboard alone, have enough time to read and act, and are not exposed to flashing content that could trigger seizures.
- Understandable: Pages behave predictably, forms explain what they need, and error messages tell people how to fix mistakes.
- Robust: The underlying code works reliably with assistive technologies, including ones that haven’t been built yet.
Under each principle are specific, testable success criteria. For example, normal body text should have a contrast ratio of at least 4.5 to 1 against its background. Form fields need visible labels that screen readers can announce. A keyboard user should always be able to see which element currently has focus.
Some criteria can be checked automatically by software. Others need a person to judge, such as whether alt text actually describes an image or whether link text makes sense out of context. Meeting WCAG 2.1 AA usually takes both.
Why web accessibility matters for nonprofits
Nonprofits exist to serve people, and the people you serve include people with disabilities. That covers donors, volunteers, program participants, board members and staff. If your donation form can’t be completed with a keyboard, or your event registration doesn’t work with a screen reader, someone who wants to support your mission is shut out.
There are practical reasons, too:
- Funders and partners are asking. Government agencies, foundations and institutional partners increasingly include accessibility expectations in grant and partnership requirements.
- Legal risk is real. Website accessibility complaints and lawsuits under the Americans with Disabilities Act are not limited to large companies. The Department of Justice has adopted WCAG 2.1 AA as the technical standard for state and local government websites, and it is widely treated as the reference point for other organizations as well.
- Accessible sites tend to work better for everyone. Clear headings, descriptive links, readable contrast and captioned video help people on phones, in noisy places, or reading in a second language.
- It supports search visibility. Many accessibility practices, like meaningful headings and descriptive alt text, also help search engines and AI tools understand your content.
For a mission-driven organization, accessibility is ultimately about whether your website reflects your values.
Common misconceptions about website accessibility
“An accessibility plugin or overlay will make us compliant.”
Toolbars and overlays that add a widget to your site do not fix the underlying code. A missing form label or a broken heading structure is still broken. Many people who rely on assistive technology find overlays get in the way. Real accessibility comes from fixing the site itself.
“We passed an automated scan, so we’re done.”
Automated tools are valuable and catch many issues quickly, but they cannot judge everything. Software can tell you an image has alt text. It can’t tell you whether that text is useful. A thorough approach pairs automated scanning with human review.
“Accessibility is a one-time project.”
Every new page, blog post, PDF and image is a chance to introduce a new barrier. Accessibility needs ongoing attention, just like security updates and content updates.
“Accessible means plain or ugly.”
Good accessible design is good design. Strong contrast, clear typography and consistent navigation make a site more polished, not less.
What to do next: a practical starting plan
You don’t have to fix everything at once. Here is a sensible order of operations for most nonprofits:
- Run a baseline audit. Scan your key pages to see where you stand. Start with your homepage, donation page, contact form, event pages and any program application forms.
- Prioritize the paths that matter most. Fix barriers on pages where people take action first, especially giving, registering, applying and contacting you.
- Fix issues at the source. If a problem comes from a theme setting or a reusable page-builder block, fixing it once can clear it across many pages.
- Review images and media. Add meaningful alt text to images, caption your videos and provide transcripts for audio.
- Train your content editors. Show staff how to use proper headings, write descriptive link text and add alt text when they publish.
- Publish an accessibility statement. Tell visitors your commitment and how to reach you if they run into a barrier.
- Monitor regularly. Rescan on a schedule so new content doesn’t quietly undo your progress.
This is the process we follow at Lookit. We built Lookit Accessibility Audit to scan WordPress sites against the standard and, importantly, trace each issue back to the specific page-builder element that caused it. That means fixes happen where the problem lives, rather than page by page. We pair those scans with human review, because no tool can judge everything on its own.
Frequently asked questions
Is WCAG 2.1 AA legally required for nonprofits?
Requirements depend on your organization, your funding sources and where you operate, and the law in this area continues to evolve. Many organizations treat WCAG 2.1 AA as the practical benchmark because regulators, courts and funders frequently reference it. Talk with a qualified attorney about your specific obligations.
What is the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2, released in 2023, adds new success criteria focused on areas like focus visibility, target size and easier authentication. A site that meets 2.2 at Level AA will also meet 2.1 at Level AA. Starting with 2.1 is a solid foundation, and moving to 2.2 is a natural next step.
How long does it take to make a website accessible?
It depends on the size of the site, how it was built and how many issues an audit finds. Some fixes, like correcting a theme color or a shared form style, can resolve problems sitewide quickly. Others, like reviewing every image and document, take longer and often become part of ongoing maintenance.
Do PDFs on our website need to be accessible?
Yes. Documents you post, such as annual reports, applications and event flyers, are part of your website experience. Where possible, publish key information as regular web pages, and make sure any PDFs you keep are properly tagged and readable by assistive technology.
This article is general information, not legal advice.
Talk to Lookit about an accessibility audit
Lookit has been building and managing WordPress sites since 2004, and we help nonprofits understand where their sites stand and what to fix first. If you’d like a clear picture of your site’s accessibility and a practical plan to improve it, get in touch with our team.