WCAG 2.2 · GIGW 3.0 · STQC · EN 301 549

Accessibility re-verification, with evidence your auditor will accept.

Continuous WCAG 2.2 AA, GIGW 3.0 and STQC checks with screenshot proof per issue and engineering-ready remediation — the audit pack between your audits.

No card requiredPublic shareable reportResults in < 2 minutes

Try it now

Run a scan in under two minutes.

Scan form

Add phone (optional)

Built against

  • WCAG 2.2 AAW3C — current revision
  • GIGW 3.0Govt. of India, MeitY
  • STQCSurveillance audits
  • EN 301 549European procurement
  • IAAP-alignedCPACC + WAS methodology
  • Section 508US federal parity

Why re-verification

An annual audit proves a moment. Compliance lives in every release.

Your IAAP or STQC certification documents what was true the day the auditor signed off. Three releases later — a redesigned header, a new circulars page, an updated form — the evidence on file is stale, and the next surveillance review starts with the gap.

AccessSure runs the re-verification pass between audits. Same standards. Same evidence format your reviewer already accepts. Continuously.

What you ship to legal

A scanner tells you what failed. Evidence tells you why it matters.

Screenshot evidence per issue

Every flagged violation ships with an annotated screenshot of the failing element in its real page context — not a DOM diff a developer has to decode.

Re-verification audit packs

STQC and GIGW surveillance reports formatted to the line items reviewers expect — exportable as PDF, DOCX or JSON. The format your auditor already uses.

Engineering remediation

Each finding includes the WCAG success criterion, the failing selector, the fix pattern and the priority — written for the developer who has to ship it.

Standards coverage

What gets checked, organised by WCAG principle.

AccessSure runs the deterministic axe-core ruleset alongside vision-model heuristics that read the rendered page. Below is a representative slice of what each scan covers — the full criterion list ships in the report appendix.

Perceivable

  • Color contrast (1.4.3 / 1.4.11)
  • Image alt text (1.1.1)
  • Captions & audio (1.2.x)
  • Resize & reflow (1.4.4 / 1.4.10)

Operable

  • Keyboard navigation (2.1.x)
  • Focus visible & order (2.4.7 / 2.4.3)
  • Skip links & landmarks (2.4.1)
  • Pointer & target size (2.5.x)

Understandable

  • Language of page (3.1.1)
  • Form labels & instructions (3.3.2)
  • Error identification (3.3.1)
  • Consistent navigation (3.2.3)

Robust

  • Valid name/role/value (4.1.2)
  • Status messages (4.1.3)
  • Parsing & ARIA hygiene
  • Document & PDF structure

The process

Four steps to defensible compliance.

  1. Point us at a URL

    Paste a domain, a sitemap, or a single page. We crawl with a real Chromium browser — same DOM your users see.

  2. Scan with axe + AI heuristics

    axe-core handles the deterministic rules. A vision model reviews each captured screenshot for issues a static analyzer can't see.

  3. Evidence is generated

    Every finding is paired with an annotated screenshot, the failing selector, and the WCAG criterion it maps to.

  4. Hand off the audit pack

    Export the GIGW / STQC formatted report. Engineering gets ticket-ready remediation; compliance gets the surveillance pack.

Built for

Three teams, one standard of evidence.

Government IT departments

Maintain GIGW 3.0 conformance between STQC surveillance cycles. Catch regressions the moment a circular or notification page ships.

Enterprise compliance teams

Annual IAAP audits prove a point in time. AccessSure re-verifies after every release so the evidence stays current — not eleven months stale.

Accessibility consultancies

Cover larger client portfolios with automated coverage layered under your manual review — in the evidence format your auditors already accept.

Pricing

Start free. Scale when the evidence matters.

Full pricing

Free Snapshot

Homepage scan, instant public report.

₹0single scan
  • Single URL
  • WCAG 2.2 AA quick check
  • Public shareable report
Run a snapshot

Automated

Continuous re-verification across your site.

₹10,000/ month
  • Multi-page crawl
  • Screenshot evidence
  • Scheduled scans
  • Team access
Start automated

IAAP Audit

Manual + automated audit, IAAP-aligned.

₹50,000/ scan
  • Reviewer-led audit
  • STQC / GIGW pack
  • Remediation handoff
  • Re-test included
Book an audit

Questions

Things compliance teams actually ask.

What is the difference between an accessibility audit and re-verification?

An audit is the initial conformance review against a standard like WCAG 2.2 AA or GIGW 3.0. Re-verification is the periodic re-test that proves the site still conforms after code changes, content updates, or a redesign. AccessSure focuses on continuous re-verification between formal audit cycles.

Does AccessSure replace a manual IAAP audit?

No. A formal IAAP-led audit is still required for certification milestones. AccessSure runs automated re-verification between those audits and supplies the evidence pack reviewers ask for during STQC and GIGW surveillance.

Which standards does AccessSure test against?

WCAG 2.1 and WCAG 2.2 (Level A and AA), GIGW 3.0, EN 301 549, and Section 508. Automated coverage typically reaches 30–40% of total criteria. The remaining criteria are flagged for human review and included in the audit pack.

How is GIGW 3.0 different from WCAG 2.2?

GIGW 3.0 is the Government of India guideline issued by MeitY. It adopts WCAG 2.1 Level AA as its accessibility baseline, then adds Indian-context requirements: bilingual and regional language support, document accessibility for PDF circulars, and security-disclosure formatting. AccessSure tests both layers.

Does it work for sites under STQC certification?

Yes. AccessSure exports surveillance-audit-ready reports formatted to the line items STQC reviewers expect, including the GIGW conformance matrix and a per-page evidence appendix.

Can an automated scanner find every accessibility issue?

No tool can. AccessSure detects the deterministic subset (around 30–40% of WCAG criteria) and adds AI-assisted heuristics on top of axe-core. Anything that requires human judgment is flagged for the manual reviewer and packaged into the audit format they already use.

What evidence is included in the report?

For each finding: the WCAG success criterion, severity, failing element selector, an annotated screenshot, the page URL, and a recommended fix pattern. Reports export as PDF, DOCX, or JSON for ingestion into GRC tools.

Ready when you are.

Run a free snapshot of any URL. No card, no commitment — just see what's there.