aria-reach

Live, local, framework-agnostic

Find the ARIA defect. Trace the likely source.

Run aria-reach against this seeded page—no install required. The runtime scanner detects ARIA anti-patterns and uses DOM fingerprints to suggest a likely component-library origin for manual confirmation.

Intentional defects: the example region below contains accessibility problems so the scanner has something real to find.

Seeded component examples

Representative runtime issues from Classes I–III.

Class I — Decorative Noise Injection

Decorative separators and an untreated SVG are exposed to assistive technology.

Class II — Live-Region Urgency

Draft saved at 09:41

A routine save notification is unnecessarily assertive.

Class III — Widget Role Contracts

Sans Serif
Serif
Monospace

The listbox lacks option semantics and the calendar uses pressed state for selection.

Clean control

Draft saved at 09:42

The fixed separator and polite status should not produce findings.

Live scan results

Click a finding to highlight its element.

Ready to scan the seeded examples.

Run the scanner to populate this report.

Framework-agnostic runtime

The browser sees rendered DOM, so these rules work across Angular, React, Vue, Svelte, and vanilla applications.

Heuristic attribution

Class and tag fingerprints suggest a likely library origin. Confirm the source before filing an upstream issue.

Complementary evidence

aria-reach supports targeted WCAG and Section 508 review; it does not replace complete audits or screen-reader testing.