Accessibility ticket template

A useful ticket lets another person reproduce the barrier, understand the user impact, and verify the fix. Copy this structure into Jira, GitHub, Linear, or your team’s tracker.

Copyable structure

Title: [Component] [problem] [state]

Environment:
Page / flow:
Viewport:
Browser:
Input method or assistive technology:

Steps to reproduce:
1.
2.
3.

Observed:
Expected:
User impact:
Evidence:
Proposed WCAG mapping:
Severity and rationale:
Acceptance checks:

What makes the ticket actionable

• Name the exact component and state instead of describing the whole page.
• Record evidence that can be repeated, not only a scanner label.
• Write acceptance checks as observable outcomes.
• Use a proposed standards mapping when qualified review is still needed.