AODA Compliance in Ontario: The Employer Handbook for 2026 Reporting and Everyday Accessibility

Ontario AODA employer guide: 2026 reporting deadline, employee thresholds, training, websites, accommodation and a free source-linked action-plan tool.

The December 31, 2026 deadline: what it means

The short answer: covered Ontario businesses and non-profits with 20 or more Ontario employees must submit their accessibility compliance report by December 31, 2026. That is a reporting deadline, not permission to postpone accessible service, employee accommodation or other existing obligations. Smaller employers can still have accessibility duties. Larger employers have additional requirements. This handbook explains the distinctions and turns them into a practical preparation process.

Source review: October 23, 2026. This guide focuses on ordinary Ontario businesses and non-profits. Designated public-sector organizations, federally regulated organizations and specialist activities require the separate coverage checks explained below. It is general information, not legal advice, an independent accessibility audit or a compliance certificate. An action plan or PDF from Canada Policy Manual does not file the government report.

Start with the free AODA readiness and action-plan tool, or download the filled-in fictional worked example without an email address. Your tailored assessment remains free on screen; a professional email address is required only when requesting your own PDF. Read the guide first if you are unsure about the employee count, the reporting route or what evidence should support an answer.

Ontario's current reporting guidance says that businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years. Their 2026 deadline is December 31. The government reporting portal is open. Designated public-sector organizations follow a different two-year cycle: Ontario identifies December 31, 2025 as their reporting deadline and says an organization that missed it still needs to file. Do not move a public-sector organization into the business category simply because a 2026 campaign is more visible. Read Ontario's current reporting instructions.

Two questions must therefore be answered separately. First, which accessibility requirements apply to the organization and its activities? Second, must it file a routine accessibility compliance report for this reporting cycle? A business with 14 Ontario employees may not meet the ordinary reporting threshold, yet still need accessible recruitment, relevant training, accessible service and suitable responses to information requests. Conversely, a company with 75 employees cannot satisfy its obligations merely by submitting a form. Reporting communicates its position; implementation is the work supporting that position.

This table is a starting map, not an exhaustive applicability decision. Organization type, Ontario employment, regulatory coverage and particular activities matter. The province's business and non-profit guide groups requirements by size, while the Integrated Accessibility Standards Regulation contains the legal detail. If the headcount or category is uncertain, keep that question open. Guessing a smaller category can hide the very work the preparation process is meant to uncover.

A useful internal conversation is: “What would let our certifier answer confidently, and what do we still need to check?” That is more productive than asking whether the company can download a certificate. Training evidence, usable procedures and actual accessibility arrangements are different kinds of work. Treat them separately, assign responsibilities and identify urgent barriers rather than starting with a marketing claim that the business is fully compliant.

There is no need to make this process intimidating. Many improvements are operational: an accessible interview invitation, a reliable feedback route, a known contact for format requests or a proper training handover. Some matters need technical expertise or legal advice. The goal is to recognize which is which, take the work seriously and avoid declaring a task finished just because a document exists.

AODA and the Human Rights Code are connected, not interchangeable

AODA stands for the Accessibility for Ontarians with Disabilities Act, 2005. Ontario's Integrated Accessibility Standards Regulation, often shortened to IASR, sets requirements across general accessibility, information and communications, employment, transportation, public spaces and customer service. For an employer, this means accessibility is not solely a website project or a single HR policy. People encounter the organization through applications, interviews, employment, premises, services, documents, technology and communication. A barrier can arise in any of those interactions. The IASR is the governing regulation.

The Ontario Human Rights Code has a separate role. It protects against disability-related discrimination and requires accommodation to the point of undue hardship in the circumstances covered by the Code. Meeting a particular AODA requirement does not automatically answer every individual accommodation question. The regulation expressly says its requirements do not replace or limit obligations under the Code or other legislation. An employer should therefore avoid telling someone, “We meet the AODA checklist, so no further adjustment is available.”

Think of the two frameworks as complementary questions. AODA standards ask whether required organizational arrangements exist and operate: for example, whether selected applicants are told that accommodation is available. A Code accommodation issue asks what a particular person needs to participate without disability-related disadvantage, and what the organization must do in the actual circumstances. A standard notice can help start that conversation; it does not determine the answer to every request.

The Ontario Human Rights Commission explains that accommodation includes both the process used to consider needs and the accommodation itself. Staff should listen, seek information relevant to the need, explore appropriate options and keep matters confidential. The undue-hardship analysis is not a general business-preference test. Ontario's prescribed considerations are cost, outside sources of funding, if any, and health and safety requirements, if any. Inconvenience or another customer's preference is not, by itself, an additional undue-hardship factor. Read the OHRC's accommodation guidance and its explanation of undue hardship.

Recognize barriers without making assumptions about disability

Disability is not limited to something immediately visible. Physical, sensory, learning, developmental and mental-health disabilities can affect participation in different ways; some are non-evident or episodic. A person's needs can vary over time. The OHRC's disability policy explains why stereotypes and a narrow picture of disability create barriers.

For example, an audio-only instruction can be a barrier for a person who needs written communication, while a dense document can be difficult for someone who needs another format or support. An employee with an episodic condition may need a discussion even though they appeared well at an earlier meeting. These illustrations do not diagnose anyone or prescribe one accommodation for a whole disability category. Ask about the person's needs, consider the actual interaction and keep the discussion respectful.

Which organizations can use the ordinary business route?

The ordinary route is intended for an Ontario business or non-profit within the relevant provincial framework. Under the IASR's general application rule, the provision of goods, services or facilities to the public or other third parties and having at least one employee in Ontario are important starting points, subject to the regulation's particular provisions. An organization does not escape accessible customer service merely because it serves other organizations rather than walk-in consumers. A manufacturer meeting suppliers, a professional firm serving corporate clients and a membership organization may encounter the same practical access questions.

Do not determine jurisdiction solely from a mailing address. A federally regulated undertaking, a designated public-sector body or an organization with uncertain status needs its own coverage assessment. A company calling itself “private” does not settle every jurisdictional question, and a non-profit label does not establish that the public-sector rules apply. Check the legal organization and relevant framework before choosing the reporting category. The free tool deliberately does not generate a completed ordinary-employer report for public, federal or uncertain-coverage selections.

For example, imagine an Ontario office team that buys a generic accessibility package online. Its policy includes a website statement but does not explain how interview accommodation requests are handled. A candidate asks for a different assessment format and receives no reply because reception thinks the website vendor owns accessibility. The failure is organizational, not merely technical. Assigning a real recruitment contact and reviewing the candidate's request is useful work even if the website has already been tested. That example also shows why a single “compliance score” can obscure more than it reveals.

Count Ontario employees carefully before choosing a threshold

Ontario's industry guide describes the employee count as the organization's peak number of employees at any one time during the previous twelve months. This is not simply today's payroll count and it is not a full-time-equivalent calculation. Include relevant Ontario full-time, part-time, seasonal and employee contract positions. Do not count employees outside Ontario, volunteers or genuine independent contractors as Ontario employees for this calculation. An employee working under a contract is not the same thing as an outside independent contractor. Check Ontario's counting guidance.

Begin by identifying the organization you are counting. Use records that can show who was employed at the same time, and involve the person who understands the employment relationships. The useful output is a dated explanation of the count and method, not a list of employee medical information. If classification is unclear, mark the count unconfirmed and obtain appropriate advice. Labelling everyone an independent contractor in a spreadsheet does not establish that the legal relationship matches the label.

Example: part-time employees still affect the count

A fictional company has 12 full-time and 10 part-time Ontario employees at its simultaneous peak. Its count is 22, not a lower figure based on the hours worked by the part-time staff. On the ordinary business route, that meets the reporting threshold. The company should then organize evidence for the 2026 report, while separately checking whether the 50-employee requirements apply. It should not leap from “we have to report” to “every large-organization rule applies.”

Example: two location peaks are not necessarily one organizational peak

A fictional employer operates two Ontario locations. One is busiest in July; the other is busiest in December. Adding each location's separate maximum can overstate a simultaneous peak if those numbers were never employed together. On the other hand, considering only one location can understate the organization's Ontario workforce. Use the organization-wide count at a point in time rather than whichever number is convenient. If separate legal entities or unusual employment arrangements complicate the exercise, resolve that question rather than assuming a rule for the whole corporate group.

A practical headcount note can record the period examined, the date or period of the peak, the categories included, the categories excluded and who checked the method. That is an organizing recommendation, not a prescribed government form. It makes a later review easier when somebody asks why the business selected a particular band. Keep identifiable payroll evidence in an appropriate internal system; the public readiness tool needs the count and confirmation, not a staff upload.

Growth or decline deserves attention. A business that is below 20 today should not assume the relevant peak was also below 20. A company moving toward 50 should prepare for additional documentation and process work rather than wait for the next marketing reminder. Ontario also says organizations must notify it of specified changes, including employee count and status, through the reporting portal. Check the current instructions when circumstances change; do not invent a universal grace period for a growing organization.

Worker numbers do not reveal every obligation. A small employer can still need accessible service and recruitment arrangements. A large employer may have a conditional website or specialist issue that cannot be solved by headcount alone. The count is an important routing input, not an assessment of the quality of the workplace. Our employee-count guide explains how to use the bands without turning uncertainty into an exemption.

Prepare the official report without confusing it with an action-plan PDF

Ontario's current process uses its Accessibility Compliance Reporting Portal. The published instructions say to register or sign in, start a new submission, select the accessibility compliance report, complete it and submit it. Ontario identifies information needed before filing, including the organization's legal name, business number, employee count and the certifier's name and contact details. Its guidance describes a senior officer with legal authority to say the report is complete and accurate. Section 15(1) of the Act permits, for the ordinary organization route, a director, senior officer or other responsible person with authority to bind the organization. Do not assume an outside preparer has that authority. Use the current government instructions rather than an old downloaded filing tutorial.

The most important preparation step is not opening the portal. It is deciding who can explain the evidence supporting each answer. A senior officer should not have to choose between guessing and relying on a broad assurance from somebody who checked only one part of the organization. Ask the relevant functions to review their own responsibilities: HR for recruitment and training, operations for service arrangements, the website team for technical scope, and management for organizational commitments and certification.

An internal pack can help with the first four steps. It does not become the government report simply because it has a logo, sources or an impressive number of pages. Canada Policy Manual's PDF is an evidence organizer and action plan. It does not sign, certify or submit anything to Ontario. Do not upload it as a substitute for completing the portal's report. Likewise, selecting “ready” in our tool is not an answer automatically mapped to a government certification question.

What should the certifier receive?

A useful handoff is concise enough to review and specific enough to investigate. Identify the organization and count, the relevant areas checked, the people responsible, the evidence locations and the unresolved issues. Explain whether a policy has been implemented, whether training records are complete, whether a claimed website exception has been examined and whether specialist activities need separate review. Do not remove unresolved issues to make the pack look cleaner. An attractive summary that conceals uncertainty is less useful than a transparent one.

Consider a fictional 28-person business. Its reporting route is clear, but two starters have missed relevant training and the interview invitation lacks an accommodation notice. Its handoff should identify those gaps and who is addressing them. It should not say “all checks passed” merely because the remaining entries have evidence references. The organization must make accurate statements in the official report and deal appropriately with any requirements it has not met. Appropriate advice or government assistance may be needed for a difficult filing question.

After submission, Ontario says a confirmation email goes to the certifier and primary contact and includes a confirmation number. Keep that record with what was actually submitted. The AODA also requires the accessibility report to be publicly available. Public access to the report is different from exposing confidential employee accommodation files; those are not material to publish with it. Follow the current official instructions for updates to address, contacts, headcount or status. Our 2026 reporting guide provides an additional preparation walkthrough.

Build policies people can follow, and plans that describe real work

Covered organizations need accessibility policies addressing how they achieve or will achieve the applicable requirements. For ordinary businesses and non-profits with fewer than 50 employees, the general policy requirement does not impose the same written-document obligation as the large-organization rule. Writing policies down may nevertheless make implementation easier. At 50 or more Ontario employees, the general rules require documented policies, an organizational commitment to meeting accessibility needs in a timely manner, public availability and accessible formats on request. Check the customer-service documentation requirements as well. Ontario explains policies and plans by organization size.

Useful policy wording answers practical questions. How does a person request support? Who receives the request? How are staff expected to respond? What happens if the usual contact is away? How does the organization provide information in a suitable format? What is the route for a complaint? Policies should describe arrangements the organization can actually deliver, not an invented help desk, nonexistent telephone service or promise of an immediate response that has never been approved.

Write the operational handover alongside the commitment

A statement of commitment can explain the organization's approach, but it does not replace instructions for the people doing the work. Reception needs to know how to handle a service animal or disruption. A hiring manager needs to know what to do when an applicant requests accommodation. The website owner needs to understand the scope of the assessment being commissioned. A policy manual can bring those arrangements together; implementation still requires communication, training and appropriate follow-through.

For example, a fictional professional-services firm writes that accessible formats are available on request. Its operations manager then checks whether the published email address reaches a monitored inbox, whether the team knows how to consult on a suitable format and whether there is a backup contact. Those checks turn a sentence into a functioning process. The business should not describe the process as tested simply because the sentence appears in a document.

What is different about a multi-year accessibility plan?

A multi-year plan is a strategy for preventing and removing barriers and meeting applicable requirements. Ordinary businesses and non-profits with 50 or more employees must establish, implement, maintain and document it, post it on their website if they have one, provide it in an accessible format on request, and review and update it at least once every five years. Do not automatically import public-sector annual progress-report or consultation rules into an ordinary private employer's description. Requirements depend on the organization.

The best planning questions are concrete. Which barrier has been identified? What action will address it? Who owns the action? What resources or decisions are required? How will the result be checked? What is the internal target? A target date should not suggest that an existing legal duty can lawfully wait until that date. Where an immediate access issue exists, deal with the need rather than using a distant plan milestone to avoid the conversation.

Smaller employers should not be told to purchase a mandatory multi-year plan solely because the 2026 report is due. Equally, a larger employer should not be sold a generic plan with every action marked complete. The policy guide and multi-year-plan guide explain how to separate requirements, preparation aids and actual implementation evidence.

For the wider Ontario policy context, see our guide to mandatory workplace policies in Ontario. Accessibility is one part of that broader employment-policy picture; the other policy requirements should not be treated as having the same AODA thresholds.

Training: teach the relevant people, then record what actually happened

Accessibility training is not simply an annual certificate purchase. The general training requirement covers the applicable accessibility standards and the disability-related provisions of Ontario's Human Rights Code. Its audiences include employees and volunteers, people involved in developing policies, and people who provide goods, services or facilities on the organization's behalf. Training must be appropriate to their duties. Customer-service training has additional relevant content and audience requirements. Training must be provided as soon as practicable, with ongoing training when relevant policies change. Ontario's training guidance is the starting point.

Begin with a role map rather than a list of certificates. HR staff need to understand recruitment and employee support. People dealing with customers or third parties need accessible-service instruction. Policy developers need to understand the standards relevant to what they design. A board member or manager who shapes policy may need different detail from a person carrying out a narrow operational task. The organization should consider people acting on its behalf rather than assuming outsourced work is somebody else's problem.

Useful training combines the framework with your own procedures

A general learning module may explain respectful communication, disability-related barriers or the relationship between the Code and AODA. Staff also need to know your actual arrangements. Where should a request be sent? What are the feedback options? Who publishes a disruption notice? How are interview adjustments arranged? A worker can complete a module yet still be unable to answer those questions. Conversely, an informal briefing that omits the relevant legal content may not meet the training requirement. Consider both parts.

A practical session can use situations staff are likely to encounter. A client asks for a document in a different format. A visitor arrives with a service animal. A new recruiter receives an accommodation request. An employee cannot use the usual feedback survey. Ask what the person would do, whom they would involve and what information is actually needed. The purpose is to make the process usable, not to test whether staff can repeat an acronym.

Training records must reflect real participation

Businesses and non-profits with 50 or more Ontario employees must keep the required training records, including dates and the number of people trained. A useful internal log can also identify the audience, training content, relevant policy version and evidence location. Those additional organizing fields should not be presented as universal statutory wording for every employer. Smaller organizations can still choose to maintain records to manage coverage and demonstrate what occurred, while distinguishing that choice from the specific large-organization recordkeeping rule.

Do not create attendance evidence by filling a worksheet with scheduled names or dates. “Training planned” and “training completed” are different states. If 26 of 28 staff have completion evidence and two starters remain outstanding, the log should say that. Role-based rows can overlap; do not add a separate policy-developer row to the all-staff total and accidentally claim more people were trained. Record absences and follow-up rather than treating a meeting invitation as proof of participation.

For example, a fictional 28-person business discovers that its onboarding checklist never assigned a training owner. Completing training for two missed starters addresses the immediate gap, while adding a responsible role and follow-up trigger addresses the process failure. Both actions matter. Neither requires inventing a rule that every employee must buy a fresh annual certificate. Our training and evidence guide helps organize the work without creating fictitious training credentials.

Accessible customer service: make the everyday interactions work

Accessible customer service is about how people obtain, use and benefit from goods, services or facilities. It is not restricted to retail stores. Business-to-business operations must consider the applicable standard too. Policies should be consistent with dignity, independence, integration and equal opportunity, and communication should take the person's disability into account. The practical question is not whether everybody receives an identical process, but whether a person can access the service in an appropriate way. Ontario's customer-service guidance explains the main requirements.

Communication and assistive devices

Staff should be prepared to ask about a suitable way to communicate rather than make assumptions. Reading an order form aloud may help one person; a written exchange may help another. Speak to the person receiving the service, not automatically to a companion. Give staff a route for arranging additional support where it is needed. Respectful communication is an operational skill, and an inaccessible form should not become the only acceptable route merely because the business has always used it.

Policies must address people's use of their own assistive devices and other measures that enable access. Consider how a wheelchair, screen reader, hearing aid, mobility aid or another device interacts with the service. Do not impose a blanket ban because an unusual device is unfamiliar. Genuine safety issues need an appropriate, individual assessment and suitable alternatives. For example, clearing space at a counter may remove a barrier without requiring the customer to abandon the device on which they rely.

Service animals: avoid invented certificates and blanket exclusions

Service animals are not limited to guide dogs. Ontario explains that an animal can be readily identifiable as being used for disability-related reasons, or the person can provide documentation from a regulated health professional confirming that need. The current rules should not be replaced with a demand for a universal purchased certificate, a particular vest and medical documentation in every case. Standards-review recommendations are not the same as enacted requirements.

Where the premises provisions apply, permit the person to enter with the service animal and keep it with them unless another law excludes the animal. If an actual law excludes it from a particular area, provide another way to access the goods, services or facilities. A staff preference is not automatically a legal exclusion. A useful procedure explains escalation, how staff check the relevant restriction and how an alternative will be arranged. Avoid turning a narrowly restricted area into a ban across the entire organization.

Support persons and admission charges

Support people may assist with communication, mobility, personal care or other daily needs. Where the premises provisions apply, the person must be able to access their support person. A provider cannot automatically require every person with a disability to bring one. Under IASR section 80.47(5), it may do so only where the support person is necessary for health or safety and there is no other reasonable way to protect health or safety, after consulting the person and considering the available evidence. If your organization requires the support person's presence for those reasons, waive their admission fee.

If admission fees are charged to support persons in other circumstances, disclose them in advance as the applicable rules require. Do not apply the Ontario Public Service's own policy as though it were the universal private-business fee rule. Also do not describe a fee policy as the complete answer to an individual human-rights accommodation issue. Keep the regulatory requirements and case-specific accommodation responsibilities in view.

Temporary disruptions, feedback and documentation

When people with disabilities normally rely on a particular facility or service that is temporarily disrupted, notices need the reason, expected duration and available alternatives. Think about where notice will actually reach people: an entrance, a booking communication, a website or another appropriate route. A notice hidden inside an internal maintenance ticket is not useful to a visitor arriving for a meeting. Assign responsibility for publishing and updating it.

Accessible feedback also needs a functioning process. Explain how feedback is received and responded to, how complaints are handled and how accessible formats or communication supports can be arranged. Large businesses and non-profits must check the standard's written-document and availability requirements, including accessible provision of required documents. A fictional venue might have a useful telephone feedback option but an outdated disruption notice. Keep those findings separate rather than marking all customer service “ready” based on one good feature.

Accessible information, feedback and formats: build a request route

Ontario's basic accessible-information guidance is practical: tell the public and employees that written information and other communication can be made accessible on request. When someone asks, consult them about what is suitable, provide or arrange the appropriate format or communication support in a timely manner considering the disability-related need, and do not charge more than the regular cost. The organization does not need to keep every possible format ready in a cupboard. It does need a process that can respond. Read the accessible-information guidance.

A format is not accessible simply because it is digital. A scanned image of text may be difficult or impossible to use with a screen reader. A visually attractive document may have no meaningful heading structure. A video may carry important spoken information that somebody cannot hear. The appropriate response depends on the information and the person. Ask rather than assume that braille, large print, audio, a structured electronic document or a conversation will suit everyone with a particular disability.

Notice, contact, consultation and delivery

Four practical steps make the process easier to manage. First, provide a clear notice that accessible formats and supports are available. Second, make the contact route usable. Third, identify who consults with the requester and arranges a suitable response. Fourth, check whether the agreed information was delivered in a usable way. These are organizing steps, not a new legal form or a promise that every request can be fulfilled by the same method. They help translate the underlying duty into an everyday workflow.

For example, a fictional supplier publishes a complex ordering guide. A client asks for a simpler supported explanation rather than the PDF. The team should not reject the request because the PDF opens on its own computer. It can discuss what the person needs and arrange an appropriate response. The useful evidence is not just that the company owns conversion software; it is that staff know how a request is handled and can implement a suitable solution.

Feedback includes more than customer complaints

Existing feedback processes must be accessible through formats and supports on request, and the availability must be communicated as required. Review employee surveys and other existing feedback arrangements as well as customer-service complaints. A company can have an accessible public feedback email while still offering an employee survey with no usable alternative. Those are two distinct findings. Keeping them separate makes the action plan more precise and avoids giving a general “ready” label to an area that has only been partly reviewed.

Public emergency or public-safety information also deserves special attention. If the organization prepares such information and makes it public, it must provide an accessible format or appropriate communication support on request as soon as practicable. A visitor's access to evacuation information is not the same as an employee's individualized workplace emergency arrangements. Both may matter, but they are different checks with different facts behind them.

Do not turn an exception into a convenient assumption

The information and communications rules include scope provisions and exceptions, including situations involving information that is technically unconvertible. Where the organization determines information is unconvertible under IASR section 12(3), it must explain why and provide a summary of the information. Establish the relevant facts; this is not a universal answer to an inconvenient request. Likewise, saying that information came from another organization does not decide every accessible-service or human-rights issue. Check the specific provision and obtain advice where necessary rather than writing “not applicable” without a reason.

A simple evidence register can identify the public notice, the request owner, the process and a suitable evidence location. Do not collect diagnoses in the register. It should help the responsible team find records, not become a public store of sensitive conversations. The tool keeps an uncertain answer visible and lets the employer assign follow-up. That is more useful than an unsupported assurance that every format is available instantly.

AODA website accessibility: use the actual rule, then test properly

AODA is not just a website law, and its public-website requirement is not a new rule beginning on December 31, 2026. Ontario identifies January 1, 2021 as the existing Level AA compliance date for the applicable public websites of designated public-sector organizations and businesses or non-profits with 50 or more employees. Direct control and contractual control matter. A website operated by a supplier should not be labelled outside the organization's responsibility without examining the arrangement. Ontario explains who must comply and what must be tested.

For the applicable public websites and web content within scope, Ontario describes WCAG 2.0 Level AA, excluding success criteria 1.2.4, live captions, and 1.2.5, pre-recorded audio descriptions. WCAG means Web Content Accessibility Guidelines. Newer versions can be relevant to good practice, contracts or other obligations, but do not silently replace the actual Ontario rule with WCAG 2.2 when explaining the AODA minimum. Equally, the two specified exceptions are not permission to ignore other captioning or media requirements that do apply.

Scope comes before a scanner score

Identify the controlled public websites, applications and relevant content first. Ontario's guidance addresses content published after January 1, 2012 and explains different treatment for internal websites. A password alone should not be treated as a complete legal analysis of whether a particular customer-facing service is in scope. Look at what the service does, who uses it and the governing provisions. Other accessible-information and human-rights duties can remain relevant even where a particular website-conformance requirement does not apply.

For a fictional 28-person business, having a public website does not by itself trigger the business 50-plus website rule. It should still take accessible-information requests and human-rights responsibilities seriously. For a fictional 65-person business, the technical review needs to examine the controlled public website within the applicable scope. Neither company receives a meaningful answer by typing a URL into a tool that claims to certify the entire business in seconds.

What a useful website assessment should cover

An automated scan can find some problems, but not every accessibility barrier or every relevant success criterion. Arrange appropriate manual testing, keyboard use, assistive-technology checks and review of important user journeys. A technically present label may still be unclear. A form may appear readable but fail to explain an error to a screen-reader user. A navigation menu may work with a mouse but not a keyboard. These examples explain why a clean scanner summary is not the same as established conformance.

Ask the provider for a defined scope, the criteria used, the test approach, the issues found and what retesting will establish. Include documents and applications where relevant rather than testing only the home page. Record which work is completed and which barriers remain. If the business changes its booking form next month, the old assessment may not describe that new journey. Accessibility maintenance needs a practical handover to the people who publish content and release changes.

Handle exceptions with facts, not slogans

Ontario discusses situations involving content dates, control, conversion limitations, available software and practicability. None should be turned into a blanket assumption that an old platform or expensive project is automatically exempt. Check the actual provision, document the facts and best efforts where relevant, and consider ongoing alternative-format requests. The IASR's practicability analysis is not interchangeable with the Human Rights Code's undue-hardship test. Read Ontario's specific website exception guidance.

A useful handoff might say: “Our web provider has identified three barriers in the recruitment form. Operations owns remediation, and HR will check that applicants can request accommodation while the work is completed.” It should not say: “A widget has made us AODA certified.” The website guide and readiness tool help organize scope and evidence; neither performs a technical conformance audit or guarantees a result.

Accessible employment starts before the first interview

Part III's employment standards concern paid employment and do not apply to volunteers or other unpaid individuals under that Part's scope rule. That is different from the broader accessibility-training audience, which includes volunteers and other relevant people. Do not infer that a volunteer has no accessibility or human-rights protections simply because the particular employment-standard provisions do not apply. Check the actual relationship and applicable framework.

The employment standards in the IASR cover more than what happens after someone discloses a disability. The recruitment requirements include notifying employees and the public that accommodation is available for applicants during recruitment. When an applicant is individually selected for assessment or selection, the employer must notify them that accommodation is available on request for the materials or process. When requested, consult about a suitable arrangement that takes the applicant's disability-related accessibility needs into account. See IASR sections 22 and 23.

In practice, check the places where recruitment actually happens: advertisements, the careers page, application instructions, interview invitations and assessment communications. One statement buried in an employee handbook does not necessarily reach an external applicant. Make the request route clear enough that an applicant does not have to guess which office to call. Recruiters and managers should know whom to involve and avoid treating a request as a sign that the candidate cannot do the job.

Use notices that lead to a functioning process

Consider an applicant invited to a timed online assessment. The invitation should explain that accommodation is available for the selection process and provide a usable way to request it. If the applicant asks for a change, the employer should consult about the actual need rather than automatically sending the same standard test again. The appropriate accommodation depends on the circumstances; this guide does not prescribe a universal extra-time percentage or require the applicant to disclose a diagnosis in a public form.

A second example involves an interview room that is difficult to access. The hiring team can discuss a suitable accessible arrangement instead of asking the applicant to manage an avoidable barrier alone. A remote interview may be appropriate in some situations, but it is not automatically the right answer for everyone. Consult with the person and consider how the proposed process affects their ability to participate meaningfully.

Offers, onboarding and employee information

When making an employment offer, the employer must notify the successful applicant about its policies for accommodating employees with disabilities. After employment begins, employees must be informed of support policies, including job-accommodation policies, with new employees receiving the information as soon as practicable and updates provided when relevant policies change. An offer-stage notice and an onboarding conversation serve different purposes. Check both instead of assuming that a later handbook acknowledgment fixes every earlier omission.

For employees requesting accessible formats or communication supports, consult about information needed to do the job and information generally available in the workplace. That can include instructions, updates, staff communications and other relevant material. The employer should not assume that the format used for most staff is usable by everyone. Put a practical request and response route in place and keep individual discussions appropriately confidential.

Performance, development and redeployment

Where the employer uses performance management, offers career development or advancement, or redeploys employees, the relevant provisions require consideration of disability-related accessibility needs and individual accommodation plans. These are conditional requirements tied to processes the organization uses. They do not require every employer to create an elaborate performance-management system solely to satisfy a checklist. They do require attention when existing processes could create barriers.

A fictional manager reviewing performance should consider agreed accommodation arrangements rather than evaluate an employee as though those arrangements did not exist. A development opportunity should be communicated and delivered accessibly where needed. If redeployment is used instead of layoff because a role or department is eliminated, accessibility needs and accommodation plans must be considered in that process. Difficult employment decisions can involve other laws and should receive appropriate advice. The accessible-employment guide helps organize these checks without trying to decide an individual employee's legal situation.

Larger-employer accommodation plans and return-to-work processes

At 50 or more Ontario employees, ordinary businesses and non-profits must check the additional IASR requirements for a written process to develop documented individual accommodation plans and a documented return-to-work process for relevant disability-related absences. A smaller employer's exemption from these particular documentation requirements does not remove its separate Human Rights Code duty to accommodate. Keep the difference between the required organizational process and an actual person's accommodation needs clear. IASR sections 28 and 29 contain the detailed requirements.

The written individual-plan process needs more than a blank form

Section 28 identifies elements that the process must address. These include employee participation, individual assessment, how an employer can request an outside expert evaluation at its expense, representation, privacy, reviews and updates, how reasons for a denial are provided, and accessible delivery of the plan. The plan must also identify relevant accommodations and include the applicable communication-support or emergency information where required. A form with a name and signature line does not, on its own, explain that process.

Ask how an employee requests accommodation and participates in developing the plan. Explain how the need is assessed individually rather than through a fixed assumption about a disability. Provide the relevant representation route, including the bargaining-agent or workplace representative provisions. Decide how privacy is protected and how the plan will be reviewed. The process should make an employee's participation possible, not require them to understand an internal department structure before asking for support.

Do not design the process around collecting the largest possible medical file. Information requests should have a legitimate connection to assessing and arranging accommodation. The OHRC's accommodation guidance, including sections 8.7 on medical information and 8.8 on confidentiality, explains the importance of disability-related limitations, needs and the person's ability to perform essential duties with accommodation. It is unsafe to claim that a diagnosis is always required; it is also too absolute to claim that additional medical information can never be relevant. Sensitive or disputed cases need an appropriate, proportionate process and qualified advice.

Documented return to work is a process, not a promised outcome

The large-employer return-to-work requirement concerns employees absent because of disability who require disability-related accommodation to return. The documented process outlines the steps to facilitate return and uses documented individual accommodation plans. It does not replace rights or processes arising under another statute. For example, workers' compensation arrangements may need separate attention. An AODA worksheet should not be presented as resolving every return-to-work obligation or deciding when an employee is medically fit to return.

A useful process identifies who communicates with the employee, how relevant functional information is considered, how proposed arrangements are discussed, and how the plan is checked and adjusted. Keep the employee involved. Do not automatically promise a particular job modification before examining the role and circumstances, and do not reject an option merely because it differs from the usual schedule. The actual accommodation analysis is more detailed than selecting a box in a public tool.

A realistic planning example

A fictional 65-person service company has a general accommodation policy but no written process covering the section 28 elements. Its action is to develop and implement the missing process, train the relevant managers and arrange secure record handling. It cannot mark the requirement complete because it has downloaded a generic template. If an employee needs accommodation during that work, the company must address the actual request rather than postpone it until the document project finishes.

The organization can use a preparation pack to identify the missing process, assign an owner and record where the approved procedure will be stored. It should keep individual employee plans out of the public pack. A plan can contain sensitive information even when no diagnosis is written down. Appropriate access controls and careful sharing support both dignity and practical implementation. That is why our tool asks for an evidence location, not an upload of the employee's accommodation file.

Individualized emergency information and careful handling of records

Individualized workplace emergency response information is not limited to large organizations. Under the IASR, it is required where an employee's disability makes it necessary and the employer is aware of the need. Provide it as soon as practicable after becoming aware of that need. Where the employee needs assistance, the employer provides the information to the designated helper with the employee's consent. Review the arrangements when the employee changes location, when overall accommodation needs or plans are reviewed, and when general emergency response policies are reviewed. Ontario provides an emergency-information guide and examples.

The relevant question is how the employee can receive and use emergency information and assistance. Do they need a different alert, an accessible route explanation or agreed help? Do not assume that every disability is visible or permanent. Section 27 depends on employer awareness, and a need can become apparent without formal disclosure. Managers should respond appropriately to known signs and inquire about accommodation needs while respecting privacy; the OHRC explains the duty to inquire in section 8.6.1. Staff should also know how to raise concerns and whom to speak with. Ontario's examples encourage practical discussion rather than a one-size-fits-all emergency plan for every person with a disability.

Share what the helper needs, not the whole medical history

Imagine a fictional employee temporarily unable to use stairs safely. The employer and employee discuss suitable emergency arrangements and identify the people who need relevant information. The purpose of sharing is to implement that arrangement, not to circulate a diagnosis to everyone on the floor. Obtain the required consent for sharing with the designated helper and keep the information proportionate to the task. A public checklist is not the place for that person's identity, medical documents or detailed emergency plan.

A second example concerns a change of work location. The old instructions may describe a route that no longer makes sense. Reviewing the arrangements after the move is more useful than keeping a signed document untouched in a folder. Similarly, a general emergency-policy review should prompt consideration of existing individualized information. Build those triggers into the operational process so that the employer does not rely only on somebody remembering a previous conversation.

Separate an evidence register from confidential case files

A preparation register can say that a confidential process exists, identify the responsible role and point to a secure evidence location. It does not need to reproduce employee names, diagnoses, leave details or accommodation discussions. Staff reviewing the public report preparation should receive only information appropriate to their role. A website provider checking forms does not need access to employee medical records, and a public accessibility policy should not contain individual accommodation arrangements.

Privacy obligations depend on the organization, records, activity and applicable legal framework. Do not assume that one privacy statute automatically governs every Ontario private-sector employment record in the same way. Obtain appropriate advice for the actual situation. Regardless of that analysis, collecting unnecessary sensitive information in a public readiness tool is poor preparation practice. Use role names and secure references instead of copying records into notes.

Retention also deserves a deliberate decision. The AODA training-record requirement does not establish a universal retention period for every document mentioned in this guide. Other obligations, disputes or organizational needs may matter. Decide what must be retained, why, where, for how long and who may access it using the applicable requirements. Avoid inventing a seven-year rule for all accessibility material simply because the business uses seven years for an unrelated record category.

Public spaces, transportation, education and other specialist activities

A strong employer guide should explain where a core checklist stops. Transportation, educational and training resources, libraries and the design of public spaces can involve detailed requirements that do not reduce to an office HR questionnaire. The tool identifies these activities and flags a separate review. Completing a handoff question does not verify the specialist standard. This limitation matters most when a business is planning construction, delivering transport or operating an institution with accessibility duties beyond ordinary employment practices.

Public spaces and the Building Code are not the same project

Ontario's Design of Public Spaces standards address specified new construction and redevelopment. The requirements depend on the element, organization and other conditions. Some duties can apply to small organizations too, including relevant service counters, fixed queues, fixed-seating waiting areas or off-street parking. Larger organizations have additional matters to check. Do not turn the 50-employee threshold into a blanket exemption for every small-employer public-space project. Ontario's public-space guidance provides the starting categories.

There is not a blanket Design of Public Spaces obligation to retrofit every existing space simply because the 2026 report is due. That does not settle a Human Rights Code accommodation issue or a separate building requirement. The Building Code deals with many building accessibility matters, and a project can need both sets of checks. Ask a qualified project adviser to identify the applicable requirements, permits, exceptions and technical specifications. This handbook does not certify dimensions, design drawings or construction work.

For example, a fictional small business planning to change its customer-service counter should not assume that fewer than 50 employees makes every design rule irrelevant. A larger employer redeveloping a parking area should not rely on a generic web checklist to decide the number, layout or exemption status of accessible spaces. Review the actual project and current law. Ontario's 2026 regulation amendment includes public-space terminology and Building Code cross-reference changes; it is not a new general reporting or WCAG deadline.

Transportation needs a service-specific assessment

The IASR contains separate provisions for different transportation services and roles. Conventional and specialized transportation, school transportation, ferries, municipalities and taxicab-related responsibilities should not be collapsed into a single rule saying every employer must supply accessible transport. First identify what the organization actually provides and which provisions apply. Then examine the relevant service requirements and evidence with appropriate expertise. Ontario's transportation guidance explains several public-sector and municipal responsibilities; check the regulation for the specific service and role. A company arranging an ordinary staff meeting is not automatically in the same position as a regulated transportation provider.

Education, training resources and libraries

Specified educational and training institutions, producers of educational materials and libraries have additional rules concerning accessible resources, information and training. These provisions do not mean that every business conducting an internal staff briefing becomes an educational institution for all purposes. Public libraries and educational or training libraries also have different provisions and exceptions. Check the organization's role before selecting requirements. Ontario's accessible-information guidance includes educational resources and materials. The relevant IASR information-and-communications sections need their own review where these activities are involved.

Procurement and kiosks: avoid importing public-sector rules wholesale

Businesses and non-profits must have regard to accessibility when designing, buying or acquiring self-service kiosks. Ontario explains the distinction between that requirement and public-sector incorporation requirements. The general public-sector procurement provision should not be described as a blanket private-employer rule. It can still be good operational practice to consider accessibility when buying systems and services, but label the legal requirement and recommended practice accurately. Read the kiosk guidance and the relevant regulation before making a purchasing or design claim.

Evidence and enforcement: be accurate without creating unnecessary alarm

The best evidence explains what was checked, what occurred and what remains unresolved. It does not need to be a huge folder of duplicated paperwork. A dated training log, an implemented policy, a functioning request route, a plan review record or a scoped technical assessment can each support a different part of the preparation. Keep the distinctions. Evidence that a document was approved is not necessarily evidence that all relevant staff received training, and evidence that one form was tested does not establish website-wide conformance.

An evidence register can record a check, its responsible role, a secure location and follow-up. Avoid attaching material merely to increase the size of the report. A certifier should be able to find the supporting record and understand its scope. If the evidence is missing, old or incomplete, state that clearly. An honest “needs checking” entry is a useful control, not an embarrassment that must be hidden before the report is shown to management.

Keep requirement, evidence and action separate

That separation prevents a common error: using an action as evidence of completion. “We will train staff next week” can be a sensible next step, but it does not mean training has happened. “The supplier will review our website” identifies work, not conformance. Dates should have a clear meaning too. A source-review date describes the content review; an internal target describes planned work; a legal deadline comes from the applicable requirement. They are not interchangeable.

What enforcement means in practical terms

Ontario describes reporting, audits, inspections and enforcement as parts of its accessibility compliance approach. Failure to submit a required report can lead to enforcement action. The right response is to understand the requirements, answer accurately, retain appropriate records and address gaps—not to assume that a checklist gives immunity from inspection. The reporting guidance explains the government's compliance role.

Different penalty mechanisms should not be confused. Administrative penalties under the regulation are separate from maximum fines available on conviction under the Act. The often-quoted daily maximum figures are not automatic invoices sent to every organization that misses a filing. This guide does not estimate a particular employer's penalty exposure from a few questionnaire selections. If the organization receives an official request, inspection communication, order or legal notice, read it carefully, preserve relevant records and obtain appropriate advice about its actual obligations and response.

Do not fabricate a government approval badge, backdate a training log or replace a genuine review date with today's date to improve the appearance of readiness. Those shortcuts make records less reliable. A practical register should preserve what was known, who checked it and what changed. If new evidence corrects an earlier answer, update the working record honestly rather than pretend the earlier gap never existed.

Finally, consider how responsibilities survive staff changes. A procedure known only to one HR coordinator is vulnerable when that person is away. Use role-based ownership, backup arrangements and a suitable handover. These are practical management recommendations, not a claim that AODA prescribes a particular software package or reporting dashboard. The value lies in making access and evidence dependable, not in buying a label.

Three employer examples: 14, 28 and 65 Ontario employees

The following fictional examples show how the same framework leads to different preparation work. They are not assessments of real organizations, model government answers or promises that a particular document guarantees compliance. Each begins with confirmed ordinary Ontario business coverage and a checked employee count. A change to those facts could change the route. Notice that the examples separate ongoing duties, reporting and large-organization requirements rather than treating them as one package.

Example A: a 14-person business with no routine reporting obligation

A fictional supplier confirms a peak of 14 Ontario employees and serves other businesses. It does not need the routine business/non-profit accessibility report on that confirmed count. It still reviews relevant accessibility policies, training, service communication, recruitment notices, employee supports and information requests. Its manager discovers that interview invitations have no accommodation notice and that staff do not know who handles accessible-format requests. Those are useful findings even though the company is not preparing the ordinary 2026 report.

The business assigns HR to fix recruitment communications and operations to establish a reliable request route. It does not buy a mandatory multi-year plan on the mistaken assumption that every AODA employer needs one. It also does not announce that fewer than 20 employees means it has no accessibility responsibilities. If it later plans a new counter or redevelopment, it checks the relevant project-specific duties rather than assuming its size settles every public-space issue.

Example B: the 28-person worked assessment

Our public worked example uses a fictional business with 28 Ontario employees: 22 full-time and six part-time at the simultaneous peak. It has a public website, serves customers or third parties, and has no specialist activities selected. Its confirmed count identifies the ordinary December 31, 2026 reporting deadline, but does not impose the 50-plus website or multi-year-plan requirement merely because a public website exists.

The example answers all 27 applicable checks. Twenty are marked ready with explicitly illustrative evidence; seven need action. Those actions concern the certifier handoff, training coverage, training timing, disruption notices, employee feedback accessibility, the accessible-format notice and interview invitations. The training worksheet says 26 of 28 staff have evidence and two starters are outstanding. The certifier worksheet says the official report has not been submitted. It does not turn a future retention procedure into proof that a filing occurred.

You can download the full fictional example PDF without providing an email address. It shows the action plan, actual example answers, evidence references, responsible roles, planning targets and filled implementation worksheets. Every page identifies it as a fictional sample. Its evidence references are invented illustrations, not records to copy into your own organization's audit file. The sample demonstrates the structure of a useful preparation pack, not the substance of your employer's compliance.

Example C: a 65-person service company with additional requirements

A fictional 65-person company confirms the same ordinary Ontario business coverage. It must prepare the 2026 report and review additional large-organization matters. It checks written accessibility policies, its commitment statement and public access arrangements, the multi-year plan, training records, documented accommodation and return-to-work processes, and the scope of its controlled public website. It separately flags planned public-space redevelopment for a project-specific review.

The company finds an outdated plan and a website assessment that did not include its newer booking application. It assigns plan work to management and HR, and a scoped technical review to the website owner. It does not mark the website compliant based on a scanner run against the homepage. It does not treat an internal target as a new legal deadline. Where an employee or customer needs accommodation during the project, the organization addresses that actual need rather than wait for a future plan milestone.

Across all three examples, the discipline is the same: confirm the facts, identify what applies, distinguish evidence from planned work and keep unresolved issues visible. The difference is the route and scope, not the seriousness with which a smaller employer should treat accessibility.

A practical timetable before the 2026 reporting deadline

Use the timetable below as a management aid, not a legal extension or a promise that every organization can complete all work in a fixed number of days. Existing duties should already be implemented, and an immediate access need should be addressed promptly. An employer with complex technology, multiple locations or specialist activities may need a longer technical project and appropriate advice about current obligations. Start with the actual gaps rather than a countdown graphic alone.

First: establish the route and responsible people

Confirm the organization category, coverage and Ontario employee count. Identify the certifier for a required report and the people responsible for HR, service, information and technical work. Check the official reporting instructions and portal access. Record uncertainty rather than make a convenient assumption. A good first meeting ends with named roles and evidence requests, not a vague instruction for HR to “get us AODA certified.”

Next: collect evidence and identify gaps

Review policies, training, recruitment communications, feedback arrangements, accessible-information processes and emergency procedures. At 50 or more employees, include the additional documentation, planning, employment-process and applicable website work. Ask what each record actually proves. A training invitation, for example, does not prove attendance. A website contract does not prove conformance. A policy draft does not prove implementation.

Then: implement and verify the actions

Prioritize actual barriers and missing duties. Revise communication, complete relevant training, test request routes and arrange technical or specialist review where needed. Assign a responsible role and realistic internal target, while making clear that the target does not authorize delaying an existing obligation. Check the outcome. If a feedback email bounces or an invitation still lacks the revised notice, an action is not complete merely because somebody sent an instruction to change it.

Before filing: give the certifier a truthful handoff

Review the actual government questions and instructions. Explain the evidence, scope and unresolved matters to the authorized certifier. Do not automatically copy tool answers into government answers without reviewing the wording. Resolve or properly address issues using the applicable requirements and appropriate advice. Complete the official process, keep the confirmation and submitted information, and establish public availability of the report as required.

After filing: keep accessibility functioning

A reporting cycle does not pause onboarding, support requests, service changes or website releases. Maintain training arrangements, update relevant communications, review individualized emergency information when its triggers occur and keep plans and evidence meaningful. When organizational details change, follow Ontario's update instructions. The practical reward is a system that works between reporting dates, not only a folder assembled in December.

A compact weekly management check during preparation can ask: What changed? Which actions are complete? What evidence supports completion? Which issues need escalation? This meeting frequency is a suggested project practice, not an AODA requirement. Keep the focus on implementation and decisions rather than repeatedly changing status colours in a dashboard without improving access.

Use the free tool to produce an action pack, not a false certificate

The Canada Policy Manual AODA readiness tool is designed to reduce typing while preserving the important distinctions. Select the organization category, coverage, peak employee count, whether the count has been checked, relevant website and service information, and any specialist activities. Every input has an explanation and example. The result then focuses on applicable core checks rather than presenting the same undifferentiated list to every employer.

For each check, select the response that best describes the evidence: ready, action needed, unsure or a reasoned not-applicable position. Add a responsible role, target and evidence location where useful. Do not enter diagnoses, confidential employee files or sensitive case details. A secure reference is enough for an internal owner to locate the supporting record. Unanswered items remain unresolved, and a not-applicable selection is not accepted as a verified legal exemption.

How to work through one question

Take the selected-applicant accommodation check. Read the explanation, then locate the actual interview invitation and instructions used by recruiters. If the notice is missing, select action needed. Assign HR, record an appropriate target and identify the template that needs revision. After the revision, check that the new wording is actually used and that somebody can arrange a requested accommodation. That sequence creates more value than selecting “ready” because a general accessibility policy exists elsewhere.

All on-screen results are free without contact details. A professional email address is required only to request your tailored PDF, which is delivered by email. The tool explains the request limits and delivery arrangements beside the form. No automatic marketing subscription is created by requesting the report. Receiving a PDF does not prove that the underlying facts are correct, that a website was tested or that a government report was filed.

Understand the worked example before entering your own answers

The direct-download worked example is a filled fictional case. It shows what responsible roles, evidence references and open actions can look like without pretending that any real employer was assessed. The interactive example is different: it can load a fictional profile while leaving evidence answers unresolved, so you can practise the assessment. Do not assume the example's 20 ready answers apply to your business or import its invented records as your evidence.

The tool also offers seven supporting guides: 2026 reporting, employee count, accessibility policies, multi-year planning, training records, accessible employment and website accessibility. Use the relevant guide when a check raises a question; follow the official sources for the governing requirements.

For broader employment-record preparation, the HR inspection-readiness tool and free resource directory can help organize other work. They do not replace this AODA scope review or provide an inspection guarantee. If an Ontario policy manual is part of your implementation, make sure the actual workplace practices match its wording. You can also read how Canada Policy Manual describes its source and review process. A well-organized document is valuable when it supports a real process, not when it conceals gaps behind a claim of perfection.

Frequently asked questions

Is December 31, 2026 the AODA compliance report deadline?

Yes, for covered Ontario businesses and non-profits with 20 or more Ontario employees. Ontario's reporting page identifies that date and a three-year business/non-profit cycle. Designated public-sector organizations follow a different cycle, and Ontario says their overdue 2025 reports still need to be filed. The December 2026 deadline does not postpone the accessibility duties already in force.

Does a business with fewer than 20 employees have no AODA responsibilities?

No. The ordinary reporting exemption is not a general accessibility exemption. A smaller covered employer can still have relevant policies, training, customer-service, information, employment and conditional project duties. Confirm the Ontario count and scope first, then review the requirements that apply. Do not decide the whole question from the fact that no routine report is due.

Do part-time employees count toward the reporting threshold?

Yes. Ontario's counting guidance includes full-time, part-time and seasonal employees and employee contract positions in the relevant Ontario count. Use the simultaneous peak in the preceding twelve months, not a full-time-equivalent calculation. Genuine independent contractors and employees outside Ontario are treated differently. Resolve uncertain employment relationships instead of relying only on the label used in a contract.

Can a company count each Ontario office separately?

Do not assume a separate threshold for every location of the same organization. Identify the correct organization and its simultaneous Ontario employee count. Adding separate location peaks from different dates can also be wrong. Separate legal entities, unusual corporate arrangements or uncertain worker relationships may need advice; this guide does not create an automatic group-aggregation or entity-splitting rule.

Must every employer have a written multi-year accessibility plan?

No. The general multi-year-plan requirement applies to specified organizations, including ordinary businesses and non-profits with 50 or more Ontario employees. Smaller employers can choose to plan improvements, but that choice should not be sold as the same universal statutory requirement. Larger organizations must implement and maintain the required plan, publish it as applicable and review/update it at least every five years.

Is AODA training an annual paid recertification?

There is no blanket AODA rule requiring every worker to purchase a new annual certificate. Training must address the applicable standards, relevant human-rights provisions and duties, with appropriate customer-service content. It must be provided as soon as practicable and updated when relevant policies change. Use actual attendance and completion evidence rather than treating a certificate purchase or a scheduled meeting as proof that the requirements were met.

Does an accessibility policy replace employee accommodation?

No. A policy can explain the process, but the Human Rights Code's duty to accommodate applies to the person's actual circumstances. Staff need a meaningful way to request support, and employers must consider the request appropriately. An AODA checklist is not permission to refuse a suitable accommodation simply because the business has published a policy or met another standard.

Can an employer routinely demand an employee's diagnosis?

Do not build a process around a blanket diagnosis demand. Information requests should be relevant to understanding disability-related needs and arranging accommodation. The appropriate information can depend on the circumstances, and additional medical information may sometimes need careful consideration. Follow OHRC guidance and obtain advice for sensitive or disputed situations. Never upload medical files to the public readiness tool.

Does AODA require WCAG 2.2 for every Ontario website?

That is not an accurate description of the current ordinary Ontario public-website rule. Ontario's guidance identifies WCAG 2.0 Level AA within the applicable scope, excluding success criteria 1.2.4 and 1.2.5. Size, organization type, control and content scope matter. Newer standards may be useful or required by other commitments, but should not be confused with the specific AODA requirement.

Can an automated website checker certify our entire business?

No. A scan can identify some technical issues, but cannot establish every relevant website criterion or verify policies, training, service and employment practices. Use a scoped technical assessment with appropriate manual and assistive-technology testing. Keep organization-wide readiness separate from website conformance and keep both separate from the official government reporting process.

Are service animals required to have one universal certificate?

No. Ontario describes current identification through readily identifiable disability-related use or documentation from a regulated health professional confirming the need. Do not demand a generic purchased certificate in every case. Check actual legal exclusions for a particular area and arrange alternative access where required. Recommendations from a standards review should not be treated as enacted replacement rules.

Must support persons always receive free admission?

Do not apply one blanket statement to every private-provider situation. The rules address access to support persons, advance notice of fees and the limited circumstances in which a provider may require a support person. When the provider requires the person's presence for the specified health or safety reasons, the support person's admission fee must be waived. Individual accommodation duties also need appropriate consideration.

Do small employers have no public-space design obligations?

No. Applicable Design of Public Spaces requirements depend on the project and element as well as organization size. Some can apply to small organizations. New construction and redevelopment should receive a project-specific review, with the Building Code considered separately. This does not mean every existing space must be retrofitted under that standard merely because the 2026 report is due.

Does this tool submit the report or create a government certificate?

No. The tool produces a self-reported preparation and action pack. An authorized certifier must review the actual facts and use Ontario's official reporting process where required. The PDF is not the government's report, a submission confirmation, a legal opinion or proof of full accessibility. Its purpose is to make the preparation work clearer.

Can we see results without providing an email address?

Yes. The assessment and on-screen results are free without contact details. A professional email address is required only when requesting your own tailored PDF. The filled fictional worked-example PDF can be downloaded directly without email. The example's invented evidence must not be copied into your organization's records as though it described real training, testing or a filing.

What should we do if a check is marked not applicable?

Write a real reason and verify the scope against the official requirement. A not-applicable selection is not an independently established exemption. For example, having no self-service kiosk is different from claiming all customer-service duties are irrelevant. Keep uncertain coverage visible and seek appropriate help where the answer depends on a technical, legal or specialist fact.

Will a ready result prevent an inspection or penalty?

No. Self-reported readiness is not an inspection guarantee, government approval or immunity from enforcement. Ontario may audit or inspect organizations to verify requirements. Use the result to locate evidence and address work, answer official questions accurately and respond properly to government communications. Do not advertise a downloaded action plan as protection from every accessibility issue.

What is the most useful first step today?

Confirm the organization, coverage and peak Ontario headcount, then identify the responsible people and evidence behind the applicable checks. If the report is required, confirm the certifier and current government process. Start with known access barriers and missing duties, not a search for a universal certificate. The free tool and worked example can make that discussion more structured.

Official sources and your next step

Use this guide as an organized route into the requirements, not a substitute for them. Start with Ontario's business and non-profit rules, reporting instructions and Integrated Accessibility Standards Regulation. Use the OHRC accommodation guidance for the separate human-rights framework. Where the facts, legal category or specialist requirements are uncertain, obtain appropriate advice.

Next step: build your free AODA action plan. Review the questions, record actual evidence and keep missing work visible. If you want to see the finished structure before starting, download the fictional worked example. The objective is a workplace process that people can use and a reporting handoff the authorized certifier can understand—not a claim that accessibility has been solved forever.

Key Takeaways

• The ordinary Ontario business/non-profit accessibility report is due December 31, 2026 at 20 or more Ontario employees; ongoing duties already apply.
• Confirm the peak simultaneous Ontario employee count during the preceding twelve months; do not use full-time equivalents.
• The 20-employee reporting threshold differs from the 50-employee threshold for additional documentation, planning and applicable website requirements.
• AODA standards and the Human Rights Code work together; a checklist or policy does not replace individual accommodation.
• Evidence must describe actual practices, training and testing—not planned work or invented records.
• The free action-plan PDF is preparation, not the government filing, an independent audit or a compliance certificate.

Disclaimer: General information for ordinary Ontario businesses and non-profits, not legal advice, an independent audit or a compliance certificate. Requirements depend on coverage, activities and individual circumstances. Human Rights Code, Building Code and specialist obligations may require separate review. An authorized certifier must verify the facts and use Ontario’s official reporting process where required. No tool result or PDF guarantees compliance or submits the government report.