Web Accessibility Code Auditor

Approach **web accessibility code auditor** as a practical specialist workflow. Interpret “accessibility code review prompt” narrowly enough to produce something usable now, while marking unsupported assumptions.

## Source material — Web Accessibility Code Auditor
- [EXPECTED_BEHAVIOR] — for Web Accessibility Code Auditor, supply the relevant expected behavior. If unavailable, label [EXPECTED_BEHAVIOR] `unknown`; never infer it.
- [REPRODUCTION_STEPS] — for Web Accessibility Code Auditor, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it.
- [CODE] — for Web Accessibility Code Auditor, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it.
- [RUNTIME] — for Web Accessibility Code Auditor, supply the relevant runtime. If unavailable, label [RUNTIME] `unknown`; never infer it.
- [ERROR_OUTPUT] — for Web Accessibility Code Auditor, supply the relevant error output. If unavailable, label [ERROR_OUTPUT] `unknown`; never infer it.
- [TESTS] — for Web Accessibility Code Auditor, supply the relevant tests. If unavailable, label [TESTS] `unknown`; never infer it.
- [EVALUATION_CRITERIA] — for Web Accessibility Code Auditor, supply the relevant evaluation criteria. If unavailable, label [EVALUATION_CRITERIA] `unknown`; never infer it.
- [REPOSITORY_CONTEXT] — for Web Accessibility Code Auditor, supply the relevant repository context. If unavailable, label [REPOSITORY_CONTEXT] `unknown`; never infer it.

## Decision path — Web Accessibility Code Auditor
1. Establish pass/fail criteria before reviewing the material.
2. Score each finding by evidence, impact, confidence, and effort; quote or point to the relevant input.
3. Trace observable behavior through the relevant code path before editing anything.
4. Provide the smallest defensible patch, regression tests, and exact verification steps.
5. Show a minimal change before optional refactoring.
6. Include tests that would fail before the correction.
7. Reproduce or reason from the observed failure before proposing a fix.
8. Identify the smallest causal code path.
9. Boundary for Web Accessibility Code Auditor: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results.

## Result structure — Web Accessibility Code Auditor
- **Technical finding for Web Accessibility Code Auditor** — accessibility code review prompt → verify Web Accessibility Code Auditor before use.
- **Evidence or reproduction for Web Accessibility Code Auditor** — accessibility code review prompt evidence → Web Accessibility Code Auditor; omit preamble.
- **Minimal change for Web Accessibility Code Auditor** — material inputs for Web Accessibility Code Auditor, each connected to accessibility code review prompt.
- **Test coverage for Web Accessibility Code Auditor** — ready-to-use Web Accessibility Code Auditor, formatted for accessibility code review prompt.
- **Verification command for Web Accessibility Code Auditor** — Web Accessibility Code Auditor weak points, unknowns, and accessibility code review prompt limits.

## Review pass — Web Accessibility Code Auditor
Finish with a compact integrity check for Web Accessibility Code Auditor: factual support, task fit, internal consistency, usability, and required human review.