Accessibility

The standard we hold to

antchambers.com targets WCAG 2.1 Level AA. Every published page is tested against it automatically, and the build is expected to be clean before a deploy.

We say “targets” rather than “complies” deliberately. Automated testing catches only some of what WCAG covers; other requirements need judgement and real users. Clause 03 says where we currently stand on that.

How we check

A Playwright suite runs axe-core against every route on this site, at desktop and mobile viewports, in both cases with reduced motion requested. Beyond the automated rule set it asserts specific behaviours that are easy to break and easy to miss:

• Every page carries one h1 and a coherent heading order.
• Interactive controls on mobile meet the 44 by 44 pixel target.
• The product tour tabs respond to arrow, Home and End keys.
• The mobile menu closes on Escape and returns focus to the control that opened it.
• Pages reflow at 320 CSS pixels without the page scrolling sideways.
• The homepage keeps its content and controls at 200% text size.
• Required form fields are identified without submitting the form.

The suite covers twenty-one public routes. Run npm run test:a11yin the repository to reproduce the checks. Automated results do not establish complete WCAG conformance or replace testing with assistive-technology users.

What we know is imperfect

Stated plainly, because a statement listing no shortcomings is not a statement.

• We have not tested with real assistive-technology users. The suite is automated and our own manual checks are not the same thing as somebody navigating this site with a screen reader they use every day.
• The pricing examples table scrolls sideways inside its own container on narrow screens. Its three columns compare users, annual subscription and first-year total. The container can be focused and scrolled with the keyboard; the base price, setup fee and extra-user price also appear outside the table.
• The enquiry forms hand off to your email application. That means the experience after preparing an enquiry is your mail client's, not ours, and we cannot make promises about it.
• No formal third-party audit has been carried out. When one is, we will say who did it and what they found.

The product, as distinct from this site

This statement covers antchambers.com, the marketing site. The AntChambers application itself is a separate codebase with its own interface, and the testing described in clause 02 does not extend to it.

If accessibility in the application matters to your firm — and for a system every fee earner uses daily it should — raise it during evaluation and we will answer specifically rather than in general terms. Conflating the two would be the easy thing to do here and would not survive contact with your first user.

Telling us it did not work

If something on this site was difficult or impossible to use, please tell us atsupport@antchambers.com. What helps: the page, what you were trying to do, and what you use to browse — a screen reader and its version, keyboard only, magnification, whatever applies.

We aim to acknowledge within two business days and to tell you what we can fix and by when. Where we cannot fix something quickly, we will offer another way to get what you needed — the information on any page here is also available by writing tosales@antchambers.com.