AODA-compliant realtor websites

The BrokerFold Team — Product + Engineering

Last reviewed July 27, 2026

Reviewed against primary sources (Integrated Accessibility Standards Regulation, O. Reg. 191/11 s. 14 (AODA), accessed 2026-07-27 / Ontario.ca AODA web accessibility and compliance-reporting guidance, accessed 2026-07-27 / W3C Web Content Accessibility Guidelines (WCAG) 2.0) — last reviewed July 27, 2026. This page is general information, not legal advice.

AODA — Ontario’s Accessibility for Ontarians with Disabilities Act — requires, through O. Reg. 191/11 section 14, that designated public-sector organizations and private or non-profit organizations with 50 or more Ontario employees make their public websites and web content conform to WCAG 2.0 Level AA (excluding live captioning and pre-recorded audio description), a requirement fully in force since January 1, 2021 and covering content published since 2012. Most solo realtors sit below that threshold; many brokerages do not — and every realtor serves clients for whom accessibility is the difference between using your site and leaving it. This page states who is captured, what the standard demands, and how to audit for it, from primary sources with the review date above.

Who the law actually captures

Draw the thresholds precisely, because most of what ranks for this topic blurs them. 50+ Ontario employees: the WCAG 2.0 AA website requirement applies. 20+ employees: the organization must file the recurring accessibility compliance report with the province (the last business deadline in the cycle was December 31, 2023; the next is December 31, 2026), even where the website rule itself does not bite. Under 20: no filing, and no s. 14 website obligation — but the Human Rights Code’s duty to accommodate applies to organizations of every size, and a website that cannot be used with a screen reader is a service barrier under that lens. For a realtor the practical question is whose website it legally is: a personal site run by an agent is usually below thresholds a large brokerage crosses, and brokerage-operated agent sites inherit the brokerage’s obligations. If that sentence describes your setup, ask your broker of record what the brokerage has filed — the wider Ontario rulebook for realtor sites lives in realtor websites Ontario.

What WCAG 2.0 AA asks of a real estate site

Translated out of standardese and into the surfaces a realtor site actually has. Listing photos need alt text that says something — “3-bedroom detached, renovated kitchen” — not file names; at MLS volume this must be generated sensibly, not hand-typed. Search must work by keyboard: filters, map alternatives, and result lists reachable without a mouse, which in practice means a proper list view alongside any map. Forms — your lead capture — need labelled fields and error messages that announce themselves, because an inaccessible contact form is a lead leak as much as a legal issue. Contrast and text sizing rule out the pale-grey-on-white aesthetic entirely. Headings and structure must be real HTML hierarchy, not styled paragraphs. None of this constrains good design; it constrains careless design.

How to audit any realtor site, today

A usable audit costs an hour. Run an automated checker (open-source tools cover WCAG basics) across your homepage, a listings search page, one listing detail page, and every lead form — those four page types cover a realtor site’s surface. Then do the two manual tests automation cannot: unplug your mouse and complete a search and an inquiry by keyboard alone, and turn on your phone’s screen reader and listen to your own homepage. Log what fails, fix the template-level issues once (they repeat on every page), and re-test. If a vendor runs your site, this audit is a fair demand to hand them — and a revealing one, per the tests in choosing a web design company.

Where this fits in a build decision

Accessibility is a property of the platform and template underneath you far more than of your content. Ask any prospective vendor — ourselves included — how their templates handle alt text at listing scale, keyboard navigation of search, and form labelling, and expect specifics rather than a “fully compliant” badge; WCAG conformance is a per-page, per-content fact, and anyone selling it as a sticker has told you how seriously they take it. The honest posture for an Ontario realtor in 2026: build accessible because a meaningful share of your buyers and sellers need it, treat the 50-employee line as the legal floor rather than the target, and keep your site inside the design practices that make compliance a by-product of quality.

Frequently asked questions

Does AODA apply to a solo realtor's website?

The WCAG requirement in O. Reg. 191/11 applies to organizations with 50 or more Ontario employees, so a solo practice or small team is usually below the legal threshold. Two caveats: employee counts are assessed at the organization level, which can capture a brokerage, and Ontario's Human Rights Code duty to serve people with disabilities applies at every size. Below the threshold, accessibility is strongly advisable rather than regulated.

What does WCAG 2.0 Level AA require in plain terms?

That a person using assistive technology can do what every other visitor can do: images carry meaningful alt text, text keeps sufficient colour contrast, everything works by keyboard, forms have labelled fields and clear errors, pages are structured with real headings, and video carries captions. It is a usability bar, not a design aesthetic — well-built sites clear most of it by being well built.

What are the penalties for AODA non-compliance?

The Act provides for administrative penalties up to $100,000 per day for corporations and $50,000 per day for individuals and unincorporated organizations at the maximum, with directors' orders and compliance orders as the usual first steps. Enforcement in practice has centred on the reporting obligation — but the exposure is written into the statute, not theoretical.