If this site gets in your way, that is our problem to fix, not yours to work around.

We aim at the recognized standard, we are not fully there, and we will tell you where we fall short.

Our target is WCAG 2.2 Level AA, the technical standard the US Department of Justice points to for public-facing websites. Most of the site meets it. A handful of things do not yet, and they are listed on this page by name rather than hidden behind a promise of continuous improvement.

If you hit a barrier, email [email protected]. You will get a reply from Gabriel, usually within one business day, and if the barrier stops you reaching the practice he will simply carry the conversation on by email instead.

WCAG 2.2 Level AA, across every public page.

Why Level AA. The Web Content Accessibility Guidelines are the standard the rest of the world measures against, and Level AA is the tier that regulators and enterprise buyers ask for.

Areas it checks. It covers the things that decide whether a site is usable: keyboard access without a mouse, sufficient colour contrast, text alternatives for images, content that works with a screen reader, and respect for a visitor who has asked their system to reduce motion.

We treat that standard as a floor for the whole public site, not only the contact form. We do not claim full conformance today, because we have not finished. Claiming it before it is true would be exactly the kind of statement this practice exists to argue against.

The parts that were built for this from the start.

• Keyboard navigation. Every page can be moved through with the Tab key, the focus outline is always visible, and a "skip to content" link lets you jump past the menu. The section tabs move with the arrow keys, as their announcement promises.
• Reduced motion. If your system is set to reduce motion, the opening animation is skipped entirely and the scrolling effects, the moving band, and the animated demonstrations all stop. The site does not override that setting.
• Touch targets. Buttons, links, and sliders are sized above the standard's minimum, so they do not demand fine pointer control.
• The contact form. Every field has a real label, the fields autofill correctly, the dialog keeps focus inside it while open, and closing it returns you to where you were. Hidden until opened. While it is closed it is not on the page at all, so you can never land in it by accident. Error messages. If something is missing, the reason is attached to the field itself.
• Structure. Pages use real headings and landmarks, so a screen reader can jump between sections instead of reading everything in order. Collapsed answers and case-study details are out of the reading order until you open them.
• Colour contrast. All text meets the standard's minimum contrast against its background, including small links, labels, and the numbers in the side menu.
• The intro video. It carries English captions, and the full transcript sits under the player.

The list we are working from, in plain terms.

A full review of the site in September 2026 found eleven problems. Eight have since been fixed and are described in the section above, along with a colour-contrast problem found afterwards. These three remain. This list shrinks as fixes land, and it is checked whenever anything on the site changes.

• The calculator still demonstrates itself with a mouse. Shortly after that section comes into view, a slider moves on its own to show how it works. When it stays still. It no longer runs on a touch screen, for anyone navigating by keyboard, or while you are working in that section, and it stops the moment you touch any control. What still moves. With a mouse it is still a control moving without you asking for it.
• The moving phrase band has no pause button. It runs continuously. It stops while you hover or focus it, and it does not run at all if your system is set to reduce motion, but there is no visible control to stop it.
• The site still needs JavaScript for the contact form. If scripts are blocked, the buttons do nothing. The page now says so and gives the email address instead, and the address in the footer works regardless. It reaches the same person.

One address, one person, and a real answer.

Email [email protected] with whatever detail you have. What helps most: the page you were on, what you were trying to do, what happened instead, and the browser or assistive technology you were using. None of that is required. "The contact form does not work with my screen reader" is a perfectly good report.

You never have to get through the website to reach the practice.

Ask for help. Everything the site offers is available another way. If a page, a form, or a document is unusable for you, email [email protected] and say what you need.

Other formats. Content can be sent as plain text, read out on a call, or provided in another format.

The first call. The introductory conversation the site keeps offering is a phone or video call anyway; the form is only one way of asking for it.

A full review, then a check on everything that ships after it.

The site was reviewed against WCAG 2.2 Level AA in September 2026, page by page, covering keyboard access, screen-reader behaviour, colour contrast, motion, and target sizes. That review produced the list above. Accessibility is now part of the check every change goes through before it goes live, rather than an audit that happens once and then ages.

This is a small practice and we make no claim of a formal third-party certification. What we can offer instead is the list of what is wrong, kept honest and kept current, and a named person who answers when you write.