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, calendars, drawers and modal dialogs, where editing functionality using a keyboard is limited.
• Some parts of the platform cannot be enlarged or used on small screens, because page zoom and scaling are restricted.
• Status messages, such as confirmations and validation errors, are not always announced to screen reader users.

Accessibility varies between the different parts of the platform. Newer functionality, built on our common component library, is substantially more accessible than older functionality that has not yet been migrated. Where an older part of the platform is not accessible, an accessible alternative route to the same task is often available.

‍

The parts of the platform this statement covers

Our most recent assessment covered the following areas:

• Schedule Suite — Schedule and Activity Manager scheduling, Data Manager activity editing, Allocate, Reserve, Viewer, Assessment, and Data collection form submission.
• Curriculum and Workload Suites — Curriculum and Workload, and the Study Catalogue.
• Engagement Suite — Engage Student, Engage Academic, Engage Flow, Engage Chippo (Android mobile app), and Evaluation surveys.
• Hub — Schedule, Upcoming exams, Schedule preferences, Group registration, Availability, and Exam invitations)
• Platform and administration — Authentication (login, logout and password reset), and Admin.
  ‍

Legacy products

While we did test student and staff-facing applications in this round of accessibility testing, our intention is to soon replace those interfaces with the Hub which we are making our best effort to make accessible and WCAG compliant. Viewer and Reserve will be replaced by the Hub.

‍

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.

‍

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

‍

In the European Union, the European Accessibility Act (Directive (EU) 2019/882) is enforced by the designated national authority in each member state. If you are not happy with how we respond to your complaint, you can contact the market surveillance or enforcement authority in your country.

‍

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 and the European Accessibility Act (Directive (EU) 2019/882).
‍

Our own standard for the platform is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We test and report against that standard, which also covers the web content requirements of the European harmonised standard EN 301 549.

‍

Compliance status

The web 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.

‍

What is accessible

Across every area we assessed, navigation and controls behave consistently from page to page, help is available in a consistent place, and you are not asked to re-enter information you have already given. Logging in does not depend on remembering or transcribing a code. Nothing on the platform flashes in a way that could trigger seizures, no function requires a complex gesture or device motion, and audio never plays automatically.
‍

Some areas performed considerably better than the platform average: the Study Catalogue, the Hub exam flows, the authentication flows and Engage Chippo each met the large majority of the criteria that applied to them. No single area of the platform is yet fully compliant with WCAG 2.2 AA.

‍

‍

Non-accessible content

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

‍

Non-compliance with the accessibility regulations

‍

Keyboard and Focus Issues‍

• Some tasks cannot be completed using a keyboard alone. This mainly affects tables, where expanding, sorting and selecting rows often needs a mouse, and drawers and modal dialogs, which, for example, in Assessment cannot be opened or used with a keyboard at all. Sliders, tab groups and scrollable areas are also affected in places. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 2.1.2 (No keyboard trap). Planned remediation: Q2, 2027.‍
• It is not always clear which element a keyboard user is on, because focus marking is missing on some controls. Focus can also move in an illogical order, jump past content, or end up hidden behind an open drawer or menu. This fails WCAG 2.2 success criterion 2.4.7 (Focus visible), 2.4.3 (Focus Order) and 2.4.11 (Focus Not Obscured (Minimum)). Planned remediation: Q2, 2027.
• There is no way to skip past the navigation that repeats on every page, so keyboard and screen reader users have to move through it each time to reach the main content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). Planned remediation: Q1, 2027.
• Some actions can only be carried out with a pointing device: reordering items in Data Manager requires dragging, some controls act as soon as they are pressed rather than on release, so an action cannot be cancelled, and in Core and Activity Manager scheduling single-key shortcuts cannot be turned off or remapped. This fails WCAG 2.2 success criterion 2.5.7 (Dragging Movements), 2.5.2 (Pointer Cancellation) and 2.1.4 (Character Key Shortcuts). Planned remediation: Q3, 2027.

Semantics, Structure, and Labeling Issues

• Buttons and links that show only an icon do not always have a text alternative, so a screen reader cannot say what they do. Decorative icons are not consistently hidden either, so their internal names get read out. This affects close, expand, edit and delete controls throughout the platform. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content), 4.1.2 (Name, Role, Value) and 2.4.4 (Link Purpose (In Context)). Planned remediation: Q1, 2027.
• Form fields are missing labels, or the label is not properly connected to the field, so a screen reader cannot say what to enter. Some fields rely on placeholder text alone, which disappears as soon as you start typing. This is most severe in the older Curriculum forms, where labels, fields, validation messages and character counters are not connected to each other. Some instructions also rely on the shape of an icon alone, such as marking a required field with an asterisk. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions), 1.3.1 (Info and Relationships), 1.3.5 (Identify Input Purpose) and 1.3.3 (Sensory Characteristics). Planned remediation: Q2, 2027.
• Page structure is not always marked up correctly. Headings are skipped or used out of order, some tables are missing headers so a screen reader cannot connect a cell to its column, and some content sits outside any landmark region, which makes menus in particular hard to find. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels). Planned remediation: Q2, 2027.
• Some controls describe themselves incorrectly to assistive technology, so a screen reader announces the wrong thing or refers to content that does not exist. This affects progress bars, tooltips and table sorting controls. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). Planned remediation: Q2, 2027.
• Orienting yourself is harder than it should be in places. The order content is read in does not always match the order it appears in, several products use the same page title on every page, and some products offer only one route to a given page with no search or site map alternative. This fails WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence), 2.4.2 (Page Titled) and 2.4.5 (Multiple Ways). Planned remediation: Q2, 2027.
• The page language is missing or incorrect in places, and does not always update when you change language, which stops screen readers pronouncing content correctly. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page) and 3.1.2 (Language of Parts). Planned remediation: Q2, 2027.
• Where the visible text of a control differs from the name assistive technology reads, speech recognition users cannot activate it by saying what they see. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name). Planned remediation: Q2, 2027.

Visual and Device-Independence Issues

• Page zoom and scaling are restricted in some parts of the platform, which prevents people with low vision from enlarging the text or viewing content without losing information. Some products disable scaling outright, and some tables and rows do not wrap or reflow when enlarged, do not adapt to increased text spacing, or do not fit in portrait orientation. This fails WCAG 2.2 success criterion 1.4.10 (Reflow), 1.4.4 (Resize text), 1.4.12 (Text Spacing) and 1.3.4 (Orientation). We have added support for this in our design system and are currently updating the products. Planned full remediation: Q3, 2027.
• Text is hard to read in places because the contrast against the background is too low. This most often affects placeholder and search text, badges, notification popups, headings on coloured backgrounds and unselected dates in date pickers. The borders and indicators on inputs, checkboxes and disabled buttons are also too faint. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)) and 1.4.11 (Non-text Contrast). Planned remediation: Q2, 2027.
• Colour alone is used to convey meaning in several places, so the information is lost if you cannot distinguish those colours. This affects booking and reservation states in Reserve and Viewer (soon to be replaced by the Hub), workflow step states in Curriculum, and attendance states in Engage Academic. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color). Planned remediation: Q2, 2027.
• Some controls are too small or too close together to activate reliably, which is a barrier for people with limited dexterity. This affects table expand and sort controls, clear-input icons, radio buttons and date picker arrows. This fails WCAG 2.2 success criterion 2.5.8 (Target Size (Minimum)). Planned full remediation: Q3, 2027.
• Content that appears when you hover over or focus something, such as a tooltip, cannot always be reached with the pointer, dismissed with the Escape key, or kept open long enough to read. Some of it is not available to screen readers at all. This fails WCAG 2.2 success criterion 1.4.13 (Content on Hover or Focus). Planned remediation: Q2, 2027.
• In Engage, some information is only available as an image, and some charts have no equivalent in text or table form. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text). Planned remediation: Q2, 2027.

Forms, Errors, and Status Message Issues

• Screen reader users are not told when something has happened. Save and submit confirmations, validation errors, progress updates, and the opening and closing of dialogs are not announced. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages). Planned remediation: Q3, 2027.
• When you make a mistake in a form, the problem is not always explained. In some places a field only turns red, with no message saying what is wrong, and where an error is described a correction is not always suggested. Required formats, such as how to write a date, are not always given. This fails WCAG 2.2 success criterion 3.3.1 (Error Identification) and 3.3.3 (Error Suggestion). Planned remediation: Q3, 2027.
• Some forms change without being asked to. Selecting a value can rebuild the form or navigate you elsewhere, focus can be lost when that happens, and in Engage Student some values change automatically without telling you or letting you undo it. Some views also refresh on their own, with no way to pause or stop the update. This fails WCAG 2.2 success criterion 3.2.2 (On Input), 3.2.1 (On Focus), 3.3.4 (Error Prevention (Legal, Financial, Data)), 2.2.1 (Timing Adjustable) and 2.2.2 (Pause, Stop, Hide). Planned remediation: Q3, 2027.

‍

What we have fixed since our last statement

• The keyboard trap previously reported on the login page, at the "Change organization" link, has been resolved. Our most recent test confirmed that the login, logout and password reset journeys are free of keyboard traps.
  ‍

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 as well as having full compliance of the combination of the common components.
‍

Our testing confirms the effect of this approach: the parts of the platform already built on the common component library, and the newer products, met substantially more of the WCAG 2.2 AA criteria than the older functionality they are replacing.

‍

Preparation of this accessibility statement

This statement was last reviewed on 21 September 2026.

This web application was last tested on 3 June 2026 against the WCAG 2.2 AA standard.

The test was carried out by the development teams at TimeEdit. The most used workflows in the web application were tested using automated testing tools and manual testing, by our product team. Testing covered 21 separate assessments across the scheduling, curriculum and workload, engagement and administration areas of the platform.

‍

How we tested

Each assessment combined automated scanning with manual testing of a defined set of user workflows, and the results were recorded against every WCAG 2.2 success criterion using the WebAIM WCAG checklist.

• Screen readers — VoiceOver on macOS, NVDA on Windows, and TalkBack on Android for our mobile application.
• Browsers — Chrome, Firefox and Edge, on current versions at the time of testing.
• Automated tooling — BrowserStack Accessibility for web workflows and BrowserStack App Accessibility for our mobile application, the axe-core rules engine, and the WAVE evaluation tool.
• Manual testing — keyboard-only operation of each workflow, screen reader walkthroughs, zoom and reflow at 200% and above, and inspection of markup, ARIA and colour contrast.

Automated tooling alone cannot detect every barrier, and it also reports issues that turn out not to be real, so automated findings were reviewed by a tester before being recorded as a failure.

‍