Skip to content

Accessibility

Accessibility statement

Last updated

We want everyone to be able to use this website, including people who use a screen reader, a keyboard, magnification or voice control. We design and test against the Web Content Accessibility Guidelines (WCAG) 2.1 AA.

What we do

  • Semantic HTML with one h1 per page, landmarks, and a “skip to content” link.
  • Every interactive element is reachable and operable by keyboard and shows a designed, high-contrast focus ring.
  • Touch targets are at least 44 by 44 CSS pixels.
  • Text and interface colours meet the contrast ratios below. An automated check runs before every release and fails the build if any pair drops below its threshold.
  • Icons are decorative and hidden from assistive technology, or carry a text label.
  • Motion is limited to short transitions and stops if you have asked your device to reduce motion.
  • Content, figures and times are rendered on the server, so they are present without JavaScript.
  • Form fields have visible labels, and errors are described in text, not colour alone.

Contrast pairs

UseRatioRequired
Body text on the page18.0:14.5:1
Body text on cards18.8:14.5:1
Secondary text on the page8.6:14.5:1
Secondary text on the alternate surface7.8:14.5:1
Primary button label9.3:14.5:1
Link hover and focus ring on the page8.8:13:1
Text in dark bands18.0:14.5:1
Secondary text in dark bands7.9:14.5:1
Buttons, links and focus ring in dark bands6.0:14.5:1
Form field borders9.0:13:1

Known limitations

  • Some older case-study pages contain dense figure tables that are being restructured for easier reading with a screen reader.
  • The booking page is provided by a third party. We have asked them to confirm its conformance, and you can always contact us to book instead.

Report a barrier

If something on the site does not work for you, email info@aitropolis.com with the page address and what happened. We will reply within 5 working days and, where we can, provide the information in another format.

Questions about this page? Contact us.