Website accessibility compliance under WCAG 2.1 means your site can be used by people with disabilities through keyboard navigation, screen readers and other assistive tools. In 2026, it is a legal requirement in Canada, the U.S. and the EU. Non-compliant businesses face lawsuits, fines and lost customers.
What Is WCAG 2.1 and Why Should You Care?
WCAG stands for Web Content Accessibility Guidelines. Version 2.1, published by the World Wide Web Consortium (W3C), defines the technical standards that make websites usable for people with visual, auditory, motor and cognitive disabilities. The “AA” level is the standard most laws reference. It covers things like text contrast, keyboard navigation, form labels and video captions.
If that sounds like a developer problem, it is not. It is a business problem. Here is why.
Lawsuits are accelerating. ADA-related web accessibility lawsuits in the United States have increased over 300% since 2018. In 2025, more than 4,600 federal lawsuits were filed against businesses with inaccessible websites. These are not just targeting large corporations. Small businesses, local restaurants and e-commerce shops are getting hit. The average settlement ranges from $5,000 to $150,000 depending on the case.
Canada has its own rules. In Ontario, the Accessibility for Ontarians with Disabilities Act (AODA) requires all organizations with 50+ employees to meet WCAG 2.0 AA standards. Federal accessibility legislation under the Accessible Canada Act extends similar requirements nationally. Non-compliance results in fines up to $100,000 per day for corporations.
Accessible sites rank better. The same practices that make a site accessible also make it easier for search engines to crawl and understand. Proper heading structure, descriptive alt text, semantic HTML and labeled form fields all send strong relevance signals to Google. Businesses that invest in accessibility often see measurable improvements in organic traffic within months.
One in four adults in North America lives with a disability. That is roughly 25% of your potential market. An inaccessible website turns those visitors away before they ever see your product or service.
The Legal Landscape in 2026
Three major regulatory frameworks now govern web accessibility. If your business operates online, at least one applies to you.
Americans with Disabilities Act (ADA) – United States. The U.S. Department of Justice formally ruled in 2024 that websites and mobile apps qualify as “places of public accommodation” under Title III. This ended years of legal ambiguity. Any business that serves the public must provide accessible digital experiences. Domino’s Pizza, Beyonce’s Parkwood Entertainment and thousands of small businesses have faced ADA web accessibility lawsuits. The plaintiff does not need to prove damages. They only need to prove the site is inaccessible.
AODA and the Accessible Canada Act – Canada. Ontario’s AODA has required WCAG 2.0 AA compliance for large organizations since 2021. The Accessible Canada Act now extends accessibility requirements to federally regulated industries including banking, telecommunications and transportation. British Columbia and Manitoba have introduced their own accessibility legislation. If you operate in Canada, assume you need to comply.
European Accessibility Act (EAA) – European Union. The EAA took effect on June 28, 2025. It requires all digital products and services sold in the EU to meet accessibility standards based on WCAG 2.1 AA. This includes e-commerce sites, banking platforms and any digital service available to EU residents. Canadian businesses selling to European customers are within scope.
Real enforcement is happening. In 2024, a New York federal court awarded $100,000 in damages to a blind plaintiff who could not navigate a regional grocery chain’s website. In Ontario, a financial services firm was fined $50,000 for failing to meet AODA web standards. These are not hypothetical risks. They are operational costs that compliance prevents.
Common Accessibility Issues on Business Websites
Most accessibility failures are not complex technical problems. They are oversights that compound over time. Here are the issues we find on nearly every site audit.
Low Color Contrast
WCAG 2.1 requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px bold or 24px regular). Light gray text on a white background, trendy pastel color schemes and low-contrast placeholder text in forms all fail this requirement. If your visitors squint to read your content, search engines notice too. Poor contrast correlates with higher bounce rates.
Missing Alt Text on Images
Every image on your site needs a text alternative that describes its content and purpose. Not “image1.jpg” or “photo.” A product image needs alt text like “Red leather crossbody bag with adjustable strap.” A team photo needs “Quake Media team at Vancouver office.” Screen readers announce these descriptions to blind users. Google uses them to understand your visual content.
No Keyboard Navigation
Many visitors cannot use a mouse. People with motor disabilities, repetitive strain injuries and power users all rely on keyboard navigation. Every interactive element on your site (links, buttons, form fields, dropdown menus) must be reachable and operable using only the Tab and Enter keys. Custom JavaScript menus and modal popups are the most common offenders.
Missing Form Labels
If your contact form, search bar or checkout page has input fields without proper <label> elements, screen readers cannot tell users what information to enter. Placeholder text is not a substitute for labels. It disappears when the user starts typing and is not reliably announced by assistive technology. Every input needs a visible, associated label.
Poor Heading Structure
Headings (H1 through H6) are not just visual formatting. They create an outline that screen readers use to navigate your content. Skipping from an H2 to an H4, using headings purely for font size or having multiple H1 tags breaks this navigation. Proper heading hierarchy also helps Google understand the topical structure of your pages.
Missing Skip Links
A skip link is a hidden link at the top of the page that lets keyboard users jump directly to the main content, bypassing the navigation menu. Without it, a keyboard user must Tab through every single nav link on every page load before reaching your content. Most business websites lack this basic feature.
Inaccessible PDFs and Documents
PDFs are some of the worst accessibility offenders. Scanned documents without optical character recognition (OCR), PDFs created from images and documents without tagged structure are completely invisible to screen readers. If you offer downloadable menus, brochures, contracts or reports, they need to be accessible. The simplest solution is often to provide the same content as an HTML page.
WCAG 2.1 AA Compliance Checklist
This checklist covers the four WCAG principles: Perceivable, Operable, Understandable and Robust. Work through each item. If you can check every box, your site meets the AA standard.
Perceivable (users can see or hear your content)
- Text contrast meets 4.5:1 ratio for normal text and 3:1 for large text against all backgrounds.
- All images have descriptive alt text that conveys purpose and content, not just file names.
- Videos include captions for spoken dialogue and audio descriptions for visual-only content.
- Content is readable at 200% zoom without horizontal scrolling or overlapping elements.
- Color is not the only way to convey information. Error messages use text labels, not just red highlighting.
Operable (users can interact with your site)
- All functions work with keyboard only. Every link, button, form field and menu is reachable via Tab and activatable via Enter.
- Focus indicators are visible. Users can see which element is currently selected when tabbing through the page.
- A skip link exists at the top of every page to bypass repeated navigation.
- No content flashes more than three times per second. Flashing content can trigger seizures.
- Users have enough time to read and interact. Session timeouts are adjustable or warn before expiring.
Understandable (users can comprehend your content)
- Page language is declared in the HTML
langattribute (e.g.,lang="en"). - Form errors are identified clearly with text descriptions that explain what needs to be corrected.
- Navigation is consistent across all pages. Menus appear in the same location and order.
Robust (your site works with assistive technology)
- HTML is valid and well-structured. No duplicate IDs, unclosed tags or improper nesting that confuse screen readers.
- ARIA attributes are used correctly where native HTML elements are insufficient. Custom widgets include proper roles, states and properties.
If your team cannot evaluate these items internally, an accessibility audit gives you a prioritized list of what to fix first.
Free Tools for Testing Accessibility
You do not need an expensive consultant to identify your biggest accessibility problems. These free tools catch the majority of automated issues.
WAVE (Web Accessibility Evaluation Tool). A browser extension from WebAIM that overlays accessibility errors, warnings and structural elements directly on your page. It highlights missing alt text, contrast failures, empty links and heading issues visually. Run it on every page of your site.
axe DevTools. A browser extension from Deque Systems that integrates into Chrome and Firefox DevTools. It scans for WCAG violations and provides detailed remediation guidance for each issue. The free version catches most critical problems.
Google Lighthouse. Built into Chrome DevTools, Lighthouse includes an accessibility audit that scores your page and identifies specific failures. It tests color contrast, ARIA usage, image alt text, form labels and more. Run it from the “Audits” panel in Chrome DevTools or from PageSpeed Insights.
Colour Contrast Analyser. A free desktop app from The Paciello Group that lets you test any color combination against WCAG contrast requirements. Point it at any element on screen and it reports the exact ratio. Essential for design reviews.
Manual screen reader testing. Automated tools catch about 30-40% of accessibility issues. The rest require manual testing. NVDA (free, Windows) and VoiceOver (built into macOS and iOS) let you experience your site the way blind and low-vision users do. Navigate your entire checkout flow, contact form and key pages with the screen reader. If you get stuck, your customers will too.
Cost of Compliance vs Cost of Non-Compliance
The numbers make the decision obvious.
Cost of getting compliant: A professional WCAG 2.1 AA remediation for a typical business website (10-30 pages) runs between $2,000 and $10,000 depending on the severity of existing issues. Sites with heavy custom functionality or e-commerce platforms may reach $15,000-$25,000. Annual maintenance and monitoring adds $500-$2,000 per year.
Cost of ignoring it: A single ADA web accessibility lawsuit costs $10,000-$50,000 to settle, even if you win. If you lose, damages and legal fees range from $50,000 to $150,000 or more. Repeat plaintiffs and serial litigators target businesses that have already been sued. AODA fines in Ontario reach $100,000 per day for corporations. EU enforcement under the EAA includes market access restrictions that can block your products entirely.
The hidden cost: Beyond legal exposure, inaccessible websites lose revenue from the estimated 1.3 billion people worldwide who live with disabilities. That population has a combined spending power of over $8 trillion. Even capturing a fraction of that market through better accessibility pays for remediation many times over.
Remediation is an investment with measurable returns in reduced legal risk, expanded market reach and improved search rankings. Non-compliance is a liability that grows more expensive every year. If you need a cost estimate for your site, our web development team provides fixed-price accessibility remediation quotes.
FAQ
Is WCAG compliance legally required for small businesses?
In the U.S., any business that serves the public can be sued under the ADA for having an inaccessible website, regardless of size. In Ontario, AODA applies to organizations with 50 or more employees. The EU’s European Accessibility Act applies to businesses selling digital products or services within the EU. Even if your specific jurisdiction does not have explicit web accessibility laws yet, courts increasingly reference WCAG 2.1 AA as the standard of care.
What is the difference between WCAG 2.0, 2.1 and 2.2?
WCAG 2.0 (2008) established the foundation with four principles: perceivable, operable, understandable and robust. WCAG 2.1 (2018) added 17 new success criteria focused on mobile accessibility, low-vision users and cognitive disabilities. WCAG 2.2 (2023) added nine more criteria including focus appearance, dragging movements and accessible authentication. Most current legislation references WCAG 2.1 AA as the minimum standard.
Can an accessibility overlay or plugin make my site compliant?
No. Accessibility overlay widgets (like AccessiBe, UserWay or EqualWeb) do not fix the underlying code issues that cause accessibility failures. Multiple lawsuits have been filed against websites using overlays, with courts ruling they do not constitute compliance. The National Federation of the Blind has publicly opposed overlay products. Real compliance requires fixing your site’s HTML, CSS and functionality at the code level.
How long does it take to make a website WCAG compliant?
A typical business website with 10-30 pages takes 2-6 weeks for full remediation depending on the number and severity of issues. Sites built on modern, well-structured platforms are faster to fix. Legacy sites with custom functionality, complex forms and extensive PDF libraries take longer. An initial audit takes 1-3 business days and gives you a clear scope of work.
Does accessibility help with Vancouver SEO?
Yes. Proper heading hierarchy helps Google understand your content structure. Descriptive alt text makes your images indexable. Semantic HTML improves crawlability. Page speed improvements from clean code benefit Core Web Vitals scores. Google has stated that accessibility best practices align with search quality guidelines. Sites that fix accessibility issues routinely see organic traffic increases of 10-30% within three to six months.
How do I know if my website is accessible?
Start with a free automated scan using WAVE or Google Lighthouse. These tools identify the most common issues like missing alt text, color contrast failures and form label problems. Then test your site manually using only a keyboard (no mouse) and a screen reader like NVDA or VoiceOver. If you can complete all key tasks (finding information, filling out forms, making a purchase) without a mouse, your site has a solid foundation. For a comprehensive evaluation, request a professional accessibility audit.
What are the most common WCAG failures on WordPress sites?
The top failures on WordPress sites are missing image alt text, themes with poor color contrast, plugins that generate inaccessible markup, missing form labels in contact form plugins, no skip link in the theme header and PDF documents uploaded without accessibility tagging. Most of these are fixable through theme adjustments, plugin configuration and content updates without a full rebuild.
Get Your Website Accessibility Compliant
Every month your site stays non-compliant is another month of legal exposure and lost customers. We provide fixed-price WCAG 2.1 AA remediation with a full audit, prioritized fixes and ongoing monitoring. No hourly billing surprises. No vague timelines.
Call us at 604-901-7668 or fill out the form below to get a compliance assessment for your site.
Want a quick look at where you stand? Run our free website audit for an instant accessibility snapshot. You can also explore our web development services or read about web design trends shaping 2026 to see how accessibility fits into the bigger picture.
Related: marketing strategy guide
Need help with this?
Quake Media helps businesses across Vancouver and Canada with SEO, PPC and custom web development. Get a free audit and see where your site stands.


