Accessibility statement

v1.0 · Updated 12 August 2026

Short version: Halo HSE follows your iOS accessibility settings automatically, and lets you switch the same features on for Halo alone under Settings → Accessibility. Colour is never the only way a result is communicated, and every text and control colour is measured against WCAG 2.1 AA. Full text sizing is still in progress — see section 07.

01Our commitment

Halo HSE is a tool for Health, Safety and Environment professionals. A misread exposure result is a compliance error, not a cosmetic one — so accessibility here is a correctness requirement before it is a courtesy.

We build against Apple's Human Interface Guidelines for accessibility and WCAG 2.1 Level AA. This page states plainly what is supported today, where to find it, and what is not finished yet.

02Where to find these settings

Open the app and go to Settings → Accessibility. Each row shows one of three states, so you always know why a feature is active:

Via iOS — on because your device-wide iOS setting is on.
Always on — on because you switched it on for Halo specifically.
Off — off in both places.

The in-app switches can only ever add support on top of what iOS asked for. There is deliberately no way to turn a system accessibility setting off from inside Halo.

03Differentiate without colour

Every severity tier in the app carries a distinct shape as well as a colour: a circled tick for the safe band, a circled exclamation for the first action value, a filled triangle for the upper band, and a filled octagon for an exceeded limit. That escalating vocabulary is deliberate — it mirrors the road-sign convention the underlying regulations use, and the four silhouettes stay separable in greyscale and under any colour-vision deficiency.

Some cues are always on, because colour was never sufficient on its own: every result card states its verdict in words next to the glyph ("ELV exceeded", "Below EAV"), and a threshold you have not reached is drawn as a hollow ring rather than a dimmed dot.

Switching Differentiate without colour on adds the tier glyph to every remaining colour-coded surface: each cell of the risk matrix, the status dots and pills in the Saved list, the marker on a calculator's summary card, and the colour legend in a record's change history.

04Reduce motion

With Reduce motion on, the rotating ring behind each screen header stops completely rather than slowing down, the risk-matrix selection loses its spring and scale, the confirmation toast cross-fades instead of sliding, and button presses acknowledge with a dim instead of a scale.

Press feedback is reduced rather than removed. Taking the acknowledgement away entirely would be a usability regression dressed up as an accessibility win.

05Dark interface

A full dark theme is available under Settings → Appearance, with System, Light and Dark options. System follows your device.

The dark theme is a dark forest green, not pure black — chosen so the app stays legible in low light without the halation that pure black plus white text produces on OLED screens.

06Colour contrast

Every foreground and background pairing in the app has been measured against WCAG 2.1 AA: 4.5:1 for body text, 3:1 for large text, and 3:1 for icons and other non-text elements that carry meaning. That includes colours composited over one another — a dimmed label on a tinted row is measured as it actually renders, not as its nominal value.

Where a brand colour could not meet the ratio in a given role, it was replaced rather than waived. Severity dots on a saturated result card, for example, now carry their contrast on a ring in the card's own text colour, so the dot's boundary is defined even where the fill hue cannot be.

07Known limitations

Dynamic Type. Halo HSE does not yet scale fully with the iOS text-size setting. The typography is built on fixed sizes, and converting it is a substantial piece of work we would rather do properly than partially. It is the next accessibility item on our list.

VoiceOver. Controls carry labels and hints, and decorative elements are hidden from the accessibility tree, but the app has not yet been through a full end-to-end VoiceOver audit. If you rely on VoiceOver and something is unclear or unreachable, please tell us — that feedback goes to the top of the queue.

We would rather list these here than let you discover them on site.

08Feedback

If something in Halo HSE is hard to use, email hello@halosafety.io and tell us what you were trying to do. We respond within one working day.

Accessibility reports are treated as defects, not feature requests.