What the issue log looks like
Below is an excerpt in the exact format you receive (the full deliverable is an Excel workbook plus a PDF executive summary and a drafted accessibility statement).
Sample data. These rows come from our deliberately-broken
test site — the one our pipeline is tested against — not from a real client. Client data
never appears in marketing.
| # | Page | Issue | WCAG | Severity | Who it locks out | How to fix | Verification stamp |
|---|---|---|---|---|---|---|---|
| 1 | /index.html | Keyboard focus gets trapped in the newsletter widget | 2.1.2 No Keyboard Trap | critical | Keyboard users get stuck and cannot reach the rest of the page at all. | Ensure Tab/Shift+Tab can leave the component; close on Escape and return focus to the trigger. | ✓ Verified — pressed Tab 21× from page top; focus cycled between 2 elements for 12 consecutive stops. 2026-07-12 |
| 2 | /index.html | Image has no text alternative | 1.1.1 Non-text Content | critical | Blind users hear "image" or the file name instead of what the picture shows. | Add alt="…" describing the image's purpose; decorative images get alt="". | ✓ Verified — every accessible-name source re-inspected (alt, aria-label, aria-labelledby, title): none present. 2026-07-12 |
| 3 | /index.html | Promo text has insufficient contrast | 1.4.3 Contrast (Minimum) | serious | Low-vision users (and anyone on a phone in sunlight) cannot read this text. | Darken the text or lighten the background to reach 4.5:1. | ✓ Verified — recomputed from rendered styles: 2.81:1 measured, 4.5:1 required (16px/400). 2026-07-12 |
| 4 | /index.html | "Order pickup" control cannot receive keyboard focus | 2.1.1 Keyboard | serious | Keyboard users cannot reach or operate this control — it only works with a mouse. | Add tabindex="0" plus Enter/Space handlers — or use a native <button>. | ✓ Verified — element.focus() invoked; focus refused to move to the element. 2026-07-12 |
| 5 | /index.html | Links show no visible focus indicator | 2.4.7 Focus Visible | serious | Sighted keyboard users cannot see where they are on the page. | Remove outline:none, or add a clearly visible :focus style. | ✓ Verified — viewport screenshots byte-compared unfocused vs focused: no pixel changed. 2026-07-12 |
| 6 | /contact.html | Form fields have no labels | 4.1.2 Name, Role, Value | critical | Screen-reader users reach the field and hear nothing about what to type in it. | Associate a visible <label for="…"> with each field; placeholders are not labels. | ✓ Verified — label association, aria attributes, and title re-inspected: no name source found. 2026-07-12 |
| 7 | /menu.html | List contains invalid child markup | 1.3.1 Info and Relationships | serious | Screen readers announce wrong item counts, so users skip or repeat content. | Only <li> elements may be direct children of <ul>/<ol>. | ✓ Verified — list children re-inspected in the live DOM: non-<li> child present. 2026-07-12 |
What accompanies the log
- Evidence folder — an annotated screenshot per finding (the element outlined on the page).
- Summary worksheet — live counts by severity, status, and page; methodology and disclaimer built in.
- "Not reproduced" worksheet — everything the scanner claimed that our re-execution ruled out. We show that too.
- Executive summary (PDF) — top risks and a 0–14 / 30 / 60-day remediation plan.
- Drafted accessibility statement — W3C format, placeholders for your details.