Skip to main content
Halo Aware

Accessibility Statement

Last updated: 13 July 2026

Not everyone browses the same way. Some people navigate by keyboard, some use a screen reader or magnifier, some need higher contrast or bigger text. Halo Aware should work for all of them. This page is an honest account of where we are: what we've tested, what we found, and how to reach us when something gets in your way.

What this statement covers

This statement covers the three parts of Halo Aware: this website (haloaware.com), the parent dashboard (app.haloaware.com), and the Halo Aware browser extension.

The standard we work to

We work to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.

As of 13 July 2026, the parent dashboard, this website and the browser extension are each fully conformant with WCAG 2.2 level AA against our own assessment: every issue our testing found has been fixed, and we keep no list of accepted exceptions. That's a strong claim, so the next section explains exactly what the assessment involved and where its limits are.

How we tested

All three surfaces were assessed between 11 and 13 July 2026. It was a self-assessment, not an external audit, and it ran in five passes on each surface:

  • Automated scans (axe-core) against the full WCAG 2.2 A and AA rule set, covering every page, view and overlay state, in dark and light appearances, at desktop and mobile sizes.
  • Scripted keyboard testing: tab order, visible focus indicators, no focus traps, skip links, and Escape closing every dialog.
  • Structural checks for the things automated rule engines can't see: real labels rather than placeholders, heading levels that never skip, one main landmark per page, and dialogs that actually behave as dialogs.
  • Hand measurement of the criteria no tool implements: non-text contrast for form controls (1.4.11), focus never fully hidden behind fixed bars (2.4.11), reflow at 320px (1.4.10) and text spacing overrides (1.4.12). Two real failures were found this way and fixed.
  • Screen-reader passes using Orca (the Linux screen reader): the dashboard with a human listener, and the website and extension popup by capturing Orca's spoken output as a transcript and reviewing every announcement. All three passed.

Every one of these checks now runs automatically on every code change, in all three codebases. A change that reintroduces a failure cannot ship without the build going red.

The limits of our claim

  • This is a self-assessment. We haven't commissioned an external audit yet.
  • Orca is the only screen reader we've tested with. We haven't yet run NVDA, VoiceOver or TalkBack, so we won't claim them.
  • Parts of our design use translucent layered surfaces that automated contrast checkers can't measure. We computed those contrasts by hand where tools gave up, but hand checks cover what we thought to check.

If any of these limits hide a problem, we want to know about it. That's what the next section is for.

Tell us what's in your way

If any part of Halo Aware is hard or impossible for you to use, email hello@haloaware.com and tell us what happened and what you were using at the time (browser, device, and any assistive technology). Accessibility reports are treated as bugs, not suggestions. We aim to reply within five working days, and it's usually much sooner.

About this statement

Halo Aware is built with standard HTML, CSS and JavaScript (React). Keyboard-only use is tested and supported on all three surfaces, and all three have passed screen-reader testing with Orca; claims about other screen readers will follow as that testing extends.

This statement was prepared on 11 July 2026 and last revised on 13 July 2026, when the website and extension assessments completed and the dashboard's remaining issues were fixed. We'll update it whenever the picture changes, and review it at least once a year.