Documentation
How AccessSure scans, and how to read the report.
No SDK to install, no config file to maintain. This page covers the scan engine, the audit pack format, and how findings map to WCAG 2.2 AA and GIGW 3.0.
How a scan runs
You give AccessSure a URL and a depth (how many linked pages to crawl). We launch a real Chromium browser per page, wait for the document to settle, then run axe-core 4.10 plus our custom checks for the WCAG 2.2 additions. Each finding is captured as an annotated screenshot with the offending DOM selector. No iframes, no synthetic shortcuts — what you see in the report is what was actually rendered.
What the report contains
For every issue: the WCAG success criterion mapping (e.g. 1.4.3 Contrast — Minimum), the conformance level (A / AA / AAA), the affected URL, the DOM selector, an annotated screenshot with the violating element highlighted, and a concise remediation suggestion. Issues are grouped by criterion and by severity. The report exports cleanly to PDF for auditor sign-off.
How to interpret findings
AccessSure marks issues as Critical, Serious, Moderate, or Minor — these are derived from axe-core impact ratings. Critical and Serious are the ones that fail STQC surveillance and IAAP-aligned reviews, so fix those first. Moderate and Minor are typically polish that improves user experience but does not block conformance.
What needs a human
About 30–40% of WCAG 2.2 AA can be tested automatically. The rest — meaningful sequence, error suggestion quality, complex reflow behaviour, real assistive-tech testing — is flagged in the report as "needs review" with screenshots and selectors prepared. We never mark a manual-only criterion as passed.
Wiring it into release flow
On paid plans you schedule scans (daily, weekly, per-deployment). The dashboard shows a trend of findings per criterion over time, so you see whether a release introduced new violations before the next surveillance audit. API access (for CI integration) is on the roadmap — talk to us if you need it sooner.
Sharing the report
Every scan has a public share URL — useful for forwarding to a developer, an auditor, or a procurement reviewer who does not have a dashboard login. The URL is unguessable; revoke it from the scan settings any time.
Standards reference
What we test against.
WCAG 2.2
The 50 Level AA success criteria, plus the 9 additions in 2.2.
GIGW 3.0
The Indian government website standard, mandatory for ministries and PSUs.
IAAP CPACC / WAS
Auditor certifications recognised globally for accessibility sign-off.
EN 301 549
European Standard for ICT accessibility, referenced by the EAA.
Need help?
We answer every support email.
Stuck on a finding, need a custom standards mapping, or running a scan that does not look right? Email us with the scan ID.