Accessibility statement for Retrofit Information, Support and Expertise
Accessibility statement for Retrofit Information, Support and Expertise
This accessibility statement applies to Home | Retrofit Information, Support and Expertise.
This website is run by the Department for Energy Security and Net Zero (DESNZ). We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
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.
How accessible this website is
We know some parts of this website are not fully accessible:
- images do not contain the correct alternative attributes
- some elements cannot be interacted with via keyboard navigation alone
- videos do not have text transcripts or audio descriptions
- the focus order of some pages is illogical
- the “Skip to main content” link is not visible on screen
- there is moving content observed without a way to stop, pause or hide it
- text error descriptions are not provided for some form fields
- mandatory form fields do not show a text error when left blank
- related links are not grouped together within a <nav> element
- ARIA landmarks are not used to contain all the content on screen
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email Wyatt.Conneely3@energysecurity.gov.uk
- call +442072158519
We’ll consider your request and get back to you in 14 days.
Enforcement procedure
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).
Technical information about this website’s accessibility
The Department for Energy Security and Net Zero (DESNZ) is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some informative images lack a descriptive text alternative, so people using a screen reader cannot access the information. This can be seen on all pages where the main logo is situated. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
We plan to resolve this by: 10/05/2026
Decorative images have informative alternative attributes, which present unnecessary information to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
We plan to resolve this by: 10/05/2026
Throughout the site, some buttons share the same accessible name, which may mean that users of screen readers do not know how to proceed. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
We plan to resolve this by: 10/05/2026
Buttons do not have appropriate labels. Buttons without labels do not provide information about the functionality of the button to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
We plan to resolve this by: 10/05/2026
Audio-only content is present, which does not have a text transcript, preventing some users from accessing this information. This fails WCAG 2.2 success criterion 1.2.1 (pre-recorded audio-only and video-only).
We plan to resolve this by: 26/05/2026
Video-only content is present, which does not have a text transcript or audio description, which may create barriers for some users. This fails WCAG 2.2 success criterion 1.2.1 (pre-recorded audio-only and video-only).
We plan to resolve this by: 26/05/2026
Pre-recorded videos do not have synchronised captions, which may impact users with hearing impairments. This fails WCAG 2.2 success criterion 1.2.2 (captions (pre-recorded)).
We plan to resolve this by: 26/05/2026
Pre-recorded videos do not have a text transcript or audio description track. This fails WCAG 2.2 success criterion 1.2.3 (audio description or media alternative).
We plan to resolve this by: 26/05/2026
Pre-recorded videos do not have an audio description track, which may affect access to this content. This fails WCAG 2.2 success criterion 1.2.5 (audio description (pre-recorded)).
We plan to resolve this by: 26/05/2026
List elements have been used incorrectly on the carousel controls, which may reduce accessibility for some screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
We plan to resolve this by: 10/05/2026
ARIA landmarks aren’t used to identify all page content, including the ‘Getting Started in Retrofit’ page, where there is no main landmark. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
We plan to resolve this by: 10/05/2026
Identical ARIA landmarks are not distinguished. This can be seen on the ‘Homepage’, where all carousels have been given the same name. This could make it difficult for the screen reader user to navigate this page. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
We plan to resolve this by: 10/05/2026
Grouped fields are not contained within a fieldset element, which may result in screen reader users not being able to understand the relationships between certain form fields. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
We plan to resolve this by: 10/05/2026
Some navigational links on the site are not contained within a navigation element. This stops users who navigate using landmarks from being able to navigate to the navigational links directly. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).
We plan to resolve this by: 10/05/2026
A valid autocomplete attribute is not present, and form fields cannot be programmatically determined. This fails WCAG 2.2 success criterion 1.3.5 (identify input purpose).
We plan to resolve this by: 10/05/2026
Favouring a piece of content is communicated only by colour. Users with visual impairments or colour blindness may not be able to recognise that these articles have been chosen. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).
We plan to resolve this by: 10/05/2026
The error message text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).
We plan to resolve this by: 10/05/2026
Rendering issues with the main navigation are present when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (resize text).
We plan to resolve this by: 10/05/2026
Some navigational content is not available when the browser size is reduced to 1280px and zoomed in 400%. This makes mobile navigation difficult. This fails WCAG 2.2 success criterion 1.4.10 (reflow).
We plan to resolve this by: 10/05/2026
Some non-textual content lacks contrast against the background page. This includes form field boundaries and checkboxes across the site. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).
We plan to resolve this by: 10/05/2026
There is not enough contrast between the foreground and background within a graphical object. This includes the non-selected favourite buttons situated on the ‘Homepage’. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).
We plan to resolve this by: 10/05/2026
Content that appears on hover or focus is unable to be dismissed without moving the pointer cursor. This includes the sub-menu of the main navigation. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).
We plan to resolve this by: 10/05/2026
Some content is inaccessible when using a keyboard to navigate the site. This includes the notification which appears after the user has favoured a piece of content. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).
We plan to resolve this by: 10/05/2026
Content which automatically moves is present on the ‘Homepage’, with no mechanism available to stop, pause or hide it. This fails WCAG 2.2 success criterion 2.2.2 (pause, stop, hide).
We plan to resolve this by: 10/05/2026
A ‘Skip to Main Content’ link is present but is not visible on screen. This may mean that users of keyboard-only navigation miss this link and continue to tab through repeated content. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).
We plan to resolve this by: 10/05/2026
Skipped heading levels are present across the site. This may reduce accessibility for screen reader users who navigate the site via heading levels. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).
We plan to resolve this by: 10/05/2026
Frame elements are not appropriately titled, which may prevent screen reader users from understanding their purpose or exploring the frame further. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).
We plan to resolve this by: 10/05/2026
The focus order of the site is not logical. Users who rely on keyboard-only access for operating a website benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (focus order).
We plan to resolve this by: 10/05/2026
Links with identical text are not distinguished by their accessible labels. This could confuse screen reader users and they may not know how to proceed. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).
We plan to resolve this by: 10/05/2026
The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard-only users to track the elements in focus. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).
We plan to resolve this by: 10/05/2026
The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (label in name).
We plan to resolve this by: 10/05/2026
Required form fields do not have a text error, which may mean users do not know which field needs to be corrected before proceeding. This fails WCAG 2.2 success criterion 3.3.1 (error identification).
We plan to resolve this by: 10/05/2026
Form fields, including the email address field on the ‘Login’ and ‘Register’ pages, do not show a text error message if an invalid email address is entered. This fails WCAG 2.2 success criterion 3.3.1 (error identification).
We plan to resolve this by: 10/05/2026
Form fields which have a text error do not provide adequate suggestions on how to fix the error. This fails WCAG 2.2 success criterion 3.3.3 (error suggestion).
We plan to resolve this by: 10/05/2026
The ‘Homepage’ carousels have ARIA hidden elements that are either focusable or contain focusable elements. This may cause problems for users of screen readers. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
We plan to resolve this by: 10/05/2026
While navigating with a screen reader, the footer and logo imagery is announced as “Lead Genera Desktop”, due to the aria-label. This is not a helpful description to the user and may cause disorientation on the page. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
We plan to resolve this by: 10/05/2026
Within the ‘Homepage’, when the carousels automatically update, an unexpected announcement of “Current item” is made each time a new slide appears. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
We plan to resolve this by: 10/05/2026
Throughout the site, there are various incorrect announcements which are made by screen readers. Within the ‘Register’ page, the user is informed of email addresses missing an apostrophe, and while navigating with MacOS VoiceOver, the error message of a blank form field is announced before it is visually seen. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).
We plan to resolve this by: 10/05/2026
Status messages are not announced by screen readers. This includes the error messages which appear on the ‘Register’ and ‘Newsletter Sign Up’ pages. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 (status messages).
We plan to resolve this by: 10/05/2026
Additional content is not announced by a screen reader. This can be seen on all pages when interacting with the main navigation, on the ‘Homepage’ when selecting a new carousel slide and when the filter results appear on the ‘Getting Started in Retrofit’ page. This fails WCAG 2.2 success criterion 4.1.3 (status messages).
We plan to resolve this by: 10/05/2026
Preparation of this accessibility statement
This statement was prepared on 12th February 2026. It was last reviewed on 12th February 2026.
This website was last tested on 11th February 2026. The test was carried out by Zoonou.
Zoonou used WCAG-EM to define the pages tested and test approach.