This accessibility statement applies to https://www.homesenglandcareers.co.uk/
This website is run by Homes England. We want as many people as possible to be able to use this website. For example, that means you should be able to:
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We’ll consider your request and get back to you in 2 working days. We can call or email so please advise how you would prefer to be contacted.
We’re always looking to improve the accessibility of this website.
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: RecruitmentInfo@homesengland.gov.uk
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Homes England is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below.
The content listed below is non-accessible for the following reasons.
Our forms are built and hosted through third party software and made to look like our website. The current version we are using fails several WCAG 2.1 success criterion.
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).
The structure of the page cannot be programmatically determined. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
A correct reading sequence cannot always be programmatically determined. This fails WCAG 2.1 success criterion 1.3.2 (Meaningful Sequence).
Some navigation elements do not have text descriptions. This fails WCAG 2.1 success criterion 1.3.3 (Sensory Characteristics).
Not all fields have labels. This fails WCAG 2.1 success criterion 1.3.5 (Identify Input Purpose).
When keyboard focus triggers additional content to become visible it is not easily dismissible. This fails WCAG 2.1 success criterion 1.4.13 (Content on Hover or Focus).
Not all of the controls are accessible using keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
For some applications there may be a timed assessment, there is no ability to request additional time. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable).
The loading animation has no controls, so people are unable to pause it. This fails WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide).
The website has no means to skip the navigation using a screen reader. This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks).
Some pages do not have clear titles. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).
Not all focusable components receive focus in an order that preserves meaning and operability. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order).
Not all links or buttons have descriptive title. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)).
Not all pages have multiple routes to them. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways).
Not all headings or labels describe topic or purpose. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).
Not all elements have a visible focus indicator. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
Not all fields have text labels. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name).Some components initiate a change of context when receiving focus. This fails WCAG 2.1 success criterion 3.2.1 (On Focus).
Not all fields have labels. This fails WCAG 2.1 success criterion 3.3.2 (Labels or Instructions).
Some pages may not conform 100% to the HTML specifications. This fails WCAG 2.1 success criterion 4.1.1 (Parsing).
Some custom fields cannot be programmatically determined. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Not all status messages can be programmatically determined. This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).
We plan to move to a newer, more accessible version of the careers website software in April 2026.
This statement was prepared on the 26th November 2020. It was last reviewed on the 26th November 2020.
This website was last tested on 22nd January 2025. The test was carried out by Genius Online Ltd.