Payload Accessibility

Assess accessibility as part of the change, not as a scan added afterward. Scope conclusions to the behavior and states actually evaluated.

Change assessment

For every affected component or flow:

1. Identify the rendered states, input methods, viewport conditions, and assistive-technology behavior the change can affect.
2. Read wcag-2.2-aa.md. Assess every plausibly affected WCAG 2.2 Level A and AA criterion; do not limit review to criteria named in an issue.
3. Prefer native HTML semantics. When a composite ARIA pattern is necessary, implement its complete semantics and keyboard behavior rather than adding roles or states in isolation.
4. Read testing.md and select evidence based on the observable outcome.
5. Exercise the changed behavior in every relevant state. Accessibility checks must cover the production component and integration context, not a simplified substitute.

Test placement