Loading sample report…
Sample report
Explore a fictional example showing automated findings, root causes, visual issue evidence, remediation guidance, human-review checks, responsive differences, and professional exports.
The public website scanner is temporarily unavailable while production network controls are verified.
Sample report
This is a fictional example created to demonstrate the type of accessibility findings, remediation guidance and reporting available in Accessible Content Preflight.
See shared patterns instead of duplicate cards per element.
Illustrative highlights with selectors and rule context.
Ordered remediation with read-only status examples.
Guided checks that automation cannot fully decide.
Copy or download a markdown ticket for engineering.
PDF, Excel, CSV, JSON, and evidence ZIP from one dataset.
Prepared for: Northstar Community Library — Fictional Demonstration · March 2026 (demonstration data)
Summary status: Automated issues found · Human review required
Pages reviewed
8
Likely root causes
1
Affected elements (approx.)
35
Human review signals
0
Priority considers serious impact, 7 pages affected, 18 occurrences, likely shared component pattern. This is not a legal-risk rating.
18 element(s) · 7 page(s) · Fix once may improve 18 occurrences across 7 pages
Priority considers critical impact, 2 occurrences. This is not a legal-risk rating.
2 element(s) · 1 page(s) · 2 occurrence(s) on 1 page(s)
Priority considers serious impact, 2 occurrences. This is not a legal-risk rating.
2 element(s) · 1 page(s) · 2 occurrence(s) on 1 page(s)
Priority considers serious impact. This is not a legal-risk rating.
1 element(s) · 1 page(s) · 1 occurrence(s) on 1 page(s)
Priority considers critical impact. This is not a legal-risk rating.
1 element(s) · 1 page(s) · 1 occurrence(s) on 1 page(s)
Illustrative visual evidence from this fictional sample report.
header nav button.menu-togglebutton-nameGrouped patterns — not one card per affected element.
18 occurrence(s) on 7 page(s) · Likely shared component (fix once may resolve many)
Example selectors: header nav button.menu-toggle
2 occurrence(s) on 1 page(s)
Example selectors: #search-input
2 occurrence(s) on 1 page(s)
Example selectors: a[href="/pdf"]
1 occurrence(s) on 1 page(s)
Example selectors: footer .secondary-link
1 occurrence(s) on 1 page(s)
Example selectors: form.membership #email
1 occurrence(s) on 1 page(s)
Example selectors: form.membership #zip
1 occurrence(s) on 1 page(s)
Example selectors: main img.hero-card
1 occurrence(s) on 1 page(s)
Example selectors: #contact-name
Fix once may improve 18 occurrences across 7 pages
Example status: User Marked Fixed
Fix Lab
Button accessible name — deterministic guidance first; AI is optional.
Problem: A button lacks an accessible name.
Why: Assistive technology needs a name to announce the control's purpose.
User impact: Screen-reader users may encounter a button without knowing what action it performs.
<button type="button">Open menu</button>
<!-- or -->
<button type="button" aria-label="Open menu">…</button>Before
<button type="button"><svg aria-hidden="true">…</svg></button>After
<button type="button" aria-label="Open menu"><svg aria-hidden="true">…</svg></button>Common mistakes: Do not rely on icon-only buttons without aria-label or visible text.
Sample AI-Assisted Guidance
Static example — no live OpenAI call.
Icon-only controls in the shared header may not expose a meaningful accessible name.
How to verify
2 occurrence(s) on 1 page(s)
Example status: User Marked Fixed
Fix Lab
Form field label — deterministic guidance first; AI is optional.
Problem: A form control does not have an associated visible or programmatic label.
Why: Users need to know what to enter and which field has focus.
User impact: Screen-reader and voice-input users may not know what information a form field expects.
<label for="email">Email</label>
<input id="email" name="email" type="email">Before
<input type="text" placeholder="Email">After
<label for="email">Email</label><input id="email" type="email" name="email">Common mistakes: Do not rely on placeholder text alone as the only label.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
2 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Link accessible name — deterministic guidance first; AI is optional.
Problem: A link has no discernible accessible name.
Why: Link lists and screen readers read the name without surrounding context.
User impact: Users navigating links out of context may not understand the link destination or purpose.
<a href="/pricing">View pricing</a>Before
<a href="/details"><span class="icon-arrow"></span></a>After
<a href="/details">View product details</a>Common mistakes: Avoid vague link text like "click here" without context.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Text color contrast — deterministic guidance first; AI is optional.
No detailed template yet for this rule. Use axe documentation and verify manually after fixing.
How to verify
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Form field label — deterministic guidance first; AI is optional.
Problem: A form control does not have an associated visible or programmatic label.
Why: Users need to know what to enter and which field has focus.
User impact: Screen-reader and voice-input users may not know what information a form field expects.
<label for="email">Email</label>
<input id="email" name="email" type="email">Before
<input type="text" placeholder="Email">After
<label for="email">Email</label><input id="email" type="email" name="email">Common mistakes: Do not rely on placeholder text alone as the only label.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Form field label — deterministic guidance first; AI is optional.
Problem: A form control does not have an associated visible or programmatic label.
Why: Users need to know what to enter and which field has focus.
User impact: Screen-reader and voice-input users may not know what information a form field expects.
<label for="email">Email</label>
<input id="email" name="email" type="email">Before
<input type="text" placeholder="Email">After
<label for="email">Email</label><input id="email" type="email" name="email">Common mistakes: Do not rely on placeholder text alone as the only label.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Image alternative text — deterministic guidance first; AI is optional.
Problem: An image is missing alternative text or has an empty alt.
Why: Non-visual users cannot perceive information conveyed by the image.
User impact: People who cannot see the image may miss information conveyed visually.
<img src="chart.png" alt="Sales increased 12% in Q3">
<!-- decorative: alt="" -->Before
<img src="logo.png">After
<img src="logo.png" alt="Acme Corporation">Common mistakes: Do not use alt text that repeats nearby visible text without purpose.
How to verify
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Form field label — deterministic guidance first; AI is optional.
Problem: A form control does not have an associated visible or programmatic label.
Why: Users need to know what to enter and which field has focus.
User impact: Screen-reader and voice-input users may not know what information a form field expects.
<label for="email">Email</label>
<input id="email" name="email" type="email">Before
<input type="text" placeholder="Email">After
<label for="email">Email</label><input id="email" type="email" name="email">Common mistakes: Do not rely on placeholder text alone as the only label.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Form field label — deterministic guidance first; AI is optional.
Problem: A form control does not have an associated visible or programmatic label.
Why: Users need to know what to enter and which field has focus.
User impact: Screen-reader and voice-input users may not know what information a form field expects.
<label for="email">Email</label>
<input id="email" name="email" type="email">Before
<input type="text" placeholder="Email">After
<label for="email">Email</label><input id="email" type="email" name="email">Common mistakes: Do not rely on placeholder text alone as the only label.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Isolated occurrence: frame-title — deterministic guidance first; AI is optional.
No detailed template yet for this rule. Use axe documentation and verify manually after fixing.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Link accessible name — deterministic guidance first; AI is optional.
Problem: A link has no discernible accessible name.
Why: Link lists and screen readers read the name without surrounding context.
User impact: Users navigating links out of context may not understand the link destination or purpose.
<a href="/pricing">View pricing</a>Before
<a href="/details"><span class="icon-arrow"></span></a>After
<a href="/details">View product details</a>Common mistakes: Avoid vague link text like "click here" without context.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Link accessible name — deterministic guidance first; AI is optional.
Problem: A link has no discernible accessible name.
Why: Link lists and screen readers read the name without surrounding context.
User impact: Users navigating links out of context may not understand the link destination or purpose.
<a href="/pricing">View pricing</a>Before
<a href="/details"><span class="icon-arrow"></span></a>After
<a href="/details">View product details</a>Common mistakes: Avoid vague link text like "click here" without context.
How to verify
Re-run the scan after fixing, then spot-check with keyboard and a screen reader where relevant.
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Text color contrast — deterministic guidance first; AI is optional.
No detailed template yet for this rule. Use axe documentation and verify manually after fixing.
How to verify
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Text color contrast — deterministic guidance first; AI is optional.
No detailed template yet for this rule. Use axe documentation and verify manually after fixing.
How to verify
1 occurrence(s) on 1 page(s)
Example status: Not Started
Fix Lab
Image alternative text — deterministic guidance first; AI is optional.
Problem: An image is missing alternative text or has an empty alt.
Why: Non-visual users cannot perceive information conveyed by the image.
User impact: People who cannot see the image may miss information conveyed visually.
<img src="chart.png" alt="Sales increased 12% in Q3">
<!-- decorative: alt="" -->Before
<img src="logo.png">After
<img src="logo.png" alt="Acme Corporation">Common mistakes: Do not use alt text that repeats nearby visible text without purpose.
How to verify
Accessibility: Button accessible name
# Accessibility: Button accessible name ## Summary A button lacks an accessible name\. The pattern was detected across 7 scanned page\(s\) and affects 18 element\(s\)\. This appears to be a repeated shared pattern\. Desktop: 13 occurrence\(s\); Mobile: 5 occurrence\(s\)\. ## Accessibility impact **Automated impact:** serious **Remediation priority:** high Screen\-reader users may encounter a button without knowing what action it performs\. ## Scope - Pages affected: 7 - Elements affected: 18 - Potential shared fix: Yes - Likely root cause: Likely shared navigation: Button accessible name - Confidence: high - This appears to be a repeated shared pattern\. ### Representative pages - `/` - `/events` - `/membership` - `/resources` - `/contact` - `/about` - `/news` ## Technical evidence **Rule:** `button-name` **WCAG:** 4\.1\.2 — Level A Representative selectors: 1. `header nav button\.menu\-toggle` 2. `header nav button\.menu\-toggle` 3. `header nav button\.menu\-toggle` Example: ```html <button class="menu-toggle" aria-label=""><svg aria-hidden="true"></svg></button> ``` ## Recommended fix A button lacks an accessible name\. Assistive technology needs a name to announce the control's purpose\. Recommended approach: - <button type="button">Open menu</button> - <!-- or --> - <button type="button" aria-label="Open menu">…</button> Avoid: Do not rely on icon\-only buttons without aria\-label or visible text\. Possible implementation pattern: ```html <button type="button" aria-label="Open menu"><svg aria-hidden="true">…</svg></button> ``` ## Acceptance criteria - [ ] Each affected interactive button exposes an accessible name\. - [ ] The accessible name describes the button's purpose or action\. - [ ] Visible labels and accessible names do not conflict\. - [ ] Decorative icon content is not announced redundantly\. - [ ] The automated \`button\-name\` finding is no longer detected on affected pages after rescan\. - [ ] Relevant keyboard and screen\-reader behavior has been manually reviewed\. ## Verification 1. Implement the change in the shared component or template before editing each occurrence independently\. 2. Inspect the affected control\. 3. Give the button a visible text label or valid accessible name\. 4. Ensure the name communicates the button's purpose\. 5. Re\-run the automated scan\. 6. Test affected controls using keyboard navigation\. 7. Inspect accessible names, labels, or contrast where relevant\. 8. Re\-run the Website Accessibility Scanner on affected pages\. 9. Confirm the \`button\-name\` finding is no longer detected for affected occurrences\. ## Standard reference WCAG 2.2 — 4\.1\.2 — Level A Automated source: axe-core `button-name` ## Scan context - Origin: https://example\.com - Viewport: Desktop \+ Mobile \(compare\) - Scan completed: 2026-03-15T14:05:00.000Z - Verification status: User Marked Fixed - Visual evidence is available in the current scan session \(View on Page\)\. ## Notes / limitations - Automated testing does not replace human accessibility evaluation\. - 18 total affected elements; 3 representative selector\(s\) shown\.
This summary counts criteria by how they are covered in our matrix — not a compliance percentage.
| Criterion | Level | Automation | Automated result | Human review |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | partial | issue_detected | required |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | manual | not_tested | required |
| 1.2.2 Captions (Prerecorded) | A | manual | not_tested | required |
| 1.2.3 Audio Description or Media Alternative | A | manual | not_tested | required |
| 1.3.1 Info and Relationships | A | partial | issue_detected | required |
| 1.3.2 Meaningful Sequence | A | manual | not_tested | required |
| 1.3.4 Orientation | AA | manual | not_tested | required |
| 1.3.5 Identify Input Purpose | AA | partial | no_issue_detected | required |
| 1.4.1 Use of Color | A | manual | not_tested | required |
| 1.4.2 Audio Control | A | manual | not_tested | required |
| 1.4.3 Contrast (Minimum) | AA | partial | issue_detected | required |
| 1.4.4 Resize Text | AA | manual | not_tested | required |
| 1.4.10 Reflow | AA | manual | not_tested | required |
| 1.4.11 Non-text Contrast | AA | partial | no_issue_detected | required |
| 1.4.12 Text Spacing | AA | manual | not_tested | required |
| 1.4.13 Content on Hover or Focus | AA | manual | not_tested | required |
| 2.1.1 Keyboard | A | manual | no_issue_detected | required |
| 2.1.2 No Keyboard Trap | A | manual | not_tested | required |
| 2.1.4 Character Key Shortcuts | A | manual | not_tested | required |
| 2.2.1 Timing Adjustable | A | manual | no_issue_detected | required |
| 2.2.2 Pause, Stop, Hide | A | manual | no_issue_detected | required |
| 2.3.1 Three Flashes or Below Threshold | A | partial | no_issue_detected | required |
| 2.4.1 Bypass Blocks | A | partial | no_issue_detected | required |
| 2.4.2 Page Titled | A | automated | no_issue_detected | not_started |
No automated finding detected does not establish conformance with the criterion.
Progress: 5 of 6 relevant checks reviewed. Keyboard, zoom, and media checks still need human judgment.
Manual review statuses shown below are fictional sample values for demonstration only.
Automated rules cannot reliably determine whether every interactive control is reachable and operable with a keyboard.
Automated checks cannot confirm that focus order matches a meaningful reading sequence.
Automation can detect missing alt attributes but not whether alt text is appropriate in context.
Automated rules cannot fully evaluate error identification, suggestions, and recovery.
Focus management in dialogs requires interactive testing.
Automation cannot verify caption accuracy or whether audio description is needed.
| URL | Title | Viewport | Completeness | Issues |
|---|---|---|---|---|
| https://example.com | Northstar Community Library | Both | complete | 5 |
| https://example.com/contact | Contact — Northstar Community Library | Both | complete | 5 |
| https://example.com/membership | Membership — Northstar Community Library | Both | complete | 3 |
| https://example.com/resources | Resources — Northstar Community Library | Both | complete | 3 |
| https://example.com/news | News — Northstar Community Library | Desktop 1440 × 900 | complete | 3 |
| https://example.com/events | Events — Northstar Community Library | Both | complete | 2 |
| https://example.com/about | About — Northstar Community Library | Desktop 1440 × 900 | complete | 2 |
| https://example.com/services | Services — Northstar Community Library | Desktop 1440 × 900 | complete | 2 |
Illustrative before/after counts from a fictional second scan — not a live rescan on this page.
Navigation accessible names
Before: 12 occurrences · After: 0
Example status: Verified resolved
Form labels
Before: 8 · After: 2
Example status: Partially improved
Mobile viewport
New: 1 mobile-only finding in demo
Resolved: 11 · New: 0 · Still present: 11 · Changed: 2. Fingerprint matching may be imperfect after DOM changes.
Problem: A button lacks an accessible name.
Why: Screen-reader users may encounter a button without knowing what action it performs.
Where: https://example.com, https://example.com, https://example.com/events
Fix: <button type="button">Open menu</button>
Verify: Re-scan after fixing; use checklist in Fix Lab.
18 element(s) affected · showing 3 example(s)
Problem: A form control does not have an associated visible or programmatic label.
Why: Screen-reader and voice-input users may not know what information a form field expects.
Where: https://example.com, https://example.com, https://example.com/membership
Fix: <label for="email">Email</label>
Verify: Re-scan after fixing; use checklist in Fix Lab.
2 element(s) affected
Problem: A link has no discernible accessible name.
Why: Users navigating links out of context may not understand the link destination or purpose.
Where: https://example.com/contact, https://example.com/contact, https://example.com/services
Fix: <a href="/pricing">View pricing</a>
Verify: Re-scan after fixing; use checklist in Fix Lab.
2 element(s) affected
Problem: A form control does not have an associated visible or programmatic label.
Why: Screen-reader and voice-input users may not know what information a form field expects.
Where: https://example.com, https://example.com, https://example.com/membership
Fix: <label for="email">Email</label>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: A form control does not have an associated visible or programmatic label.
Why: Screen-reader and voice-input users may not know what information a form field expects.
Where: https://example.com, https://example.com, https://example.com/membership
Fix: <label for="email">Email</label>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: An image is missing alternative text or has an empty alt.
Why: People who cannot see the image may miss information conveyed visually.
Where: https://example.com/resources, https://example.com/news
Fix: <img src="chart.png" alt="Sales increased 12% in Q3">
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: A form control does not have an associated visible or programmatic label.
Why: Screen-reader and voice-input users may not know what information a form field expects.
Where: https://example.com, https://example.com, https://example.com/membership
Fix: <label for="email">Email</label>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: A form control does not have an associated visible or programmatic label.
Why: Screen-reader and voice-input users may not know what information a form field expects.
Where: https://example.com, https://example.com, https://example.com/membership
Fix: <label for="email">Email</label>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: A link has no discernible accessible name.
Why: Users navigating links out of context may not understand the link destination or purpose.
Where: https://example.com/contact, https://example.com/contact, https://example.com/services
Fix: <a href="/pricing">View pricing</a>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: A link has no discernible accessible name.
Why: Users navigating links out of context may not understand the link destination or purpose.
Where: https://example.com/contact, https://example.com/contact, https://example.com/services
Fix: <a href="/pricing">View pricing</a>
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: An image is missing alternative text or has an empty alt.
Why: People who cannot see the image may miss information conveyed visually.
Where: https://example.com/resources, https://example.com/news
Fix: <img src="chart.png" alt="Sales increased 12% in Q3">
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: Elements must have sufficient color contrast (4.54:1 measured for sample).
Why: Low-vision users may have difficulty reading text when foreground and background colors are too similar.
Where: https://example.com, https://example.com/news
Fix: https://dequeuniversity.com/rules/axe/
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: Accessibility issue detected.
Why: frame-title
Where: https://example.com/services
Fix: https://dequeuniversity.com/rules/axe/
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: Elements must have sufficient color contrast (4.54:1 measured for sample).
Why: Low-vision users may have difficulty reading text when foreground and background colors are too similar.
Where: https://example.com, https://example.com/news
Fix: https://dequeuniversity.com/rules/axe/
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: Elements must have sufficient color contrast (4.54:1 measured for sample).
Why: Low-vision users may have difficulty reading text when foreground and background colors are too similar.
Where: https://example.com, https://example.com/news
Fix: https://dequeuniversity.com/rules/axe/
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Problem: Accessibility issue detected.
Why: heading-order
Where: https://example.com/about
Fix: https://dequeuniversity.com/rules/axe/
Verify: Re-scan after fixing; use checklist in Fix Lab.
1 element(s) affected
Exports are generated in your browser from the same fictional dataset — no signup and no server storage.
Preview workbook structure — download the .xlsx for the full multi-sheet export.
| Pages scanned | 8 |
|---|---|
| Root causes | 1 |
| Total occurrences | 35 |
This sample separates machine-detected issues from guided human-review items. Automated findings come from axe-core rules on rendered pages; human-review sections highlight checks that still need judgment, context, or content decisions.
For how we describe limits, tooling, and review posture across the product, see our methodology page.
This report provides automated, measured, AI-assisted, and human-review accessibility guidance. It is not legal advice, legal certification, or a guarantee of compliance with ADA, WCAG, Section 508, or other accessibility requirements.
Use the same export and fix workflows on your public pages when the scanner is enabled for your environment.
Explore accessibility tools