Sample audit and re-test report
This is what you get after a full audit and remediation: what we tested, how, what we found, what changed and what’s still open. Open any finding to see the evidence and the fix.
Report summary
- Site
- northgatehomeservices.example
- Client
- Northgate Home Services (fictional plumbing and HVAC company)
- Tested
- September 8–10, 2026
- Re-tested
- October 2, 2026
- Benchmark
- Selected WCAG 2.2 Level A and AA success criteria applicable to the pages in scope
In scope
- Home
- Services
- Book a visit (form and date picker)
- Contact
- Site header, footer and cookie banner
Not in scope
- Online payment page hosted by the payment provider
- PDF price sheets
- Pages not listed in scope
How we tested
- Automated checks with axe-core on every page in scope
- Keyboard-only testing in Chrome and Safari
- Screen readers: NVDA with Firefox (Windows), VoiceOver with Safari (macOS and iOS)
- Zoom to 200% and reflow at 320 CSS pixels wide
- Manual review of contrast, headings, link text and form errors
11 confirmed issues
7 found only by manual testing
8 fixed and re-tested
3 open or third-party
Findings
Showing 11 of 11 findings.
- How it was found
- Found in manual testing
- What we observed
- On screens narrower than 1024px the menu toggle is a <div> with a click handler. Tab skips it and Enter does nothing, so keyboard users can’t reach any page except the one they’re on.
- Who it affects
- Keyboard users, switch users and many screen-reader users on tablets and small laptops.
- WCAG
- 2.1.1 Keyboard (A); 4.1.2 Name, Role, Value (A)
- Recommended fix
- Use a real <button> with aria-expanded and aria-controls, and move focus into the menu when it opens.
- Code
Before
<div class="menu-toggle" onclick="toggleNav()">☰</div>After
<button class="menu-toggle" aria-expanded="false" aria-controls="site-nav">Menu</button>- Re-test, October 2
- Fixed. Menu opens with Enter and Space; state is announced as expanded/collapsed in NVDA and VoiceOver.
- How it was found
- Found in manual testing
- What we observed
- The theme stylesheet sets outline: none on every element. While tabbing, there is no indication of which link or field is active.
- Who it affects
- Anyone navigating with a keyboard, including many people with motor disabilities.
- WCAG
- 2.4.7 Focus Visible (AA)
- Recommended fix
- Remove the global reset and add a high-contrast :focus-visible style that works on both light and dark sections.
- Code
Before
*:focus { outline: none; }After
:focus-visible { outline: 3px solid #1a1a1a; outline-offset: 2px; box-shadow: 0 0 0 6px #ffd02b; }- Re-test, October 2
- Fixed. Focus visible on all interactive elements in scope, including the dark footer.
- How it was found
- Detected automatically, manually confirmed
- What we observed
- Seven fields use placeholder text as their only label. The text disappears on typing, and two fields have no accessible name at all.
- Who it affects
- Screen-reader and voice-control users; people who lose track of what a field asked for.
- WCAG
- 1.3.1 Info and Relationships (A); 3.3.2 Labels or Instructions (A); 4.1.2 Name, Role, Value (A)
- Recommended fix
- Add visible <label> elements tied to each field and keep placeholders as optional hints.
- Re-test, October 2
- Fixed. All fields have visible, programmatically associated labels.
- How it was found
- Detected automatically, manually confirmed
- What we observed
- Six photos showing the work for each service have no alt attribute. Screen readers read the file names, such as “DSC_0412 dot jpg”.
- Who it affects
- Blind and low-vision visitors using screen readers.
- WCAG
- 1.1.1 Non-text Content (A)
- Recommended fix
- Add short descriptions to the four informative photos; mark the two decorative ones with alt="".
- Re-test, October 2
- Fixed.
- How it was found
- Detected automatically, manually confirmed
- What we observed
- White text on the light orange “Book a visit” button measures 2.4:1. Footer links measure 3.1:1.
- Who it affects
- People with low vision, older visitors, anyone on a phone outdoors.
- WCAG
- 1.4.3 Contrast (Minimum) (AA)
- Recommended fix
- Darken the brand orange for buttons to #B4470F (4.9:1 with white) and footer link color to #C9D3DF.
- Re-test, October 2
- Fixed. All text in scope measures at least 4.5:1.
- How it was found
- Found in manual testing
- What we observed
- The embedded scheduling widget’s calendar responds only to mouse clicks. Arrow keys and Tab don’t move between dates.
- Who it affects
- Keyboard and screen-reader users can’t choose a visit date, which blocks booking.
- WCAG
- 2.1.1 Keyboard (A)
- Recommended fix
- The widget is hosted by the vendor, so its code can’t be changed. We added a text “preferred date” field as an alternative path and sent the vendor a written issue report.
- Re-test, October 2
- Workaround verified: booking can be completed by keyboard. The vendor widget itself is unchanged.
- How it was found
- Found in manual testing
- What we observed
- Until dismissed, the fixed cookie banner covers the bottom 30% of the screen. Tabbing moves focus behind it, out of sight.
- Who it affects
- Keyboard users, and people using screen magnification.
- WCAG
- 2.4.11 Focus Not Obscured (Minimum) (AA)
- Recommended fix
- Place the banner first in the focus order and reserve page space for it instead of overlaying content.
- Re-test, October 2
- Fixed.
- How it was found
- Found in manual testing
- What we observed
- At 400% zoom (320 CSS pixels wide), the four-column pricing table extends past the screen and each row has to be scrolled horizontally.
- Who it affects
- People who zoom in to read, especially on smaller laptops.
- WCAG
- 1.4.10 Reflow (AA)
- Recommended fix
- Restructure the table as stacked plan cards below 40em wide, keeping a real table on larger screens.
- Re-test, October 2
- Open. Scheduled for the owner’s planned pricing update; workaround not needed for other content.
- How it was found
- Found in manual testing
- What we observed
- Eight links are labeled “Learn more”. In a screen reader’s list of links they are indistinguishable.
- Who it affects
- Screen-reader users scanning links; voice-control users.
- WCAG
- 2.4.4 Link Purpose (In Context) (A)
- Recommended fix
- Rename to the destination, for example “Learn more about water heater repair”, or add visually hidden text.
- Re-test, October 2
- Fixed.
- How it was found
- Detected automatically, manually confirmed
- What we observed
- The home page starts with an <h3> and has no <h1>. Section titles are styled text rather than headings.
- Who it affects
- Screen-reader users who navigate by headings.
- WCAG
- 1.3.1 Info and Relationships (A)
- Recommended fix
- Make the hero title the <h1> and mark section titles as <h2> in order.
- Re-test, October 2
- Open. Waiting on content edits in the CMS by the owner’s team; instructions provided.
What the report says about itself
Every report ends with a plain statement of its limits. For this one: results apply to the pages and features listed above, as they existed on the re-test date. Content, plugins or features added later weren’t tested. The report describes technical findings against WCAG criteria. It isn’t legal advice or a certification of legal compliance.