EntryAtlas
Check a journey

EntryAtlas / Accessibility

Travelplanningshould stayusable.

EntryAtlas is designed to be usable by as many people as possible, in as many situations as possible. We follow international accessibility standards and test, learn, and improve continuously.

Accessibility at a glance

Built for different ways of browsing.

Continuous review

Accessibility is part of the interface, not an extra layer added afterwards.

Keyboard ready

Navigate core tools without a mouse.

Zoom & reflow

Content adapts at up to 400% zoom.

Checked contrast

Readable colours in light and dark mode.

Motion choice

Reduced-motion preferences are respected.

AA
WCAG 2.2Target: Level AA

We design and test around the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA principles.

Learn more

How we make EntryAtlas accessible

Keyboard

Full keyboard support for navigation and all interactive features.

Reflow & zoom

Content reflows and adapts across devices and at up to 400% zoom.

Focus

Visible focus states show where you are on the page at all times.

Contrast

Strong colour contrast supports readability in every environment.

Reduced motion

We respect reduced motion preferences to minimise distractions.

Language & direction

Clear language and multilingual support help more travellers feel at home.

Current status

WCAG 2.2 AA is the target.

We're committed to making EntryAtlas usable for everyone, everywhere. We follow WCAG 2.2 Level AA and test across real-world scenarios to find issues early and fix them.

What we support

  • Skip navigation and landmark regions.
  • Keyboard-operable navigation, selectors and filters.
  • Visible focus indicators and controls sized for touch and pointer.
  • Responsive layouts that reflow without horizontal scrolling.
  • Clear text and interface colours chosen to meet contrast requirements.

What we test

  • Automated testing for colour contrast, semantics and ARIA usage.
  • Cross-device and browser testing including zoom up to 400%.
  • Screen-reader-oriented checks for headings, landmarks, labels and announcements.
  • Manual keyboard testing across core flows, with assistive-technology verification for complex interactions.

What still requires manual verification

  • Complex data tables and map interactions.
  • Embedded third-party content.
  • Edge cases across assistive technologies and configurations.

Need help or found a barrier?

We're here to help. Let us know what you were trying to do and where you encountered a problem.

entryatlas.co.uk@gmail.com

Accessibility review: 12th August 2026.

Help us keep EntryAtlas accessible.

Report barriers, share feedback, or check travel guidance that fits your needs.