1. Accessibility statement for the Flo iOS app

Accessibility statement

This is the accessibility statement for the Flo iOS app, run by Flo.

Reporting problems

If you find any problems not mentioned in this statement, or if you think we are not meeting your accessibility requirements, please let us know by email: info@flo.health

Technical information

Flo is committed to making its app as accessible as possible.

Compliance status

This app is not compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard, for the reasons shown below.

Non-accessible content

We know about the following areas where the app does not meet accessibility standards and we have a plan to address each of them.

Text Alternatives
  • Some images are not associated with a text description, which makes the information and functionality they provide unavailable to screen reader users. This fails WCAG 2.1 Success Criteria 1.1.1 Non-text Content (A) and 4.1.2 Name, Role, Value (A). We plan to add equivalent text descriptions by October, 1st, 2024.
Time-based Media
  • The audio track of videos does not contain all the information conveyed visually, which means that people unable to see the videos have no access to such information. This fails WCAG 2.1 Success Criteria 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) and 1.2.5 Audio Description (Prerecorded) (AA). We plan to add any missing information to the audio track of all videos by October, 1st, 2024.
Adaptable
  • Headings are not identified as such in the app code, which prevents screen readers from announcing them as headings. This fails WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (A). We plan to identify all headings in the app code by October, 1st, 2024.
  • Labels and error messages are not associated with the related form controls in the app code, which can make it difficult for blind people to fill in forms. This fails WCAG 2.1 Success Criteria 1.3.1 Info and Relationships (A) and 4.1.2 Name, Role, Value (A). We plan to associate each label and error message with the related control in the app code by October, 1st, 2024.
  • Not all content is exposed to screen readers in a logical order, which can make it difficult for blind people to understand the information in the app. There are significant pieces of content that are not exposed which makes it impossible for screen reader users to access this content. This fails WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (A). We plan to fix the order of content in the app code by October, 1st, 2024.
  • The app does not support landscape mode, as such it is inaccessible to anyone who uses mobile devices in landscape mode. This fails WCAG 2.1 Success Criterion 1.3.4 Orientation (AA). We plan to implement support for both portrait and landscape orientations by October, 1st, 2024.
Distinguishable
  • In some instances, active or selected items are identified by colour alone, which can make it difficult for some people to distinguish them. This fails WCAG 2.1 Success Criterion 1.4.1 Use of Color (A). We plan to identify active / selected items in a way that does not rely on colour perception by October, 1st, 2024.
  • The contrast ratio between some text and background colour combinations, and between the colour of informative images and their adjacent colours, is lower than the minimum required by WCAG. As a result, some people may find it difficult to read text or perceive icons and form controls. This fails WCAG 2.1 Success Criteria 1.4.3 Contrast (Minimum) (AA) and 1.4.11 Non-text Contrast (AA). We plan to increase the contrast ratio between text and background colours, and between icons and adjacent colours, by October, 1st, 2024.
  • It is not possible to change the size of text content, which makes the app inaccessible to people unable to read content in its default size. This fails WCAG 2.1 Success Criterion 1.4.4 Resize Text (AA). We plan to support text resizing by October, 1st, 2024.
Keyboard Accessible
  • Many actionable components cannot be reached and operated using an external keyboard (or similar input device), which makes some of the functionality in the app unavailable to people unable to use touch screen gestures. This includes both keyboard and screen reader users. This fails WCAG 2.1 Success Criteria 2.1.1 Keyboard (A) and 2.4.3 Focus Order (A). We plan to implement full keyboard support by October, 1st, 2024.
Enough Time
  • Some screens include carousels that start playing automatically and cannot be paused, which can be problematic for a number of people. This fails WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide (A). We plan to add an option for people to pause carousels by October, 1st, 2024.
Navigable
  • In several instances, interactive content is not in the keyboard focus order and therefore cannot be accessed by keyboard users. In some cases this also affects screen reader users. This fails WCAG 2.1 Success Criterion 2.4.3 Focus Order (A) and 2.4.7 Focus Visible (AA). We plan to ensure that the focus order is correct by October, 1st, 2024.
  • In one instance, content outside of the application viewport is focusable but not pulled into view when using a screen reader; while the focus outline is visible the content is not visible and therefore liable to cause confusion for sighted screen reader users. This fails WCAG 2.1 Success Criterion 2.4.7 Focus Visible (AA). We plan to ensure that a focus indicator is visible at all times by October, 1st, 2024.
Input Assistance
  • Input fields that are part of the Sign Up and Log In screens have no visible label, which can make it difficult for people to remember the information they are required to enter. This fails WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions (A). We plan to add visible text labels across the app by October, 1st, 2024.
Compatible
  • Accurate name, role and state information is missing from the code of many actionable components, which may prevent screen reader users from understanding their purpose. This fails WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value (A). We plan to add accurate name, role and state information to the code of all actionable components by October, 1st, 2024.
  • Many sections of content are not exposed to screen readers, which means that blind and low vision people have no access to them. This fails WCAG 2.1 Success Criteria 4.1.2 Name, Role, Value (A), 1.3.1 Info and Relationships (A), 1.3.2 Meaningful Sequence (A) and 2.5.3 Label in Name (A). We plan to ensure that all content is exposed to screen readers by October, 1st, 2024.

Statement preparation

This statement was prepared on 15 October 2021. It was last reviewed on October, 21st, 2021.

This app was last tested in September 2021. The test was carried out by TetraLogical.

© TetraLogical Ltd. All Rights Reserved.