Accessibility statement for Catalyst

This accessibility statement applies to Catalyst. It is an online application which allows users to access prescribing data.

This website is run by the NHS Business Services Authority (NHSBSA). 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 and contrast levels using browser or device settings
navigate most of the website using just a keyboard or speech recognition software (Dragon)
listen to most of the website using a screen reader (including the most recent version of NVDA)
access the website on desktop and mobile devices

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, as:

on many pages form labels are empty or missing
on some pages contrast is low
there are some instances of redundant, repetitive or empty alternative text
no pages have an appropriate heading structure
the purpose of some links cannot be determined from the text alone
the use of very small, close together or rotated text is sometimes required for charts
some pages have a device-dependent event handler
some pages have duplicate or blank titles, which may make it difficult for users to orientate themselves and find the right content
layout tables are used on most pages
there's a lack of page regions and field sets on several pages
main content and footer sections are incorrectly assigned or missing
all pages contain Accessible Rich Internet Applications (ARIA) that have not been applied correctly
there are no script elements present
there are inline frame elements present
there are language issues in the background of some pages
some pages and forms are difficult to navigate using only a keyboard or speech recognition software
screen readers cannot always skip to the main content
there’s a limit to how far you can magnify pages without content spilling off the screen
errors are often unclear and not always read out by a screen reader
some URLs linked on pages have unnecessary words
some pages have inconsistent tab index properties
filter selections are not always carried forward between pages of the same dashboard
on some pages additional information is provided when certain content is hovered over
when CSS styling is disabled, some hidden elements are visible and overlap
none of the pages work when JavaScript is disabled
the target size of some objects is too small
there are some occasions where content is obscured and is not perceivable to users in ways that are independent of sight and vision
screen readers do not always announce time out warnings

How to request content in an accessible format

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

Email: accessibility@nhsbsa.nhs.uk

We’ll consider your request and get back to you in 5 working days.

This email address is only for accessibility queries. It is not for technical queries or IT problems. If you have a query that is not about accessibility, go to the ‘Contact us’ section of this page.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we’re not meeting accessibility requirements, you can contact us by:

Email: accessibility@nhsbsa.nhs.uk

Contact us

For all queries not accessibility related, you can contact us by:

Email: DataServicesSupport@nhsbsa.nhs.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).

Technical information about this website’s accessibility

The NHSBSA 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 listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

On many pages form labels are empty or missing. This fails WCAG 2.2 criterion 2.4.6 (Headings and Labels).

On some pages contrast is low, which can make it difficult for some people to see. This fails WCAG 2.2 criteria 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text Contrast).

There are some instances of redundant, repetitive or empty alternative text. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text).

No pages have an appropriate heading structure, making them difficult to navigate when using a screen reader. This fails WCAG 2.2 criteria 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels) and 3.3.2 (Labels or Instructions).

The purpose of some links like 'create’ or ‘open’ cannot be determined from the text alone. This fails WCAG 2.2 success criteria 2.4.4 (Link Purpose (In Context)) and 2.4.9 (Link Purpose (Link Only)).

The use of very small, close together or rotated text is sometimes required for charts, but this can make it difficult for people with low vision, dyslexia or dyscalculia to understand. This fails WCAG 2.2 criteria 1.4.3 (Contrast (Minimum)), 1.4.4 (Resize Text), and 1.4.12 (Text Spacing).

Some pages have a device-dependent event handler that may not be accessible. This fails WCAG 2.2 criteria 2.1.1 (Keyboard), 1.4.13 (Content on Hover or Focus) and 4.1.3 (Status Messages).

Some pages have duplicate or blank titles, which may make it difficult for users to orientate themselves and find the right content. This fails WCAG 2.2 success criteria 2.4.2 (Page Titled), 2.4.5 (Multiple Ways) and 2.4.6 (Headings and Labels).

Most pages contain layout tables to position content visually which can cause reading and navigation issues especially for people using screen readers. This fails WCAG 2.2 success criteria 1.3.1 (Info and Relationships), 1.3.2 (Meaningful Sequence), 3.2.3 (Consistent Navigation) and 1.4.10 (Reflow).

There are a lack of page regions and field sets on several pages. This fails WCAG 2.2 success criteria 1.3.5 (Identify Input Purpose), 1.3.6 (Identify Purpose) and 3.3.2 (Labels or Instructions).

Main content and footer sections are incorrectly assigned or missing. This fails WCAG 2.2 success criteria 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), 2.4.10 (Section Headings) and 3.3.2 (Labels or Instructions).

All pages contain Accessible Rich Internet Applications (ARIA) that have not been applied correctly which makes using assistive technology difficult. This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels) and 4.1.2 (Name, Role, Value).

There are no script elements present. This fails WCAG 2.2 success criteria 2.4.3 (Focus Order) and 4.1 (Compatible).

There are inline frame elements present. This fail WCAG 2.2 success criteria 2.4.2 (Page Titled), 2.4.6 (Headings and Labels) and 2.4.10 (Section Headings).

There are language issues in the background of some pages. This fails WCAG 2.2 success criteria 3.1.1 (Language of Page) and 3.1.2 (Language of Parts).

There are some instances where the pages and forms are difficult to navigate using only a keyboard or speech recognition software. This fails WCAG 2.2 success criteria 1.3.5 (Identify Input Purpose), 2.1.1 (Keyboard), 2.1.2 (No Keyboard Trap), 2.4.1 (Bypass Blocks), 2.4.3 (Focus Order), 2.4.4 (Link Purpose (In Context)), 2.4.7 (Focus Visible), and 2.4.11 (Focus Not Obscured (Minimum)).

Screen reader users cannot always skip to the main content. This fails WCAG 2.2 success criteria 2.4.1 (Bypass Blocks), 3.2.3 (Consistent Navigation), and 3.2.4 (Consistent Identification).

There’s a limit to how far you can magnify our pages without content spilling off the screen. This fails WCAG 2.2 success criteria 1.3.4 (Orientation), 1.4.4 (Resize Text) and 1.4.10 (Reflow).

Errors are often unclear and not always read out by a screen reader. This fails WCAG 2.2 criteria 3.3.1 (Error Identification), 3.3.3 (Error Suggestion), 3.3.5 (Help) and 4.1.3 (Status Messages).

Some URLs contain unnecessary words. WCAG 2.2 requires that content must be readable and understandable. This fails WCAG 2.2 success criterion 3.1 (Readable).

Some pages have inconsistent tab index properties. This fails WCAG 2.2 success criteria 2.4.3 (Focus Order), 3.2.3 (Consistent Navigation) and 2.1.2 (No Keyboard Trap)

Some filter selections are not always carried forward between pages of the same dashboard. This fails WCAG 2.2 success criterion 3.3.7 (Redundant Entry).

Some pages have additional information provided when certain content is hovered over. This fails WCAG 2.2 success criteria 1.4.13 (Content on Hover or Focus), 3.2.3 (Consistent Navigation), and 3.2.4 (Consistent Identification).

When CSS styling is disabled, there are some instances where hidden elements become visible and overlap. This fails WCAG 2.2 success criteria 1.4.3 (Contrast (Minimum)),1.4.6 (Contrast (Enhanced)), 2.4.11 (Focus Not Obscured (Minimum)), 2.4.12 (Focus Not Obscured (Enhanced)), and 2.4.13 (Focus Appearance).

None of the pages works when JavaScript is disabled. This fails WCAG 2.2 criteria 1.3 (Adaptable), 2.0 (Operable), and 4.1 (Compatible).

The size of some objects is too small to target with a pointer device. This fails WCAG 2.2 criteria 1.4.11 (Non-text Contrast), 2.5.5 (Target Size (Enhanced)), and 2.5.8 (Target Size (Minimum)).

There are some occasions where content is obscured and is not perceivable to users in ways that are independent of sight and vision. This fails WCAG 2.2 success criteria 1.4.3 (Contrast (Minimum)), 2.4.11 (Focus Not Obscured (Minimum)), 2.4.12 (Focus Not Obscured (Enhanced)).

Screen readers do not always announce time out warnings. This will mean that the user will not be able to extend or cancel the timeout. This fails WCAG 2.2 success criteria 2.2.1 (Timing Adjustable), 2.2.4 (Interruptions), 2.2.5 (Re-authenticating) and 2.2.6 (Timeouts).

We plan to fix these issues. When we publish new content, we’ll make sure it meets accessibility standards.

What we’re doing to improve accessibility

We’re committed to making sure this website is compliant to WCAG 2.2 ‘AA’ standard.

Our accessibility compliance statement will be reviewed regularly. Every newly released website will be designed, built, and tested to meet ‘AA’ standards by default

Preparation of this accessibility statement

This statement was originally prepared on 15 September 2020. It was last reviewed on 7 October 2024.

This website was last tested on 3 October 2024 against the WCAG 2.2 AA standard.

The test was carried out by the NHSBSA test and development teams. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.

We tested all the website screens to meet ‘AA’ WCAG 2.2 standards, using manual and automated tests.

We run each webpage through automated Wave, Lighthouse and Axe accessibility tools then manually test with screen readers (NVDA) and standards checklists.

We run representative user journey tests through speech recognition software (Dragon).

These checklists contain standards that have been compiled using WCAG, the NHS service manual and the Government Digital Service (GDS) guidance. 