ConversionEX
Services
WorkReviewsAboutContact
Last updated July 2026

Accessibility

What we have done to make this site usable for everyone, and how to tell us where we fell short.

Our target

We build to WCAG 2.1 Level AA. We treat that as a floor, not a finish line — and we hold client projects to the same standard.

What is built in

Contrast. Every text colour on this site was contrast-checked against its actual background, compositing any translucent layers in between. Body text clears 9:1 in both themes. The dimmest tier we use for content — stat captions and metric footnotes — measures 4.6:1, above the 4.5:1 AA threshold. Our cyan accent measures 8.0:1 on the brand navy, AAA in both directions.

Keyboard. Everything is reachable and operable by keyboard, in a logical order, with a visible focus ring. There is a skip link to the main content as the first focusable element.

Motion. All entrance animation, the marquee and smooth scrolling are disabled automatically when your system requests reduced motion.

Structure. One h1 per page, headings in order, landmark regions, real <a href> links rather than click handlers, and labelled form fields with descriptive error messages.

Zoom and reflow. The layout reflows to 320px and stays usable at 200% zoom without horizontal scrolling.

Themes. A light theme is available from the header, and your choice is remembered.

Known limitations

Fonts load from Fontshare and Google Fonts; if those requests fail, the site falls back to system fonts and metrics shift slightly. The service × location matrix produces long link lists on some pages — we group them under headings, but they remain long to navigate by screen reader.

The mobile menu closes on Escape and returns focus to the button that opened it, but it does not yet trap focus — tabbing past the last link moves into the page behind it. The desktop navigation uses menu roles without arrow-key support. Both are known and on the list.

Tell us

If something here blocked you, email [email protected] with the page and what happened. We treat accessibility bugs as bugs, not as feature requests, and we will reply within five business days.