56 pages passed automated AA checks; seven actions remain.

This report covers our own website, written up the way a client's audit report is. It says what we tested, what the tests found and what was fixed. Then it lists what no test covered, and what to do next, in order. A client's audit also ends in a follow-up session with their team, which a sample page cannot show.

The standards are the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and Section 508, the accessibility rule for US federal technology. Level AAA is the stricter level above AA.

• Site: lastdoorsolutions.com, the 56 pages in its sitemap on 23 October 2026.
• Standards: WCAG 2.1 levels A and AA, and Section 508. Additional AAA and WCAG 2.2 AA rules are reported alongside, without blocking a release.
• Method: four automated checks, each loading every page in Chrome at 1440 by 900 pixels.
• Not in scope: the pages outside the sitemap, and anything listed under "Not tested" below.

All four checks ran on the 56 sitemap pages on 23 October 2026. Passing these checks does not establish full WCAG or Section 508 conformance.

• The gate, WCAG 2.1 A and AA and Section 508, tested with axe, an open-source testing engine: 0 violations.
• The additional report, automated AAA and WCAG 2.2 AA rules, including enhanced contrast: no findings.
• Page-structure rules, for landmarks, headings, link and button names, focus and labels: 0 findings.
• Reading order, names, roles and sequence in Chrome's accessibility tree: 0 findings.

A change that fails the gate, the page-structure rules or the reading-order check does not go live.

• 6 September 2026: 2 colour contrast failures, at 3.14:1 and 4.08:1. Both raised the same day, to 5.80:1 and 5.11:1.
• 9 September: duplicated headings in the accessibility tree, a logo outside the keyboard path, and a skip link detected as absent. All three fixed in the same change.
• 9 September: 315 faults on 46 pages, including 174 unnamed figures, 47 unnamed forms and 26 unnamed tables. Figure wrappers were made presentational, and forms and tables were named.
• 22 to 23 September: the checks did not run for 2 days, and animation work brought back 3 faults. Fixed, and every check now waits for the opening animation to finish.
• 17 October: 19 AAA failures, all small text below 7:1. Each colour moved to a darker shade already in the colour system, at 7.37:1 and 8.98:1.
• 23 October: 1 AAA finding, a blog label at 5.07:1. Changed to slate, at 8.98:1.

Automated checks cover only part of WCAG. None of these rest on a check today:

• A person using a screen reader, such as VoiceOver or NVDA, by hand.
• A whole task by keyboard alone, such as filling in and sending the contact form.
• Form errors: what a screen reader announces when a form is sent with a mistake.
• Zoom and reflow: pages at 200% and 400%, and at 320 pixels wide.
• Reduced motion: the site's own control and the device setting.
• Contrast in other states: hover, focus and the dark sections are tested only as they first load.
• The access pages, which sit outside the sitemap.
• What a machine cannot judge: whether alt text means the right thing, or whether a link makes sense in its sentence.
• An independent audit, or an Accessibility Conformance Report (ACR), the report written on the VPAT template that procurement teams use.

The order follows who would be shut out, and where.

1. Fill in and send every form by keyboard alone, and with mistakes in it. The contact, newsletter and access forms are how anyone reaches us, and no check drives them from start to finish.
2. Test the home page, the contact form and the work list with VoiceOver and NVDA. A person hears what the checks only read.
3. Check every page template at 200% and 400% zoom, and at 320 pixels wide. A reader who zooms in meets a different layout, and the checks run at one width.
4. Add the access pages to the checks. A buyer who asks to see protected work passes through them.
5. Test the reduced-motion control and the device setting on the animated pages. Motion can make a page unusable for some readers.
6. Measure contrast on hover, on focus and in the dark sections. The checks see each page only as it first loads.
7. Write an Accessibility Conformance Report for the site. Procurement teams ask for one. It records how the site meets each criterion, and changes nothing for a visitor, so it comes last.

For a client, the same report covers their website or product, and a follow-up session takes their team through the actions. The audit is fixed in scope, and if the client goes on to build with us, the audit fee is credited against that work. See the audit on our consulting page.