Skip to main content

Usage analytics is on by default to improve Otranspo. You can turn it off here.

FR

Election Day. Polls are open until 8 pm.

Public rider information

Accessibility

Plan with accessibility choices, check what is known, and find official help or report a barrier.

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. They are never assumed.

Scope of this review

Reviewed 2026-09-14. This source review covers the following areas; it is not an independent conformance audit.

  • English and French public rider pages on phone and desktop layouts.
  • Keyboard completion of departures, planning, status, map alternatives, evidence, reporting, privacy and settings tasks.
  • Light and dark themes, reduced motion, 200 percent text resize, 320 CSS pixel reflow and WCAG text-spacing overrides.
  • Automated WCAG 2 A and AA scans on representative pages and interactive states.

Known barriers and unverified environments

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.

  • No independent WCAG audit or independent retest is on file.
  • No retained physical screen-reader, switch-control, voice-control, low-end-device or 400 percent zoom acceptance session is on file.
  • Operator data can leave elevator, sidewalk, boarding-path or vehicle-accessibility state unknown.

Accessibility support

Report an Otranspo accessibility barrier through the private accessibility choice on the contact page. Include the page, task, browser or assistive technology and the barrier; do not include sensitive journey details. Emergencies and operator service complaints must go to the appropriate official service.

O-Train and Para Transpo coverage

Otranspo includes O-Train lines, stations, scheduled trips, accessible routing, and official service notices. OC Transpo does not publish train positions or train arrival predictions in the realtime feed available to Otranspo, so rail remains clearly labelled timetable-only instead of showing invented train movement.

For Para Transpo and STO paratransit, Otranspo can keep official eligibility, booking, contact, accessibility, and service-information handoffs easy to find. It cannot safely track or score an individual adapted-service trip without an authorized public feed, and it will not collect or expose private rider journeys to fill that gap.

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.

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.

Technical record

Methods, assurance checks, and release evidence for people who need to inspect them.

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-09-14. No independent verification date is published because that work is pending.

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.

Contact without voice

You do not have to make a voice call. Each way below works by text, email, a web form, relay or sign language.

The other contact options were checked on their linked pages on October 3, 2026.