Current conformance statement

Otranspo targets WCAG 2.2 Level AA. This is not a claim of full conformance: current evidence is source-level automated and keyboard coverage, while an independent audit and physical assistive-technology acceptance are not on file.

Source evidence reviewed 2026-08-12. No independent verification date is published because that work is pending.

• Machine-readable assurance and remediation log

Evidence and retest status

• Source evidence present — The release corpus includes automated WCAG checks in English and French across desktop and mobile profiles. A retained production result is still required after deployment.
• Source evidence present — Keyboard-only trip planning, focus order, visible focus, and truthful unknown accessibility states are covered in the release source.
• Human review evidence pending — No current structured manual WCAG review covering every public responsive variation and complete core process is on file.
• Independent evidence pending — No current independent WCAG 2.2 AA audit report is on file.
• Independent evidence pending — No current independent retest is on file because the independent audit and resulting remediation cycle have not been completed.
• Independent evidence pending — Screen-reader, switch-control, voice-control, low-end device, and 400 percent zoom acceptance evidence from physical environments is pending.

Known limitations and remediation log

• Open — Independent audit and paid assistive-technology evaluation have not been completed. Next: Commission the audit, publish findings without participant data, remediate material barriers, and publish the independent retest.
• Mitigated in source — The drawn map is supplementary and is not itself a complete keyboard interface. Next: Retain and retest the structured text explorer, departure boards, alerts, and itinerary equivalents with every material map change.
• External data limitation — Operator feeds do not consistently publish complete elevator, sidewalk, boarding, or vehicle-accessibility state. Next: Continue to label missing states unknown, retain official assistance links, and never infer a complete accessible chain.

Using Otranspo

• Keyboard-operable controls with visible focus and logical order.
• Touch targets at least 44 by 44 CSS pixels where applicable.
• Browser zoom, text reflow, reduced motion, and high-contrast preferences remain supported.
• Departure, alert, itinerary, and vehicle information is available as text; the map is supplementary.
• Accessibility states are accessible, unavailable, unknown, or not applicable—never assumed.

Limits and official assistance

Realtime feeds may not include elevator, sidewalk, boarding, or vehicle-accessibility state. Otranspo labels that information unknown when it cannot be confirmed.

Otranspo cannot decide eligibility, book a trip, or dispatch Para Transpo or STO paratransit. Use the official service handoffs below. Eligible Para Transpo customers may have regional options subject to the operators’ current rules, approval, and availability; Otranspo does not imply that a booking exists.

• OC Transpo accessibility
• Para Transpo
• STO paratransit information
• Contact STO paratransit
• WCAG 2.2

Report a barrier

Use the authorized accessibility contact shown on the contact page. Include the page, task, browser or assistive technology, and the barrier; do not include sensitive journey details.