Is your website accessible? An AODA checklist for Ontario businesses
If your business is in Ontario, there is a good chance your website has to follow accessibility rules, or will once you grow. Many owners in Milton and across the GTA have heard of the AODA but are not sure what it means for a website, especially a small one. This guide explains who the website rule applies to, what everyone else still has to do, and a set of quick checks you can run on your own site this afternoon. It is based on the Government of Ontario’s own guidance and the W3C’s web accessibility resources.
A quick note before we start: this is practical guidance, not legal advice. Ontario’s pages say the same about their own guidance. If you are unsure which rules apply to your organization, check with the province or a lawyer.
1. Who has to make their website accessible
Ontario says that, as of January 1, 2021, the Accessibility for Ontarians with Disabilities Act (AODA) requires public websites to be accessible if you are a designated public sector organization, or a business or non-profit with 50 or more employees. (ontario.ca: How to make websites accessible)
A few details in that guidance matter for business owners:
- Whoever controls the site is responsible. The organization that controls the website, directly or through a contract, has to meet the requirements. Hiring a web designer does not hand the obligation to them. (ontario.ca)
- The standard is WCAG 2.0 Level AA. Public websites and web content posted after January 1, 2012 must meet the WCAG 2.0 Level AA success criteria, except live captions (1.2.4) and pre-recorded audio descriptions (1.2.5). (ontario.ca)
- Internal sites are treated differently. A business does not have to make its intranet or extranet meet WCAG 2.0 A/AA, but if someone asks for content in an accessible format, you must work with them to meet their needs. (ontario.ca)
When counting employees, Ontario says to include full-time, part-time, seasonal and contract workers in Ontario, and not to count volunteers, independent contractors or staff outside Ontario. (ontario.ca: Accessibility rules for businesses and non-profits)
2. What smaller businesses still have to do
If you have fewer than 50 employees, the WCAG website requirement does not apply to you. Some rules that touch your website still do. Ontario’s guidance for businesses with fewer than 20 employees says you must let the public know you will make written information and other communication accessible on request, and that a note on your website is one way to do it. (ontario.ca)
The same page says that if someone with a disability asks for accessible information, you need to work with them and provide it in a timely way, and you cannot charge more for an accessible format. That covers public information such as menus, order forms and information you provide on websites. You also need accessible ways for people to give feedback about how you serve people with disabilities. (ontario.ca)
In practice, for a small clinic, law office or shop, that usually means three things on the website: a short accessibility statement, a clear way to ask for information in another format (a phone number and an email address, not just a form), and a contact or feedback option that works with a keyboard and a screen reader.
3. A deadline to know about: December 31, 2026
Ontario says businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years, and that the deadline for the current report is December 31, 2026. (ontario.ca) Reports are filed through the province’s Accessibility Compliance Reporting portal.
The report covers more than your website. Ontario’s guidance also lists policies, staff training, accessible customer service and employment practices. If you have 20 or more staff and have not looked at this yet, this is the month to do it. Ontario also offers a free self-assessment Accessibility Standards Checklist on the same page. (ontario.ca)
4. Quick checks you can run yourself
The W3C, the group that publishes the WCAG standard, has an “Easy Checks” resource for a first look at any page. It is clear that these checks are quick rather than complete, and that a page can pass them and still have serious barriers. (W3C: Easy Checks) They are still a useful way to spot obvious problems. Based on its list, try these on your home page and your contact or booking page:
- Image text. Images that carry meaning, such as a logo, a photo of your team or a graphic with words in it, need a short text description (alt text) for people who cannot see them.
- Page titles. Look at the browser tab. Each page should have its own clear title, like “Contact | Your Business Name,” not the same title everywhere. Screen readers read the title first.
- Headings. Headings should outline the page like a table of contents. Screen reader users often move around a page by its headings, so big bold text that is not a real heading does not help them.
- Colour contrast. Light grey text on white, or white text on a pale photo, is hard for many people to read. Pay special attention to buttons and links.
- Keyboard only. Put your mouse aside and press Tab to move through the page. You should always be able to see where you are, and reach and use the menu, the phone link and the form.
- Skip link. The first thing you reach with Tab should ideally be a link to skip straight to the main content, so keyboard users do not have to tab through the whole menu on every page.
- Page language. The page code should say which language it is in, so screen readers pronounce it correctly. Your web developer can check this in a minute.
The W3C Easy Checks page explains how to do each of these in a regular browser, and points to more thorough evaluation resources when you are ready. (W3C: Easy Checks)
5. Do not forget videos, PDFs and forms
Accessibility problems often hide outside the main pages. WCAG 2.0 Level A includes captions for pre-recorded audio in synchronized media, so a video on your site with people talking needs captions. (ontario.ca, WCAG 2.0 criteria list) Our vertical video checklist covers captioning short videos.
Scanned PDFs, such as intake forms or price sheets saved as images, cannot be read by a screen reader. Where you can, put the information on a normal web page or use a text-based PDF. Online forms should have a visible label on every field, and error messages that say what went wrong in words, not just a red outline.
6. Questions to ask your web designer
Ontario’s guidance suggests asking a developer whether they are familiar with WCAG 2.0 Level A and AA, whether they have built accessible sites before, and whether they test with automated tools, manual checks and assistive technology such as screen readers. It also suggests asking for a plan that covers how the site will be tested and maintained, including training your staff to add accessible content. (ontario.ca)
The province also recommends keeping a record of the accessibility issues that have been fixed. That record helps if you are ever asked to show your site meets WCAG 2.0 Level AA. (ontario.ca)
A short checklist
- Count your Ontario employees the way the province does, and note whether you are under 20, 20 to 49, or 50 and up.
- If you have 20 or more, plan to file your compliance report before December 31, 2026.
- If you have 50 or more, make sure your public site and anything posted after 2012 meets WCAG 2.0 Level AA.
- Whatever your size, add an accessibility note to your site and a clear way to ask for information in another format.
- Run the quick checks above on your home, services and contact pages.
- Caption your videos, and replace scanned PDFs with real text.
- Ask your web designer how they test for accessibility, and keep a record of fixes.
Hook Labs designs fast, clean websites for local businesses and professional practices, and we build with accessibility in mind from the start. If you would like us to look over your current site, you can book a call.