Accessibility statement
This website is run by WSP on behalf of xxxxxxxxxxxxx. 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 (use our high contrast toggle at the top of this page) 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).
- Most of the website text is provided by project partners. We work with our partners to make text simple to understand.
How accessible is this website
We know some parts of this website are not fully accessible:
- XXXXXXXXXXXXXXXXX This fails WCAG 2.1 success criterion X.X.X (title name). We plan to fix this as soon as possible.
- XXXXXXXXXXXXXXXXX This fails WCAG 2.1 success criterion X.X.X (title name). We plan to fix this as soon as possible.
- XXXXXXXXXXXXXXXXX This fails WCAG 2.1 success criterion X.X.X (title name). We plan to fix this as soon as possible.
- XXXXXXXXXXXXXXXXX This fails WCAG 2.1 success criterion X.X.X (title name). We plan to fix this as soon as possible.
| Potential issues | Status | Action |
|---|---|---|
| Insufficient contrast | Project specific | Each WSP website can be branded based on project partners' branding. Whilst WSP advises on contrast accessibility, it's the responsibility of the project partners to choose colours that are compliant. |
| Modify the line height or spacing of text | Alternative available | Project teams can opt into adding a plugin such as User Way. |
| Interactive media elements such as before and after image sliders, interactive ConnectAll virtual room or embedded questionnaires may not be screen reader accessible | Project specific | These are typically included in WSPs using third party tools. When selecting such tools, accessibility should be considered. |
| Most PDF documents are not fully accessible to screen reader software | Project specific | It's the responsibility of the project partners to provide PDFs that are accessible. A helper text can be added using WSP when mediums uploaded to state whether or not these are accessible. |
| Embedded videos may not have captions | Project specific | It's the responsibility of the project partners to prepare and embed videos that are accessible. |
| esri GIS Maps | Alternative available | https://www.esri.com/en-us/accessibility/overview. |
| Interactive map cannot be navigated using keyboard or screen reader voice commands | Alternative available | WSP hope to be able to provide a guide |
Interactive Maps
Esri continually monitors and tests accessibility standards across all of their products, our mapping based platforms use the Esri functionality a link to the conformance report for the online maps can be found here.
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, contact pinpoint.support@wsp.com
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) .
Information about this website’s accessibility and Compliance Status.
This web Site Accessibility Status - AA
WSP Ltd is committed to making its websites 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.1 AA standard, due to the non-compliances and exemptions listed previously.
Content that’s not within the scope of the accessibility regulations
- PDFs and other documents Project partners often prepare presentations and plans to communicate proposals or research results and make them available as PDFs. These PDFs often use a lot of images and they may not be structured in a way to be accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.We encourage project partners to include all essential content in the platform pages in the HTML rather than rely on PDF content. Links to PDFs state whether or not the PDF it is linked to is accessible. The accessibility regulations do not require WSP to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. It's the responsibility of our project partners to upload PDFs that are accessible.
- Images of text News posts may include images that contain text for example a preview of a leaflet for an invitation to a workshop. We advise our project partners that this type of content is not accessible and to include all essential information such as purpose of workshop, address etc in the news post.
How we tested this website
WSP uses XXXXXXXXXXX.com to Audit this site. The Design Feedback platform was tested in 2016 and accredited WCAG 2.0 AA Standard by the The test was carried out by the internal product team at WSP using Wave and Lighthouse browser extension tools. We also manually tested keyboard navigation and screen reader capabilities on macOS.
What we’re doing to improve accessibility
We continuously work with project partners to check their WSPs for AA compliance. If you come across something that could be improved. Please get in touch by emailing pinpoint.support@wsp.com This statement was prepared on xx/xx/xxxx. It was last updated on xx/xx/xxxx.
PREPARATION OF THIS ACCESSIBILITY STATEMENT
[Note: the wording about when the statement was prepared is legally required, so do not change it.] This statement was prepared on [date when it was first published]. It was last reviewed on [date when it was last reviewed].
This website was last tested on [date]. The test was carried out by [add name of organisation that carried out test, or indicate that you did your own testing].
We used this approach to deciding on a sample of pages to test [add link to explanation of how you decided which pages to test].
[Note: you do not have to use this approach to sampling, but you should link to a full explanation of what you tested and how you chose it. If you get a third party auditor to test your website for you, they should include sampling details in test report - so you can just to link to that.]
You can read the full accessibility test report [add link to report].
[Note: publishing the test report is optional, but doing so may allow you to make your accessibility statement shorter and more focused.]