Accessibility statement

Accessibility statement for the Flo corporate website

This is the accessibility statement for the Flo corporate website https://flo.health/, 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 corporate website as accessible as possible.

Compliance status

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

Non-accessible content

We know about the following areas where the website 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

Captions are not available for some of the video content on the website, which means that people unable to hear the audio track have no access to the information it conveys. This fails WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded) (A). We plan to add captions to all videos whose audio track provides information by October 1st, 2024.
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

Not all text that acts as a heading is identified as such in the website code, which prevents screen readers from announcing it as a heading. This fails WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (A). We plan to identify all headings in the website code by October 1st, 2024.
Not all list items are identified as such in the website code, which prevents screen readers from announcing content as a list and informing users of the number of items in it. This fails WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (A). We plan to identify all list items in the website code by October 1st, 2024.
Not all content is coded with the most appropriate mark-up, which can make it difficult for screen reader users to understand its purpose and its relationship with surrounding content. This fails WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (A). We plan to correct the code behind such content by October 1st, 2024.
Some form fields are not associated with their label in the website code, which can make it difficult for screen reader users to understand the information they need to enter. 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 add an accessible name to the code of all form fields by {Date}.
Modal content does not retain screen reader and keyboard focus, which can result in people accidentally leaving the modal content and finding it difficult to move back to it. This fails WCAG 2.1 Success Criteria 1.3.2 Meaningful Sequence (A), 2.4.3 Focus Order (A) and 2.4.7 Focus Visible (AA). We plan to ensure that all modals retain focus by October 1st, 2024.
When new content is displayed screen reader and keyboard focus is not set to it, which can make it difficult for people to find the new content. This fails WCAG 2.1 Success Criteria 1.3.2 Meaningful Sequence (A) and 2.4.3 Focus Order (A). We plan to ensure that focus is set to the beginning of new content by October 1st, 2024.
Content not visible on screen is not always correctly hidden from screen reader and keyboard users, which can be confusing. This fails WCAG 2.1 Success Criteria 1.3.2 Meaningful Sequence (A), 2.4.3 Focus Order (A) and 2.4.7 Focus Visible (AA). We plan to ensure that content not visible on screen is correctly hidden from all website users by October 1st, 2024.

Distinguishable

Some links are identified by colour alone, which can make it difficult for some people to find them. This fails WCAG 2.1 Success Criterion 1.4.1 Use of Color (A). We plan to identify all links via additional visual cues by October 1st, 2024.
Not all text and background colour combinations have sufficient contrast, which can make it difficult for some people to perceive the text. This fails WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum) (AA). We plan to replace the colours that fail the minimum required contrast ratio by October 1st, 2024.
The website contains some images of text, which some people may be unable to perceive. This fails WCAG 2.1 Success Criterion 1.4.5 Images of Text (AA). We plan to replace images of text with real text by October 1st, 2024.
Not all content is available when pages are resized up to 400%, which can make some information unavailable to people relying on a large zoom level. This fails WCAG 2.1 Success Criterion 1.4.10 Reflow (AA). We plan to ensure that all content remains available at all zoom levels by October 1st, 2024.
The colour of some informative icons and form control borders does not have sufficient contrast with adjacent colours, which can make it difficult for some people to perceive the icons and the form controls. This fails WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast (AA). We plan to replace the colours that fail the minimum required contrast ratio by October 1st, 2024.
It is not possible to dismiss pop-up content without moving the cursor away from the item that triggered it, which can be problematic for people using magnification software. This fails WCAG 2.1 Success Criterion 1.4.13 Content on Hover or Focus (AA). We plan to implement a way for people to dismiss pop-up content without having to move the cursor by October 1st, 2024.

Keyboard Accessible

Not all actionable components can be reached and operated with a keyboard, which makes the functionality they provide inaccessible to keyboard users. This fails WCAG 2.1 Success Criterion 2.1.1 Keyboard (A). We plan to implement full keyboard support by October 1st, 2024.

Navigable

Skip links are not available on the website, which prevents keyboard users from easily reaching the main content area of pages. This fails WCAG 2.1 Success Criterion 2.4.1 Bypass Blocks (A). We plan to add skip links by October 1st, 2024.
Not all pages have a title, which can make it difficult for people to recognise their purpose. This fails WCAG 2.1 Success Criterion 2.4.2 Page Titled (A). We plan to ensure that all pages have a title by October 1st, 2024.
Not all text acting as a link clearly and accurately describes its destination content, which means that people (screen reader users especially) will not know what content is loaded until they activate the link. This fails WCAG 2.1 Success Criterion 2.4.4 Link Purpose (In Context) (A). We plan to make all link as descriptive and accurate as possible by October 1st, 2024.
When most focusable items receive the keyboard focus no focus indicator appears, which makes it very difficult or impossible for keyboard users to navigate the website. This fails WCAG 2.1 Success Criterion 2.4.7 Focus Visible (AA). We plan to implement a noticeable focus indicator by October 1st, 2024.

Input Modalities

The accessible name of some actionable components does not match their visible label, which can make it difficult for voice recognition software users to operate them. This fails WCAG 2.1 Success Criterion 2.5.3 Label in Name(A). We plan to ensure that the accessible name of all actionable components matches or contains their visible label by October 1st, 2024.

Input Assistance

Some input fields do not have a visible label, which can make it difficult for people to know what information they need to enter. This fails WCAG 2.1 Success Criterion 3.3.2 Labels or Instructions (A). We plan to give all input fields a visible text label by October 1st, 2024.

Compatible

The website code contains some errors that could impact the way assistive technology interprets and conveys content. This fails WCAG 2.1 Success Criterion 4.1.1 Parsing (A). We plan to rectify such errors by October 1st, 2024.
The code of some components does not include the necessary role and state information, which means that screen reader users may struggle to understand the components purpose and current state. This fails WCAG 2.1 Success Criterion 4.1.2 Name, Role, Value (A). We plan to add accurate role and state information to the code of all actionable components by October 1st, 2024.

Statement preparation

This statement was prepared on 17 March 2022. It was last reviewed on May 12th, 2022.

This website was last tested in March 2022. The test was carried out by TetraLogical.