Website Accessibility for B2B Companies: WCAG, AODA, ADA and SEO
What WCAG requires, how Ontario's AODA and the US ADA relate to business websites, the most common accessibility failures and how accessibility supports SEO.

In this article
- WCAG in Brief
- Legal Context in Canada and the US
- The Most Common Failures
- Where Accessibility and SEO Overlap
- How to Test
- Building Accessibility into Delivery
- About Overlay Products
- Cost and Timeline Considerations
- Recommendations
- How Webespire Consulting Can Help
- Frequently Asked Questions
- Conclusion
- Further Reading
Website accessibility means people with disabilities, including those who use screen readers, keyboard navigation, magnification or captions, can use your site. The Web Content Accessibility Guidelines (WCAG) are the international reference, with level AA the usual target. In Canada, Ontario's AODA requires many organisations to meet WCAG for their public websites, and federal accessibility laws apply to federally regulated sectors. In the US, the ADA is widely applied to websites through litigation and regulation. Accessibility also overlaps strongly with good SEO: clear structure, descriptive links, text alternatives and fast, usable pages benefit search engines and people alike.
This article is general information, not legal advice.
WCAG in Brief
WCAG is published by the W3C. Versions 2.0, 2.1 and 2.2 build on each other, and WCAG 2.2 became a W3C Recommendation in October 2023. Criteria are grouped under four principles: content must be perceivable, operable, understandable and robust. Each criterion has a level, A, AA or AAA. Most laws and policies reference level AA.
Legal Context in Canada and the US
- Ontario (AODA). The Integrated Accessibility Standards Regulation requires designated public sector organisations and private and non-profit organisations with 50 or more employees in Ontario to make public websites conform to WCAG 2.0 level AA, with limited exceptions, and to file accessibility compliance reports.
- Federal Canada. The Accessible Canada Act applies to the federal government and federally regulated sectors such as banking, telecommunications and transportation.
- Other provinces including Manitoba, Nova Scotia and British Columbia have accessibility legislation with standards developing over time.
- United States. Title III of the ADA has been applied to business websites in many lawsuits, though there is no single regulation setting a technical standard for private businesses. The Department of Justice's 2024 rule for state and local governments adopts WCAG 2.1 AA. Federal agencies follow Section 508.
If you sell to public-sector or enterprise customers, their procurement may also require accessibility conformance reports.
The Most Common Failures
| Issue | Who it affects | Fix |
|---|---|---|
| Missing or poor image alt text | Screen reader users | Describe informative images; use empty alt for decorative ones |
| Low colour contrast | Users with low vision | Meet 4.5:1 for normal text at AA |
| Unlabelled form fields | Screen reader and voice users | Visible labels associated with inputs |
| Keyboard traps or no focus indicator | Keyboard users | Logical focus order and visible focus styles |
| Links like "click here" | Screen reader users scanning links | Descriptive link text |
| Missing heading structure | Screen reader users navigating by headings | One H1, logical H2/H3 hierarchy |
| Videos without captions | Deaf and hard-of-hearing users | Accurate captions and transcripts |
| Inaccessible custom components | Many users | Native elements first; ARIA only when needed and correctly |
Where Accessibility and SEO Overlap
- Headings help both screen readers and search engines understand page structure.
- Alt text gives images meaning for assistive technology and for image search.
- Descriptive link text clarifies destinations for users and crawlers.
- Transcripts and captions make media content indexable.
- Semantic HTML and server-rendered content are easier for assistive technology and crawlers to interpret.
- Performance and mobile usability support both goals; see Core Web Vitals explained.
Accessibility should be done for users first; the SEO benefits follow.
How to Test
- Automated tools such as axe, Lighthouse or WAVE catch a portion of issues quickly. They cannot judge alt text quality or many interaction problems.
- Keyboard testing. Navigate every page and form using only the keyboard.
- Screen reader testing with NVDA or JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android.
- Zoom and reflow at 200 percent and 400 percent.
- Expert manual audit against WCAG criteria for key templates and journeys.
- Testing with disabled users where possible, for real-world insight.
Building Accessibility into Delivery
- Include accessibility criteria in design reviews and acceptance criteria.
- Use accessible component libraries and test custom components.
- Add automated checks to the CI pipeline.
- Train content editors on headings, alt text and link text.
- Publish an accessibility statement with a way to report problems.
About Overlay Products
Third-party overlay widgets that promise instant compliance do not fix underlying code issues and are criticised by many accessibility practitioners and users. Fix the source instead.
Cost and Timeline Considerations
An audit of key templates and journeys typically takes days to a few weeks depending on site size. Fixes range from quick content and CSS changes to rebuilding inaccessible components. Building accessibility into new projects from the start costs far less than retrofitting.
Recommendations
- Target WCAG 2.2 level AA for new work.
- Audit your main templates and conversion journeys.
- Fix the common failures first: alt text, contrast, labels, keyboard access, headings.
- Add automated checks and editor training to prevent regressions.
- Publish an accessibility statement and feedback route.
How Webespire Consulting Can Help
Our web application development team audits and fixes accessibility in code and design, and our technical SEO team aligns structure and content with search best practice. Planning a redesign? Read how to plan a website redesign without losing rankings.
Frequently Asked Questions
Which WCAG version should we follow?
WCAG 2.2 AA is the current best target. Some laws reference earlier versions, and meeting 2.2 generally covers them.
Does AODA apply to companies outside Ontario?
AODA applies to organisations that provide goods or services in Ontario and meet its criteria. Check with an adviser.
Can automated tools prove compliance?
No. They catch some issues; manual testing is essential.
Does accessibility improve rankings?
Accessibility is not a direct ranking factor, but many accessibility practices also improve how search engines understand and present your pages.
How often should we test?
On every release for automated checks, and with a manual review at least annually or after major changes.
Conclusion
Accessibility is a quality standard for every business website, and a legal requirement for many in Canada and the US. Target WCAG AA, fix common failures at the source, build checks into delivery and treat the SEO benefits as a welcome side effect.
Further Reading
Want an accessibility review of your website? Email info@webespire.com or visit webespire.com.



