Submit a ticket My Tickets
Welcome
Login  Sign up

Accessibility statement for the MySense Dashboard

This accessibility statement applies to the MySense Web Dashboard.


The Web Dashboard is built and run by MySense Ltd. We want as many people as possible to be able to use this product. This means you should be able to:


  • change colours, contrast levels and fonts

  • zoom in up to 300% without the text spilling off the screen

  • navigate most of the web dashboard 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 versions of JAWS, NVDA and VoiceOver)


We’ve also made the web dashboard 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 web dashboard is


We know some parts of this web dashboard are not fully accessible:

  • the text contrast on sub-navigation and table headers is not strong enough 

  • Some of our buttons are not labelled well enough for screen readers

  • Some of our tables are not readable by screen readers.


Feedback and contact information


If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:


Reporting accessibility problems with this website


We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: support@mysense.ai.


Contacting us by phone


We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.

Find out how to contact us here.


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.


Key areas to improve to make our dashboard fully AA compliant:


Improve text contrast on sub-nav (Insights, Wellbeing, Visualise, Info, and History). This currently fails WCAG 2.1 success criterion 1.4.3 (text-contrast).


We plan to improve contrast for all text by September 2022. When we publish new features we’ll make sure our use of text contrast meets accessibility standards.


Improve text contrast on table headers. This currently fails WCAG 2.1 success criterion 1.4.3 (text-contrast).


We plan to improve contrast for all text by September 2022. When we publish new features we’ll make sure our use of text contrast meets accessibility standards.


Relabel (or add appropriate aria tags) to a small subset of buttons to make them screen reader friendly. The lack of this fails WCAG 2.1 success criterion 1.3.1 (sufficient techniques)


We plan to improve labelling and tagging for all buttons by September 2022. When we publish new features we’ll make sure they meet accessibility standards.


Improve the experience of reading our tabular or list data using assistive technology, like a screen reader. The lack of this fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence)


We plan to programmatically fix a correct reading sequence by September 2022. When we publish new features we’ll make sure our use of tables and lists meet accessibility standards.


What we're doing to improve accessibility


Our accessibility roadmap shows how and when we plan to improve accessibility on this website. Please contact us if you would like to obtain a copy.


Preparation of this accessibility statement


This statement was prepared on 5 January 2019. It was last reviewed on 24 January 2022.


The MySense Dashboard was last tested on 18th January. The test was carried out by our QA and UX team.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.