דלג לתוכן / Skip to content

Accessibility Statement

Last updated: November 2026

The accessibility work in the game and how to reach us

We work to make GeoPinpoint usable by everyone, including people with disabilities, targeting WCAG 2.2 level AA — the current W3C recommendation — the European standard EN 301 549, Israeli Standard 5568, the European Accessibility Act and the US ADA. This statement lists what is accessible, how each of the six criteria added in 2.2 is handled, the known limitations and how to contact us.

1. Commitment

Accessibility is part of the service, not an add-on. We test the main screens, keyboard navigation and screen-reader announcements, and fix defects we find.

2. Standards applied

  • WCAG 2.2 level AA (the W3C recommendation of October 2023) — the game's primary accessibility target. WCAG 2.1 and 2.0 are subsets of it, so meeting 2.2 AA also meets them.
  • EN 301 549 — the harmonised European standard for accessible digital content and products; today's binding version rests on WCAG 2.1 AA, and the game targets the stricter 2.2 AA.
  • Israeli Standard 5568 (built on WCAG 2.0 AA) and the regulations under the Equal Rights for People with Disabilities Law, 5758-1998.
  • The European Accessibility Act (applicable since 28 June 2025) and the EU Web Accessibility Directive.
  • The US ADA, assessed against WCAG 2.1 AA; the game's 2.2 AA target is stricter than that.
  • Our full list of standards — accessibility, privacy, security, performance, search and sharing, bilingual support and engineering quality — is published in the standards document (the "/standards" page, linked from the guide and every page).

3. The six criteria added in WCAG 2.2, and how each is handled

  • 2.4.11 Focus not obscured: every focused control shows a visible ring, and the browser scrolls it into the visible area with margins that keep it clear of the top bar and the bottom navigation.
  • 2.5.7 Dragging movements: the map can be dragged by finger or mouse, and it can equally be moved with the zoom buttons, by clicking the target and with the arrow keys — no action in the game depends on dragging alone.
  • 2.5.8 Target size: a CSS floor of 24×24 px for icon-only buttons and 44×44 px for regular buttons, at every screen width.
  • 3.2.6 Consistent help: on every screen that shows the page navigation, Help sits in the same position and the same order, so it never has to be hunted for again.
  • 3.3.7 Redundant entry: an email address already given at sign-up is never asked for again at the verification-code step.
  • 3.3.8 Accessible authentication: no CAPTCHA and no cognitive test, and pasting a password or verification code is allowed.

4. What is accessible today

  • Full keyboard navigation, including the map controls (pan, zoom, reset, guess), a "skip to main content" link and a visible focus ring on every control.
  • Screen-reader announcements of each round's result, distance and score, with aria-live updates when the game state changes.
  • Text contrast checked against 4.5:1 on the main screens, and touch targets of at least 24×24 px for icon-only buttons.
  • Support for the reduce-motion preference, with looping animations switched off.
  • Full Hebrew and English support, including text direction (RTL/LTR) and the correct page language for screen readers.
  • A text alternative to the map: study mode lists cities and countries with search, so the material can be learned without a visual map.
  • Correct heading structure, image alternatives, and feedback forms with properly linked labels.

5. Known limitations

  • This statement rests on our own testing. We hold no certificate of conformance and have had no audit by a qualified external body, so it describes what was actually checked rather than a formal approval.
  • The map itself is a visual surface: it can be panned and clicked from the keyboard, but pointing precision is lower than with a mouse or touch.
  • Map tiles are third-party images and cannot be read by a screen reader; city names are shown as text above the map.
  • Statistics charts come with numbers and a text summary, but are not fully screen-reader accessible in every browser.
  • Real-time multiplayer depends on the link between players, so some updates are too fast for complete announcements.

6. Accessibility contact

Found an accessibility defect, or need a personal adjustment or a different way to play? Write to shahar@rotshtein.com with the screen, the device and the assistive technology you use. We reply within 30 days and handle a defect according to its severity.

7. Enforcement

If you did not receive an answer, you may approach the Commission for Equal Rights of Persons with Disabilities at the Israeli Ministry of Justice, the national accessibility authority in your EU or UK country, or the route provided by the ADA in the United States.

8. Review

This statement is reviewed with every material interface change, and at least once a year. The update date appears at the foot of this page.

Version 2.2 · November 2026 · shahar@rotshtein.com