Accessibility

Accessibility

This accessibility statement applies to Worcestershire Pension Fund's website

This website is run by Worcestershire Pension Fund. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • zoom in without the text spilling off the screen
  • navigate most of the website using just a keyboard (including skip to content or skip to main navigation)
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader
  • attend the online events that we host via Zoom; for more information please visit Zoom - Accessibility

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website aren’t fully accessible:

  • most older PDF documents aren’t fully accessible to screen reader software
  • live video streams do not have captions

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, please contact: pensions@worcestershire.gov.uk

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: pensions@worcestershire.gov.uk.

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)

Contacting us by phone or visiting us in person

Some of our offices have audio induction loops. You may wish to check whether a loop is available before your visit, please see the contact us page.

Technical information about this website’s accessibility

Worcestershire Pension Fund is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1. AA standard, due to the non-compliances listed in the Non-accessible content section.

Non-accessible content

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

Non-compliance with the accessibility regulations

  • some video content does not have an alternative for non-sighted users in the form of an audio description or transcript, this fails 1.2.5 Audio Description (Pre-recorded)
  • some embedded videos do not have captions or a transcript, this fails 1.2.2 Captions (Pre-recorded)
  • some images do not have alt text or have alt text when it should be decorative, this fails 1.1.1 Non-text content
  • some menu items and menus in the contacts' area do not announce open and closed states, this fails 1.4 Distinguishable
  • some carousels read in an illogical order, this fails 1.3.2 Meaningful Sequence
  • some tables do not have a caption element to describe their content, this fails 1.3.1 Info and relationships
  • in some areas of the site text falls on poor contrast background, this fails 1.4.3 Colour contrast minimum
  • scroll bars appear in some menus on smaller screen sizes hiding some menu content, this fails 1.4.10 Reflow
  • some text size in our website is very small and does not zoom, this fails 1.4.4 Resize text
  • some text and interactive functions are close together meaning it might be difficult to use with poor dexterity, this fails 1.4.12 Text Spacing
  • the A-Z features on the site use anchors to display filtered results, this means those on the keyboard don’t benefit from filtered content and have to always navigate the whole page, this fails 1.3.2 Meaningful Sequence, 2.4.1 Bypass blocks and 2.1.1 Keyboard
  • the back to top function is a floating object that may obscure content, this fails 2.4.11 Focus Not Obscured (Minimum)
  • some download links may not make sense when read on their own; this fails 2.4.4 link purpose in context
  • the same link text is used for links going to different destinations; this fails 2.4.4 link purpose in context
  • there are forms where the form elements are not grouped; this fails WCAG 2.1 success criteria 1.3.1 (info and relationships) and 3.3.2 (labels or instructions)
  • text on some focus elements and forms do not meet minimum contrast, this fails 1.4.3 contrast minimum
  • lists of related links should be written semantically as a list, this fails 1.3.1 info and relationships
  • some table headings are missing a scope, this fails 1.3.1 info and relationships
  • there are some pages where we use input fields that have no description; these fail 2.1, 1.3.1 info and relationships, 3.3.2 labels or instructions and 4.1.2 name, role, value
  • when using Twitter feeds users on keyboard or screen readers are trapped in the Twitter feed and cannot return to the site, this fails 2.1.2 No keyboard trap
  • not all elements on focus have an obvious change of appearance to those with low vision, this fails 2.4.13 Focus Appearance
  • carousels don’t announce logically for users, you get to the left arrow, then the carousel items and then after the right arrow, this fails 2.1.1 Keyboard
  • some items on homepage carousels do not announce, this fails 2.4.6 Headings and labels and 1.4 Distinguishable
  • users with difficulties of dexterity will struggle with the target size of some buttons, this fails 2.5.5 Target Size (Minimum)
  • some pages use collapsible content instead of navigating to a new page, which maybe confusing as its inconsistent navigation, this fails 3.2.3 Consistent Navigation
  • some page titles throughout the site do not announce, this fails 2.4.2 page titled
  • filters on the news, events and language are actioned by focus and not select as it currently announces, this fails 2.1.1 Keyboard 3.2.1 On focus and 3.3.2 Label instructions
  • some icons announce the full url rather than descriptive, this fails 2.4.4 Link purpose
  • some pages have unexplained abbreviations, this fails 3.1.4 Abbreviations
  • some pages have a considerable amount of text and complex language, this fails 3.1.5 Reading Level
  • on the homepage users are announced the heading latest news, then a button for ‘view all news’, this is illogical, this fails 2.4.3 Focus Order
  • on load of the website the cookie item receives focus which is confusing for keyboard navigation, this fails 3.2.1 On focus
  • on the search page screen reader users do not know that the search results have been actioned or how many results their search found, this fails 4.1.2 Name Role Value
  • back button cannot be selected with a keyboard (this error is likely to appear on all pages using this element), this fails 2.1.1 Keyboard
  • navigation closes on keyboard focus, this fails 3.2.1 On Focus
  • multiple elements using the same identifier (#ID) on the Home page, this fails 4.1.1 Parsing
  • ARIA hidden element contains focusable descendants in the footer, this fails 4.1.2 Name Role Value
  • no accessible name on the ‘Select language’ dropdown, this fails 4.1.2 Name Role Value
  • text gets cut off when viewing the page at 200% zoom, this fails 1.4.4 Resize text
  • back button cannot be selected with a keyboard, this fails 2.1.1 Keyboard
  • unable to open and close search bar with a keyboard, this fails 2.1.1 Keyboard
  • navigation closes on keyboard focus, this fails 3.2.1 On Focus
  • multiple elements using the same identifier (#ID) on the Search page, this fails 4.1.1 Parsing
  • ARIA hidden element contains focusable descendants in the footer, this fails 4.1.2 Name Role Value
  • unordered list contains content that is not allowed, this fails 1.3.1 Info and Relationships
  • ARIA-hidden elements contain focusable descendants on the Events page, this fails 4.1.2 Name Role Value
  • text not contained in semantic HTML on the Tabletop club page, this fails 1.3.1 Info and Relationships
  • list with four rows of information is only announced as one list item to screen reader users, this fails 1.3.1 Info and Relationships
  • text not contained in semantic HTML on the descriptions in some pages, this fails 1.3.1 Info and Relationships
  • state is not announced when toggling the ‘in this section’ dropdown, this fails 4.1.2 Name Role Value
  • unable to amend select options after navigating forward and backwards with a keyboard, this fails 2.1.1 Keyboard

We intend to fix these items in due course.

Issues with files

  • there may be some files that are not fully accessible

We use Siteimprove tool to monitor any issues regarding accessibility and aim to fix any issues that has been found as soon as possible. We use Adobe Pro's accessibility checker to check the PDF documents and Microsoft Office Accessibility Checker to check any Microsoft Office files. We have also created a guidance for our staff how to make accessible documents, for more information on this, please see the SCULPT for Accessibility page.

Language of the page has not been set

  • the webpages on this site are missing a definition of the natural language; this fails WCAG 2.1 success criterion 3.1.1 (language of page) 

Issues with third-party applications

We use some third-party applications which might not all be fully accessible, but the third-party companies are either in the process of reviewing their applications or have reviewed the applications and given a statement when the issues are going to be fixed.

Disproportionate burden

We have not identified anything that qualifies as disproportionate burden yet, but we are still evaluating our sites and may update this when we identify issues.

Content that’s not within the scope of the accessibility regulations

Regulations do not apply to the following content of a website or mobile application of a public sector body:

Older files

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. 

Online maps

Geographic Information System (GIS) maps, online maps, mapping services are exempt from meeting the accessibility regulations.

Third party content that we have not paid for

Social media buttons such as Tweet/Like

What we’re doing to improve accessibility

We use Silktide to check this site for accessibility issues.

Worcestershire County Council's IT and Digital Team uses WAVE Evaluation Tool to for checking individual web pages, and the Silktide tool for checking and monitoring the whole site's accessibility status. Silktide crawls the site every five days.

See the SCULPT for Accessibility pages for more information on what we are doing to improve accessibility.

Preparation of this accessibility statement

Preparation of this accessibility statement

This statement was prepared on February 2023. It was last reviewed on 5 June 2023.

This website was last tested during June 2023. The test was carried out by using our own testing methods and using third party input.

Manual testing

To do our testing we chose a selection of home pages, document pages, custom pages and a typical form to offer a cross-section of page types within the website.

The pages on this pensions website follow the same template and functions of the Worcestershire County Council website.

We tested the following pages on the main template to ascertain accessibility issues throughout our suite of microsite websites.

Manual user testing reports for the Worcestershire County Council website

Automated testing

Worcestershire County Council do the following regular testing
Subscribe and pay for the Silktide tool for checking and monitoring the whole website's accessibility status regularly to identify any ongoing issues.

Was this page useful
Close