Accessibility Statement for MyTimetable
At the University of Birmingham, we want to ensure that as many people as possible can use our website, and we are working to improve our digital services.
This accessibility statement covers this website: https://mybhamtimetable.bham.ac.uk
MyTimetableis provided by Semestry for use at the University of Birmingham.
The event details are managed by the University of Birmingham.
How accessible this website is
We know some parts of this website are not fully accessible.
- It is not possible to scale text without the use of a screen magnifier
- Some calendar elements/controls are not accessible via a keyboard
- Visitors using a keyboard to navigate the site may not be able to see their location on the page
- Some images/icons do not have appropriate alternative text, or are not properly labelled as decorative
- Some form elements/controls on some pages are missing labels or don’t have the purpose of fields identified programmatically.
- Some form elements have been used as calendar controls and may not be labelled appropriately
- Some labels do not match their accessible name, making it difficult for speech-input or screen reads to use the site
- Some accessible names are not consistently labelled across the site
- Some of our pages do not use headings appropriately
- Some pages have duplicate headings, which may make it difficult for screen reader users to navigate
- Tables are used to display calendar content, but do not have headers for the columns or rows
- The date picker does not move tab focus back to the top of the page – this may cause confusion for screen reader users
- Colours are used to convey activity information without also showing type in text when viewing list views (activity information can be seen in the full details view).
- PDF, Excel and CVS documents are not accessible
What to do if you can’t access parts of this website
While not ideal, many of the above issues can be avoided if the mobile version the application is used.
Calendar data is also available if it is exported to a more accessible application such as Outlook.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please email accessibility@contacts.bham.ac.uk.
In your message please include the following:
- the web address (URL) of the content
- your email address and name
- the format you need.
We’ll consider your request and get back to you within 10 days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website and are continuing to audit our content. If you find something that you are unable to access, or we have failed to identify a barrier, please let us know.
If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, please email accessibility@contacts.bham.ac.uk
Enforcement procedure
If you are unhappy with the response you have received from the University about your accessibility-related issue, you can make a complaint to the University by emailing accessibility-complaint@contacts.bham.ac.uk.
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
The University of Birmingham 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 website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non-compliance with the accessibility regulations
WCAG 2.1 success criterion 1.1.1 (non-text content).
Some images do not have text alternatives for non-text content or do not correctly identify images as decorative.
The application developer plans to resolve this by redesigning the application 2025.
Form inputs may be missing associated labels, or have been used as calendar controls on the desktop interface. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 1.3.1 (info and relationships).
Semantic markup is not used to designate headings, landmarks, lists or to emphasise text.
This should be fixed by September 2023.
Tables are used for the calendar layout but have no headers for the columns or rows. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 1.3.2 (meaningful sequence)
The reading/navigation order (determined by the code order) is not logical. The sidebar panel comes before the calendar display. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 1.4.1 (use of colour)
Only colours are used to display information for Activities in the list view.
As the information is available in the full details view, the developer has chosen not to fix this issue.
WCAG 2.1 success criterion 1.4.3 (contrast minimum).
Some text and images do not have sufficient contrast between the text and background colours. They currently meet a ratio of 4.48:1 instead of 4.5:1.
Most examples should be fixed by December 2023 (others are planned via the roadmap).
WCAG 2.1 success criterion 1.4.4 (resize text)
It is not possible to resize text. Although, some browsers may allow resizing of the text, regardless of the current setting.
A fix is scheduled for December 2023.
WCAG 2.1 success criterion 1.4.10 (reflow)
Resizing the browser to 400% may cause some horizontal scrolling. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 1.4.11 (non-text contrast)
One icon used does not have enough contrast and focus, hover and active states do not currently have a contrast of 3:1.
A fix has been scheduled for end of 2023.
WCAG 2.1 success criterion 1.4.12 (text spacing)
Adapting the font size can impact the font spacing negatively, making it difficult to read.
A fix is scheduled for end of 2023.
WCAG 2.1 success criterion 2.1.1 (keyboard) and WCAG 2.1 success criterion 2.1.2 (keyboard trap)
Keyboard users are not able to navigate to the calendar selection on the desktop interface. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 2.4.1 (bypass blocks)
No link is provided to skip to content.
Proper heading structure or identification of page landmarks are present.
The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
For the mobile interface a skiplink will be added by August 2023
WCAG 2.1 success criterion 2.4.2 (page titled)
The page title is repeated across all pages. This makes it difficult for users to identify their location in the site.
A fix is scheduled for the mobile interface by August 2023.
A fix for the desktop interface has been road mapped for 2024
WCAG 2.1 success criterion 2.4.3 (focus order).
The order of navigation links is not logical or intuitive on the desktop interface. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
The mobile interface navigation menu button does not move the keyboard focus to the menu, making it hard to navigate the menu.
This is scheduled to be fixed by end of December 2023.
WCAG 2.1 success criterion 2.4.4 (link purpose (in context))
The datepicker provides no context for which day is being picked. The developer will not be fixing this issue as the mobile interface provides a more accessible version.
WCAG 2.1 success criterion 2.4.6 (headings and labels)
Page headings and labels for form controls are not always informative. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 2.4.7 (focus visible)
Most elements do not have a focus indicator, making it easier to navigate the site with a keyboard. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
WCAG 2.1 success criterion 2.5.3 (label in name)
The visible labels in the website are not always equal to their accessible name, which makes it harder for speech-input or screen reader users to use the site.
A redesign of the admin portal is scheduled for 2024.
WCAG 2.1 success criterion 4.1.2 (name, role, value)
This issue relates to the administration portal:
- Expandable items in navigation incorrectly marked as link. Should be button.
- Dropdown menu for Language picker marked as 'menu', but children are not 'menuitem'.
- 'Admin 1' dropdown incorrectly marked as link.
- Logout 'link' marked as link, but missing href-value.
A redesign of the administrative portal is scheduled to begin in 2024.
Aria is not always used appropriately. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
Markup is not always used in a way that facilitates accessibility. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
Additional notes:
Some of the PDFs and Word documents produced by the application fail WCAG 2.1 success criterions. The developer has claimed disproportionate burden regarding this issue. They recommend using the mobile interface as it is more accessible.
What we’re doing to improve accessibility
We are working with the developer to create a more accessible application. Fixes are scheduled for both the mobile and desktop interfaces throughout 2023.
A redesign of the administrative portal is scheduled for 2024.
Preparation of this accessibility statement
This statement was prepared on 10th July 2023.
This website was last tested on 5th July 2023.
The test was carried out by the developer and by the University using Silktide.