ADA Checker

What's new in this beta

Recent changes, improvements, and known limitations. The checker is still in beta — no warranty is given.

← Back to scanner

  1. v1.0.1

    • AddedAt-a-glance compliance summary at the top of the PDF report — overall score, severity counts, and issue breakdown by WCAG level (A / AA / AAA + best practice).
    • AddedScore breakdown by category (contrast, keyboard, screen reader, and more) on the scan results page.
    • AddedActionable remediation checklist grouped by severity, with per-step progress tracking and mark-all-done / reset controls.
    • AddedCSV export of scan issues alongside the existing PDF report.
    • ImprovedPDF and CSV export filenames now include the analyzed site's domain and scan date so each download is unique and easy to file.
    • FixedHardened the URL scanner against SSRF: hostnames are resolved and checked against private / loopback / cloud-metadata ranges, and redirects are re-validated on every hop.
  2. v1.0.1

    • Added"What's new in this beta" changelog page.
    • Added"How this checker works" expandable section on scan results explaining automated vs. manual review.
    • AddedBeta disclaimer and checker version included in exported PDF reports.
    • AddedChecker version and page load timestamp shown in the site footer for traceability.
    • AddedBeta / no-warranty disclaimer in the site footer.
    • AddedPersistent scope note under each scan score summarizing which WCAG tiers ran and which were skipped.
    • Added"Why this is flagged" expandable explanation on every violation, including WCAG level and whether it would be skipped at your target.
    • AddedTooltips on the WCAG target selector explaining what each level (A / AA / AAA) means.
    • AddedCompliance target control in the scan options panel; results reflect the selected target.
  3. vbeta

    • Known issueOnly a portion of WCAG failures are machine-detectable — roughly 30–40%. Manual review is still required.
    • Known issueSingle-page apps may be partially scanned if content loads after the initial render.
    • Known issueColor contrast checks rely on computed styles and may miss issues in background images or video.