Skip to main content Skip to footer

Accessibility statement for MyFunding

This accessibility statement applies to MyFunding.

This website is run by the NHS Business Services Authority. 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, contrast levels and fonts
  • 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 most recent version of NVDA)

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:

  • when the user triggers a field error, they are sometimes presented with error text that does not correctly describe the issue
  • some error summary links do not correctly place focus on the field
  • some buttons are not correctly marked as a button which could make interactions difficult for Dragon voice recognition users
  • some Accessible Rich Internet Applications (ARIA) attributes do not have valid values or do not match their roles, some ARIA IDs are not unique and some ID attributes are not unique, meaning users could face difficulty understanding some fields
  • some links are missing visually hidden text which may cause confusion for screen reader users and difficulty in navigating for Dragon voice recognition users
  • screen readers will sometimes read out change links with visually hidden text as one continuous word
  • there are some orphaned form labels which do not correctly label fields
  • links which open a file do not include the file type in the link text, meaning users may not be aware of what will happen when selecting the links
  • all pages are missing the service name from the page titles which could confuse some users
  • users are not warned of timeouts or given the opportunity to stop an incoming timeout with a popup

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 inbox is only for accessibility queries. This inbox 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

This inbox is only for accessibility queries. This inbox 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.

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

Contact us

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

Email: swbteam@nhsbsa.nhs.uk

Technical information about this website’s accessibility

The NHS Business Services Authority 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 below.

Non-accessible content

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

Non-compliance with the accessibility regulations

All pages are missing the service name which could confuse users. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled). 

When the user triggers a field error, they are sometimes presented with error text that does not correctly describe the issue. This fails WCAG 2.1 success criterion 3.3.3 (Error Suggestion). 

Some error summary links do not correctly place focus on the field. This fails WCAG 2.1 success criterion 3.3.1 (Error Identification) and 3.3.3 (Error Suggestion). 

Some buttons are not correctly marked as a button which could make interactions difficult for Dragon voice recognition users. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). 

Some Accessible Rich Internet Applications (ARIA) attributes do not have valid values or do not match their roles, some ARIA IDs are not unique and some ID attributes are not unique, meaning users could face difficulty understanding some fields. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). 

Some links are missing visually hidden text which may cause confusion for screen reader users and difficulty in navigating for Dragon voice recognition users. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)). 

Screen readers will sometimes read out change links with visually hidden text as one continuous word. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)).

There are some orphaned form labels which do not correctly label fields. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).

Links which open a file do not include the file type in the link text, meaning users may not be aware of what will happen when selecting the links. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)).

All pages are missing the service name from the page titles which could confuse some users. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).

Users are not warned of timeouts or given the opportunity to stop an incoming timeout with a popup. This fails WCAG 2.1 success criterion 2.2.6 (Timeouts).

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

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

Dragon voice recognition software

Due to an issue with Dragon and some older versions of this assistive technology, users will have difficulties interacting with certain fields. We advise Dragon users to use the mouse grid feature to interact with these features. 

What we’re doing to improve accessibility

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

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

Preparation of this accessibility statement

This statement was prepared on 17 September 2019. It was last reviewed on 19 September 2023.

This website was last tested on 24 July 2023. The test was carried out by the NHSBSA test and development teams.

We tested all of the website screens to meet ‘AA’ WCAG 2.1 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 or VoiceOver) and standards checklists.

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

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