Epicpaths.com Announcements
Website is being Updated - Stay Tuned.
Sample report · illustrative data Fictional fixture • Epic Scanner output + Compliance Engine hand-off

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.

Sample Target Site (Fictional Fixture)
https://northstar-civic.example
Northstar Civic Portal — Representative whole-site sample (14 of 148 pages scanned)
Screen Sizes & Page States (Live)
4 screen sizes × top & scrolled (8 states)
375×812, 768×1024, 1280×800 & 1920×1080 (reduced set on extra template samples)
Live in Epic Scanner Sample report · illustrative data

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.

Chart Equivalent: 20 Total Automated Findings (Slices ≥ 10% Labelled)
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.

WCAG Rules — 10 Violations, 4 Needs review (never combined)
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
Why Needs Review Shows “Potential impact, if confirmed”: When 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.
Live Sample report · illustrative data

Automated Findings Table — 4 Screen Sizes × Top & Scrolled (8 Page States)

Single-page scans check Mobile (375×812), Tablet (768×1024), Desktop (1280×800), and Large desktop (1920×1080), each at the top of the page and again after scrolling through it (8 page states). Whole-site scans use all 8 states on the start page, one-off pages, and each template group’s first pick, and a reduced set on extra sampled template pages.

Showing 6 illustrative findings across all 4 screen sizes (top and scrolled = 8 page states).

Illustrative Findings Rows (Real Epic Scanner Column Structure)
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.

Live

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.

Live

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.

Planned — Phase 6

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.

Planned Site-Scanning Roadmap (Labelled in Text)

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.

Planned — Phase 5b Page Picker Live

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.

Planned — Phase 5b

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

Planned — Phase 7

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
Illustrative Site Profile & Inventories (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
Epic Compliance Engine Output • After Human Testing Not Scanner Output

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.

Compliance Engine Audit Summary (Human-Verified)
21 of 27 in-scope WCAG 2.2 criteria verified Pass or Fixed by an auditor
Engine Audit Status (27 In-Scope Criteria)
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
Human Audit Severity & Third-Party Scope
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.

User-Agent, Allowlisting & Audit Record Reference Public /scanner Guide & Fixed U.S. IP Planned (Phase 5)

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.

Live today: Normal desktop Chrome user-agent string ending in epic-scanner/<version> (for example, ... Safari/537.36 epic-scanner/0.1.0)
Planned (Phase 5): Appending +https://epicpaths.com/scanner to the token alongside the public /scanner allowlisting page
Allowlisting First — Never Evasion Epic Scanner never uses IP rotation, proxies, a Virtual Private Network (VPN), or user-agent spoofing to get past a Web Application Firewall (WAF). When the hosted Virtual Private Server (VPS) scanner launches in Phase 5 (Planned), scans will originate from a single fixed U.S. server with a published IP, a “Scanned from the United States” notice, and a site-owner allowlist guide. No IP address is published here yet.
Retention & Audit Record Only the copy imported into an Epic Compliance Engine project is the project’s audit record. Today scans stay available until deleted by the user. In the planned hosted service (Phase 6), unimported member scans are planned for 90-day retention (30 days after import, with one 90-day extension and advance reminders), and guest scans for 7 days.
Questions or Scan Verification? Have questions about an epic-scanner entry in your logs or want to verify or object to a scan? Contact our team through the Epicpaths Contact Portal.