TE Academy is now live! We will improve the site step by step - read more here!

Accessibility Statement

‍

This accessibility statement applies to the TimeEdit Academic Operations platform.

‍

This web application is run by TimeEdit AB. We want as many people as possible to be able to use this web application. For example, that means you should be able to:

  • change colours, contrast levels and fonts using browser or device settings
  • zoom in up to 200% without the text spilling off the screen
  • navigate most of the web application using a keyboard or speech recognition software

AbilityNet has advice on making your device easier to use if you have a disability.

‍

How accessible this web application is

Some parts of this web application are not fully accessible:

  • All content is not fully accessible using a screen reader. There are limitations on certain pages where:
    • all content cannot be reached
    • machine readable text is missing
    • ARIA labels are not correct
    • Semantic heading levels is incorrect
  • All workflows cannot be completed using only a keyboard. This mainly affects tables and calendars where editing functionality using keyboard is limited.
Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: support@timeedit.com. If you need information on this web application 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 seven 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

TimeEdit AB is committed to making its web application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

‍

Compliance status

The webb application has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard. This web application 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

‍

Keyboard and Focus Issues

  • Certain interactive elements are not operable via a keyboard, so people who rely on keyboard navigation cannot use features like enabling shared activities or editing specific data. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). Planned remediaton in Q2, 2026.
  • A "keyboard trap" exists on the Login page where people navigating with a keyboard cannot move past the "Change organization" link. This fails WCAG 2.2 success criterion 2.1.2 (No keyboard trap). Planned remediaton in Q1, 2026.
  • Focus marking is missing for some interactive elements, making it difficult for people using a keyboard to know which element is currently active. This fails WCAG 2.2 success criterion 2.4.7 (Focus visible). Planned remediaton in Q2, 2026.

Semantics, Structure, and Labeling Issues

  • Interactive elements, such as a button on the Product selector page, are missing a text alternative, so people using a screen reader cannot identify their purpose. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content) and 4.1.2 (Name, Role, Value). Planned remediaton in Q1, 2026.
  • Form inputs, such as those for data entry and period selection, are missing or have empty labels, which makes it hard for people using screen readers to understand what information to enter. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions) and 1.3.1 (Info and Relationships). Planned remediaton in Q2, 2026.
  • The first-level heading (H1) is missing on pages, and in other cases, heading levels are skipped, which makes it hard for people using screen readers to understand the content hierarchy. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels). Planned remediaton in Q2, 2026.
  • Some elements are missing accessible names, making their purpose unclear to people using screen readers. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). Planned remediaton in Q2, 2026.
  • Tables are missing headers, which prevents people using screen readers from understanding the association between cells and column/row data. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships). Planned remediaton in Q2, 2026.
  • Broken ARIA references and invalid ARIA properties, such as on a progress bar, lead to incorrect information being conveyed to screen reader users. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value) and 1.3.1 (Info and Relationships). Planned remediaton in Q2, 2026.

Visual and Device-Independence Issues

  • Page zoom is restricted on all pages, which prevents people with low vision from being able to enlarge the text or view the content without losing information. This fails WCAG 2.2 success criterion 1.4.10 (Reflow) and 1.4.4 (Resize text). We have added support for this in our design system and are currently updating the products. Planned full remediaton in Q3, 2026.
  • Low contrast between placeholder text or links and the background makes text hard to read for people with low vision. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)). Planned remediaton in Q2, 2026.
  • Interactive elements in the top bar do not meet the minimum size or spacing requirements, which makes them difficult for people with motor disabilities to activate. This fails WCAG 2.2 success criterion 2.5.8 (Target Size (Minimum)). Planned full remediaton in Q3, 2026.
  • The page language is missing or invalid on some pages, which prevents screen readers from pronouncing the content correctly. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page). Planned remediaton in Q2, 2026.

‍

What we’re doing to improve accessibility

Our road to full compliance focuses on replacing each non-compliant part with our common component library, as this inherently only contains components that meet the criteria, instead of re-building parts of the system. Our aim is to have replaced the complete product suite with our common component library by the end of 2026 as well as having full compliance of the combination of the common components, but every release (normally every week) normally contains component replacements.

‍

‍

Preparation of this accessibility statement

This statement was prepared on November 25, 2025. It was last reviewed on December 2, 2025.

This webb application was last tested on November 25, 2025 against the WCAG 2.2 AA standard.

The test was carried out by the product team at TimeEdit. The most used workflows in the web application were tested using automated testing tools and manual testing, by our product team.

‍