Skip to main content
Contact
Sample audit report

What we tested, fixed and still need to verify.

A sample of the report our accessibility audit delivers, written about our own website. It retains the 23 October automated results and adds a scoped browser review from 27 October 2026.

About this report

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. It distinguishes automated rules, browser interaction checks and the verification still needed from people. 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.

Scope

  • 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.
  • Historical exclusions: pages outside that sitemap and human interaction tests. The separate 27 October sample below includes the public access-request page.

Results

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.

Found and fixed

  • 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.

Browser interaction review, 27 October 2026

We checked nine public routes in Chrome: Home, Contact, Access request, Work, TraqIT, Anchor Wave, Content & SEO, the WCAG 2.2 article and this report. These are scripted browser observations and scoped interface checks, not a person’s screen-reader assessment.

  • Target size: the axe target-size rule returned no violations or incomplete results on the nine routes at desktop and phone widths. This measures the initial page states, not every later interaction.
  • Keyboard focus: sequential Tab traversal at 1440 by 900 and 390 by 900 pixels, with reduced motion enabled, found no fully hidden focused control after scrolling settled. This covers the sampled page states, not every possible interaction.
  • Phone menu: Escape originally closed the menu while leaving focus on a hidden navigation link. The correction returns focus to Menu. Local checks passed on Home, Contact and the WCAG article.
  • Form errors: invalid contact input exposed field-linked errors. The access form lacked those links; its errors now identify each field, including the confidentiality checkbox. Invalid access and newsletter submissions now focus the field needing attention. Desktop and phone checks passed for repeated errors and retained values.
  • Repeated entry: name, email, company, message and the chosen service survived switching the contact form from project to partnership and back. Invalid access submissions retained their entered values.
  • Reflow: the nine sampled routes had no document-level horizontal overflow at 320 CSS pixels. This width check is separate from physical browser zoom and a person checking whether the layout remains usable.
  • Help and dragging: the sample retained its header and footer contact routes. No authored drag-only control was found on Home, Work, TraqIT or Anchor Wave; the homepage capability choices use buttons.
  • Access: the request fields and password-free explanation were inspected. No protected story was opened, and no approved email-link journey was completed.

Only invalid local submissions were used for error-response tests. No enquiry, access request or newsletter subscription was delivered. These results do not establish full WCAG conformance.

Still awaiting human verification

  • Screen-reader listening: complete the sampled tasks with VoiceOver and NVDA, including error announcements, focus changes and the confidentiality checkbox.
  • Successful journeys: send an intended contact enquiry, subscribe with an authorised address and complete an approved email-link access journey. Confirm the responses and that information is not unnecessarily requested again.
  • Zoom and visual states: verify physical 200% and 400% browser zoom, focus visibility, state contrast and the meaning of images and links. A 320-pixel width result covers only part of this review.
  • Motion: verify comfort and usability with the site control and device preference on the pages containing transitions. The logo’s two reduced-motion settings have been checked separately; that is not a whole-site motion verdict.
  • Complete assessment: extend the sample to all relevant templates, states and processes before a conformance claim. No independent audit or Accessibility Conformance Report has been issued.

Next actions

  1. Verify the corrected phone menu and invalid forms using a keyboard and a screen reader.
  2. Complete the intended successful form and approved access journeys, recording the browser, assistive technology, pages and date.
  3. Finish zoom, contrast, motion and content-meaning review across the remaining templates and states.
  4. Assess each applicable criterion and its evidence before preparing an Accessibility Conformance Report. A clean automated result alone is insufficient.

What a client receives

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.

Get an accessibility report for your website.

Tell us the site and the standard you have to meet. We will say what the audit would cover.

Ask about an accessibility audit