Accessibility statement for Intedashboard (Cognalearn) platform at Imperial College London

This accessibility statement applies to Cognalearn online TBL Software supplied by Intedashboard. 

This platform is run by Imperial college London. We want as many people as possible to be able to use this software. For example, that means you should be able to:

  • Change colours, contrast levels and fonts
  • Zoom in up to 400% without the text spilling off the screen.
  • Navigate most of the website using a keyboard or speech recognition software.
  • 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 platform is

We know some parts of this platform are not fully accessible:

  • There are parts that keyboard only navigation is not possible
  • Some buttons and links lack labels, or alternative names or text
  • Some elements lack accessible labels or do not match the visual names
  • Some pages are missing headings labels or heading structure is incorrect
  • Status messages are incorrect or missing

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the ICT Service Desk.

If you need information on this platform in a different format like accessible PDF, large print, easy read, audio recording or braille:

We’ll consider your request and get back to you in 2 business days.

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).

Technical information about this website’s accessibility

Imperial College London 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 platform is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Most pages are missing page landmarks, and several pages either lack a a heading structure or tit is wrong, Layout tables lack markups and/or captions. This may cause screen reader users, and speech to text users’ difficulties. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships). We are aiming to resolve all these by early 2025.

Keyboard only functionality is not enabled in the following areas:  Date pickers in course or activity creation, Number pickers in activity duration and drag and drop activities. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard only navigation). We are aiming to make all this platform navigable by keyboard only by early 2025.

In the following areas, there are drag and drop functionalities with no alternative option, Date pickers in course or activity creation, Number pickers in activity duration. This fails WCAG 2.2 success criterion 2.5.7 (Dragging Movements). We are aiming to make sure All functionality that uses a dragging movement is achievable by a single pointer without dragging, by early 2025.

There are serious issues with header hierarchy therefore tabbing order is not intuitive. Most landmarks and bypass (skip to main content) are also not possible for screen reader or speech to text users. This fails WCAG 2.2 success criterion 2.4.1 (Bypass blocks). We are aiming to correct the tabbing order, heading hierarchy and add skip to main content functionality on all pages by early 2025.

Some pages have input fields, buttons or links that are missing labels, or it is not matching the visual names or texts semantically. This may cause confusion to screen reader users. This fails WCAG 2.2 criterion 2.5.3 (Label in name). We are aiming to correct all label names semantically, make sure that all elements have visual and programmatic labels and names by early 2025.

Some buttons do not match the visual names semantically and/or the relevant state is not announced by the screen readers. This fails WCAG 2.2 criterion 4.1.2 (Name, role, value). We are aiming to label all elements correctly, match the visual names to the same alternative text and make sure that relevant value is announced for each type of element by early 2025.

Some elements have low contrast. This fails WCAG 2.2 criterion 1.4.3 (contrast minimum). We are aiming to correct all low contrast issues on this platform by early 2025.

The layout does not respond to 200-400% zoom. This fails WCAG 2.2 criterion 1.4.10 (reflow). We are aiming to make sure all pages and relevant components (drop downs etc) respond to 200-400% zoom and that no information is lost under such zoom, and two-dimensional scroll is not needed. By early 2025.

Some pages are missing headings. This fails WCAG 2.2 criterion 2.4.6 (headings and labels). We are aiming to add correct headings to all pages by early 2025.

On some pages especially on tables focus indicator is not visible. This fails WCAG 2.2 criterion 2.4.7 (Focus visible). We are aiming to add visible focus borders (both for hover and tabbing) by early 2025.

Status messages especially for alerts are not announced by screen readers. Especially for activity timers. This may cause serious delays and difficulties for screen reader users. This fails WCAG 2.2 criterion 4.1.3 (status messages). We are aiming to implement these status messages that is recognisable instantly by the screen users by early 2025.

Disproportionate burden

N/A

Content that’s not within the scope of the accessibility regulations.

PDFs and other documents

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. 

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

InteDashboard by default does not contain video content. And we do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

What we’re doing to improve accessibility

We are in continuous contact with InteDashboard to make improvements on accessibility. We are expecting updates to their accessibility in line with WCAG 2.2 AA in early 2025.

Preparation of this accessibility statement

This statement was prepared on 16/10/2024. It was last reviewed on 16/12/2024. This platform was last tested on 01/07/2023 against the WCAG 2.1 AA standard.

The test was carried out internally by InteDashboard-cognalearn.

Most pages were tested using automated testing tools, Google Chrome, Mac OS and screen readers, voiceover.