AODA Accessible Formats for Ontario Translation Agencies

What to take away

Who has jurisdiction over AODA

The Accessibility for Ontarians with Disabilities Act, 2005 is provincial legislation, and its offence section, which sets a fine of not more than $50,000 for each day or part of a day on which the offence occurs or continues to occur and, if the person is a corporation, a fine of not more than $100,000 for each day or part of a day, is public on the Ontario statute page. The Ontario government administers the Act.

Accessibility standards are set by regulation under that Act. The one that matters here is Ontario Regulation 191/11, Integrated Accessibility Standards, and its Information and Communications Standard is the part that reaches documents. Section 12 requires an obligated organization, upon request, to provide or arrange for accessible formats and communication supports for persons with disabilities in a timely manner that takes the person's accessibility needs into account. For websites and web content the same regulation points to the Web Content Accessibility Guidelines (WCAG) 2.0, at Level AA.

That means three layers of rules can touch a single translated file. Provincial law sets the obligation. A municipal client may add its own procurement terms on top, which are contractual, not statutory. A private sector client may impose a house style guide that goes further than the law requires. Only the first layer is AODA.

Federal bodies are a separate matter. The Accessible Canada Act governs federally regulated employers and government departments, described on the federal accessibility program page, and it does not replace Ontario's rules for provincially regulated clients.

What triggers the accessible format obligation

The trigger is a request, not a document type. If a person with a disability asks an organization for a document in an accessible format, the organization must provide it. Translation agencies meet this in two ways.

First, the client may specify accessible output in the project brief. Second, the client may come back weeks after delivery because an end user asked. The second path is the one that catches agencies out, because the original quote rarely covered it.

Under the Act, the organization cannot charge the requester extra for the accessible format. That constraint flows down to whatever the agency charges the client.

What to submit and how approval works

AODA has no application, no permit and no approval queue for a translation agency. There is no filing to the province before you take on accessible document work. Compliance is a standing duty, and the province checks it through compliance reports and, where warranted, inspections.

Organizations with 20 or more employees must file an accessibility compliance report on a set cycle. The report asks whether the organization has met its requirements, and a false answer is itself an offence.

What you actually assemble is internal evidence, not a submission. Keep the client's written format request, the delivered accessible file, and a record of the remediation. If an inspector asks, that file is your answer.

The practical submission is to the client. Send the accessible file with a short note naming the standard it was built to, and keep a copy.

Example: a hospital discharge instruction

A Toronto clinic sends 800 words of discharge instructions for translation into Simplified Chinese. The quote covers translation only. Six weeks later the clinic asks for a screen-reader-friendly version because a patient cannot read the printed sheet.

The agency rebuilds the file with proper heading tags, a logical reading order and alt text on the dosage table. That is remediation work, and the clinic cannot be charged for the accessible format itself. The agency absorbs the rebuild or renegotiates the original scope. Either way, the client's obligation is met and the patient gets a usable file.

Agencies that write accessible output into every quote avoid that argument. The contract terms that prevent disputes are worth reading before the next accessible format request lands.

What happens if you skip it

Non-compliance is an offence under the Act. Individuals can face fines, and corporations face larger ones, with the daily maximums set in the statute's offence section described above. Counted per day, they are not trivial for a small agency.

Beyond the penalty, there is the practical cost. A client that gets a complaint from an end user will look at the vendor chain. If the agency quoted accessible output and delivered an untagged PDF, the agency owns the problem. Rebuilding a 40-page tagged document after the fact takes longer than building it correctly the first time.

There is also a reputational layer that is hard to price. Ontario public sector buyers now ask accessibility questions in requests for proposals, and a weak answer can disqualify a bid before the price is opened. The federal language rules for Ottawa contractors show how those screening questions work in practice.

Building accessible output into the workflow

Treat accessible output as a deliverable, not a favour. Ask about format at intake, alongside language pair and deadline. Train whoever handles desktop publishing on tag structure and reading order, and add it to your employee training checklist rather than assuming a translator will pick it up.

Keep the scope language tight in the master services agreement. Say that accessible formats are included, and say what counts as accessible for your shop. That single sentence removes most of the argument later.

If you also serve Quebec clients, note that accessibility duties and language duties are separate obligations that can land on the same project. The Bill 96 requirements for localization agencies cover the language side.

Common questions