App 2 · is your website legally accessible?

Accessibility Readiness + Scanner

Scan, score, and get a fix plan mapped to WCAG 2.2.

‹ Suite
The standard, in plain English
WCAG 2.2 (mapped to ADA expectations)
WCAG 2.2 — 1.1.1 Non-text Content
Alt text on all meaningful images
Every informative image, icon button, and chart needs a text alternative. Decorative images get empty alt. This is the single most common failure.
WCAG 2.2 — 1.4.3 Contrast (Minimum)
Sufficient color contrast
Body text needs a 4.5:1 contrast ratio against its background (3:1 for large text). Run the scanner to find low-contrast pairs.
WCAG 2.2 — 2.1.1 Keyboard
Everything works without a mouse
Every control must be reachable and operable by keyboard alone, with a visible focus ring. Test by unplugging your mouse.
WCAG 2.2 — 3.3.2 Labels or Instructions
Form fields have programmatic labels
Associate a real <label> with every input. Placeholder text is not a label. Error messages must be announced.
WCAG 2.2 — 1.2.2 Captions
Captions and transcripts for media
Pre-recorded video needs synchronized captions; audio needs a transcript. This also helps SEO and noisy environments.
WCAG 2.2 — 1.3.1 Info and Relationships
Logical heading structure & landmarks
Use real heading levels (one h1, nested h2/h3) and landmark regions so screen-reader users can navigate by structure.
ADA Title II — web rule
Government site: meet WCAG 2.1 AA on the public timeline
State/local government web content has a hard ADA Title II conformance expectation. Prioritize a full-site audit and a dated remediation plan.
Automated scans catch a subset of issues. Full accessibility requires manual review and assistive-technology testing. This is readiness guidance, not legal advice.
Good to knowAutomated scans catch a subset of issues. Full compliance needs manual + assistive-tech testing. Not legal advice.