# Accessibility Issue Remediation Log

Assign, resolve, verify, and document content accessibility defects, affected users, reproduction conditions, standards, ownership, and regression coverage.

## Usage note

Use this log for confirmed accessibility barriers, linking to your main issue system when appropriate. Describe user impact and reproducible evidence rather than treating a scanner label as the finding. Apply the standards and severity model chosen by your organization. Do not close an issue because code changed; verify the outcome in the original and relevant regression environments.

## How to use this template

1. Reproduce the issue and record task, environment, state, expected behavior, actual behavior, and user impact.
2. Identify affected pattern, pages, components, locales, and relevant requirement.
3. Set severity, owners, acceptance criteria, and a source-level remediation plan.
4. Implement and test original plus boundary and regression states.
5. Record verification, residual risk, prevention, release, and closure approval.

## Blank template

### Issue record

- **Issue ID and title:** [Stable identifier]
- **User task:** [What the person needs to do]
- **Affected users:** [Access method or need, not diagnosis assumption]
- **Page/component/state:** [Exact location]
- **Environment:** [Browser, device, AT, zoom, locale, build]
- **Steps to reproduce:** [Ordered steps]
- **Expected behavior:** [Accessible outcome]
- **Actual behavior:** [Observed barrier]
- **User impact:** [Blocked, confusion, loss, effort, risk]
- **Requirement/reference:** [If reviewed]
- **Severity and rationale:** [Model used]

### Remediation and verification

- **Root cause:** [Content, design, code, data, process]
- **Affected scope:** [Components, pages, locales]
- **Acceptance criteria:** [Observable outcomes]
- **Content owner:** [Name/team]
- **Technical owner:** [Name/team]
- **Temporary mitigation:** [If any]
- **Fix version/build:** [Identifier]
- **Verification environment/result:** [Exact]
- **Regression prevention:** [Test, guidance, component rule]

### Closure checks

- [ ] Reproduction evidence avoids sensitive data.
- [ ] User impact is described independently of tool severity.
- [ ] Shared patterns and locales were searched.
- [ ] Acceptance criteria include important states.
- [ ] Original task is retested after remediation.
- [ ] Automated and manual checks are combined appropriately.
- [ ] Temporary mitigation is not mistaken for closure.
- [ ] Verification owner and residual risk are documented.