This accessibility statement applies to the website MyTimetable.
This website is run by Erasmus University Rotterdam. We want as many people as possible to be able to use this website. For example, that means you should be able to:
We've also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
If you find any problems not listed on this page or think we're not meeting accessibility requirements, please contact the service desk.
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).
Erasmus University Rotterdam is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
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.
The content listed below is non-accessible for the following reason(s):
| Success Criterion | Issue | Note |
|---|---|---|
| 1.1.1 Non-text Content | Some images or image buttons do not have appropriate, equivalent alternative text. | |
| 1.4.1 Use of color | Colours are used to depict activity type, without having a textual alternative. | No fix planned. Details view provides a textual description of the activity type. Not including this in the list view is on purpose - it is not very important information to most users, similar to other data (e.g. activity size). |
| 1.4.3 Contrast (Minimum) | Week and day labels in several views do not have a contrast ratio of at least 4.5:1. |
| Success Criterion | Issue | Note |
|---|---|---|
| 1.4.3 Contrast (Minimum) | Some headings and text do not have enough contrast between text and its background, making it hard to read for people with moderately low vision. | This is only an issue when customers select colours from the corporate identity that do not have enough contrast. |
| 1.4.4 Resize text | Legacy HTML attribute prevents users from scaling the text. | This works as expected in modern browsers, as they ignore the legacy HTML attribute. The attribute will be removed in a future MyTimetable version. |
| 2.4.3 Focus Order | Opening the navigation button in the mobile view of the help page doesn't move the keyboard focus to the menu, making it hard to navigate the menu by keyboard. | |
| 2.4.4 Link Purpose (In Context) | Links in the MyTimetable screenshot have no discernible text, not allowing assistive technologies to provide a meaningful description of the links to users. |
| Success Criterion | Issue | Note |
|---|---|---|
| 1.4.1 Use of color | Colours are used to depict activity type, without having a textual alternative. | No fix planned. Details view provides a textual description of the activity type. |
| 2.4.2 Page Titled | The page title is the same for all pages, which does not help in identifying their current location on the website. | |
| It is not possible to connect to Microsoft Office 365 and Google Calendar using the mobile version. | This only concerns the integration where activities from the timetable become appointments in the calendar, which is a separate module in MyTimetable. iCalendar subscriptions do work from the mobile interface. |
PDF, Excel and CSV documents are not accessible. We do not plan to provide accessible PDF, Excel and CSV documents exported by MyTimetable and consider them out of scope. As an alternative, the mobile interface can be used to view live data.
The administrative portal is not in scope at the moment due to the limited amount of users and necessary investment to mitigate the issues. A redesign of the administrative portal will include relevant fixes.
| Success Criterion | Issue | Note |
|---|---|---|
| 1.1.1 Non-text Content | Some images do not have a text alternative, so people using a screen reader cannot access the information. | |
| 1.3.1 Info and Relationships | Some headings are not marked up as being headings, making them not perceivable by screen readers. | |
| 1.3.1 Info and Relationships | Closing the date picker moves the tab focus back to the top of the page. Screen reader users may be confused or disoriented when using the date picker. | |
| 1.4.3 Contrast (Minimum) | Some headings and text do not have enough contrast between text and its background, making it hard to read for people with moderately low vision. | Colours are usually determined by the customer based on their corporate identity, which might impact this criterion. |
| 2.4.2 Page Titled | The page title is the same for all pages, which does not help in identifying their current location on the website. | |
| 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. | |
| 4.1.2 Name, Role, Value | Items in navigation incorrectly marked as link. |
The desktop interface is mostly not in scope at the moment as it has not been designed with accessibility in mind and would require a very high investment to mitigate the issues. A redesign of the desktop interface will include relevant fixes. We recommend using the mobile interface as an accessible alternative.
| Success Criterion | Issue | Note |
|---|---|---|
| 1.1.1 Non-text Content | Form inputs have associated text labels. While not technically implemented as forms, there are various control mechanisms for the calendar, such as the selection of calendars. There's no association of the checkbox and the associated label. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 1.3.1 Info and Relationships | There's limited use of semantic markup. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 1.3.2 Meaningful Sequence | The reading and navigation order is not always logical. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 1.4.10 Reflow | The Desktop interface cannot be scaled to smaller devices. | The Desktop interface has not been built using Responsive Web Design technologies. The mobile interface can be used as an accessible alternative. |
| 2.1.1 Keyboard | Not all content can be navigated using the keyboard. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 2.1.2 No keyboard trap | Not all content can be navigated using the keyboard. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 2.4.1 Bypass blocks | No skip-link available to navigate quicker to useful content. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. A skip-link to the mobile interface is implemented to guide users to the accessible interface. |
| 2.4.3 Focus Order | The order of content is not always logical, which impacts navigation using a keyboard. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. We recommend the mobile interface or another calendar client with an iCalendar link (Google Calendar, Outlook) for this. |
| 2.4.4 Link Purpose (In Context) | The date-picker provides no context for which day is being picked. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. A skip-link to the mobile interface is implemented to guide users to the accessible interface. |
| 2.4.6 Headings and labels | Not all page headings and labels for form and interactive controls are informative. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. A skip-link to the mobile interface is implemented to guide users to the accessible interface. |
| 2.4.7 Focus Visible | Most elements have no focus indicator. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. A skip-link to the mobile interface is implemented to guide users to the accessible interface. |
| 3.1.2 Language of Parts | Text from external systems (e.g. timetabling software) is not marked as having a different language than the full page (e.g. English timetabling content on a Dutch page). This prevents user agents to correctly present content written in multiple languages. | MyTimetable does now know what language is being used in these external data sources. These systems do not expose the language used per value. This issue cannot be fixed. |
| 4.1.2 Name, Role, Value | 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. | Due to limitations of the frameworks we use for the desktop interface this is a disproportionate burden. A skip-link to the mobile interface is implemented to guide users to the accessible interface. |
| Success Criterion | Issue | Note |
|---|---|---|
| 3.1.2 Language of Parts | Text from external systems (e.g. timetabling software) is not marked as having a different language than the full page (e.g. English timetabling content on a Dutch page). This prevents user agents to correctly present content written in multiple languages. | MyTimetable does now know what language is being used in these external data sources. These systems do not expose the language used per value. This issue cannot be fixed. |
This statement was prepared on 18 August 2020. It was last reviewed on 5 December 2024.