Skip to main content

    AODA Compliance Examples: What It Looks Like in Practice

    Before-and-after website fixes mapped to WCAG, and the notices every Ontario business needs, ready to adapt.

    Last reviewed . Accessibility rules change, so check the official sources linked below before you rely on a detail.

    What does AODA compliance look like?

    Mostly like a well-made website and a few clear notices. On the website, AODA compliance means meeting WCAG 2.0 Level AA: text alternatives, labelled forms, visible focus, enough contrast, captions and pages that work without a mouse. Off the website, it means telling people they can ask for accessible formats and give feedback.

    You will find lists of "AODA compliant websites" online. We do not publish one, because nobody can confirm a whole site conforms from the outside. What we can show you is the patterns that make the difference, each mapped to the WCAG success criterion it meets, so you can check your own site.

    The website rule applies to businesses with 50 or more employees. The notices apply to everyone with at least one. See AODA requirements by size for the full list.

    Website examples: before and after

    Images have a text alternative

    WCAG 1.1.1 Non-text Content (Level A)

    A screen reader reads the alt text out loud. With no alt text it reads the file name, which is rarely poetry.

    Before: fails

    <img src="IMG_4471.jpg">

    After: passes

    <img src="team.jpg" alt="Our three technicians outside the Guelph shop">
    <img src="divider.svg" alt="">  <!-- decorative: empty alt -->

    Form fields have real labels and clear errors

    WCAG 1.3.1, 3.3.1, 3.3.2 (Level A) and 3.3.3 (Level AA)

    Placeholder text disappears when you start typing and is often skipped by assistive technology. A red border alone tells a colour-blind visitor nothing.

    Before: fails

    <input type="email" placeholder="Email">

    After: passes

    <label for="email">Email</label>
    <input id="email" type="email" aria-invalid="true"
           aria-describedby="email-error">
    <p id="email-error">Enter an email address, like name@example.com</p>

    Vortio's own contact and enquiry forms work this way: visible labels, the error written under the field and linked to it, and focus moved to the first problem.

    Keyboard focus is visible

    WCAG 2.4.7 Focus Visible (Level AA) and 2.1.1 Keyboard (Level A)

    People who navigate with a keyboard or switch need to see where they are. Removing the outline is the web equivalent of turning off the hallway lights.

    Before: fails

    button:focus { outline: none; }

    After: passes

    button:focus-visible {
      outline: 2px solid #1e1b4b;
      outline-offset: 2px;
    }

    Text has enough colour contrast

    WCAG 1.4.3 Contrast (Minimum), Level AA

    Normal text needs a contrast ratio of at least 4.5:1, and large text 3:1. Low-contrast text was found on 83.9 percent of the top million home pages in WebAIM's 2026 scan, the most common failure by a distance.

    Before: fails

    color: #9ca3af;  /* on white: 2.54:1, fails */

    After: passes

    color: #4b5563;  /* on white: 7.56:1, passes */

    Check your own colours with the free contrast checker.

    Links say where they go

    WCAG 2.4.4 Link Purpose (In Context), Level A

    Screen reader users often pull up a list of links. Ten links called "click here" is a list of nothing.

    Before: fails

    <a href="/menu.pdf">Click here</a> for our menu.

    After: passes

    <a href="/menu.pdf">Dinner menu (PDF, 2 pages)</a>

    Pre-recorded video has captions

    WCAG 1.2.2 Captions (Prerecorded), Level A

    Captions help people who are deaf or hard of hearing, and everyone watching on a bus with the sound off. Live captions are one of the two criteria Ontario excepts.

    Before: fails

    <video src="tour.mp4" controls></video>

    After: passes

    <video src="tour.mp4" controls>
      <track kind="captions" src="tour.en.vtt"
             srclang="en" label="English" default>
    </video>

    There is a way to skip the menu

    WCAG 2.4.1 Bypass Blocks, Level A

    Without it, a keyboard user tabs through every navigation link on every page before reaching the content.

    Before: fails

    <header>...40 menu links...</header>
    <main>...</main>

    After: passes

    <a href="#main" class="skip-link">Skip to main content</a>
    <header>...</header>
    <main id="main" tabindex="-1">...</main>

    The page declares its language

    WCAG 3.1.1 Language of Page, Level A

    It tells a screen reader which voice and pronunciation rules to use. Without it, English can come out with a confused accent.

    Before: fails

    <html>

    After: passes

    <html lang="en-CA">

    WebAIM's 2026 scan of the top million home pages found detectable WCAG failures on 95.9 percent of them, and six error types (low contrast, missing alt text, missing form labels, empty links, empty buttons and missing page language) made up 96 percent of everything it detected. These eight examples cover that ground. They are not the whole standard. WCAG 2.0 Level AA has 38 success criteria in total, and Ontario excepts two of them. The accessibility checklist and testing guide walk through the rest.

    Notice and policy examples you can adapt

    Starting points, not legal text. Replace the brackets, make sure the promise matches what you actually do, and put the notices where people will find them: your website footer or contact page, your front counter and your printed materials.

    Accessible formats and communication supports notice

    O. Reg. 191/11, s. 12 (every business with 1+ employees)

    Accessible formats and communication supports are available on request. If you need information from us in another format, such as large print or plain text, or need help communicating with us, contact [name] at [phone] or [email].

    Feedback notice

    O. Reg. 191/11, s. 11 and s. 80.50

    We welcome feedback on how we provide accessible service. You can give it in person, by phone at [phone], by email at [email] or in writing to [address]. Feedback is available in accessible formats on request. We aim to respond within [number] business days.

    Temporary service disruption notice

    O. Reg. 191/11, Customer Service Standard (Part IV.2)

    Our accessible entrance at [location] will be closed from [date] to [date] for repairs. Please use [alternative entrance] or call [phone] and we will assist you. We apologize for the inconvenience.

    Service animals and support persons (policy line)

    O. Reg. 191/11, Customer Service Standard (Part IV.2)

    People with disabilities may be accompanied by a service animal in the parts of our premises open to the public, unless the animal is excluded by law. People accompanied by a support person may bring that person with them.

    For a public accessibility statement, use our accessibility statement template.

    Official Ontario templates

    Ontario publishes free samples you can build from, including an accessibility policy template, a multi-year accessibility plan sample, an accessible recruitment process, an accommodation process, a return-to-work process and a staff training checklist. They are listed under "Forms, checklists and sample templates" on Ontario's accessibility laws (opens in a new tab) page.

    Questions about AODA compliance examples

    What does an AODA compliant website look like?

    Usually like a normal, well-made website. Compliance shows up in details: real text alternatives on images, labelled form fields, a visible keyboard focus, enough colour contrast, captions on video and pages that still work at 200 percent zoom. Good accessibility is mostly invisible until it is missing.

    Can you name AODA compliant websites?

    Not honestly from the outside. Conformance is a claim about every page and process, so a list of "compliant websites" is a list of sites someone liked. We show patterns you can check and copy instead, with the WCAG success criterion each one meets.

    Is an accessibility statement enough for AODA?

    No. A statement explains your commitment and how to ask for help. It does not fix barriers. Organizations with 50 or more employees still need the site itself to meet WCAG 2.0 Level AA.

    Do I have to tell visitors about accessible formats?

    Yes. Section 12 of O. Reg. 191/11 requires every obligated organization to notify the public that accessible formats and communication supports are available. A short note on your website, such as in the footer or on the contact page, is one common way to meet it.

    Sources

    Checked on November 5, 2026.

    Want these checked on your own site?

    We look at a few key pages for free and send back the barriers that matter most, with how to fix them.

    Get a free AODA first look

    Continue the AODA Guide