# Event website accessibility issue decision log

Use for a specific launch. This is a work-priority record, not a declaration of conformance or legal advice. Keep contact and sensitive user details in the approved issue system; link a restricted reference ID here.

| Event and launch date | Accessibility lead | Product owner | Support contact | Last review |
|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [ ] |

| Issue ID | Attendee task and page/step | Observed barrier and reproduction context | Affected route, language and device | Can the attendee actually finish the task? Evidence | Shared component or third party? | Decision and owner | Fix / vendor action | Retest method and owner | Public limitation and contact update | Release decision / residual owner |
|---|---|---|---|---|---|---|---|---|---|---|
| [ ] | Find event facts / access info | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | Register or purchase ticket | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | Receive/read confirmation | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

## Decision prompts

- Is the issue reproduced, and what task does it stop or distort?
- Does it appear in a common component, a particular language or an external checkout?
- Is the proposed temporary route tested with an affected attendee, or only assumed?
- Who can ship the fix, who can retest the complete task, and who will update public information?
- What remains unresolved and owned after launch?

A support path or statement can help communication, but it is not evidence that the original digital journey has been repaired. Revisit local legal obligations with qualified advice.