Accessibility Statement
Last reviewed:
We want as many people as possible to be able to use iPO Hub. This page says how accessible the website and portals are, what we know is not yet right, and how to get help.
What this statement covers
This statement applies to the iPO Hub website at www.ipohub.co.uk and to the iPO Hub portals: the landlord and agent dashboard (dashboard.ipohub.co.uk), the tenant portal (tenancy.ipohub.co.uk) and the contractor portal (services.ipohub.co.uk). It does not cover the staff console, which only iPO Hub staff use. iPO Hub Limited runs this service.
For example, you should be able to:
- change colours, contrast levels and fonts using your browser or device settings
- zoom in up to 400% without the text spilling off the screen
- navigate most of the service using just a keyboard
- navigate most of the service using speech recognition software
- listen to most of the service using a screen reader (including recent versions of JAWS, NVDA and VoiceOver)
- turn off animations by choosing "reduce motion" in your device settings
We have also made the text as simple as we can to understand.
AbilityNet (opens in new tab) has advice on making your device easier to use if you have a disability.
The standard we aim for
We are aiming to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 (opens in new tab) at level AA. We do not yet meet it everywhere: the known issues are listed below, with what we are doing about each one.
iPO Hub is a private company, so the public sector accessibility regulations do not apply to us directly. We follow their standard because councils and housing partners expect it, and because of our duty under the Equality Act 2010 to make reasonable adjustments.
Known issues
We know some parts of the service are not fully accessible yet:
Some loading placeholders in the dashboard and the tenant portal are not announced to screen reader users. The portal home pages, the billing page and the contractor jobs list now announce loading.
- Standard:
- WCAG 2.2 success criterion 4.1.3 (status messages)
- What we are doing:
- Move the remaining placeholders to one shared loading component that announces loading.
Some older dashboard forms (for example work orders and property details) mark required fields with an asterisk only, and show some validation errors without linking them to the field.
- Standard:
- WCAG 2.2 success criteria 3.3.1 (error identification) and 3.3.2 (labels or instructions), in places
- What we are doing:
- Move these forms to a shared field pattern with a label, hint and linked error message.
Some wide data tables in the dashboard need sideways scrolling on a phone.
- Standard:
- Allowed for data tables under success criterion 1.4.10 (reflow), but harder to use
- What we are doing:
- Offer a stacked layout on phones for the busiest tables.
Some status labels, badges and table details use small text (11 pixels).
- Standard:
- Not a WCAG failure, but harder to read
- What we are doing:
- Raise the smallest text sizes in a design pass.
Our automated checks cover the public website and the home page of each portal, but not yet every page inside the portals.
- Standard:
- Not a failure in itself: issues there may not be found yet
- What we are doing:
- Add the busiest portal pages (properties, tenancies, compliance and maintenance) to the automated checks.
Content we do not control, and so cannot fix ourselves:
- The demo booking calendar on the contact page, which is provided by a third party. You can ask for a demo with the contact form or by email instead.
- The Google sign-in page, which Google provides.
- PDFs of statutory notices (for example Form 4A and Form 3A), which follow the official government wording and layout.
Asking for help or another format
If you need information on this website in a different format, such as accessible PDF, large print, easy read, audio recording or braille, or you find a problem not listed on this page, use the contact page and choose “Accessibility” as the type of enquiry, or email [email protected].
Tell us the page address, what you were trying to do and what assistive technology you use, if any.
We will reply within 5 working days.
If you are not happy with our response
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS) (opens in new tab).
How we test
Every change to the website and portals is checked automatically before it is released: an accessibility linter checks the code, and an automated scan (axe-core) checks the main pages against WCAG 2.2 AA at desktop and phone widths.
The service was last tested on 22 November 2026 by iPO Hub, using those automated tools and a manual review of shared components, keyboard use, forms, colour contrast and motion. We tested the public website (home, pricing, audience, solution, platform, resource, tool and legal pages), the sign-in page of each portal and the home page of each portal.
We have not yet had an external accessibility audit, and the service has not yet been tested by disabled users. We review the known issues above every quarter.
Preparation of this statement
This statement was prepared on 22 November 2026. It was last reviewed on 22 November 2026.