Accessibility statement

Updated November 2023

This accessibility statement applies to the remote patient monitoring services provided by Luscii.

User experience and accessible software for all patients and healthcare professionals is a key priority for Luscii, also when users have special requirements for using browsers and apps. This statement explains how we make the service easy to use, and what accessibility changes can be done by users having difficulty accessing digital technology.

Accessing via the Luscii App (patients)

Patients access Luscii using a special app built for iOS and Android devices. Our apps are fully compliant with the accessibility requirements since patients can use the built-in accessibility settings on their phone to adjust the way the app works in order to make it suit to their needs. This video illustrates how a patient with a visual impairment uses the Luscii app to stay connected to his care team ensuring to leave no one behind.

These links explain how the accessibility settings can be adjusted:

- iOS accessibility settings

- Android accessibility settings

Accessing via the Luscii website (healthcare staff)

When accessing Luscii via the website, 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)

How accessible this website is

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

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.

 

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard, due to the non-compliances listed below.

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.

 

How we test the Luscii Platform

The Luscii Platform was last tested on 1 October 2023 and was checked for compliance with AA level of the Web Content Accessibility Guidelines (WCAG) version 2.1.

Non-accessible content

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

Non-compliance with the accessibility regulations

Perceivable  
Non-text Contrast Low contrast focus indication style on: links, buttons, form fields, and search components
Identify Input Purpose The purpose of each input field collecting information about the user cannot be programmatically determined.
Contrast The visual presentation of text and images of text does. not have a contrast ratio of at least 4.5:1 in all cases
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.

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 and our teams focus on an accessible service 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.1

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 2024
  • 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 November 2023.

This website was tested in October 2023 by our Design System Team who performed an expert evaluation of over 30 pages against all level A and AA success criteria of WCAG 2.1. Content was selected to make sure a good representation of different pages, templates and components were tested as well as key content and user journeys.

This website's accessibility will be reviewed on a regular basis. We will continue to update this accessibility statement with any relevant changes.