Accessibility statement
1. Our commitment
Navido should be usable by everyone, including people who use a screen reader, a keyboard alone, a magnifier, or who need larger text or stronger contrast. Accessibility is treated here as part of whether the app works at all, not as an extra.
2. The standard we build to
This website and the app are built to WCAG 2.1 level AA. That is the standard behind Israeli Standard 5568 (under the Equal Rights for Persons with Disabilities Regulations), behind EN 301 549 and the European Accessibility Act, and the one against which accessibility is measured in the United States. Where the three differ, we take the strictest.
3. What has been done
- Every page can be used with the keyboard alone, and the first thing the Tab key reaches is a link that skips the navigation.
- Focus is always visible: whatever the keyboard is on is drawn with a thick outline.
- Every control has a name that says what it does, including the ones whose shape alone says it to a sighted user — a date box, a remove cross, a drag handle.
- Text and background are checked automatically to at least 4.5:1, in both the light and the dark theme, and the check runs on every change.
- Text can be enlarged to 200% without losing content, and no page scrolls sideways at 390 pixels wide.
- Tables that scroll sideways can be reached and scrolled with the keyboard, and are announced with the caption above them.
- Nothing flashes, nothing moves on its own, and nothing is conveyed by colour alone.
- The app works in six languages, including Hebrew right-to-left, and declares its language so a screen reader pronounces it correctly.
- Every page is checked automatically against WCAG 2.1 AA at two widths and in both themes before it is published, and it is not published while a violation stands.
4. What is known not to be perfect
- The map. The route map is Google's own component. It is supplementary — every stop, address, time and instruction is also in the table above it, which is fully accessible — but the map itself is not under our control and should not be relied on with a screen reader.
- Google's own pages. Payment happens on Lemon Squeezy's pages and the app is served from Google's servers; we do not control the accessibility of either.
- Automated checking has limits. It finds a part of what can be wrong, not all of it. If something is hard to use and this page does not mention it, that is a gap in our knowledge, and we would like to hear about it.
5. Accessibility coordinator
Noam Brand
Email: support@excel-armor.com
Telephone: +972 54 283 7000
Rabbi Averbuch 26, Ramat Hasharon 4740020, Israel
If any part of Navido is hard or impossible for you to use, write and say which page and what happened. We answer within a few working days and will either fix it or tell you honestly when we can.
6. Complaints
If our answer does not satisfy you, you may complain to the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice in Israel, or to the equivalent body in the country you live in.