• This statement covers whg.uk.com

The purpose of the website is to provide information and access to whg services. This web platform is run by whg and M3 Digital. 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 200% 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
• navigate 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.

We know some parts of the website are not fully accessible:

• Older PDF documents are not fully accessible and there is no text alternative
• The colour contrast is too low on some links and buttons
• Alternative text is not available for all images

If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact us.

If you need information on this website in an alternative format, such as accessible PDF, large print, easy read, audio recording or braille: please contact us. We’ll consider your request and get back to you in 10 working days.

• Email: communicationsteam@whgrp.co.uk
• Call: 0300 555 6666
• Write to us: Communications team, 100 Hatherton Street, Walsall, WS1 1AB

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).

whg 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

The content listed below is non-accessible for the following reasons.

• Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails the WCAG 2.2 Success Criterion 1.1.1 (Non-text Content). We plan to add text alternatives for all images by September 2024. When we publish new content we’ll make sure our use of images meets accessibility standards.
• Some pages use colour as the only way of distinguishing and highlighting important information. This fails the WCAG 2.2 Success Criterion 1.4.1 (Use of Colour). We plan to correct these pages by September 2024. When we publish new content we’ll make sure it meets accessibility standards.
• Text colours on some buttons and links do not have sufficient contrast. This fails the WCAG 2.2 Success Criterion 1.4.3 (Contrast (Minimum)). We plan to correct button and link colours by September 2024.
• Some links include ‘click here’ wording which is not meaningful for all users. This fails the WCAG 2.2 Success Criterion 2.4.4 (Link Purpose). We plan to correct these pages by September 2024. When we publish new content we’ll make sure it meets accessibility standards.
• Some PDFs 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.2 success criterion 4.1.2 (name, role value). We are making improvements to our website and plan to provide a text alternative for new PDFs by December 2024.

• We test our website for accessibility and fix identified issues on an annual basis.
• We have included accessibility training as a learning objective for each web editor this year, so the team understand the legislation and requirements for producing accessible content.

This statement was prepared on 24 July 2024. It was last reviewed on 24 July 2024.

This website was last tested on 24 July 2024 using WAVE and SiteImprove.