Florence 2.0 Accessibility Statement for

florence.uk.net

Accessibility statement for florence.uk.net

This accessibility statement applies to the web-based application Florence, a persona based digital tool to support patient engagement and extend the reach of clinicians using intelligent text messages.

This website is run by Mediaburst Ltd. We want as many people as possible to be able to use this website. For example, that means you should be able to:

·        zoom in up to 200% without the text spilling off the screen

·        navigate most of the website using just a keyboard

·        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 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:

·        zoom in above 200% will cause the text to spill off the screen

·        the text will not reflow in a single column when you change the size of the browser window

·        you cannot modify the line height or spacing of text

·        some of our online forms are difficult to navigate using just a keyboard

·        you cannot skip to the main content when using a screen reader

·        there’s a limit to how far you can magnify the map on our ‘contact us’ page

      

   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:

email: help@florence.uk.net

We’ll consider your request and get back to you in 10 working days.

 

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of the Florence website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, email us at help@florence.uk.net  and our support team will investigate further.

 

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 by phone or visiting us in person

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

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Find out how to contact us getflorence.net

Technical information about this website’s accessibility

Mediaburst Ltd 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

 

1. Perceivable
  • 1.4 Distinguishable:
    • 1.4.3 Contrast (Minimum): The visual presentation of text has a contrast ration of 2.89:1 for the lowest contrast text.
    • 1.4.10: Reflow: Vertical scrolling in two directions is required for > 200% zoom.

.

2. Operable
  • 2.4 Navigable
    • 2.4.3 Focus Order: In some cases, the focus order does not that preserves meaning and operability of the intended workflow.
    • 2.4.5 Multiple ways: Some content is only accessible in one way, for example, the Patients screen is not accessible from Groups, and Groups not accessible from Patient.
  • 2.5 Input Modalities
    • 2.5.3 Label in Name: In some cases, the name does not exist or does not contain the text that is presented visually.
 
3. Understandable
  • 1 Readable
    • 1.2 Language of Page: No language attribute on HTML elements exist.
 
4. Robust
  • 1 Compatible
    • 1.2 Name, Role, Value: It cannot be guaranteed that:
      • the name and role can be programmatically determined;
      • states, properties, and values that can be set by the user can be programmatically set;
      • notification of changes to these items is available to user agents, including assistive technologies

         

Non-compliance with the accessibility regulations

WCAG 2.1 AA success criteria the problem fails on items listed in the ‘Non-accessible Content’ section

The non-compliant issues are resolved in the next generation Florence application (Flo-3.0).  An upgrade programme is in progress and clients will be offered upgrade to Flo-3.0

 

Navigation and accessing information

WCAG 2.1 AA success criteria the problem fails on items listed in the ‘Non-accessible Content’ section

The non-compliant issues are resolved in the next generation Florence application (Flo-3.0).  An upgrade programme is in progress and clients will be offered upgrade to Flo-3.0

 

Interactive tools and transactions

WCAG 2.1 AA success criteria the problem fails on items listed in the ‘Non-accessible Content’ section

The non-compliant issues are resolved in the next generation Florence application (Flo-3.0).  An upgrade programme is in progress and clients will be offered upgrade to Flo-3.0

 

PDFs and other documents

Some of our PDFs and Excel documents are essential to providing our services. For example, weekly and monthly reports are provided in either PDF or Excel. With Flo-3.0, we will provide with accessible HTML pages.

Live video

There is no live video content on the Florence application.

What we’re doing to improve accessibility

Accessibility issues with the Florence application are resolved in Flo-3.0.

Preparation of this accessibility statement

This statement was prepared on 1st September 2021. It was last reviewed on 1st September 2021.

This website was last tested on 16th August 2021. The test was carried out by internally by the CTO.

We used this approach to deciding on a sample of pages to test: The application has a low number of pages which enables all pages to be teste.