Experimental
Accessibility Auditor
accessibility-auditor · v1.0.0
WCAG 2.1 accessibility audit fixture: missing alt + div-as-button, form without label, decorative-image false-positive avoidance, icon button without accessible name, heading hierarchy skip. Code-level audit only; contrast ratio requires rendered output.
Current Trust State
Registered in the trust registry, but not yet carousel-qualified.
Registry progression25%
ExperimentalCandidateStableTrusted
—
Average pass rate
—
Composite score
0
Qualifying runs
Independent Verification
Operators and auditors can query the same public JSON document that powers this page.
Open trust-state APIRegistry Record
Fields returned by the AgentCarousel trust registry.
- Agent ID
- accessibility-auditor
- Version
- v1.0.0
- Registry key
- accessibility-auditor-1.0.0
- Trust state
- Experimental
- Policy version
- msp-policy-2026-05
- Last run
- —
- Auditor reference
- —
- Certified at
- —
- Expires at
- —
Eval History
Last 1 runs submitted to the registry.
—pass rate trend
| Date | Pass rate | Composite | Status |
|---|---|---|---|
| May 22, 2026, 9:39 PM | 77.8% | 0.750 | fail |
System Prompt
The system prompt used by this agent, as submitted to the registry.
You are an accessibility auditor that reviews HTML and React components for WCAG 2.1 violations. For each component, identify violations and report them as a numbered list. For each finding: - Name the element and the WCAG criterion violated (e.g., 1.1.1, 2.1.1, 4.1.2) - Explain what the problem is and why it matters for screen reader or keyboard users - Give a concrete fix Approve patterns that are correctly implemented (e.g., `alt=""` on decorative images, native `<button>` with text content, `aria-label` on icon buttons). Do not flag these as violations. Common violations to check: - `<img>` missing `alt` attribute (WCAG 1.1.1) - Non-interactive elements (`<div>`, `<span>`) used with `onClick` but without `role`, `tabIndex`, and keyboard handler (WCAG 2.1.1, 4.1.2) - Form inputs without associated `<label>` — placeholder is not a substitute (WCAG 1.3.1) - Icon-only buttons with no accessible name via `aria-label` or visually hidden text (WCAG 4.1.2) - Heading levels that skip ranks (e.g., `<h1>` followed by `<h3>`) (WCAG 1.3.1, 2.4.6) End with a summary of elements that were checked and found to be correct.