XClose

Accessibility

Menu

SEAtS accessibility statement

This accessibility statement applies to SEAtS.

SEAtS (https://ucl.seats.cloud/) is run by University College London (UCL). 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 300% 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

We’ve also made the website text as simple as possible to understand.

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 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 us, there is a process in place that will acknowledge your contact, tell you who is dealing with it and give you a timescale by which you can expect a reply.

We aim to respond to all contacts within 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, contact us.

Read tips on contacting organisations 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 not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliance and exemptions are listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

SEAtS Software have produced an accessibility statement that indicates the following non-compliances:

  • WCAG 2.4.3 Focus Order (A)
  • WCAG 2.4.6 Headings and Labels (AA)
  • WCAG 2.5.8 Target Size (Minimum) (AA)
  • WCAG 2.1.1 Keyboard (A)
  • WCAG 1.4.3 Contrast (Minimum) (AA)
  • WCAG 2.4.1 Bypass Blocks (A)

In addition we have identified the following issues through local testing:

  • Illogical heading structure. This fails WCAG 1.3.1 Info and Relationships (A).
  • Visual headings are marked up as labels (days/term) or as divs (lecture titles). This fails WCAG 1.3.1 Info and Relationships (A).
  • No visible focus indicator on time slider control. This fails WCAG 2.4.7 Focus Visible (AA).
  • Settings icon link does not have any text content. This fails WCAG 2.4.4 Link Purpose (A). 
  • Text cannot be resized with browser controls (non-zoom). This fails WCAG 1.4.4 Resize Text (AA).
  • SVG attendance chart has generic alt text. This fails WCAG 1.1.1 Non-text Content (A).
  • Page reflows but calendar control headers do not fix meaning context for dates is lost. This fails WCAG 1.4.10 Reflow (AA).
  • Multiple elements fail contrast requirements. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

Mobile application issues (Android/iOS)

  • There is no non-visual means of identifying that there is an event on a given day. Days with events have a blue underline but this is not conveyed to screen reader users on both Android and iOS. This fails WCAG 1.3.3 Sensory Characteristics (A).
  • There is an orientation issue on both Android and iOS in landscape view where it becomes difficult to access the list view below the calendar. This fails WCAG 1.3.4 Orientation (AA).
  • On the calendar screen where the lecture room details text and the attendance status of the student text are displaced due to a long room name. Although this works in landscape mode there is a separate issue with orientation outlined above. This fails WCAG 1.4.10 Reflow (AA).
  • When you tap on a date to highlight it, list information is not read effectively to screen reader users e.g. list 8 items, so non-visual users do not know how many events are available to swipe through. This fails WCAG 1.3.1 Info and Relationships (A). 
  • When checking in using Bluetooth the status message is not effectively conveyed to screen reader users. On Android the Searching Alert message is focussed but the full text of the alert is not conveyed. On iOS the message is not focussed by default and can only be accessed after swiping through the elements on the screen behind. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.4.3 Focus Order (A).
  • When checking in using QR code if you focus on an incorrect QR code the error message is not communicated non-visually. This fails WCAG 4.1.3 Status Messages (AA).

Android

  • On Android when swiping between month views of calendars the screen reader reads different information than is visually selected. This fails WCAG 2.4.3 Focus Order (A) and WCAG 1.3.1 Info and Relationships (A).
  • When moving through the calendar a user can click on the "<" or ">" button to move to another month, but if they continue to swipe they will hear the month behind the dates shown. The month or date shown is not read out. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.4.3 Focus Order (A).

iOS

  • A user can move down to check in to a class via Bluetooth or QR code, but the information heard is interrupted when the user hears 3 buttons that are not on the dialogue box [Ellipsis/Calendar/Current Events] from the screen behind, so the dialogue box is split in to 2 parts. This fails WCAG 1.3.1 Info and Relationships (A) and WCAG 2.4.3 Focus Order (A).
  • iOS refresh screen did not work (3 finger pull down). This fails WCAG 2.1.1 Keyboard (A).
  • When checking in using QR code the status message is not effectively conveyed to screen reader users. On Android the Code Entry modal is focussed but on iOS the modal is not focussed by default and can only be accessed after swiping through the elements on the screen behind. In addition the Checking In modal status is not conveyed effectively. This fails WCAG 1.3.1 Info and Relationships (A), WCAG 2.4.3 Focus Order (A), and WCAG 4.1.3 Status Messages (AA).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

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 contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours 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 the website using a combination of manual and automated checks alongside reference to the accessibility statement produced by SEAtS Software. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the website owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.

Preparation of this accessibility statement

This statement was prepared on 25 October 2022. It was last reviewed on 18 September 2023. The website was last tested on 6 September 2023. The mobile application was last tested on 24 August 2023. The test was carried out by SEAtS Software and UCL.

What we’re doing to improve accessibility

UCL are working with SEAtS Software 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.