AODA (Canada)

AODA conformance is bringing the site to the accessibility requirements of Ontario's AODA law: its Information and Communications Standard requires WCAG 2.0 Level AA conformance for web content (for organizations of a certain size). We conduct/use an audit (803), remove barriers (805-826), prepare documentation and, if needed, help with the reporting side. Honestly about the main thing, this is critical: WCAG conformance substantially REDUCES regulatory risk in Ontario, but is NOT a legal guarantee. The reasons honestly: (1) AODA is the law of a specific PROVINCE of Canada (Ontario), not the whole country; other provinces have their own rules — it is important not to confuse them; (2) applicability depends on the type and SIZE of the organization (there are thresholds, e.g. by number of employees), and there are obligations for periodic compliance reporting; (3) the final assessment of whether and to what extent you fall under AODA is given by a lawyer. Honestly about the standard version: AODA historically references WCAG 2.0 AA (not the newer 2.1/2.2) — we do at least what is required, and higher if desired. Honestly about overlays: widgets do not ensure conformance — real fixes are needed. Honestly about the process: accessibility must be maintained. Honestly about scope: it depends on the site size and state (an audit as a basis). Honestly about access: access to the site is needed. An important boundary: this is AODA (Ontario, Canada); ADA/508 (US) is 827, EAA (EU) is 828; legal assessment and reporting are a lawyer's. Picture this: instead of 'we work with Ontario but know nothing about AODA' — a technical WCAG 2.0 AA conformance base + documentation. The base price starts from 30,000 ₽ (depends on the site size; the audit/fixes may be priced separately).

• You work with an Ontario audience but know nothing about AODA.
• You confuse AODA (Ontario) with the requirements of other provinces/countries.
• You do not know whether you fall under AODA by organization size.
• There is neither WCAG 2.0 AA conformance nor documentation/reporting.

• Bringing to WCAG 2.0 AA (AODA requirement) — audit 803 as a basis
• Removing barriers (services 805-826) by priority
• Preparing documentation (accessibility statement 831)
• Accounting for AODA (Ontario) specifics at the technical level
• A clear statement of boundaries (a provincial law; size thresholds; reporting)
• A warning about overlays (they do not ensure conformance)
• A recommendation of a legal review of applicability and reporting
• Handover and review with you

• A technical WCAG 2.0 AA conformance base (AODA requirement)
• Accessibility documentation is prepared
• Regulatory risk in Ontario is substantially reduced
• Good-faith effort is documented (applicability/reporting — a lawyer)

• We assess the state (audit 803) and AODA coverage at the technical level; collect access
• We remove barriers, prepare documentation
• We honestly set the boundaries (a lawyer for applicability/reporting), review with you

• Is AODA for all of Canada?

  No, and it is important not to confuse this. AODA is the law of a specific PROVINCE, Ontario, not all of Canada; other provinces have their own accessibility rules. We build a technical base for the AODA requirement (WCAG 2.0 AA), but applicability to your specific situation and province is confirmed by a lawyer.

• Do you guarantee AODA conformance?

  We build a strong technical base (WCAG 2.0 AA) and documentation, which substantially reduces risk, but this is not a legal guarantee. Applicability depends on the type and size of the organization (there are thresholds), plus there are obligations for periodic compliance reporting. The final assessment and reporting are handled by a lawyer — we do the technical part.

• Why WCAG 2.0, not 2.1/2.2?

  Because AODA historically references WCAG 2.0 AA as the requirement. We do at least what AODA requires, and if desired can do higher (2.1/2.2) for better real accessibility and a buffer for the future. We will honestly advise what is reasonable in your case.