Proof, not policy
Accessibility conformance — this site
Standard: WCAG 2.1 Level AA. Last verified 16 August 2026. Every figure below is a measurement, not a target.
Conformance claim
This site conforms to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. The claim covers every page on this domain, in the state published on 16 August 2026. There are no excluded pages, no excluded content types, and no third-party content on any page at all.
We sell accessibility conformance work. Publishing our own conformance report — with the measurements and the limitations — is the only version of that claim you should accept from anybody, including us.
How it was tested
Automated testing alone is not sufficient to establish conformance, and no honest conformance statement rests on it. The US Department of Justice has said the same in the rulemaking behind the ADA Title II web rule, noting that automated remediation tools lack sufficient reliability for complex content. Automated tools catch a minority of the success criteria; the rest require a person.
Automated
- axe-core via the command line, run against every route on every build. A non-zero violation count fails the build and the site does not deploy.
- Lighthouse accessibility, performance, best-practices and SEO categories, with thresholds enforced as release gates.
- Contrast validation of every colour token against every surface it can appear on, in both light and dark schemes — not against white only.
Manual
- Keyboard-only traversal of every page: full reachability, no traps, a visible focus indicator throughout, and a skip link first in tab order.
- Screen reader testing with NVDA on Windows and VoiceOver on macOS, covering the homepage and the service page.
- JavaScript disabled: every page is fully readable and fully operable, including the enquiry form, which is plain HTML and submits without a line of script.
- Reduced motion and 200% zoom, plus reflow at 320px with no horizontal scrolling of the page body.
Verified results
Measured on 16 August 2026 against the live site, not a local copy. Lighthouse figures are the median of repeated runs, discarding any run where Lighthouse's own host-speed index showed the measuring machine was degraded — an overloaded machine scores a static page badly and that would be our measurement error published as your information. These figures are stored in the repository and re-checked on every build: if a number here stops matching what the tooling reports, the build fails rather than the page going quietly stale.
| Measure | Result | Threshold | Status |
|---|---|---|---|
| axe-core violations | 0 | 0 | Pass |
| Lighthouse accessibility | 100 | 100 | Pass |
| Lighthouse performance | 98 | ≥ 98 | Pass |
| Lighthouse best practices | 100 | ≥ 98 | Pass |
| Lighthouse SEO | 100 | ≥ 98 | Pass |
| Largest Contentful Paint | 1.30s | < 1.80s | Pass |
| Cumulative Layout Shift | 0.000 | < 0.050 | Pass |
| Homepage transfer weight | 10 KB | < 150 KB | Pass |
| Client-side JavaScript on the homepage | 0 bytes | 0 | Pass |
| Cookies set | 0 | 0 | Pass |
Known limitations
An empty limitations section reads as untested. These are the real ones.
- Enquiry form errors are reported on a separate page, not beside the field that caused them. With no JavaScript on the site there is no way to surface a validation message inline, so a rejected submission lands on a page that explains what happened and gives the email address instead. That is a worse experience than inline errors, and we would rather name it than let the word "accessible" imply we had solved it.
- Screen reader testing covers NVDA and VoiceOver. JAWS, TalkBack and Narrator have not been tested on this site. That is a real gap and we would rather state it than let the phrase "screen reader tested" imply more than it does.
- Automated coverage is partial by nature. axe-core reliably detects a minority of WCAG success criteria. Zero violations means zero detected violations, not zero violations, which is why the manual pass above exists and why this sentence is here.
Tell us if something is wrong
If any part of this site is difficult or impossible for you to use, email info@anthropicusa.com. Tell us the page and what happened — your assistive technology and browser help but are not required.
We will respond within five business days with either a fix or a date for one. That commitment is the part of an accessibility statement that actually matters and the part most of them leave out.
Need this for your own site?
Accessibility conformance work opens as a second service line. If you have an ADA Title II deadline, email us and we will tell you honestly whether we can help by then.