Accessibility
We want HomeAtlas to work for everyone who runs a home, including people who use a screen reader, navigate by keyboard, need larger text, or find motion uncomfortable. This page says plainly where we are, what still needs work, and how to tell us when we've got it wrong.
How accessible HomeAtlas is
HomeAtlas aims to meet WCAG 2.2 Level AA, the international standard referenced by the European Accessibility Act, the UK Equality Act and the Americans with Disabilities Act. We believe the app currently meets that standard, with the exceptions listed below.
Accessibility is checked automatically every time we change the code. Our build will not ship if a control loses its keyboard focus outline, if a form field has no label, if a colour combination drops below the required contrast, or if an animation ignores your system's "reduce motion" setting.
What we've built in
- Every control can be reached and operated with a keyboard alone, and shows a clear outline when focused.
- Dialogs keep your keyboard inside them while open and return you to where you were when they close.
- Things that change on their own, saving, loading, errors, credit warnings, are announced to screen readers, not just shown.
- Text meets a 4.5:1 contrast minimum. Colours are chosen from a small set of palettes, and every colour pair in every palette is measured against that minimum before it ships, so there is no combination you can select that leaves text you can't read.
- Turning on "reduce motion" in your device settings stops animations rather than just slowing them.
- Pinch-zoom is never blocked, and the app reflows down to small screens without horizontal scrolling.
Where we fall short
We would rather name these than let you discover them:
- Small controls. Some compact buttons are around 26 pixels. That meets the AA requirement of 24 pixels, but it is below the 44 pixels we would prefer on a phone. We are enlarging these.
- Native app settings. In the Android and iOS apps, your system text-size and reduce-motion settings do not yet carry into every screen. The same screens in a mobile browser do respect them.
- Automated testing has limits. Our checks read the code, not a live screen. Reading order and announcements are checked by hand, which means a new screen can occasionally ship with a gap we then fix on report.
Tell us about a barrier
If something blocks you, we treat it as a fault, not a feature request. Two ways to reach us:
- The Send feedback button in the app header. It records the page you were on and gives you a reference id.
- Email [email protected] with "Accessibility" in the subject.
We aim to reply within two business days. Please tell us the screen, what you were trying to do, and what assistive technology you use. It helps us reproduce the problem quickly. If you are not satisfied with our response, you can escalate to the equality or accessibility regulator in your country.
About this statement
Prepared on 31 July 2026 following an internal audit of the whole application against WCAG 2.2 AA, combined with automated checks that run on every change. It is reviewed whenever a significant new area ships, and at least once a year.