- An accessible site works for people using screen readers, keyboards, magnification, and other assistive tech. That is 27% of Canadians 15 and over, about 8 million people (StatCan).
- In Ontario, the AODA requires WCAG 2.0 AA for public sites of businesses with 50+ employees, a deadline that passed in 2021. Reporting deadlines continue into 2026.
- The legal risk is real but concentrated: 4,187 US digital accessibility lawsuits in 2024 (UsableNet). The bigger everyday cost is customers who quietly leave.
- Almost everyone fails right now: 94.8% of the top million homepages have WCAG failures, led by low contrast on 79.1% of pages (WebAIM, 2025).
- The same fixes help SEO: alt text, heading structure, labels, and semantic HTML are what crawlers and AI tools read too.
- Most failures are cheap to fix and nearly free to avoid at build time. Skip the overlay widgets; fix the page.
Does your small business website need to be accessible? In Ontario, legally, yes once you have 50 or more employees. Practically, yes regardless, because 27% of Canadians aged 15 and over live with a disability (Statistics Canada), and a site they cannot use is a customer you never hear about.
Most of what gets written on this topic is either legal panic or jargon. This is neither. It is what accessible actually means, what the rules say in plain English, why the fixes overlap almost perfectly with good SEO, and how to check your own site this week for free.
What does "accessible" actually mean?
That a person can use your site regardless of how they see, hear, move, or process information. Concretely: someone using a screen reader (software that reads the page aloud) can understand your images and links; someone who cannot use a mouse can reach every button by keyboard; someone with low vision can read your text without archaeology-grade squinting.
The gap between how a page looks and what assistive tech receives is where most sites fail, and it is invisible until you look at it from the other side:
The same page, heard instead of seen
Three common page elements and what a screen reader announces. Toggle between a typical build and an accessible one.
What do AODA and the ADA require, in plain English?
In Ontario, the AODA (Accessibility for Ontarians with Disabilities Act) says public-sector organizations and private businesses with 50 or more employees must make public websites meet WCAG 2.0 Level AA, and that deadline passed on January 1, 2021. WCAG is the technical checklist (contrast, alt text, keyboard support, and so on); AODA is the law pointing at it. Businesses with 20 or more employees also file recurring accessibility compliance reports, with the next round due at the end of 2026. Under 50 employees, there is no website mandate today, but every revision of these rules has moved one direction.
South of the border, the ADA has produced an actual litigation industry: 4,187 digital accessibility lawsuits were filed in the US in 2024 (UsableNet), and 2025 filings are pacing higher. That matters to you mainly if you sell to US customers. For most Ontario small businesses, the honest framing is not "you will be sued." It is that the standard exists, the direction is set, and the practical work is the same either way.
The US lawsuit machine, for context
Digital accessibility lawsuits filed in US courts per year. Toggle the view.
Why does accessibility help SEO too?
Because Google's crawler experiences your site the way a screen reader does: no eyes, just structure. Alt text is how it knows what your photos show. Heading hierarchy is how it maps your page. Labeled forms, descriptive link text, and semantic HTML are how it understands meaning instead of guessing. Write "click here" everywhere and you have hidden your content from a customer and a crawler in one move.
The overlap runs deeper now that AI tools answer questions by reading pages. A machine deciding whether to cite you rewards the same clarity a screen reader needs. This is why accessibility basics are baked into every RMCM build rather than sold as an add-on: the semantic structure, contrast tokens, labeled forms, and alt text that make a site usable are the same things that make it citable. One job, two payoffs.
What are the common, fixable failures?
The same short list, on almost every site. WebAIM scans the top million homepages every year, and the 2025 results are a repair manual disguised as a survey:
What actually fails, and how hard it is to fix
The most common WCAG failures across a million homepages. Toggle between how common and how fixable.
Read that list again and notice what is not on it: nothing exotic. Contrast is a color change. Alt text is a sentence per image. Form labels and link text are copywriting. Keyboard support is mostly using real buttons and links instead of styled divs. This is why the "accessibility is expensive" reputation is mostly wrong; what is expensive is retrofitting it onto a site built carelessly, which is an argument about when, not whether.
Want a read on your site's basics?
Run the free RMCM audit. It checks the health fundamentals, and we will flag the obvious accessibility gaps while we are in there.
START WITH A FREE AUDITHow do you check your own site?
Two free tools and two manual tests, one evening total. First the tools: run your homepage through WAVE (WebAIM's checker, which highlights errors right on the page) and through Lighthouse in Chrome's developer tools, which scores accessibility out of 100. Both will overwhelm you slightly; focus on the error counts for contrast, alt text, labels, and empty links, because those are the big four.
Then the tests no tool can run. Put your mouse away and Tab through the page: can you reach the menu, every link, and the contact form, and can you always see where you are? Then zoom the browser to 200%: does the page still work, or do things overlap and vanish? Odds are you will find something, because 94.8% of the top million homepages have detectable failures, and the top million are the well-funded ones.
Almost everyone is failing this test
Share of the top one million homepages with detectable WCAG failures. Toggle the year.
Where does this sit on the priority list?
Below a working, converting site; alongside everything else you fix when you touch the code. If your contact form is dead or your first screen says nothing, fix those first, because an accessible site nobody can use is not the goal either. But accessibility should never be a separate project with its own budget line on a small business site. It is a standard you hold while doing the work you were already doing.
That is also the honest cost story. On a new build, doing this right costs close to nothing; the developer just has to care. On a retrofit, the price depends on how carelessly the site was built, which is one more question for the hiring conversation: ask a prospective designer how they handle accessibility, and listen for specifics like contrast, labels, and keyboard testing. "We install a widget" is the wrong answer; the widgets bolt a settings panel over broken code, and UsableNet's reports keep finding companies getting sued while using one.
| Fix | What it takes | Who benefits |
|---|---|---|
| Text contrast | Adjust colors to meet the WCAG ratio | Low vision, everyone on a phone in sunlight |
| Alt text | One honest sentence per meaningful image | Screen reader users, Google, AI tools |
| Form labels | A visible label on every field | Assistive tech, autofill, every rushed visitor |
| Link text | "Get a quote" instead of "click here" | Screen readers, scanners, crawlers |
| Keyboard support | Real buttons and links, visible focus | Motor impairments, power users, you someday |
Frequently asked questions
Does my small business website need to be accessible?
What is AODA website compliance in Ontario?
Does website accessibility help SEO?
How do I check if my website is accessible?
Do accessibility overlay widgets make my site compliant?
Build it for everyone, not for a lawsuit
The lawsuit framing gets attention, but it aims at the wrong target. A site built to dodge lawyers is a site built to a minimum; a site built for actual people, including the 8 million Canadians the average design brief forgets, is just a better site. It reads better in sunlight, works when the trackpad dies, converts the customer whose screen reader met your alt text instead of a filename.
So skip the panic and the widgets, and do the boring version: check your contrast, write your alt text, label your forms, and Tab through your own site once. If the check turns up a mess, the fixes ride along with whatever site work you do next; they are a standard, not a surcharge. And if you want to know where you stand today, the free audit is the place to start.
