Reporting accessibility problems with this website
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, email email@example.com or call 0300 123 6633.
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).
Contacting us by phone or visiting us in person
We are always looking at ways to make access to our services easier for everyone.
Some of the ways we can help support you include:
help with filling in forms
British Sign Language (BSL) Interpreting and Lip Speakers
written information in a range of languages and electronic formats (for example email) or in large print
Braille or audiotape
arranging for an interpreter to explain our written information
welcoming calls through Typetalk
arranging for you to speak to a member of staff of the same gender as you
home visits to customers who are unable to access out offices
To find out more please contact us on 0300 123 6633 (Textphone users please prefix our telephone number with 18001).
The content listed below is non-accessible for the following reasons.
Non compliance with the accessibility regulations
The colour contrast makes it hard to read text on some parts of the website. This does not meet WCAG 2.1 success criterion 1.4.3 (contrast minimum).
The search boxes at the top of the website and on the news page don't have visible label field, so people might not know what the boxes are for. This doesn't meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
The search box on the news page doesn't have a description, so people might not know what the box is for. This doesn't meet WCAG 2.1 success criteria 1.3.1 (info and relationships) 3.3.2 (labels or instructions) and 4.1.2 (name, role, value).
The label on the news search box isn't connected to the search control, so people might not know what it is for. This doesn't meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
On some pages the same link text is used for links going to different destinations, so people might not know which link to click on. This doesn't meet WCAG 2.1 success criterion 2.4.4 (link purpose, in context).
External links are identified only by colour, so people might not know if text is a link. This doesn't meet WCAG 2.1 success criterion 1.4.1 (use of colour).
On some pages the HTML is used to format content. This doesn't meet WCAG 2.1 success criterion 2.4.4 (link purpose, in context).
On some pages iFrames are missing titles. This doesn't meet WCAG 2.1 success criterion 4.1.2 (name, role, value).
Not all content is included in HTML5 or WAI-ARIA landmarks. This doesn't meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
Some pages contain HTML5 or WAI-ARIA landmarks that have not been named, so people might know the difference between them. This doesn't meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
The homepage does not have a top level heading. This doesn't meet WCAG 2.1 success criterion 1.3.1 (info and relationships).
When navigating with a keyboard, it isn't always clear to see which link or element is highlighted. This doesn't meet WCAG 2.1 success criterion 2.4.7 (focus visible).
PDFs and Word documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and some forms published as PDF and Word documents. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
Some PDFs and Word documents published after 23 September 2018 do not meet accessibility standards - for example, they may not be structured so they're accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
We are continuing to work through these accessibility issues. We are making sure any new content or digital services we build meet accessibility standards.
Our accessibility roadmap has more information about what we're doing to improve accessibility on this site.
Our accessibility roadmap explains how we will decide which PDFs and Word documents we can provide in an accessible format and when doing so would be a disproportionate burden.
Following an assessment, if we decide that meeting the accessibility requirement would be a disproportionate burden, we will explain this here and provide details of how you can request the information in a different format like accessible PDF, large print, easy read, audio recording or braille.
Something which is a disproportionate burden now will not necessarily be a disproportionate burden forever. If circumstances change, we will re-assess whether we can provide the information in an accessible format.
Content that's not within the scope of the accessibility regulations