The short version
Last updated 11 November 2026 · Version 1.0
We want everyone who manages a property with Harthing to be able to use it, including people who use a keyboard instead of a mouse, zoom in, change text spacing or use a screen reader.
- The Harthing web app partially meets WCAG 2.1 at level AA. Most of it meets the standard; three known gaps are listed below.
- You can reach and use every control with a keyboard, and you can always see where the focus is.
- Pages work at 200% zoom, and most reflow to a single column at 400%.
- If something is hard to use, or you need information in another format, email [email protected] and we aim to reply within 5 working days.
Found a problem? Email us: [email protected]
The full statement follows below.
1. What this statement covers
This statement covers the Harthing web app at app.harthing.co.uk, run by Harther Ltd. It says how accessible the app is today, what we know does not work well yet, and how to tell us about a problem. It does not cover this website, harthing.co.uk, which was not part of the audit.
2. Accessibility status
The Harthing web app partially conforms to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. "Partially" means most of the app meets the standard, but some parts do not yet. Those parts are listed in section 5.
3. How we test
We audited the app against WCAG 2.1 AA between September and October 2026 and fixed most of what we found. We tested:
- every screen using only a keyboard
- with browser zoom at 200% and 400%, and at a width of 320 pixels
- with increased line, letter and word spacing
- with automated checkers (axe and Lighthouse)
- with the NVDA screen reader on Windows, in Chrome
4. What you can expect
- You can reach and use every control with a keyboard, and on every control you can see where the keyboard focus is.
- Pages work when zoomed to 200%, and most pages reflow to a narrow single column at 400% without scrolling sideways.
- Text stays readable when you increase line, letter and word spacing; long names wrap rather than being cut off.
- Text and important controls meet the WCAG colour contrast ratios.
- Buttons, links, form fields and groups of options have names a screen reader can announce, and the current page is marked in the navigation.
- If you are signing in with a code, or setting up two-factor authentication, and the time limit runs out, the message stays on screen until you choose to start again.
5. Known limitations
We know about these problems:
- The bottom navigation's labels are shortened on very narrow screens. At high zoom or on small phones, the tab names at the bottom are cut short. Each tab still has its full name, which screen readers announce.
- On a phone or in a narrow window, pages are not divided into regions, and there is no "Skip to content" link. Screen reader users cannot jump between the navigation, the header and the main content, and keyboard users must pass the header's controls before reaching the content. This does not fully meet WCAG 1.3.1 (Info and Relationships) and 2.4.1 (Bypass Blocks). On wider screens these regions and the link are in place.
- Two-factor codes have a time limit you cannot extend. You have 5 minutes to enter a sign-in code and 10 minutes to finish setting up two-factor authentication. The limit is shown on screen, and if it runs out you can start again, but you are not warned before it runs out and cannot ask for more time. This does not meet WCAG 2.2.1 (Timing Adjustable).
6. Tell us about a problem
If something in Harthing is hard to use, or you need information in a different format, email us at [email protected]. Tell us the page you were on and what happened. We aim to reply within 5 working days.
7. About this statement
We prepared this statement on 8 October 2026 and last updated it on 11 November 2026, based on our own testing of the web app. The app relies on HTML, CSS, JavaScript and WAI-ARIA to work with assistive technology. We will review this statement whenever we fix one of the problems above, and at least once a year.