Accessibility for Ontario Business Sites (AODA Without Theatre)

You open the site. The hero looks finished. The type is crisp. Then you try to tab through the menu. Focus vanishes. The form has no labels. Contrast fails on the CTA. Captions are “coming later.” Someone on the team says the accessibility badge in the footer covers it.

That is theatre.

Accessibility for Ontario business sites is not a costume you put on before an audit. It is whether real people can use the thing: keyboard, contrast, captions, forms, focus, and alt text that means something. If they cannot, trust dies before your offer gets a hearing.

This piece is plain-English AODA and WCAG clarity for Ontario businesses who want substance over costume, without invented legal advice and without a late remediation circus. A smoke-test checklist. Then a soft ask if you are building something that must work for real people.

AODA, WCAG, ADA: plain English

People mash these words together. They are related. They are not the same.

**WCAG** (Web Content Accessibility Guidelines) is the technical standard most teams mean when they say “accessible site.” Levels (A / AA / AAA), success criteria, testable checks. It is the shared language for what “works for more people” looks like in a browser.

**AODA** is Ontario’s Accessibility for Ontarians with Disabilities Act. It is law and policy in Ontario: obligations, timelines, and compliance language that sit above “we tried to be nice.” For websites and web content, Ontario’s public guidance has long pointed teams toward WCAG as the practical bar. Exact obligations, who is covered, and what “compliance” means for your organization change over time. Do not take a blog as legal advice. Read the current official Ontario accessibility guidance for your organization type, and get counsel when stakes are high.

**ADA** is US law (Americans with Disabilities Act). If you sell into the US, serve US users, or run a US entity, ADA risk shows up differently: lawsuits, demand letters, another enforcement culture. Ontario businesses still feel it when their site is the face for US buyers. Again: not legal advice. Know which jurisdictions you serve, then verify against current official sources.

Stop treating “AODA” as a sticker and “WCAG” as optional. One is the Ontario compliance conversation. The other is the practical standard you design and build to. Requirements move, so re-check official sources instead of freezing a 2019 blog post into policy.

Trust is use, not a badge

A footer badge does not make a site usable. A PDF audit from last year does not mean the redesign you shipped last month still works. A chatbot that greets screen-reader users with a trap is not hospitality.

Trust on a business site is built from boring, honest work. Can someone move with a keyboard and always see where they are? Can someone with low vision read the text and the controls? Can someone who is deaf or hard of hearing follow the video? Can someone finish a form without guessing what the field wants? Can assistive tech name buttons, links, and images without nonsense?

Those questions are not “extra.” They are what a scared client, a tired buyer, or a partner on a phone in bright sun is already asking with their body. Accessibility is whether the site respects that person. Costume is buying the appearance of care and skipping the use.

If you are in a trust-heavy vertical (law, health-adjacent, professional services), this is part of the face, not optional flavour. Related reading on trust as product: law firm website design in Toronto. Proof in the wild: Smithen Family Law.

Undirected AI makes the costume easier to buy. It will give you finished-looking pages, fluent copy, and plausible layouts. It will not give you accessibility. It invents alt text that describes nothing useful, colour pairs that look fine in a screenshot and fail contrast, focus order buried under clever motion, and form copy that sounds confident while leaving the label off the input. Having a model is not an advantage here. Every mill shares it. Edge is humans who push tools under rules that survive a keyboard pass.

If your “accessibility plan” is “ask the model to make it accessible,” you do not have a plan. You have theatre with a prompt.

A buyer smoke test (without costume)

Use this when you brief a redesign, review a vendor, or decide whether “we’re fine” is a feeling or a fact. Not a substitute for official guidance. A practical smoke test.

**Keyboard and focus**

- Tab order matches the visual reading order

- Focus is always visible

- Menus, modals, and drawers can be opened and closed without a mouse

- No keyboard traps

**Vision and contrast**

- Text and interactive controls meet a real contrast bar (aim WCAG AA as a working baseline unless your counsel or official guidance says otherwise for your case)

- Information is not colour-only

- Zoom and reflow do not destroy the layout

**Structure and meaning**

- One clear H1; headings in a sensible nest

- Links make sense out of context (“read more” is not a strategy)

- Images that carry meaning have honest alt text; decorative images are marked empty on purpose

- Tables and lists are real markup, not pictures of tables

**Forms and errors**

- Every field has a visible label

- Errors are named in text, not only in red

- Required fields are clear before submit

- Autocomplete where it helps; no mystery captchas that block real people

**Media and motion**

- Captions for meaningful audio/video

- Transcripts when the content is the point

- Motion that can be reduced or paused; no seizure-risk flashing

**Process, not poster**

- Accessibility is in the brief, not a post-launch surprise

- Someone owns the checks before ship

- Content editors know how to keep headings, alt, and forms intact after launch

- You re-test when the design system or CMS templates change

If a vendor cannot walk this list without sliding into badge talk, you are buying costume.

Refuse theatre without freezing the product

Refuse the late audit that only exists because a deadline got close. Refuse the “accessibility overlay” sold as a cure-all while the underlying markup stays broken. Refuse the redesign brief that never mentions keyboard, forms, or captions, then acts shocked at remediation cost. Refuse the homepage that looks cinematic and fails the first tab.

Also refuse the opposite theatre: performative maximalism that freezes the product while nobody ships. Accessibility is iterative work under a known standard. It is not a reason to never launch, and not a reason to launch garbage with a promise to fix it later.

When you write a redesign brief, put access in scope like you put SEO, CMS, and photography in scope. The website redesign brief frame still applies: name what must be true, not only what must look expensive. Soft path: Digital Experiences. Related selection context: how to choose a web design agency in Toronto.

We do not invent statutes. We do not sell fear. We build sites real people can use, under WCAG as the working language, and we tell clients to verify Ontario AODA obligations against current official guidance for their organization. In practice that means access in early discovery, not only in a pre-launch panic; systems that carry focus, contrast, and form patterns; semantic HTML over theatre components; content rules editors can follow without a specialist on every Tuesday; and humans who refuse undirected AI when it invents unusable confidence.

Tell us what you’re building. Start at /start-a-project, or explore soft context on /what-we-do/digital-experiences first. Bring the real constraints: who must use the site, which jurisdictions you serve, what already fails keyboard and forms. We will say fit or not. No badge theatre. No invented legal advice.