Tessello Learning Platform

Accessibility Statement

Tessello learning platform accessibility conformance statement

The platform was checked for adherence to the internationally recognised Web Content Accessibility Guidelines (WCAG) 2.2 AA. Accessibility testing was carried out on a Windows 11 machine with the latest version of Windows Edge and JAWS 2023. Mobile testing was carried out using an iPhone SE running iOS 17.3 with VoiceOver and a Google Pixel 4a running Android 13 with TalkBack.

AbilityNet confirms that the platform tested is partially compliant with both the level A and AA guidelines as specified in the Web Content Accessibility Guidelines (http://www.w3.org/TR/WCAG/).

The platform aims to reach a high level of accessibility by following conventions and standards. The platform also aims to obtain third-party confirmation as being largely compliant with both the level A and AA guidelines as specified in the Web Content Accessibility Guidelines and, as such, will provide most users with an accessible experience.

It’s important to note that a third-party accessibility audit is currently underway. While this third party has identified the outstanding issues below, they are being actively worked on, and we aim to remediate all outstanding issues. This document will be updated as and when these issues are confirmed as fixed by the third-party auditors.

Outstanding Issues

The following identified issues remain outstanding:

High Priority

Interactive elements do not receive keyboard focus. Links on the “Communities” and “Search Results” pages cannot be controlled using a keyboard.

Medium Priority

Regular text does not have sufficient contrast on hover. There is regular text that does not meet the contrast ratio when receiving mouse hover on the “Communities” and “Search Results” pages.

Dynamic updates are not programmatically determined. There are dynamic updates that are not programmatically determined as such on the “Multi-Factor Authentication Login” page.

Decorative image has redundant text alternative. There are decorative images with redundant text alternatives on the “Communities” page.

Informative image has inappropriate text alternative. There are informative images with inappropriate text alternatives on the “Registration” pages and the “Skills Development” page.

Custom focus indication fails contrast. There is a custom focus indication that does not meet the contrast ratio on the “Profile Settings” page.

Text spacing causes content or functionality to be lost. Adjusting the text properties causes content or functionality to be lost on the “Search Results” page.

Reflow requires users to scroll in multiple directions (no exceptions). Users are required to navigate in multiple directions on the “Resources” page.

Modal heading not marked up semantically. There are elements within a modal that title or categorise other content. These elements have not been marked up as headings on the “Resources” and “Profile Settings” pages.

Status role used inappropriately which suppresses semantics. There are instances where a status role has been applied inappropriately on the “Search Results” page.

ARIA has been defined on the incorrect element. There are elements which have attempted to use ARIA. However, there is malformed ARIA on the “Communities”, “Resources” and “Skills Development” pages.

Functional icons have inappropriate text alternative. There are decorative icons that have not been hidden from assistive technology on the “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Error messages are not associated with form fields. There is a missing association between visual cues and fields on the “Your information”, “Terms of use”, “Policy agreement – Registration” pages and the “Multi-Factor Authentication” page.

Headings are not marked up semantically. Text elements that title sections of content on the “Terms of use”, “Policy agreement”, “Multi-Factor Authentication” and “Communities” pages are not marked up as headings.

Unordered lists are malformed. There are elements that are visually communicated as being interrelated. However, malformed list semantics have been used.

Form fields and visual labels are not associated. There are form fields that are not associated with their visual labels on the “Communities” and “Resources” pages.

Progress bars and visual labels are not associated. There are form fields that are not associated with their visual labels on the “Communities”, “Resources” and “Skills Development Courses” pages.

The reading order does not follow into expanded content. A meaningful reading order has not been determined on the “Multi-Factor Authentication” page.

Regular link text does not have sufficient contrast. The contrast of link text is insufficient on the “Terms of use”, “Policy agreement”, “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Regular button text does not have sufficient contrast. There are instances where button text contrast is insufficient on all pages.

Reflow causes loss of content. When subject to reflow, content is lost from the “Registration” pages, “Homepage” and “Search Results” page.

Functional non-text content fails contrast. Non-text content has insufficient contrast on the “Homepage”, “Communities”, “Resources”, “Profile Settings” and “Search Results” pages.

Text spacing causes content or functionality to overlap. Content overlaps when the text properties are adjusted on the “Multi-Factor Authentication” page.

Focus does not return to triggering element. When modal content is closed, the focus does not return to the element that triggered the content on the “Registration – Confirmation”, “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Focus not set onto modal dialog. Keyboard focus order is not logical on the “Forgotten Password” and “Communities” pages.

Background elements receive focus. There are modal dialogs where the background elements can still be accessed with a keyboard on the “Forgotten Password” page.

Focus is not managed appropriately when content is removed from the page. There are instances where the focus order is not managed when content is removed from the “Profile Settings” page.

Focus does not remain on the activated element. There are interactive elements that can be tabbed onto and activated with a keyboard. However, when this is done, keyboard focus does not remain on the element on the “Forgotten Password” page.

Focus is not managed appropriately when page is dynamically updated. There are instances where the focus order is not managed when the page is dynamically updated on the “Communities” page.

Accessible names of elements do not include visual names. There are interactive elements where the accessible name does not include the visual name on the “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Target size for pointer input does not meet minimum size requirements. There are targets which do not have the required area and are not exempt on the “Confirmation” page.

Error messages that appear on submission have no programmatic call-to-action. There are error messages that appear on the page with no programmatic call-to-action on the “Your information (Name)”, “Your Information (Localisation)”, “Terms of use”, “Policy Agreement” and “Password” pages.

Interactive elements do not have a permanent label. There are elements do not have a permanent label on the “Your Information (Localisation)” and “Forgotten Password” pages.

Interactive elements do not have explicit label. There are elements with no label on the “Multi-Factor Authentication” page.

Error messages do not identify the problem or signpost how the error can be remediated. There are vague errors on the “Login” page.

Authentication step requires transcription (paste not fully enabled). There are cognitive function tests that are required in the authentication process which require the user to transcribe information on the “Multi-Factor Authentication Setup” and “Multi-Factor Authentication” pages.

Interactive elements with overridden name. There are interactive elements with overrirden accessible names on the “Registration – Your Information (Name)” page.

Interactive elements have no accessible name. There are interactive elements that do not have an accessible name on the “Registration – Your Information (Localisation)” page.

Disabled element is not programmatically identified. There are disabled elements that are not programmatically determined as such on the “Login” page.

Button elements with overridden name. There are interactive elements with overridden accessible names on the “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Interactive elements have the wrong role. There are interactive elements that have a role. However, they use the wrong role on the “Homepage”, “Communities”, “Resources”, “Profile Settings”, “Search Results” and “Skills Development” pages.

Modal dialogs with inappropriate name. There are interactive elements that have inappropriate accessible names on the “Homepage” and “Communities” pages.

Expandable elements are not programmatically identified. There are expandable elements that are not programmatically determined as such on the “Communities” and “Search Results” pages.

Modal dialogs with no accessible name. There are interactive elements that do not have an accessible name on the “Communities” and “Resources” pages.

Interactive elements with inappropriate name. There are interactive elements that have inappropriate accessible names on the “Profile Settings” page.

Current state is not programmatically identified. There are elements that are visually highlighted as currently relevant and are not programmatically determined as such on the “Search Results” page.

Static element has interactive role. There are static elements that inappropriately have an interactive role on the “Communities” page.

Search results not programmatically identified. There are dynamic search results that are not programmatically determined as such on the “Search Results” page.

Low Priority

Inappropriate page titles. There are inappropriate page titles on the “Multi-Factor Login” pages.

Unordered lists are not marked up semantically. Description lists on the “Confirmation” and “Policy agreement” pages, and lists on the “Policy agreement”, “Communities” and “Search Results” pages are not marked up with the correct code.

Modal: Decorative icons are not hidden from assistive technology. Icons have inappropriate text alternatives on the “Sitemap” and “Share with community” modals.

The platform was checked for adherence to the internationally recognised Web Content Accessibility Guidelines (WCAG) 2.2 AA. Accessibility testing was carried out on a Windows 11 machine with the latest version of Windows Edge and JAWS 2023. Mobile testing was carried out using an iPhone SE running iOS 17.3 with VoiceOver and a Google Pixel 4a running Android 13 with TalkBack.


.GOV Service ONLYSkills development modules

The modules reach a high level of accessibility by following conventions and standards. They are confirmed as being largely compliant with both the level A and AA guidelines as specified in the Web Content Accessibility Guidelines and as such will provide most users with an accessible experience.

The following issues remain:

  • When using a screen reader, the keyboard focus lands on some inoperable elements in the Menu and in the Knowledge check section.
  • When using a screen reader on mobile devices, the keyboard focus lands on all the menu elements even if they are visually obscured when the side menu is expanded on the menu screen.

The modules were checked for adherence to the internationally recognised Web Content Accessibility Guidelines (WCAG) 2.2 AA. Accessibility testing was carried out on a Windows 11 machine with the latest version of Windows Edge and JAWS 2023. Mobile testing was carried out using an iPhone SE running iOS 17.3 with VoiceOver and a Google Pixel 4a running Android 13 with TalkBack.

Date of publish
15.05.2024
Next review date
15.06.2024
If you have any questions or queries regarding this accessibility statement, please contact support@brightwave.zendesk.com.