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 “Skills development” page 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”.
- 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.
- Functional non-text content fails contrast: The chevron that appears as an option for the user to scroll back to the top of the page failures colour contrast.
- 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.
- 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 “Search Results” page.
- 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.
- Headings are not marked up semantically. Text elements that title sections of content on the “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.
- Functional non-text content fails contrast. Non-text content has insufficient contrast on the “Homepage”, “Communities”, “Resources”, “Profile Settings” and “Search Results” pages.
- Focus not set onto modal dialog. Keyboard focus order is not logical on the “Forgotten Password” pages.
- Background elements receive focus. There are modal dialogs where the background elements can be accessed with a keyboard on the “Forgotten Password” page on Android and IOS.
- Focus is not managed appropriately when content is removed from the page. There are instances on IOS and Android where the focus order is not managed when content is removed from the “Profile Settings” 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 “Communities” 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 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.
- 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.
- 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.
- Search results not programmatically identified. There are dynamic search results that are not automatically announced to the screen reader.
- Status role used inappropriately and suppress semantics. Search heading has a role of status which overrides the heading role.
Low Priority
- Unordered list not marked up semantically. Lists of posts, and lists of comments, are still not marked up using appropriate list mark-up.
.GOV Service ONLY – Skills 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 |
| 21.06.2024 |
| Next review date |
| 01.08.2024 |