# Accessibility on our own website

> Automated accessibility checks on our sitemap pages, the findings and fixes recorded since September 2026, and the tests that still need people.

Source: https://lastdoorsolutions.com/work/accessibility-audit

## Why our own site

A buyer in government, health or a nonprofit often has to show that a supplier's work meets WCAG 2.1 AA and Section 508. The first proof we can offer is our own website, checked the way we check a client's.

## What the checks do

Three release checks and a separate report load each sitemap page in a browser. The gate fails a release on any WCAG 2.1 AA or Section 508 violation that axe-core can find. The separate report tests additional AAA and WCAG 2.2 AA rules without blocking a release. Two checks of our own inspect page structure and Chrome’s accessibility tree. They check names, roles and order, rather than listening to a screen reader.

## What they cannot test

Machines test only part of WCAG. No check here drives a whole task by keyboard, zooms a page to 400%, submits a form with errors, or tests the reduced-motion setting. Nor does this page rest on a test by a person using a screen reader, or on an independent audit. [Our accessibility statement](/accessibility) says the same, and lists what is tested.

## What a client receives

An audit for a client is a fixed-scope first step. It brings a senior review of the website or product, a written report with prioritised actions, and a follow-up session with the team. It is one of three audits on [our consulting page](/services/consulting), and if the client goes on to build with us, the fee is credited against that work. [Read a sample report, written about this website](/work/accessibility-audit/report).