Close
This accessibility statement applies to UCL's Online Timetable.
UCL Online Timetable is an UCL-owned application. We want as many people as possible to be able to use this website, which means that you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 400% without the text spilling off the screen
- navigate the website using just a keyboard
- navigate the website using speech recognition software
- listen to most of the website using a screen reader
There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.
Feedback and contact information
Please contact us via MyServices if you have an accessibility query including:
- If you are experiencing issues with accessing information or using the website
- If you find an accessibility problem not listed on this statement
- If you have positive feedback on the accessibility considerations made.
When you contact the Online Timetable Team, if there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline any potential timescales by which you can expect a reply.
We aim to respond to all contacts within 3-5 working days.
Reporting accessibility problems with this website
We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.2 AA standards.
We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we're not meeting accessibility requirements, please contact us via MyServices.
Read tips on contacting organisation about inaccessible websites.
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
University College London is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
The calendar dropdown view is not accessible via keyboard. This means that screen reader and keyboard assistive technology users are unable to drill down to access specific event information across a longer period. This is critical functionality, meaning keyboard users cannot browse calendar items with events marked by blue dots. This fails WCAG 2.1.1 Keyboard (A).
There is no persistent label for the manual date entry related to the calendar modal. Once something is typed in this field a user loses this guidance for acceptable formats to use. In addition, this is not presented non-visually. This fails WCAG 3.3.2 Labels or Instructions (A).
Event clashes are read out at the end of the information for screen reader users, meaning they have to wait to find out there is a clash. If the clash could be mentioned first for non-visual users that would be better. This fails WCAG 1.3.1 Info and Relationships (A).
The Event clash warning triangle is described only as an image (on MAC). This should be marked as decorative. This fails 1.1.1 Non-Text Content (A).
On the calendar and list view, there is either a number or a letter placed in the top right-hand side of the event. This is not read out to any screen reader or any user using Text to Speech. If this information is important, it should also be read out. This fails WCAG 1.3.1 Info and Relationships (A).
Heading structure is not sequential across pages. This fails WCAG 1.3.1 Info and Relationships (A).
The modal for syncing the Calendar does not trap focus inside the modal, so it is possible to move behind the modal and therefore have focus obscured when navigating the site behind. This fails WCAG 2.4.11 Focus not obscured (AA).
In the Calendar view, Calendar headers (days of the week) are read differently. Some are read as full day names, others are a shortened version. This could be confusing for some user groups. This fails WCAG 1.3.1 Info and Relationships (A).
At larger magnification levels 250%+, some events on the calendar view overlap the Header for the day of the week. Some user groups would find this confusing, as they would not be able to see what day of the week this event is on. This fails WCAG 2.4.11 Focus not obscured (AA) and 1.4.10 Reflow (AA).
With individual events, when screen reader users move on to the event element, they appear to be reading the underlying information for each event, i.e. screen reader users get more information than is visually presented to non-screen reader users. Information should be equal to both visual and non-visual users. This fails WCAG 1.3.1 Info and Relationships (A).
When using the resize text feature, only the Time and the Lecture type are changed; the rest of the text remains the same size. This fails WCAG 1.4.4 Resize Text (AA).
List view specific issues.
At larger magnification levels, the Week number and Month are too close together. This could be hard for some user groups to view. This fails 1.4.10 Reflow (AA).
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
This section covers issues that we do not need to fix right now. The law calls these exemptions.
Third-party content
Our websites may contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make our best efforts to work with the third party to improve its accessibility. This may include:
- links to non-UCL websites
- content/functionality on our website
- content hosted on other websites, such as social media sites.
To help accessibility compliance across the sector, University College London supports searchBOX, a centralised, independent directory of third-party accessibility information.
searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem.
Users can access third-party accessibility statements using the free searchBOX Finder service.
University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory.
Our testing processes
We tested this web application using a combination of manual and automated checks alongside the UCL developer. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the web app owner, who will review the issue, make sure it is included in our plan to fix issues and add it to the accessibility statement when it is next updated.
Preparation of this accessibility statement
This statement was prepared on 31 October 2025. It was last reviewed on 31 October 2025. This application was last tested on 31 October 2025. The test was carried out by the Digital Accessibility and Online Timetable teams.
What we’re doing to improve accessibility
University College London (UCL) is working to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes.