Skip to main content

Trust

Accessibility

Premium design and accessibility are not opposing goals. This page describes the standard we build to and how to tell us when we miss it.

This page describes how BC Signal intends to operate. It has not yet received professional legal review and is not a guarantee of compliance with PIPEDA, CASL, or any other statute. Last updated 2026-09-10.

What we aim for

We design the public site to be usable with a keyboard, a screen reader, and reduced motion. That includes visible focus, labelled form fields, semantic headings, and alternatives to information that is only conveyed by colour or animation.

We use WCAG 2.2 Level AA as a working target. That is an engineering standard, not a certification. We have not commissioned a formal audit yet.

What is already in the product

  • Skip-to-content link and landmark regions
  • Real labels on every form control, even when the visual design hides them
  • Error text associated with the field that failed
  • Focus styles that are never removed
  • Motion that stops under the operating-system reduced-motion setting
  • FAQ answers rendered in HTML, not only after JavaScript runs

Known limits

Some visual treatments (mountain photography, glass panels, dense dashboards) need extra care on small screens and in high-contrast modes. If a page is hard to use, that is a defect. Tell us.

Report a barrier

Email hello@bcsignal.com with the page URL, the browser and assistive technology you use, and what you were trying to do. We will acknowledge the report and fix what we can.