What Is WCAG Level AA?
WCAG stands for Web Content Accessibility Guidelines. It's a set of recommendations from the World Wide Web Consortium that tells you how to make websites accessible to everyone — including people with disabilities. Level AA is the middle tier. It's stricter than Level A but not quite as demanding as Level AAA. And here's the thing: it's become the standard most governments expect. Montreal included.
Why does this matter? When you're building something for government use — whether it's a form, a document, or a full website — you're likely going to need Level AA compliance. It's not optional. It's the baseline.
The Four Principles Behind WCAG
WCAG is built on four core principles — think of them as the foundation. Everything else rests on these. They're called POUR: Perceivable, Operable, Understandable, and Robust.
Perceivable
People need to actually perceive the content. That means sufficient contrast between text and background. It means alt text for images. Videos need captions. You're not hiding information in ways that some users can't access.
Operable
People should be able to navigate and use your site without a mouse. Keyboard navigation matters. Links need to be keyboard-accessible. There shouldn't be any content that flashes more than 3 times per second — that can trigger seizures.
Understandable
Clear language. Consistent navigation. Predictable behavior. If you use jargon, explain it. Don't make people guess how your site works. Forms should have clear labels and error messages that actually help.
Robust
Your code needs to work across different browsers, assistive technologies, and devices. Clean HTML. Proper semantic markup. Your site shouldn't break in unexpected ways.
What Level AA Actually Requires
Level AA isn't vague. It has concrete requirements. We're talking specific contrast ratios, specific timing for interactive elements, specific ways to handle text resizing.
For text, you need a contrast ratio of at least 4.5:1 between text and background. That's dark text on light, or light text on dark. Large text — anything 18 points or bigger — can go down to 3:1. But regular body text? 4.5:1 minimum. No exceptions. You'll want to test this. Tools exist. Use them.
Forms are where things get detailed. Every input field needs a label. Error messages need to be clear and specific. If someone fills out a form incorrectly, tell them exactly what went wrong. Not "Error" — that's useless. Say "Phone number must be 10 digits."
Videos need captions. Not just for people who are deaf — also for people in noisy environments or quiet ones. Audio descriptions help too if there's important visual information. This is especially important for government videos where the content matters legally.
Pro tip: Most Montreal government projects use automated testing tools first, then manual review. Automated tools catch obvious stuff. Manual review catches the nuance — like whether your form error messages actually make sense to real users.
How to Test for Level AA Compliance
You don't have to guess. Testing is straightforward. Start with automated tools — they'll scan your site and flag contrast problems, missing alt text, and structural issues. Tools like WAVE, Axe, and Lighthouse are free and they work well.
But don't stop there. Automated testing catches maybe 30% of accessibility issues. The rest need human eyes. Try navigating your site with just a keyboard. No mouse. See if you can get everywhere. Use a screen reader. NVDA is free. See how it reads your content aloud.
Test with real people when you can. Someone with low vision using magnification. Someone with tremors using voice commands. Someone using a screen reader because they're blind. Their real experience matters more than any checklist.
For Montreal government projects, documentation matters. Keep records of what you tested, how you tested it, and what you found. If something can't meet Level AA for legitimate technical reasons, document that too — and explain your workaround.
Getting Started With Your Project
If you're building something new, accessibility should be part of your process from day one. It's easier to build accessible from the start than to fix it later. Here's what that looks like.
Start with semantic HTML. Use proper heading hierarchy. Use button elements for buttons, links for links. Use form elements properly. This foundation makes everything else easier. Then layer in good contrast, clear language, and keyboard navigation.
If you're updating an existing site, prioritize. Fix critical stuff first — contrast issues, missing form labels, broken keyboard navigation. Then move to medium priority. Then nice-to-haves. You don't have to do everything at once.
For Montreal projects, budget for accessibility. It's not free. You might need to hire specialists for testing. You'll need tools. You'll spend time on implementation. But it's required, and it's worth it. Level AA compliance isn't just about following rules. It's about making sure your government services actually work for everyone who needs them.
Important Note
Individual learning outcomes vary from person to person. This guide provides educational information about WCAG Level AA standards. For specific compliance requirements for your Montreal government project, consult official WCAG documentation and consider working with accessibility specialists who can review your particular implementation.
Moving Forward
WCAG Level AA isn't complicated once you break it down. It's really just about making sure your content is perceivable, operable, understandable, and robust. Four principles. Concrete requirements. Testing methods that work.
If you're working on a Montreal government project, you already know Level AA is required. Now you understand why — and how to actually achieve it. Start with the fundamentals. Test regularly. Listen to feedback from real users. Build incrementally if you need to.
It's doable. You've got this.