Skip to main content Skip to footer

Accessibility statement for NHS Business Services Authority blog

This accessibility statement applies to the NHS Business Services Authority blog.

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
  • navigate most of the website using just a keyboard
  • listen to most of the website using the NVDA screen reader

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:

  • the search icon and the breadcrumb page navigation have very low contrast between the foreground and background colours
  • screen readers cannot read some elements on a page correctly, such as the like button, the search button, pop up messages and linked images in the Twitter feed
  • some pages do not have a descriptive page title or do not have a page title at all
  • some pages do not use headings correctly
  • some images or icon links are identical to the text links
  • some links do not make sense when read out of context or describe where they will take the user
  • some link text is not in English
  • the search input bar has prepopulated instruction text in it and it does not have an auto-complete feature
  • search functionality does not work when zoomed in to 400%
  • parts of the Twitter feed are not read meaningfully or correctly to screen readers.
  • the NHSBSA logo is not the correct logo, it does not have alternative text and it does not read as a logo to screen readers
  • some images are missing alternative text
  • you cannot navigate this website using speech recognition software

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: nhsbsa.accessibility@nhs.net

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: nhsbsa.accessibility@nhs.ne

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:  nhsbsa.digital@nhs.net

Technical information about this website’s accessibility

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

There’s a very low contrast between the foreground and background colours on the search icon and the breadcrumb page navigation. Users with low vision may not understand this content. This fails WCAG 2.1 success criterion 1.4.3 Contrast (Minimum).

Screen reader users are not made aware of the pop-up status message when the like button is selected or deselected. This fails WCAG 2.1 success criterion 4.1.3 (Status Messages).

Navigation

Some of our pages do not have a descriptive page title or do not have a page title at all. This makes it hard to navigate the website. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 2.4.2 (Page Titled) and 2.4.6 (Headings and Labels).

Some of our pages do not use headings correctly. This makes it hard for keyboard and screen reader users to navigate the website. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 2.4.1 (Bypass Blocks) and 2.4.6 (Headings and Labels).

The ‘Back to Home’ link and the page numbering links contain adjacent links that go to the same location. This causes additional navigation and repetition for keyboard and assistive technology users. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose In Context).

The ‘like button’ is not read correctly by a screen reader and it does not focus correctly when navigating using a keyboard. This makes navigation hard for keyboard and screen reader users. This fails WCAG 2.1 success criterion 1.3.6 (Identify Purpose) and 2.1 (Keyboard Accessible).

Some link text does not make sense when read out of context or describe where a link will take the user. For example, ‘Read more’ links. This may cause confusion and make navigation hard for all users, especially keyboard and screen reader users. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose In Context) and 2.4.9 (Link Purpose Link Only).

Some link text is not in English and cannot be read by a screen reader. This may cause confusion and make navigation hard for all users. This fails WCAG 2.1 success criterion 1.3.6 (Identify Purpose), 2.1 (Keyboard Accessible), 2.4.4 (Link Purpose In Context) and 2.4.9 (Link Purpose Link Only).

It’s not possible to navigate all pages on this website using speech recognition software. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value) and 4.1.3 (Status Messages).

Search

The search input bar has instruction text in it. This can be confusing for assistive technology users. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).

The search input bar does not have an auto-complete feature. This makes it harder for users to fill out the field, especially for users with cognitive disabilities. This fails WCAG 2.1 success criterion 1.3.5 (Identify Input Purpose).

The search button does not correctly describe its purpose to screen readers. This can be confusing for screen reader users. This fails WCAG 2.1 success criterion WCAG 2.1 success criterion 1.3.6 (Identify Purpose) and 2.1 (Keyboard Accessible).

The search function does not work correctly when zoomed in to 400%. This makes it harder for users with low version to search for content on the website. This fails WCAG 2.1 success criterion 1.4.10 (Reflow).

Twitter feed

Parts of the Twitter feed are not read meaningfully or correctly to screen readers such as:

  • the ‘View this image on Twitter’ alternative text on informative images
  • hashtags in posts are read as ‘number’
  • the ‘Embed’ button
  • you cannot logically navigate to the new posts which are generated after selecting the ‘load more tweets’ button

These make navigation hard for screen reader users. This fails WCAG 2.1 success criterion 1.1.1 (Non text Content), 1.3.6 (Identify Purpose), 2.1 (Keyboard Accessible), 2.4.4 (Link Purpose In Context) and 2.4.9 (Link Purpose Link Only).

Images

The NHSBSA logo is not the correct logo. It also does not have alternative text and not is not read as a logo to screen readers. This makes it hard for users to identify our website. This fails WCAG 2.1 success criterion 1.1.1 (Non text Content) and 1.4.5 (Images of Text).

Some informative images are missing alternative text or do not have meaningful alternative text. Assistive technology users will not understand these images. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).

Some decorative images do not have a null text alternative. This means the images will not be ignored by screen readers and users may find the content hard to understand. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).

Some images contain text which will not be read by screen readers. This fails WCAG 2.1 success criterion 1.4.9 (Images of Text).

We plan to fix all these accessibility issues by September 2021. When we publish new blog content we’ll make sure it meets accessibility standards.

Disproportionate burden

Not applicable

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

PDFs and other documents

Not applicable

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

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 six 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 18 September 2020. It was last reviewed on 18 September 2020.

This website was last tested on 18 September 2020. The test was carried out by the Digital and Online Team.

We tested a sample 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) and standards checklists.

These checklists contain standards that have been compiled using WCAG, NHS service manual and GDS guidance.