Website Accessibility Scanner — Sample Report
Automated Document Object Model (DOM) scanning helps teams prioritize remediation and never establishes conformance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA on its own. Epic Scanner lists and observes rendered pages across four screen sizes; a human auditor verifies and decides. For example, a scan can find an embedded video player, but it cannot judge whether its captions are accurate.
Automated Scan Results — Northstar Civic Portal
14 of 148 pages found were scanned; pages that weren’t scanned weren’t checked. The scanner reports raw axe-core observations only—it never shows Pass, Fixed, “compliant”, or a score.
| Ring & Segment | Count | Share |
|---|---|---|
| Outer: Violations | 14 | 70% |
| Outer: Needs review | 6 | 30% |
| Middle: WCAG (site’s own) | 11 | 55% |
| Middle: WCAG (third-party) | 3 | 15% |
| Middle: Best practices (site’s own) | 4 | 20% |
| Middle: Best practices (third-party) | 2 | 10% |
| Inner (violations only): Critical | 3 | 21% |
| Inner (violations only): Serious | 6 | 43% |
| Inner (violations only): Moderate | 4 | 29% |
| Inner (violations only): Minor | 1 | 7% |
The inner ring counts confirmed violations only (14 total) and displays plain grey when a scan has zero violations. Slices under 10% omit the in-ring label and remain readable in the table above.
Breakdown by Category (Violations & Needs Review Kept Separate)
Switching tabs updates only the table below; the 3-ring chart always reflects the full scan. Violations and Needs review are never added together into a combined total.
| axe-core Impact | Violations | Needs review (potential impact) |
|---|---|---|
| Critical | 3 | 1 |
| Serious | 5 | 2 |
| Moderate | 2 | 1 |
| Minor | 0 | 0 |
| Not Rated | 0 | 0 |
| Column total (kept separate) | 10 | 4 |
| axe-core Impact | Violations | Needs review (potential impact) |
|---|---|---|
| Critical | 0 | 0 |
| Serious | 1 | 1 |
| Moderate | 2 | 1 |
| Minor | 1 | 0 |
| Not Rated | 0 | 0 |
| Column total (kept separate) | 4 | 2 |
Today (Live), a finding is tagged third-party when an axe-core rule lands inside a third-party frame or script. These findings are already counted in the WCAG and Best practices tabs above—this tab is a filtered view of them. A complete list of frames, embedded players, and vendors across the site is Planned (Phase 5b).
| axe-core Impact | Violations | Needs review (potential impact) |
|---|---|---|
| Critical | 1 | 0 |
| Serious | 1 | 1 |
| Moderate | 1 | 1 |
| Minor | 0 | 0 |
| Not Rated | 0 | 0 |
| Column total (kept separate) | 3 | 2 |
axe-core marks an item incomplete (for example, text painted over a background photograph), the scanner reports the rule’s potential impact, if confirmed so an auditor knows where to look first without misstating it as a confirmed violation.
Showing 6 illustrative findings across all 4 screen sizes (top and scrolled = 8 page states).
| Rule | Category | Impact | Type | Source | Remediation scope | Criterion | Pages | Elements | Element details |
|---|---|---|---|---|---|---|---|---|---|
| label | WCAG | Critical | Violation | Site’s own | Fix on this site | WCAG 1.3.1, 4.1.2 (A) | 3 / 14 Template | 5 |
Inspect DOM & playbook
axe-core reported: Form element has no explicit label.
#checkout-form > .guest-contact > input#guest-phone<input type="tel" id="guest-phone" placeholder="Mobile number">
Epicpaths playbook: Pair a visible
<label for="guest-phone"> and verify error announcements with a screen reader (NVDA / VoiceOver).
|
| color-contrast | WCAG | Serious | Violation | Site’s own | Fix on this site | WCAG 1.4.3 (AA) | 13 / 14 Global | 26 |
Inspect DOM & playbook
axe-core reported: Foreground
#ffffff on #20c997 is 2.13:1 (below 4.5:1 minimum).#promo-drawer > button.btn-promo-code
Epicpaths playbook: Update the shared button colour token so all template instances meet ≥ 4.5:1, then check hover and
:focus-visible contrast manually.
|
| aria-required-attr | WCAG | Critical | Violation | Site’s own | Fix on this site | WCAG 4.1.2 (A) | 1 / 14 Single | 1 |
Inspect DOM & playbook
axe-core reported: Accessible Rich Internet Applications (ARIA)
role="combobox" is missing required aria-expanded and aria-controls.#delivery-method-picker > div[role="combobox"]
Epicpaths playbook: Refactor to a native
<select> or test full keyboard operation (Enter, Space, Arrows, Escape) manually.
|
| frame-title | WCAG | Serious | Violation | Third-party |
Third-party: fix through the vendor
Still counts toward alignment
|
WCAG 4.1.2 (A) | 4 / 14 Multiple | 4 |
Inspect DOM & playbook
axe-core reported: Embedded payment frame has no accessible
title attribute.iframe#municipal-card-vault (https://pay-widget.example/embed/v2)
Epicpaths playbook: Add a descriptive
title on the host <iframe> and raise internal frame defects with the payment vendor; third-party issues still count toward site alignment.
|
| color-contrast | WCAG |
Serious
Potential impact, if confirmed
|
Needs review | Site’s own | Fix on this site | WCAG 1.4.3 (AA) | 2 / 14 Multiple | 3 |
Inspect DOM & playbook
axe-core reported: Text sits over a background photo; contrast cannot be computed automatically.
.civic-hero-banner > p.hero-subhead
Epicpaths playbook: Measure the lightest pixel behind the text manually or add a solid dark scrim behind the text block.
|
| region | Best practices | Moderate | Violation | Site’s own | Fix on this site | Best practice (Advisory) | 12 / 14 Global | 12 |
Inspect DOM & playbook
axe-core reported: Scrolled mobile utility bar renders outside a landmark region (observed at 375×812 and 768×1024 after scroll).
div.mobile-utility-bar
Epicpaths playbook: Wrap sticky navigation helpers in a named
<nav> or <aside> landmark so screen-reader landmark lists stay complete.
|
Reach badges: Global marks rules present on 80% or more of scanned pages (never phrased as “on every page”); Template marks rules concentrated in one page group; Multiple marks two or more pages; Single marks one scanned page.
Choose Pages Before Scanning
Before a whole-site scan runs, you can review discovered pages and pick which ones to scan. Unscanned pages keep an explicit reason (Not selected, Left out of the sample, Over the page cap, or Not reached) so coverage stays honest.
Exports: CSV & Axe JSON ZIP
Download the full scanned result (regardless of active filters) as a Comma-Separated Values (CSV) spreadsheet (with the Category column) or a ZIP archive containing one standard axe-core JavaScript Object Notation (JSON) file per scanned page.
Send to Project (Compliance Engine)
One-click transfer from Epic Scanner into an Epic Compliance Engine project (sending clean pages and unscanned-page coverage alongside findings) is Planned (Phase 6) behind a readiness switch. Today, results are exported and uploaded into a project by hand.
Following One Site Through Three Kinds of Scan
Following https://northstar-civic.example from initial scoping through remediation shows how Epic Scanner is being built to support a full accessibility program. Choosing pages before a site scan is Live today; each planned capability below is explicitly marked Planned in text.
1. Discovery Scan
Maps the site by template, builds a site profile (platform, documents by kind, video and audio, embedded players by vendor, forms, checkout, and login) plus document and media lists, and scans the chosen sample. Its outputs prompt the Compliance Engine project’s scoping to match what was found; an auditor reviews and confirms every scope decision.
2. Follow-Up Scan
Re-scans the same agreed pages after fixes are deployed. New pages and removed pages are flagged quietly without silently changing the agreed page set, and findings are matched across scans inside the Compliance Engine. The scanner itself never labels an issue “fixed”.
3. Scheduled Scans
Runs the follow-up scan on a recurring schedule so organizations spot regressions between manual audits without rebuilding the page list each time.
Illustrative Discovery Output: Site Profile & Inventories for northstar-civic.example
Planned — Phase 5b
| Inventory Area | Illustrative Scanner Observation (Planned) | What the Auditor Decides |
|---|---|---|
| Platform & Templates | WordPress; 4 template groups (Home, Utility Checkout, Permit Guides, News) | Confirms representative sample pages before scanning |
| Documents by Kind | 9 Portable Document Format (PDF) forms & notices linked (e.g., /forms/water-service.pdf) |
Decides whether to include document remediation in project scope (scanner does not audit PDFs) |
| Video, Audio & Players | 2 YouTube embeds; 1 native HTML5 <video> with a <track> element |
Checks caption accuracy, transcripts, and audio description (a scan can note a player, never judge captions) |
| Forms, Checkout, Login & Vendors | Guest checkout, resident login, 3 forms, 1 third-party payment frame (pay-widget.example) |
Tests full keyboard flows, error recovery, and vendor accessibility documentation |
After Human Testing: Criterion-Status Audit Summary in Epic Compliance Engine
Criterion statuses (Pass, Fixed, Fail, To test, Third party), Voluntary Product Accessibility Template (VPAT®) / Accessibility Conformance Report (ACR) terms, and task-based report severity exist only inside Epic Compliance Engine after a person completes Department of Homeland Security (DHS) Trusted Tester keyboard, zoom, reflow, and screen-reader verification. They are never produced by the scanner on its own.
| Status (Code) | Criteria | VPAT® Term |
|---|---|---|
| Pass (P) | 18 | Supports |
| Fixed (X) | 3 | Supports |
| Fail (F) | 4 | Does Not Support |
| To test (R) | 2 | Review Required |
| Classification | Items | Assigned By |
|---|---|---|
| Report Severity: High | 2 | Human Auditor |
| Report Severity: Medium | 2 | Human Auditor |
| Manual Notes Logged | 2 | Human Auditor |
| Third party (T) | 1 | Vendor Review |
Example of What Only Human Verification Catches (Mobile 375×812 Keyboard Test)
Automated axe-core rules cannot judge WCAG 2.4.11 Focus Not Obscured (Minimum) or interactive target spacing under WCAG 2.5.8 Target Size (Minimum, 24×24 CSS px). During manual keyboard tabbing at 375×812, an auditor found a sticky support launcher (aside.civic-chat-fab) completely covering the focused a#cancel-checkout action and logged it as a High report-severity defect in the Compliance Engine workspace.
About the epic-scanner User-Agent & Scan Infrastructure
If you see epic-scanner in your server logs, an authorized project owner or auditor ran an accessibility scan of your site using Playwright and axe-core.
epic-scanner/<version> (for example, ... Safari/537.36 epic-scanner/0.1.0)+https://epicpaths.com/scanner to the token alongside the public /scanner allowlisting pageepic-scanner entry in your logs or want to verify or object to a scan? Contact our team through the Epicpaths Contact Portal.