Policies
Map.ca policy

Accessibility Policy

How Map.ca builds and maintains accessibility for seniors, Deaf, blind, low-vision, mobility-limited, neurodiverse, newcomer, and low-bandwidth users.

Constitution §2 principle 10 is unambiguous: Accessibility is infrastructure. That means it is not a feature, not a polish step, not something added after launch. A core flow that does not work with a keyboard, a screen reader, or a reduced-motion setting is not finished, regardless of how it looks on a designer’s monitor.

Minimum standard: WCAG 2.2 AA across all public surfaces. Practical requirements: keyboard navigation for every interactive element, screen reader compatibility verified with at least one screen reader per platform, captions and transcripts for video and audio, colour contrast that meets the WCAG 2.2 AA thresholds, plain-language copy that reads at a community-ambassador level, a reduced-motion option, non-map alternatives for any workflow whose primary surface is the map, and an accessible Civic Pin reporting flow that does not require sight, hearing, or fine motor control to use.

Ontario’s AODA framework is the regional floor for many organizations operating in Ontario. The Ontario government’s accessibility guidance explains requirements for accessible websites and accessible information and communications, and Map.ca aligns with those. Accessibility feedback comes through a dedicated channel and is treated as a product issue, not a customer-service ticket.

Accessibility reviews are part of the Policy Impact Review (Constitution §7). A feature does not ship if its accessibility review is incomplete.

Requirements

  • Ship every feature with full keyboard support.
  • Verify screen reader compatibility on at least one screen reader per platform before launch.
  • Provide captions and transcripts for video and audio content.
  • Offer a non-map alternative for any workflow whose primary surface is the map.
  • Run an accessibility review as part of the Policy Impact Review before shipping.

Prohibitions

  • Do not ship a core flow that fails WCAG 2.2 AA on a public surface.
  • Do not gate accessibility behind a paid tier.
  • Do not treat accessibility feedback as a customer-service ticket.
  • Do not use motion or autoplay without a respect for the user’s reduced-motion setting.

Related policies

DeafMap and Sign Language PolicyHow Map.ca supports the Deaf community: sign-language layers, captioning, and Deaf-community-led design.Multilingual Access PolicyMap.ca's commitment to French and English official-language access, plus the multilingual layer for newcomer communities.Low-Bandwidth and Device Access PolicyPerformance targets that keep Map.ca usable on older devices, slower connections, and rural and northern networks.Map.ca Policy ConstitutionThe non-negotiable values of the platform. Policy sits above growth, monetization, convenience, partnerships, and speed.