• Home
  • Accessibility Statement

Accessibility statement for Xyla Health & Wellbeing (trading as Pulse Healthcare Ltd)  

The statement covers the Wellbeing Way app . 

The purpose of the app is to help users manage and sustain their weight loss, diabetes and/or health and wellbeing journey through learning, exercise and healthy eating. This app is run by Xyla Health & Wellbeing (Trading under Pulse Healthcare Limited) who are committed to making their apps as accessible as possible for persons with visual, hearing, cognitive and motor impairments. The users can:  

  • change colours, contrast levels and fonts  
  • changing the size of text without any loss of content  
  • navigate the app using a screen reader (including the most recent versions of TalkBack for Android)  

We have also made the application’s text as simple as possible to understand.  

My Computer My Way has advice on making your device easier to use if you have a disability.  

How accessible the application is  

Although we constantly test our online platform to the WCAG 2.1 guidelines to ensure it works on both desktop and mobile devices, currently there are some barriers that may prevent disabled users’ access to the application, such as:  

  • Some elements cannot be focussed or read with a screen reader  
  • Modals do not trap focus  
  • The alternative text for some images is missing or not accurate  
  • Colour contrast issues for text and user interface elements  
  • Some buttons are unlabelled or the label is not appropriate  
     

Feedback and contact information  

If you need information on this application in an alternative format, such as accessible PDF, large print or audio recording, please contact us via email: accessibility@xylahealth.com   

We will consider your request and get back to you within 10 working days.  

Reporting accessibility problems with this application  

We are always looking to improve the accessibility of this application. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact: accessibility@xylahealth.com  

We will consider your request and get back to you within 10 working days.  

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

Contacting us or visiting us in person  

Contact can be made in person at one of the following office addresses however an appointment will be required. Please contact us via  accessibility@xylahealth.com to arrange an appointment:  

Leeds office:  
2nd Floor,   
Fountain House,   
4 S Parade,   
Leeds LS1 5QX  
 
London office:  
9 Appold Street 
London 
EC2A 2AP 

Technical information about this application’s accessibility  

Xyla Health & Wellbeing is committed to making its application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.  

Compliance status  

As of 30th June 2022 This application is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below. We plan to fix all these issues by September 2022. When we publish new content.

  • Text and images that are found together and that serve the same purpose should be combined. This fails under: 1.1.1 Non-text Content (Level A)   
  • Content images don’t have appropriate alternative text. This fails under: 1.1.1 Non-text Content (Level A)   
  • ListView is not used for a list structure (Android only). This fails under: 1.3.1 Info and Relationships (Level A)   
  • Native components aren’t used. This fails under: 1.3.1 Info and Relationships (Level A)   
  • Interactive components are not focusable. This fails under: 2.1.1 Keyboard (Level A)   
  • Modals, dialogs and menus don’t trap focus. This fails under: 2.1.1 Keyboard (Level A), 2.1.2 No Keyboard Trap (Level A) and 2.4.7 Focus Visible (Level AA)   
  • Interactive components are not actionable. This fails under: 2.1.1 Keyboard (Level A) and 4.1.2 Name, Role, Value (Level A)   
  • Content cannot be navigated to using assistive technology. This fails under: 2.1.1 Keyboard (Level A)   
  • Form controls have no accessible label. This fails under: 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A)   
  • Form controls are not read appropriately or are misleading. This fails under: 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A)   
  • Visible labels gain focus independently of inputs. This fails under: 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A)   
  • Errors do not gain focus on submit. This fails under: 3.3.1 Error Identification (Level A) and 3.3.3 Error Suggestion (Level AA)   
  • Dynamic changes or status updates are not being conveyed to assistive technologies. This fails under: 1.3.3 Sensory Characteristics (Level A) and 4.1.3 Status Messages (Level AA)   
  • Information is being conveyed using colour alone. This fails under: 1.4.1 Use of Color (Level A) 
  • Information is presented visually with no alternative. This fails under: 1.3.3 Sensory Characteristics (Level A)   
  • Colour contrast of text is insufficient for users with low vision. This fails under: 1.4.3 Contrast (Minimum) (Level AA)   
  • Colour contrast across borders of interactive elements is insufficient for users with low vision. This fails under: 1.4.11 Non-text Contrast (Level AA)   
  • Colour contrast on UI elements is insufficient for users with low vision. This fails under: 1.4.11 Non-text Contrast (Level AA)   
  • Application content becomes obscured or lost when text size is changed. This fails under: 1.4.4 Resize text (Level AA)   
  • Order is incorrect or illogical. This fails under: 1.3.2 Meaningful Sequence (Level A) and 2.4.3 Focus Order (Level A)  
  • Too much content is grouped. This fails under: 2.4.3 Focus Order (Level A)  
  • Button text is not descriptive of purpose. This fails under: 2.4.4 Link Purpose (In Context) (Level A) and 4.1.2 Name, Role, Value (Level A)   
  • Button text could be improved. This fails under: 2.4.4 Link Purpose (In Context) (Level A)   
  • Button text is missing. This fails under: 2.4.4 Link Purpose (In Context) (Level A) and 4.1.2 Name, Role, Value (Level A)   
  • Link text is not descriptive of the destination page. This fails under: 2.4.4 Link Purpose (In Context) (Level A)   
  • Content read by screen reader doesn’t convey the visual context. This fails under: 1.3.1 Info and Relationships (Level A)   
  • Components are missing appropriate name, role or value. This fails under: 2.4.4 Link Purpose (In Context) (Level A) and 4.1.2 Name, Role, Value (Level A)  
  • Orientation is fixed. This fails under: 1.3.4 Orientation (Level AA)   
  • An accessible label does not match the visual label. This fails under: 2.5.3 Label in Name (Level A)   

 
Disproportionate burden  

We have assessed the cost and effort of fixing the below issues and therefore have concluded the following items fall under the disproportionate burden within the meaning of the accessibility regulations. 

All those being placed in disproportionate burden are in control of a 3rd party supplier of the eLearning software. We do not have access to the elements required to improve those specific areas. 

  • Interactive components are not actionable. 
  • MOB1403-04 – Button text is missing. 
  • Visible labels gain focus independently of inputs. 
  • ListView is not used for a list structure (Android only) 
  • MOB1304-01 & MOB1304-02 – Too much content is grouped. 

 
 
What we are doing to improve accessibility  

We are doing the following to improve the accessibility of our application:  

  • We have conducted an external audit to evaluate the current state of our online platform.  
  • We have had accessibility training to better understand existing accessibility issues that are currently present on our online platform.  
  • We are planning to fix the issues based on the external audit soon.  
     

Preparation of this accessibility statement  

This statement was prepared on 17th November 2021. It was last updated on 30th June 2022.  

This application was last tested on 16th November 2021. The test was carried out by Dig Inclusion Ltd (www.diginclusion.com).   

You can read the full accessibility test report here