Integrated Accessibility Standards: General Requirements, Customer Service and Information

Ontario’s Integrated Accessibility Standards Regulation, O. Reg. 191/11 (the IASR), is made under the Accessibility for Ontarians with Disabilities Act, 2005 (AODA). It bundles several accessibility standards together. This page covers the non-employment standards: the general requirements that sit underneath every standard, the customer-service duties, the information-and-communications rules, and the reporting and administrative-penalty regime. The workplace-facing duties live in the IASR Employment Standard; transportation and the design of public spaces are covered separately; and the Act and its enforcement architecture are explained in the AODA framework page.

One idea governs everything below. What an organization owes is not uniform — it depends on which size and sector bucket it lands in, so the first task is always to figure that out. And the IASR is a floor, not a ceiling: meeting these standards does not replace, satisfy, or limit an organization’s substantive duty to accommodate disability under the Ontario Human Rights Code, which can require more.

Which organizations must comply, and what is a "small" versus "large" organization?

The regulation covers government bodies — the Government of Ontario, the Legislative Assembly, and designated public-sector organizations — and every other organization that provides goods, services, or facilities to the public or to other third parties and has at least one employee in Ontario. A “small” organization has 1 to 49 employees in Ontario; a “large” one has 50 or more.

These categories drive everything that follows: the same conduct can be mandatory for the public sector, mandatory for large organizations, softened for small ones, or not required at all, depending on the bucket. The common error is treating coverage as all-or-nothing — and, in particular, small employers assuming “small” means “exempt.” It does not; a small organization still owes accessibility policies and training. None of this replaces an organization’s duties under the Human Rights Code.

Source: Integrated Accessibility Standards (O. Reg. 191/11), s. 1.

The statute is the floor, not the ceiling. These size and sector categories define only the minimum each organization owes under the IASR. They do not displace the broader, substantive duty to accommodate disability under the Human Rights Code, which applies regardless of an organization’s size and can require more than the regulation’s baseline.

What accessibility policies, multi-year plans, and procurement rules apply?

Every covered organization must maintain written accessibility policies; those with 50 or more employees must also produce a documented multi-year plan; and the procurement rule applies only to government and the broader public sector. These are the “general requirements” that sit underneath all five accessibility standards, and what an organization owes again depends on its bucket.

• Accessibility policies (everyone). Every covered organization must develop, implement, and maintain policies governing how it meets its accessibility obligations. If the organization is not a small organization, those policies must also include a written statement committing to meet accessibility needs in a timely way, be set down in one or more documents, made public, and provided in an accessible format on request.
• Multi-year plan (50+ and the public sector). Government, the Legislative Assembly, designated public-sector bodies, and large organizations must establish, document, and maintain a multi-year plan outlining their strategy to prevent and remove barriers, post it on their website, offer it in an accessible format on request, and review it at least every five years. The public sector must additionally consult people with disabilities and publish an annual status report.
• Procurement (public sector only). Only government, the Legislative Assembly, and designated public-sector bodies must build accessibility into what they buy, unless that is not practicable — and they must explain on request when it is not.

Two traps recur here: small employers assuming “small” means exempt (it does not — they still owe policies), and private large employers assuming the procurement rule binds them (it does not; procurement is a public-sector duty). None of this replaces an organization’s duties under the Human Rights Code.

Source: Integrated Accessibility Standards (O. Reg. 191/11), ss. 1–5.

The statute is the floor, not the ceiling. A written policy and a multi-year plan are the minimum documented commitment the IASR requires; they do not measure whether the organization has in fact removed barriers or met an individual’s accommodation needs, which the Human Rights Code assesses on its own substantive terms.

Self-service kiosks and accessibility training: what is required, and of whom?

Public-sector bodies must incorporate accessibility features into self-service kiosks they design, procure, or acquire, while large and small organizations have a softer duty to have regard to accessibility. Separately, every obligated organization must train its people — not only staff — on both the accessibility standards and the Human Rights Code as it applies to disability. Both duties catch employers off guard because they apply broadly, regardless of sector.

Self-service kiosks. A “kiosk” here means an interactive electronic terminal intended for public use — for example a point-of-sale screen or a check-in terminal — that lets people access products or services. The standard differs by who the organization is:

• The Government of Ontario, the Legislative Assembly, and designated public-sector bodies must build in accessibility features when they design, procure, or acquire a kiosk.
• Large and small organizations carry a softer duty: they must have regard to accessibility for people with disabilities when designing, procuring, or acquiring one. That is a genuine consideration, not a box to ignore, but it is not the firm “must incorporate” standard the public sector carries.

Training. Every obligated organization must train its people on the accessibility standards in this regulation and on the Human Rights Code as it touches disability. “People” is broad: employees, volunteers, anyone helping develop the organization’s policies, and outside parties who deliver goods, services, or facilities on its behalf. The training has to suit each person’s actual duties, happen as soon as practicable, and be refreshed whenever the organization’s policies change. The larger bodies — the Ontario government, the Legislature, designated public-sector bodies, and large organizations — must keep records, including the dates and the number of people trained. Small organizations must train but are not required to keep that record.

The common error is forgetting that training reaches volunteers and contractors, not just staff.

Source: Integrated Accessibility Standards (O. Reg. 191/11), ss. 6–7.

The statute is the floor, not the ceiling. Training people on “the Human Rights Code as it applies to disability” is itself a minimum awareness requirement; it does not satisfy the Code’s own duty to accommodate, which is owed to each individual regardless of whether the organization has trained its staff.

What does accessible customer service require?

An organization that provides goods, services, or facilities to the public is treated as a “provider” and carries a set of customer-service duties: accessible-service policies, admitting service animals and support persons, posting notice of service disruptions, training, and an accessible feedback process.

Policies. Every provider must develop, implement, and maintain policies on serving people with disabilities. Those policies have to align with four core ideas: dignity and independence; integration (not a separate side door unless an alternative is genuinely necessary); equal opportunity to benefit; and communication that takes the person’s disability into account. The policies must also cover the use of assistive devices. A provider that is not a small organization must additionally put those policies into a written document and make it available on request.

Service animals and support persons. Where the public has access to the premises, a person with a disability may bring a guide dog or other service animal in, unless a different law excludes the animal — in which case the provider must offer another way to serve them. Support persons must be admitted alongside the person they are accompanying. A provider may require a support person only if, after consulting the individual and considering the available evidence, it determines one is genuinely needed to protect health or safety and there is no other reasonable way to manage that risk; if it imposes that requirement, it must waive the support person’s admission fee. Where a fee applies to a support person, the provider must give advance notice of the amount.

Disruptions, training, feedback. A provider must post public notice when there is a temporary disruption to facilities or services that people with disabilities rely on — including the reason, the expected duration, and any alternatives. It must train everyone who works for it or provides goods, services, or facilities on its behalf: employees, volunteers, people who help develop policies, and any other representative — not only customer-facing staff. Training happens as soon as practicable after starting and again whenever policies change. The provider must also set up a feedback process that is itself accessible to people with disabilities.

Two errors recur: thinking a service animal requires formal certification — visual indicators such as a vest or harness on the animal, or written confirmation from one of the listed regulated health professionals, qualifies — and forgetting that any document the provider must supply under these rules has to be offered in an accessible format on request.

Source: Integrated Accessibility Standards (O. Reg. 191/11), ss. 80.45–80.51.

The statute is the floor, not the ceiling. These customer-service duties set a baseline for how a provider serves the public; refusing service or failing to accommodate a person with a disability can also be discrimination under the Human Rights Code, which is enforced separately and can reach conduct the customer-service standard does not address.

Accessible formats, feedback, websites, and educational resources: what does information and communications require?

Obligated organizations must give people with disabilities accessible formats and communication supports on request, keep feedback channels accessible, meet WCAG 2.0 website standards, and — if they are educational institutions or libraries — make learning materials and collections accessible. Several of these duties came in on staggered compliance dates by size and sector.

Accessible formats and communication supports. When a person with a disability asks, the organization has to supply — or arrange to supply — an accessible format or communication support: in a timeframe that accounts for the person’s actual needs, and at no higher cost than it would charge anyone else. The organization must consult the person about which format works for them and tell the public these options exist. The compliance deadlines were staggered: the Government of Ontario and the Legislative Assembly by January 1, 2014; large designated public-sector organizations by January 1, 2015; small designated public-sector organizations and large organizations (private and broader public sector alike) by January 1, 2016; small organizations by January 1, 2017.

Feedback. If the organization already has a process for receiving and responding to feedback, that process must be made accessible — formats and communication supports available on request — and the public must be told about it.

Emergency and public safety information. If the organization prepares emergency procedures, plans, or public safety information and makes it publicly available, it must also make it available in an accessible way — the right format or communication support — as soon as reasonably possible after the request comes in.

Websites. Designated public-sector organizations and large organizations must bring their public websites and web content to WCAG 2.0 — beginning at Level A, with all content reaching Level AA by January 1, 2021. Live captions and pre-recorded audio descriptions are carved out of that deadline. The rule applies to web content published after January 1, 2012, except where compliance genuinely is not feasible.

Educational institutions and libraries. Schools, post-secondary institutions, and other educational or training bodies covered by the regulation must, when notified of need, provide educational materials and student records in accessible or conversion-ready formats. Textbook producers serving those institutions must have accessible versions ready on request — by January 1, 2015 for textbooks and January 1, 2020 for supplementary print materials. Institution libraries must supply accessible or conversion-ready versions of their collections on request — by January 1, 2015 for print and January 1, 2020 for digital and multimedia — with special collections, archival materials, rare books, and donations exempt. Public library boards must make accessible materials available where they exist and tell the public about that availability.

Limits. These obligations do not extend to products and product labels, to information that genuinely cannot be converted to an accessible format, or to information the organization does not directly or indirectly control. If a conversion truly is not possible, the organization must still tell the person why and give them a summary of what the material contained.

Three errors recur: assuming “on request” means no advance preparation is needed, treating the website deadlines as optional, and overlooking that educational institutions carry their own layer of obligations on top of the general rules.

Source: Integrated Accessibility Standards (O. Reg. 191/11), ss. 9–19.

The statute is the floor, not the ceiling. The accessible-format and communication-support duties are minimum standards triggered by a request; the Human Rights Code’s duty to accommodate can require an organization to anticipate and meet communication needs more broadly, and meeting the IASR’s format rules does not on its own answer a discrimination complaint.

Who files accessibility reports, and how are administrative penalties calculated?

Most organizations must file periodic accessibility reports, and a director can impose administrative penalties for contraventions, set by a grid that weighs how serious the breach is and how often the organization has offended before.

Who reports, and how often. Filing happens on a set cycle: the Government of Ontario and the Legislative Assembly report yearly, designated public-sector organizations every two years, and large organizations every three years. Small organizations get a break: an organization with fewer than 20 employees is exempt from filing entirely, and one with at least 20 but fewer than 50 employees reports only on the customer-service standard, and only every three years.

How penalties are calculated. A director rates each contravention by impact — minor for an administrative slip, moderate for a preparedness gap, major for a priority requirement (especially anything that risks the health or safety of people with disabilities) — and by the organization’s history over the current two reporting cycles. Those two factors meet on a grid. Individuals and unincorporated organizations face $200 to $2,000; corporations face $500 to $15,000. If both the impact and the history are major, the director can charge the penalty daily, up to $50,000 for individuals or $100,000 for corporations.

Where organizations get burned: counting starts fresh at zero at the beginning of each odd cycle, so a string of repeat breaches inside one window pushes an organization toward the top of the grid fast. An organization can ask for a review within 30 days, but only a different director hears it, and that director can lower a penalty, never raise it.

(These penalty bands and the daily maximums are set in the regulation; confirm the current figures at the official source before relying on them.)

Source: Integrated Accessibility Standards (O. Reg. 191/11), ss. 81–87.

The statute is the floor, not the ceiling. The administrative-penalty regime enforces the IASR’s own standards; it is distinct from a Human Rights Code complaint, which a person with a disability can bring separately and which can result in its own remedies regardless of whether the organization has been penalized — or has filed every report — under this regulation.

---

This page is general information about Ontario accessibility law, not legal advice. Obligations under the Integrated Accessibility Standards turn on an organization’s size category and sector, and they sit alongside — not instead of — the duty to accommodate under the Human Rights Code, so check your organization’s size category and obligations, and obtain advice, before relying on any of the above.