Accessibility statement for The Civil Service Pension Scheme (CSPS)

This accessibility statement applies to the Civil Service Pension Scheme (CSPS).

This portal has been developed by Capita plc. It is important that the portal is accessible and meets the legal requirement for businesses and organisations to make reasonable adjustments to provide accessible services and information. It is recommended that this website be used on a desktop device and a modern browser such as Chrome, Firefox, Safari, or Edge.

How you should be able to use this portal

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • We also used findings from our own testing when preparing this accessibility statement.
  • Zoom in up to 400% 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 latest 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.

How accessible this website is

We know some parts of this website are not fully accessible and we are working to improve this. Our current known issues are detailed in the 'Non-compliance with the accessibility regulations' section.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact us.

Reporting accessibility problems with this website

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

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

Technical information about this website's accessibility

CSPS 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.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The following is a list of known issues and non-compliances with the accessibility regulations. These issues have been identified and are currently being tracked.

Non-compliance with the accessibility regulations

  1. Interactive elements lack a clear and consistent visual focus indicator, making keyboard navigation difficult. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
  2. Activating navigational tabs (e.g. in the Mailbox) incorrectly triggers a full page reload, relationship between tab content is missing. This fails WCAG 2.1 success criterion 3.2.2 (On Input, Info and Relationships).
  3. The 'Back' navigation link in some instances is not keyboard operable (cannot be activated using the Enter key). This fails WCAG 2.1 success criterion 2.1.1 (Keyboard).
  4. The "Continue" or "Submit" button on some form pages are visually and programmatically disabled. This fails WCAG 2.1 success criterion 3.3.2 (Focus Order, Labels or Instructions, Error Suggestion).
  5. The mobile menu difficult to navigate and incorrect semantics: Keyboard focus is not logical, it’s not trapped and allows users to navigate to hidden content underneath the menu, when closed you can still navigate through the options and still navigable when hidden. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order, Keyboard, Focus Visible, Info and Relationship).
  6. Page layouts use tables with role="presentation" for visual arrangement, compromising the logical reading order and reading of additional content that’s not intended. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  7. The heading hierarchy is inconsistent (e.g. H2 followed by H4). This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  8. The heading hierarchy is inconsistent (e.g. H2 followed by H4). This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  9. Static information in some areas is incorrectly announced as disabled form inputs. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  10. Card components used for navigation or content grouping lack semantic structure, confusing screen reader flow. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships, Link Purpose (In Context)).
  11. Data tables are missing an accessible caption that describes the purpose of the table. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  12. The "Sort By" component uses an inconsistent and misleading accessible label. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name).
  13. The file upload button is implemented using a non-semantic element, failing to communicate its button role. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
  14. Non-urgent success or status messages use role="alert" inappropriately, interrupting screen reader users. This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).
  15. Dynamic status updates for file uploads (e.g., "Uploading...", "Complete") are not announced to screen readers. This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).
  16. Dismissal buttons for notification banners are either missing or lack a clear, accessible label. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name).
  17. Download links for publications (e.g., PDFs) do not provide context regarding the file type or size. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose).
  18. ARIA alert roles are incorrectly used for non-critical, non-time-sensitive information. This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).

Some documents are in non-HTML formats, for example PDF. They are not accessible in a number of ways including missing text alternatives and missing document structure.

Disproportionate burden

We’ve assessed the cost of fixing the accessibility problem with the JavaScript dependency issue. We believe that doing so would be a disproportionate burden within the meaning of the accessibility regulations.

The entire service is built on Microsoft Dynamics 365 Power Pages, which is a platform fundamentally dependent on client-side JavaScript for rendering, core navigation, and data interaction. Removing this dependency would require a complete platform migration away from the Power Pages architecture. We’ve assessed the cost and time of fixing the issue. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.

What we’re doing to improve accessibility

We are working alongside CSPS to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.

Preparation of this accessibility statement

This statement was prepared on 19 November 2025. It was last reviewed on 20 November 2025.

This website audit is in progress and is tested against the WCAG 2.2 AA standard. This test of a representative sample of pages is carried out by Internal QA Team and ShawTrust Auditor.

We also used findings from our own testing when preparing this accessibility statement.