In short
- We build iBus to meet Israeli Standard SI 5568, which is based on the Web Content Accessibility Guidelines (WCAG), at level AA.
- iBus has not yet been checked by an external accessibility auditor. We test it ourselves and fix the problems we find.
- If something is hard to use, write to us — we will help and fix it.
1. Standard and status
We design and test iBus to meet Israeli Standard SI 5568, Part 1, at level AA, and the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. iBus partially meets this standard: most pages and functions are accessible; the known exceptions are listed in section 3.
The iPhone and Android apps show the same pages as the web app at app.ibusisrael.online, which can also be used in a phone’s browser.
Our checks include use with the keyboard only, automated accessibility tests, large text, high contrast, zoom to 200 per cent and the right-to-left layout. A full audit by an external auditor has not yet been carried out.
2. Accessibility features
- pages, menus, forms and buttons can be used with the keyboard, with a visible focus indicator and a “Skip to content” link;
- headings, page regions and labelled buttons and fields, so that screen readers can describe the page;
- text size from small to extra large in the settings, and page zoom up to 200 per cent without loss of content;
- a high-contrast mode and light and dark themes;
- the “Motion: Minimal” setting, support for the reduced-motion setting of your device, and moving examples that can be paused;
- four languages — Hebrew, Arabic, Russian and English — with a right-to-left layout for Hebrew and Arabic;
- arrivals, routes and service changes shown as text and lists, not only on the map;
- questions to Lior by text or by voice.
The settings for text size, contrast, motion and language are in My account → Settings → Language & look.
3. Known limitations
- the map is a visual tool: stops, lines and trips shown on it are also available as text, but the map itself cannot be fully read by a screen reader;
- arrival times update automatically, and a screen reader may not announce every change;
- the transport data does not include the physical accessibility of stops and vehicles (for example access without steps), so iBus cannot show it;
- pages of other services — sign-in with Google or Apple, the app stores and the map images — are not under our control;
- the version history pages (Versions) have an older design and are less accessible than the rest of iBus.
We are working to remove these limitations. Information about the accessibility of a stop or vehicle can be obtained from the operator of the line.
4. Report a problem or ask for help
If you have difficulty using iBus or find an accessibility problem, write to us at ibus.israel@gmail.com or through the Contact page. Please tell us which page or function it was, what happened and, if possible, which device, browser and assistive technology you use. Messages about accessibility reach the operator of iBus directly. We will reply and, where we can, help you complete what you were trying to do.