Jira accessibility bug template

Keep the issue small enough to own and specific enough to retest. The goal is a clean engineering handoff, not a vague accessibility label.

Recommended Jira fields

• Summary: component + failure + state.
• Description: steps, observed result, expected result, and user impact.
• Environment: URL, viewport, browser, input method, and relevant assistive technology.
• Evidence: screenshot, short recording, DOM snippet, or repeatable observation.
• Priority: task impact, reach, and workaround quality.
• Acceptance criteria: observable checks for the fixed state.

Example summary

Checkout delivery accordion button has no accessible name

Avoid these failure modes

• Do not paste an automated scanner result without reproducing it.
• Do not assign severity from a WCAG level alone.
• Do not combine unrelated components into one issue.
• Do not claim conformance from a single passing retest.