Accessibility statement
Scope
This statement applies to the whole Time4BUS service at https://time4bus.com/en: the home page, the timetables of every city and operator, the stop, line and trip pages, the maps and the journey planner.
The service is run by GenesisMobo Sp. z o.o., and we are responsible for its accessibility, including on the timetable pages of each operator. We are not a public sector body and publish this statement voluntarily.
Date of the last major update:
Compliance status
The service is partially compliant with WCAG 2.2 at levels A and AA. WCAG 2.2 includes every WCAG 2.1 level AA requirement that the EN 301 549 standard refers to, so this statement covers those too. Non-compliance and exemptions are described below, under “Non-accessible content”.
Non-accessible content
- The map does not fully meet the contrast requirements. Names on the map have a contrast of at least 7:1 thanks to their outline, and line numbers on the vehicle markers at least 4.5:1, which is level AA, not AAA. Streets, railways, water and green areas on the base map, however, have a contrast below 3:1 against the background; in high contrast mode streets and railways stand out more. We also give the stops and vehicles from the map as text.
- Maps are hard to use without sight. We give the same information as text: stops in the map view are listed under “On the map”, and departures are on the stop pages. A departure leads to its trip page, which shows the stops the vehicle has already left and the next stop. You can also find a vehicle by its number in the search on the home page and on the city map.
- Some timetables offer a PDF printout prepared by the operator. Such a file may not be fully accessible. The same timetable is available as a web page: on the stop page in the “Timetable” tab.
- Notices and information pages in the timetables are added by the operators. They may lack text alternatives for images or a correct heading structure.
Accessibility features
- Text size A, A+ and A++ in the “Aa” panel.
- Light and dark themes and high contrast.
- Pausing animations, vehicle movement on the map and the refresh of live departures.
- Keyboard use and “Skip to content” links.
- You can resize the panel on the map on a phone without dragging: press the “Panel size” button or use the up and down arrows.
- You can move the map without dragging: the “Move the map” button shows arrows in four directions, and the arrow keys work on the focused map.
- On a phone, the list panel lowers when you Tab to the map or its buttons, so it never hides the focused element.
- Buttons and links are at least 24 by 24 pixels or have enough space around them.
- Links to help, contact and documents are in the footer, always in the same order.
- The service needs no login or account, so criterion 3.3.8 on authentication does not apply.
- Content without horizontal scrolling at a width of 320 pixels, which equals 400% zoom.
- Text contrast of at least 7:1. Exceptions: the map, operator logos and illustrations.
Keyboard shortcuts
- In the city search, the up and down arrows move between suggestions, and Enter chooses a city.
- On the map: arrow keys move the map, the plus and minus keys zoom in and out.
- On a phone, on pages with a map, the “Panel size” button changes the size of the panel with Enter or Space, and the up and down arrows make the panel bigger or smaller.
- On the journey planner map, Enter points at the centre of the map and offers “Start here” or “Destination here”.
- In tabs: left and right arrows, Home and End move between tabs.
- Escape closes the list of suggestions, the “Aa” panel, menus and dialogs.
- Escape hides the tooltip of the button that has the focus or the pointer. You can move the pointer onto the tooltip and it stays.
How we prepared this statement
We prepared this statement based on a self-assessment that we carried out ourselves. It included:
- automated tests with axe-core in about 300 variants: 31 page views and states (including open menus, panels and dialogs), in four themes, on desktop and mobile, and with the largest text size;
- manual keyboard tests of the focus order, its visibility and whether anything covers it;
- checking the layout at a width of 320 pixels and with the largest text size;
- colour contrast measurements in every theme.
We have not yet tested the service with screen readers such as NVDA, VoiceOver or TalkBack. We design it with them in mind, but we have not confirmed this with tests.
Date the statement was prepared:
Date of the last review of the statement:
Report a problem
If something on the site is hard to use or not accessible, write to us or call us. Give the page address and describe the problem. If you need information in another form, we will send it by e-mail or tell you by phone.
- biuro@genesismobo.com
- Phone
- 22 425 44 34