HFH Go Accessibility Audit
Web Accessibility Remediation for HFH Go mobile app for both iOS and Android to make it conforms with the WCAG technical standards and comply with the ADA.
This HFH Go accessibility audit and WCAG 2.1 AA remediation covered a United States mobile application from Hands Free Health — a voice-enabled health assistant that helps people track wellbeing and access health information.
A health app is judged a little differently from a website: it must meet WCAG 2.1 alongside the iOS and Android platform accessibility guidelines, and it has to work with VoiceOver and TalkBack. A voice-first design can help some users, but the visual app interface must still be fully operable for everyone.
Table of Contents
Why accessibility is critical for a health app
Mobile health apps are expected to be accessible: in the United States health services fall under the Americans with Disabilities Act (ADA) Title III, the Apple and Google platform guidelines build on WCAG 2.1 Level AA, and health information is high-stakes. A reading or alert a screen-reader user cannot hear, or a control a switch user cannot reach, can keep someone from managing their own health.
Scope and standard
Our HFH Go accessibility audit assessed the iOS and Android app against WCAG 2.1 Level AA and the platform accessibility guidelines, across the journeys that matter: onboarding and sign-in, the voice assistant and health features, readings and data display, alerts and notifications, and settings.
How we ran the HFH Go accessibility audit
- Screen-reader testing with VoiceOver on iOS and TalkBack on Android, on real devices
- Automated checks with the platform tools (Accessibility Scanner on Android, Accessibility Inspector on iOS) alongside axe-based tooling
- Keyboard, switch and external-control operation, with attention to focus order within each screen
- Touch-target size, colour-contrast and dynamic-type / text-scaling testing for low-vision users
What accessibility means on each part of the site
Because HFH Go is a mobile health app, our HFH Go accessibility audit focused on the parts a user relies on, on the device:
- Onboarding and sign-in need labelled fields, announced errors and a logical focus order, so getting started works with VoiceOver and TalkBack.
- The voice assistant and health features need accessible names, roles and states, so every control is usable by screen-reader and switch users.
- Readings and data display need to be announced clearly, not conveyed by colour or position alone.
- Alerts and notifications need to reach assistive technology, so important health prompts are never silent.
- Settings and navigation need adequate touch targets, strong colour contrast and support for the device’s text-size settings.
Outcome
This HFH Go accessibility audit, combining manual and automated testing with remediation, brought the app into line with WCAG 2.1 AA expectations, so people using a screen reader or a keyboard can use it without barriers. Every fix was verified with assistive technology rather than assumed from an automated pass, so the result holds up in real use.