Our first accessibility statement, published in full
We have published how the app is tested against WCAG 2.2 AA, what passes today, and what we are improving next.
An accessibility statement is only worth anything if it is honest, so ours says both what works and what does not yet. It is published in full on our Accessibility page, and we will keep it current rather than write it once and forget it.
Resident.Place is used by people managing something that matters — their home. That is exactly the situation where an app must not get in the way, whether someone uses a screen reader, needs larger text, or navigates entirely by keyboard.
How we test
We test against WCAG 2.2 AA using a mix of automated checks and real assistive technology, on the screens residents use most: reporting a repair, reading a document, and getting support.
- Every core flow checked with a screen reader.
- Colour and text contrast verified, not eyeballed.
- Focus always visible for keyboard users.
- Known gaps listed openly, with a date we are aiming to fix them.
The measure of an accessible product is not the badge. It is whether the person in front of it can do the thing they came to do.
If you hit a barrier we have not listed, the fastest way to tell us is through the app’s support flow — it comes straight to the team that can fix it.
