Accessibility

We build this site to WCAG 2.1 Level AA. This page is a status report, not a badge — it says what has been done, what has been tested, and what has not.

Last updated 23 September 2026.

What is in place

• Every page starts with a skip link to the main content.
• Headings run in order, and each page has exactly one h1.
• Everything that can be clicked can be reached and operated with a keyboard alone, and the focus outline is never removed — it is a visible two-pixel ring on every interactive element.
• Body text meets the 4.5:1 contrast minimum, and the interface elements meet 3:1, against the background they actually sit on.
• Images carry alternative text. Decorative marks are hidden from screen readers rather than described pointlessly.
• Audio players are standard controls with real labels, so a screen reader announces them as players. Every recording on this site has a full transcript on the page, in text, next to it — not behind a download.
• Status messages — a form saving, a call connecting — are announced through live regions rather than only appearing visually.
• Animation is limited, and everything that moves is switched off for anyone whose system asks for reduced motion.
• Text reflows to a single column at 320 px without horizontal scrolling, and the layout survives 200% zoom.
• The page works with JavaScript disabled, apart from the demos, which are audio and cannot.

What we know is not done

Being specific is more use to you than a compliance claim:

• The site has not been audited by an independent accessibility firm.
• It has been tested with VoiceOver on macOS and with keyboard-only navigation. It has not been tested end to end with JAWS, NVDA or TalkBack.
• The live “Talk to Marlin” demo relies on the browser's speech recognition, which needs a microphone and only works in Chrome. It is a demo, not a route to anything — every function it shows is available by reading the page and using the form.

The phone agent itself

A phone line is an accessible channel, and for a lot of people it is the most accessible one. Two things we do deliberately: the agent does not require touch-tone menu navigation to reach a human, and it will not rush a caller who needs longer to answer. If a caller asks for a person, they get transferred — there is no maze.

The agent is not a TTY/TDD endpoint and does not support relay protocols natively, though relay operators can and do use it as they would any voice line.

If something does not work for you

Tell us and we will fix it. Describe the page and what happened — you do not need to know the technical reason. Use the form on the contact section, and say it is an accessibility problem so it gets looked at first. We aim to reply within two business days.

If we cannot fix something quickly, we will tell you what the workaround is in the meantime rather than leaving you waiting.