Website Accessibility for Nonprofits: WCAG Basics Every Canadian Org Needs to Know

What Is WCAG (and Why It Matters for Nonprofits)?

WCAG (the Web Content Accessibility Guidelines) is the international standard for making websites usable by people with disabilities. It is organized into three conformance levels: A, AA, and AAA. Level A covers the most basic barriers, Level AA addresses the most common and significant ones, and Level AAA is the strictest tier. Level AA is the target referenced by most legislation, funders, and procurement policies, which makes it the practical goal for almost every organization.

For a nonprofit, the stakes go beyond compliance. Roughly one in four Canadian adults lives with a disability, so an inaccessible website quietly excludes a meaningful share of your donors, members, volunteers, and the communities you serve. Accessibility also affects reputation and funding: grant applications increasingly ask about inclusion practices, and a donation form that a screen reader cannot complete is a donation your org never receives. If you are planning a new build, our guide to nonprofit website design in Vancouver covers how accessibility fits into the bigger picture.

The Four Principles of Accessibility (POUR)

Everything in WCAG hangs off four principles, known by the acronym POUR. There are four principles of web accessibility:

1. Perceivable. People must be able to perceive your content with at least one sense. Example: a food bank adds alt text to its hamper photos so a blind donor using a screen reader knows what their gift provides.
2. Operable. Every function must work without a mouse. Example: a community association's event registration can be completed entirely with the Tab and Enter keys.
3. Understandable. Content and interfaces must be clear and predictable. Example: a charity's volunteer form labels every field and explains errors in plain language instead of turning a box red.
4. Robust. The site must work reliably with assistive technologies. Example: a society's site uses proper HTML headings and buttons so screen readers and browser tools interpret it correctly.

If you remember nothing else about WCAG, remember POUR. Almost every specific guideline is one of these four ideas applied to a particular type of content.

Accessibility Basics Checklist for Your Nonprofit Website

To make a nonprofit website accessible, start with these eight fundamentals:

• Sufficient colour contrast between text and background, so content is readable in bright light and for low-vision users (WCAG AA asks for a 4.5:1 ratio on normal text)
• Descriptive alt text on every meaningful image, describing what the image conveys, not just what it is
• Clear, consistent headings in a logical order (one H1, then H2s, then H3s) so screen reader users can scan the page the way sighted users do
• Keyboard navigation for everything clickable: menus, buttons, links, accordions, and modals
• Descriptive link text that makes sense out of context ("Read our 2025 annual report" rather than "click here")
• Captions or transcripts for every video and audio recording, including event recordings and impact stories
• Readable fonts and resizable text that hold up when a user zooms to 200%
• Accessible forms with visible labels on every field and error messages that explain what to fix

None of these items requires exotic technology. They are mostly disciplined content habits plus a website that was built properly in the first place.

Quick Wins You Can Fix This Week (No Developer Needed)

If your nonprofit runs on a modern CMS like Webflow, WordPress, or Squarespace, your team can fix several of the most common accessibility failures directly in the editor, today, for free.

Fix it yourself in the CMS

• Alt text. Open your media library or image settings and write a short description for every meaningful image. Decorative images can be marked decorative or left with empty alt text.
• Link text. Find every "click here," "learn more," and "read more" and rewrite it to say where the link goes.
• Heading order. Check that pages use one H1 and that headings step down in order. Never pick a heading level just because it looks nicer; style it instead.
• Colour contrast. Run your brand colours through a free contrast checker (WebAIM's is excellent) and darken or lighten text colours that fail.

Where you will likely need help

Some issues live in the template or code rather than the content: keyboard traps in custom menus, donation forms missing programmatic labels, focus states that were styled away, and missing landmarks or skip links. These need a designer or developer who understands accessible markup. The honest split matters, because a resource-constrained org should spend its own time on the content fixes and its budget on the structural ones.

Where Nonprofits Usually Fall Short

After auditing and rebuilding nonprofit sites, we see the same gaps repeatedly. They are worth calling out because most organizations have no idea these are problems:

• Inaccessible PDFs used for key documents: annual reports, AGM minutes, program applications. A scanned PDF is invisible to a screen reader. Publish important content as web pages, or remediate the PDFs.
• Donation and volunteer forms that screen readers cannot use. Third-party form embeds are frequent offenders. If your most important conversion point is inaccessible, everything else is secondary.
• Colour as the only way to convey information. "Required fields are shown in red" excludes colour-blind users. Pair colour with text, icons, or patterns.
• Auto-playing video or audio with no controls. It disorients screen reader users and can make a page unusable. Always provide pause and stop controls, or do not autoplay at all.

The pattern behind all four: the failure sits exactly where the organization's mission meets its audience. The report nobody can read, the donation nobody can complete.

Different structures also carry different expectations. Registered charities reporting to funders, member-based societies, and grassroots nonprofits each face slightly different pressures, which we break down in our guide to web design for charities, nonprofits, and societies.

How to Test Your Nonprofit Website's Accessibility

You can get a useful read on your site's accessibility in an afternoon, without spending anything. Use a three-pass approach:

1. Run an automated checker

Free tools like WAVE, Lighthouse (built into Chrome), and axe DevTools will flag missing alt text, contrast failures, and unlabelled form fields in seconds. Run them on your homepage, your donation page, and one or two content templates.

2. Navigate with keyboard only

Put your mouse aside and try to use the site with Tab, Shift+Tab, Enter, and arrow keys. Can you reach every menu item? Can you see where focus is at all times? Can you complete a donation? If you get stuck, so does every keyboard-dependent visitor.

3. Spot-check with a screen reader

Turn on VoiceOver (Mac) or NVDA (Windows, free) and listen to your homepage and a form. You will quickly hear whether images are described, buttons are named, and the reading order makes sense.

One honest caveat: automated tools catch only a portion of WCAG issues, often estimated at around a third. They cannot judge whether alt text is meaningful or whether a workflow is understandable. If your organization needs real assurance, for a funder, a board, or a procurement requirement, a professional audit with manual testing is the next step.

Accessibility and the Canadian Context

Accessibility expectations for Canadian organizations are rising on several fronts. The federal Accessible Canada Act applies to federally regulated entities, Ontario's AODA sets WCAG-based requirements for many larger organizations operating in that province, and BC's Accessible British Columbia Act is building out accessibility standards for the public sector and prescribed organizations. Human rights legislation across the country can also reach digital services, since a website is part of how an organization serves the public.

What this means for a typical BC nonprofit is nuanced. Many smaller organizations face no explicit statutory web accessibility requirement today, but the direction of travel is unambiguous, and funders frequently impose accessibility expectations through grant agreements regardless of what legislation says. Rather than treating any of this as settled legal fact, confirm your own obligations based on your province, size, sector, and funding sources, ideally with a legal advisor. Then aim for WCAG AA anyway, because it is the right thing to do for the people you serve and it future-proofs your site against requirements that are clearly coming.

Frequently Asked Questions

Accessibility Is a Mission Decision, Not a Technical One

Strip away the acronyms and WCAG asks one question: can everyone you serve actually use your website? For a mission-driven organization, that question answers itself. Start with the checklist above, fix what you can in the CMS this week, test with free tools, and bring in help for the structural pieces. The result is a site that reaches more people, earns more trust, and holds up as Canadian accessibility expectations continue to rise.

This is the standard we build to for every mission-driven client. Our work with Causeworx Inc., a Vancouver nonprofit, shows what accessible web design for nonprofits looks like in practice: a WCAG-compliant website where the donation path, the content, and the brand all work for everyone.