Web Accessibility Is Not Optional. Here’s What Your Website Is Getting Wrong.

One in four Canadians has a disability. Globally, the number is over one billion. If your website cannot be used by someone with a visual impairment, a motor disability, or a cognitive difference, you are not just creating a bad user experience. You are locking out a quarter of your potential customers, and in many jurisdictions, breaking the law.

What Web Accessibility Actually Means

Web accessibility means building websites that work for everyone, including people who navigate with a keyboard instead of a mouse, people who use screen readers to hear content read aloud, people with low vision who need to enlarge text, and people with cognitive disabilities who rely on clear, consistent navigation.

The international standard for web accessibility is the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). WCAG organizes its requirements around four principles. Content must be Perceivable (users can see or hear it), Operable (users can navigate and interact with it), Understandable (users can comprehend it), and Robust (it works across different devices and assistive technologies).

WCAG has three conformance levels: A (the bare minimum), AA (the standard that most legislation requires), and AAA (the gold standard, rarely mandated). When someone says a website needs to be "WCAG 2.1 Level AA compliant," they mean it meets the 50 success criteria across those first two tiers. That is the benchmark we will focus on here, because it is the one that matters for both legal compliance and genuine usability.

The Legal Landscape Is Tightening

Accessibility is not a suggestion. It is increasingly a legal requirement, and enforcement is accelerating worldwide.

• •In Ontario, the Accessibility for Ontarians with Disabilities Act (AODA) requires WCAG 2.0 Level AA compliance for all organizations with employees. Corporations face fines of up to $100,000 per day. Directors and officers face personal liability of up to $50,000 per day. The next mandatory compliance report is due December 31, 2026.
• •At the federal level, the Accessible Canada Act requires federally regulated industries to meet WCAG 2.1 AA standards, a stricter version of what AODA mandates.
• •In the United States, the ADA has been interpreted by courts to apply to websites. Web accessibility lawsuits have surged, with thousands filed annually.
• •The European Accessibility Act (EAA), which takes full effect in June 2025, requires WCAG 2.1 AA compliance across the EU for a wide range of digital products and services.

The trend is clear: every major jurisdiction is moving toward mandatory web accessibility. The standard they all point to is WCAG 2.1 Level AA. If your website meets that standard, you are compliant virtually everywhere. If it does not, your legal exposure is growing every year.

What WCAG 2.1 AA Actually Requires

The guidelines can seem overwhelming when you read the full specification, but most of the requirements come down to common sense once you understand them. Here are the areas where we see businesses fail most often.

• •Text alternatives for images. Every meaningful image needs an alt attribute that describes what it shows. "IMG_3847.jpg" is not an alt text. Neither is "logo." Decorative images should be explicitly marked as decorative so screen readers skip them.
• •Keyboard navigation. Every interactive element on your site, including menus, buttons, forms, and links, must be usable without a mouse. Many sites break this by removing the default focus outline in CSS, making it impossible for keyboard users to see where they are on the page.
• •Colour contrast. Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). White text overlaid on a photo does not count unless you guarantee the contrast regardless of the image content.
• •Form labels. Every form field needs a programmatic label that assistive technology can read. Placeholder text is not a label. Visually positioned text that is not associated with the input in the code is not a label.
• •Page language. The HTML document must declare its language with a lang attribute. This is literally a five-second fix, and one of the most common failures we find.
• •Heading structure. Headings must follow a logical hierarchy (H1, then H2, then H3) and describe the content they introduce. Using headings purely for visual styling breaks navigation for screen reader users who rely on heading structure to scan pages.
• •Responsive design. Content must reflow at 320 pixels wide without horizontal scrolling, and text must remain readable at 200% zoom without being clipped by fixed-height containers.

The Business Case Goes Beyond Compliance

Legal risk is a compelling reason to care about accessibility, but it is not the only one. Accessible websites consistently perform better across several business metrics.

Search engines and AI systems read websites much the same way assistive technology does. Proper heading structure, descriptive alt text, semantic HTML, and clean code are all factors that improve both accessibility and search visibility. A website that is easier for a screen reader to understand is also easier for Google to understand, and easier for ChatGPT to cite.

There is also the market size argument. In Canada alone, approximately 6.2 million people have a disability. That is 22% of the population. Their combined spending power represents billions of dollars annually. Businesses that make their digital presence accessible to this group gain a competitive advantage that most of their competitors are simply ignoring.

The Most Common Failures We Find

We run accessibility audits as part of every website assessment at Xavarro. Across dozens of audits, we see the same failures repeated over and over. Most of them are not difficult to fix. They were just never considered in the first place.

• •Missing language declaration on the HTML element. A five-second fix that almost every site we audit gets wrong.
• •Focus outlines explicitly removed in CSS. Developers remove the default browser outline because they think it looks ugly, without realizing they have made the site unusable for keyboard-only users. The fix is to replace it with a custom focus style, not to remove it entirely.
• •Images with meaningless alt text. "Logo," "image," "photo," "banner" – none of these tell a screen reader user what the image actually shows.
• •Navigation menus that only work with a mouse. Dropdown menus that open on hover but cannot be reached by keyboard. Hamburger buttons with no accessible label.
• •No skip-to-content link. Screen reader users have to listen to the entire navigation menu on every page load unless you provide a way to skip past it.
• •Fixed-height containers that clip text at 200% browser zoom. Low-vision users who enlarge text lose access to content that overflows its container.
• •No accessibility statement or compliance documentation whatsoever.

We recently audited a fitness business in Ontario whose website scored 36 out of 100 on our accessibility assessment. We found 14 distinct WCAG violations, including five Level A failures (the absolute baseline) and nine Level AA failures. The site had an "accessibility page" that consisted of two sentences and itself failed multiple accessibility standards. That business has since closed its doors.

Where to Start

If you have never thought about web accessibility before, the scope of WCAG 2.1 AA can feel overwhelming. Here is the practical approach we recommend.

First, get an honest assessment of where you stand. Run a free automated scan (tools like WAVE are available at no cost) to catch the low-hanging fruit. But understand that automated tools can only detect about 30% of accessibility issues. The rest require manual testing: keyboard navigation, screen reader verification, zoom testing, and colour contrast checks on real content.

Second, fix the quick wins. Adding a lang attribute, restoring keyboard focus indicators, labelling your navigation buttons, and writing proper alt text can be done in an afternoon. These fixes address the most critical barriers at minimal cost.

Third, plan for the deeper work. Responsive reflow, form redesign, heading restructuring, and content-on-hover patterns require more careful implementation. Build these into your next site update rather than treating them as a separate project.

Finally, make accessibility part of your ongoing process, not a one-time project. Every new page, every new feature, every content update should be checked against the guidelines before it goes live.

How We Can Help

At Xavarro, accessibility is one of the four dimensions of our AI Visibility Audit. We do not just flag failures. We score your site against the full WCAG 2.1 Level AA standard, explain what each failure means in plain language, and provide a prioritized remediation plan that distinguishes quick wins from structural changes.

We hold ourselves to the same standard. Our own website is built to WCAG 2.1 AA compliance because we believe you cannot credibly audit others for a standard you do not meet yourself.

Web accessibility is not a trend, a nice-to-have, or a checkbox exercise. It is a fundamental requirement for any business that wants to reach the widest possible audience, stay on the right side of the law, and build a digital presence that actually works for everyone.