heatpass

Accessibility

Updated October 17, 2026.

The standard we aim for

We want Heatpass to work for everyone, including people who use a screen reader, a keyboard instead of a mouse, zoom, or reduced-motion settings. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, on the public pages and in the signed-in app.

What we do

  • Check every main screen with automated accessibility tools before each release, at phone and desktop sizes, in light and dark themes.
  • Make every link, button and form field reachable by keyboard, with a visible focus outline. Dialogs keep focus inside and close with Escape.
  • Say every lead's status in words, not only in color, and give every chart and number tile its figures as text.
  • Label every form field, and say what went wrong in words.
  • Keep text contrast at 4.5:1 or more (3:1 for large text) in both themes.
  • Turn animations down when your device asks for reduced motion.

No overlays

We don't use accessibility overlay widgets. We fix the pages themselves.

Known limits

  • The maps are visual. The same places, with the same filters, are in the Leads list (“Same places as a list” on the Map tab), which works with a keyboard and a screen reader.
  • The card carousels can be turned with the arrow keys; each card's details are also in the list and in the lead's full details.
  • Device drawings are illustrations; the system names are always given as text.

Tell us about a barrier

If something in Heatpass is hard or impossible for you to use, email support@heatpass.app with the page and what happened. We reply within 5 business days and will help you get the information another way while we fix it.