For many people, their first contact with us will be via this website. By using the World Wide Web Consortium (W3C) accessibility guidelines, we’re trying to make our website as open and accessible as possible.
This accessibility statement applies to the PPF.
This website is run by the PPF. We want as many people as possible to be able to use this website. That means you should be able to:
- resize text to 200% without loss of content or function
- change text spacing
- 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.
Technical information about our online services and accessibilityThe Pension Protection Fund is committed to making its online services accessible. Our websites are partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. Listed below are areas that require improvement and when we plan to rectify them.
Non compliance with the accessibility regulations
|Problem identified||WCAG 2.1 success criteria||When we plan to fix it|
|alt text should not be an image file name||1.1.1 (Non-text Content)||Dec 2023|
|Document title must not be blank||2.4.2 (Page Titled)||Dec 2023|
|Each a element must contain text or an img with an alt attribute||2.4.4 (Link Purpose (In Context))||Dec 2023|
|Figures and images in PDF documents should have non blank ALT text, except for decorative images which should be marked as artifacts||1.1.1 (Non-text Content)||Dec 2023|
|HTML form control has no accessible name||4.1.2 (Name, Role, Value)||Dec 2023|
|Identify row and column headers in data tables using th elements, and mark layout tables with role=presentation||1.3.1 (Info and Relationships)||Dec 2023|
|img alt text must not use ASCII art (which includes smileys)||1.1.1 (Non-text Content)||Dec 2023|
|PDFs must be tagged to be accessible by screen readers||1.3.1 (Info and Relationships)||Dec 2023|
|Quote " in attribute name. Probable cause: Matching quote missing somewhere earlier||4.1.1 (Parsing)||Dec 2023|
|Removing the underline from links makes it hard for color-blind users to see them||1.4.1 (Use of Color)||Dec 2023|
|Several links on a page share the same link text and surrounding context, but go to different destinations||2.4.4 (Link Purpose (In Context))||Dec 2023|
|Some pages have the same title, so the title cannot be used to distinguish pages||2.4.2 (Page Titled)||Dec 2023|
|Use the lang attribute to identify the language of the page||3.1.1 (Language of Page)||Dec 2023|
|Ensure that text and background colors have enough contrast||1.4.3 Contrast (Minimum)||Dec 2023|
|Headings should not be empty||2.4.6 (Headings and Labels)||Dec 2023|
|Web pages must not contain large images that flash more than three times in any one second period||2.3.1 (Three Flashes or Below Threshold)||Feb 2024|
|User interface controls must have a contrast ratio of at least 3:1 against adjacent colors||1.4.11 (Non-text Contrast)||Feb 2024|
|An element with the attribute tabindex must not appear as a descendant of an element with role=button||4.1.1 (Parsing)||Feb 2024|
|Clickable controls should be keyboard accessible||4.1.2 (Name, Role, Value)||Feb 2024|
|Clickable controls should have an ARIA role||2.1.1 (Keyboard)||Feb 2024|
|Duplicate id - the same ID is used on more than one element||4.1.1 (Parsing)||Feb 2024|
|HTML form control has no accessible name||4.1.2 (Name, Role, Value)||Feb 2024|
|Link uses general text like 'Click Here' with no surrounding text explaining link purpose||2.4.4 (Link Purpose (In Context))||Feb 2024|
|The label element is blank||4.1.2 (Name, Role, Value)||Feb 2024|
|The select element must not appear as a descendant of an element with role=button||4.1.1 (Parsing)||Feb 2024|
|Use semantic markup like strong instead of using the CSS font-weight property||1.3.1 (Info and Relationships)||Feb 2024|
|The label element must not appear as a descendant of an element with role=button||4.1.1 (Parsing)||Feb 2024|
|An element with a role that hides child elements contains focusable child elements||1.3.1 (Info and Relationships)||Feb 2024|
|An element with aria-hidden=true contains focusable content||1.3.1 (Info and Relationships)||Feb 2024|
|The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline||2.4.7 (Focus Visible)||Feb 2024|
You can move between different pages on the website by:
- Using the menu at the top of the page
- Clicking on the links in the sidebar of most pages
Or you can use the sitemap - you’ll find at link to it at the bottom of every page, to quickly access all the pages on the site.
You might find it easier to use a larger font size. To increase or decrease the font size on our web pages:
- Press and hold the control button (Ctrl) while using the mouse wheel to change the font size
- Or you can press and hold Ctrl and use the + and – keys on your keyboard to change the size
- Simply press Ctrl and 0 to return to the original size
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email [email protected]
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, call our resolutions team on 03301232222 or email [email protected].
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
We’re committed to making our 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:
WCAG 3.1.1 Language of Page - PDF's may not have natural language specified.
Content that’s not within the scope of the accessibility regulations
PDFs and other 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 forms published as Word documents. By September 2022, 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.
Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared in September 2021. It was last reviewed on 1 November 2021.
This website was last tested in July 2023. The test was carried out internally by PPF.
Download and print a Letter of Authority (LOA) on our member site.
If you’d like to learn more about the W3C guidelines that we’ve used, please visit: www.w3.org/WAI.