Accessibility

What we have built into this site

• Keyboard access throughout. Every interactive element can be reached and operated with a keyboard, in a logical order, with a visible focus indicator that meets contrast requirements. A "skip to main content" link is the first thing a keyboard user reaches.
• Semantic structure. Pages use real headings in order, real lists, real landmarks and real buttons and links — a link navigates, a button acts, and neither is faked with a styled div.
• Text alternatives. Every application screenshot carries a description naming the screen and what it does. Decorative graphics are hidden from assistive technology rather than announced as noise.
• Reduced motion. The site has a small amount of ambient animation. If your system asks for reduced motion, all of it stops.
• Text scaling and reflow. Type is set in relative units and layouts reflow, so enlarging text does not clip content or force horizontal scrolling.
• No motion or colour as the only signal. Status is carried by text as well as colour, so "in development" and "planned" are distinguishable without seeing the difference between mint and lime.

What we have not verified

We want to be straightforward about the limits of the above. We have not yet:

• Commissioned an independent accessibility audit of this site.
• Completed testing with screen-reader users, rather than testing with a screen reader ourselves.
• Tested against the full range of assistive technologies, including switch control and voice control.

Until those are done, treat this page as a statement of intent and effort, not as a conformance claim.

Accessibility in BreatheFree

The application is held to a higher bar than the website, because it is used in harder circumstances. Before release it must support VoiceOver, TalkBack, keyboard-only navigation and switch control; 200% text scaling; a 4.5:1 contrast minimum; reduced motion; and meaning that never depends on colour alone. Audio and video education must carry captions and transcripts.

One constraint we have to name: where a screen is currently rendered from approved bitmap artwork, the text inside that image cannot reflow when someone enlarges type. That is why those screens are being rebuilt as native, responsive components — it is an accessibility requirement, not a modernisation exercise.

Tell us about a barrier

If any part of this site or our products is difficult or impossible for you to use, please tell us at support@tetherhealthgroup.com. It helps if you can say what you were trying to do, what happened, and what you were using — but please write to us even if you would rather not go into detail.

We treat accessibility reports as defects, not as feature requests, and we will tell you what we are doing about yours.