Accessibility statement

Updated July 2024

We want the service to be easy for all patients and care providers to use, even if they have special requirements for using browsers and apps. This statement explains how we try to make the service easy to use, and what you can do if you have any difficulties.

Compliance AA
Patient App

Our iOS and Android applications conform to WCAG 2.2 Level AA.

Compliance A
Professional App

Partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard, due to the non-compliances listed below.

Compliance A
Corporate Website

Partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard, due to the non-compliances listed below.

Our mobile applications are fully compliant with the WCAG 2.2 AA standard.

When accessing the service via the you should be able to:

  • change colours, contrast levels and fonts using browser functionality
  • zoom in up to 400 per cent 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
  • interact with most of the website using a screen reader (including recent versions of JAWS, NVDA and VoiceOver)

We know some parts of this website are not fully accessible:

  • our chart tools, which are difficult to use with screen reader software
  • some online forms that are not easy for screen readers to navigate
  • some links and images that are not self-explanatory to screen reader users
  • some elements have an illogical focus order when you use a keyboard to navigate
Perceivable  
Identify Input Purpose The purpose of each input field collecting information about the user cannot be programmatically determined.

 

Operable
  
Label in Name
 Not all elements have their name included.
Focus Visible
 Not all keyboard operable user interface elements have a key keyboard focus inducator
Focus Order
 Focusable components do not receive focus in an order that preserves meaning and operability.
Bypass Blocks There are no bypass blocks available to bypass repeated content.

 

Understandable
  
Language of Parts
 The human language of each passage or phrase in the content cannot be programmatically determined in all cases.
Language of Page
 The default human language of each Web page cannot be programmatically determined.

 

Robust
  
Status Messages
 In content implemented using markup languages, status messages cannot be programmatically determined.
Name, Role, Value
 There are pages where the name and role cannot be programmatically determined.

When accessing the service via the you should be able to:

  • change colours, contrast levels and fonts using browser functionality
  • zoom in up to 400 per cent 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
  • interact with most of the website using a screen reader (including recent versions of JAWS, NVDA and VoiceOver)

List of non conformity issues

Adapting the content to your specific needs

If you have a disability or other specific access need, you can adapt the content of the Service using your device to make it easier for you. AbilityNet has advice to help you make your device easier to use.

 

Reporting accessibility problems in the Luscii

We are always looking to improve the accessibility of this Service. If you have any problems in making the service adapt to your needs, or if you think we're not meeting accessibility requirements, then please email support@luscii.com to report the problem.

Enforcement procedure

If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS),

The Equality and Human Rights Commission (EHRC) is responsible for making sure that websites provided by public bodies meet the WCAG accessibility standards.

The content that is not accessible is listed below together with an explanation and reference to the relevant WCAG section.

What we’re doing to improve accessibility

We have published tools and guidance on accessibility in the Luscii Design System based on extensive testing. The service manual helps our teams build products and services to meet the same accessibility standards.

At Luscii, creating an accessible service is a team effort. We want our teams to make accessible services by:

  • considering accessibility at the start of their project, and throughout
  • making accessibility the whole team's responsibility
  • researching with disabled users
  • using a library of accessible components and patterns
  • carrying out regular accessibility audits and testing
  • designing and building to level AA of WCAG 2.2

We are making sure that accessibility issues highlighted in this statement are being prioritised and fixed. Measures include:

  • all content to be made AA standard when they are reviewed after 1 March 2025
  • ongoing improvements to the Luscii design system with a focus on accessibility
  • prioritising accessibility remedial work in all new development and improvement projects
  • working with suppliers to improve the accessibility of their products

Preparation of this accessibility statement

This statement was updated in July 2024.

In July 2024, our Design System Team conducted an expert evaluation of over 30 pages, assessing them against all Level A and AA success criteria of WCAG 2.2. The content selection ensured a comprehensive representation of different pages, templates, components, and key user journeys. This evaluation was carried out separately for the mobile applications, professional dashboard, and corporate website.

We are committed to regularly reviewing the accessibility of this website. We will continue to update this accessibility statement to reflect any relevant changes.