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.
This statement applies to this website only, specifically the following domains:
How accessible this website is
We know some parts of this website are not fully accessible. There are two main issues in particular which could have an impact on some users:
- PDF tagging
- some components not being keyboard operable
What to do if you cannot access parts of this website
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille contact us.
We will acknowledge your request within five working days and respond to you within 20 working days.
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 us.
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
TPR 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.1 AA standard, due to the non-compliances listed below.
Non accessible content
The content listed below is non-accessible for the following reasons.
Non compliance with the accessibility regulations
|Problem identified||WCAG 2.1 AA success criteria||When we plan to fix it|
Some images have inappropriate values for their ‘alt’ attributes which will not be meaningful to screen reader users.
1.1.1 (non-text content)
|By September 2020|
Heading elements are not used for text elements acting as visual headings, or missing from components.
Data tables need extra mark up to help screen reader users to understand the information.
PDF documents must be tagged.
iframe elements used for video content must have ‘title’ attributes.
Breadcrumb trail needs further semantic structure.
On the search results page the article tag should only be used for self-contained content.
1.3.1 (info and relationships)
By September 2020
The search filters follow the results in the reading order so some screen reader users will be unaware they are present.
1.3.2 (meaningful sequence)
By end of 2019
The focus indicator does not supply enough colour contrast.
1.4.11 (non-text contrast)
|By end of 2019|
|Some components do not supply enough colour contrast.||1.4.3 (colour contrast)||By end of 2019
The in-page navigation tools are not keyboard operable.
The accordion controls are not keyboard operable.
The mobile layout navigation menu control is not keyboard operable.
|2.1.1 (keyboard navigation)||By end of 2019|
There is no mechanism to bypass the main navigation so keyboard-only users will have to tab through all navigation links.
2.4.1 (bypass blocks)
By end of 2019
The links in the navigation flyout menus are read by screen reader software, whether they are shown on the screen or not.
The label for the search input element may cause problems for some assistive technologies.
SVG images receive keyboard focus in Internet Explorer 11.
The document language is not set in the PDFs.
2.4.3 (focus order)
By end of 2019
By September 2020
HTML non-compliances may have an impact on the accessibility of the page.
By end of 2019
Content that’s not within the scope of the accessibility regulations
Many of our older PDFs and Word documents 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).
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 forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix older research documents.
Any new PDFs or Word documents we publish will meet accessibility standards.
How we tested this website
This website was last tested between 10 July and 6 August 2019. The test was carried out by a company called net-progress.
We audited 25 pages (23 HTML pages and two PDF documents). We chose this sample of pages to include as many different types of content and audiences as possible.
We tested the following pages:
- Home page
- Employers step 2
- Step 1. Choose a pension scheme
- Employer covenant: overview
- Code 13: Governance and administration of occupational trust-based schemes providing money purchase benefits
- Media hub
- Search results
- Scheme Funding Analysis 2019
- Corporate Plan 2019 – 2022
- Current job vacancies
- Associate - Business Analyst (page no longer available)
- Recently released information
- A quick guide to measuring your data (PDF, 58KB ,5 pages)
- DB investment
- DB investment governance
- Investing to fund DB
- Matching DB assets
- DB growth assets
- Implement a DB investment strategy
- Monitoring DB investments
- Investment guidance (PDF, 1.2MB, 93 pages)
What we’re doing to improve accessibility
We are developing an accessibility roadmap to show how and when we plan to improve accessibility on this website.
The website will be re-tested by net-progress once we have made the changes recommended in their accessibility report.
We routinely test all new components, templates and functionality to ensure they are accessible before we use them on the website.
We will continue to use an automated performance monitoring service to alert us to any significant accessibility issues.
We are currently reviewing a number of our older sub-domains and will provide further clarity on the status of their accessibility in 2020.
This statement was prepared on 23 September 2019.
It was last updated on 23 September 2019.