# Ticket-link tab behavior and release sheet (English)

Event / edition: __________  Published page: __________  Review owner: __________  Review date: __________

Use one row per link placement. The destination and the tab behavior are separate approvals.

| Page / placement | Exact ticket destination | Event / date checked | Same tab or new tab | Why this choice? | Visible and spoken new-tab notice, if used | Owner | Phone signed-out | Keyboard / focus | Return path or preserved state | Release / retest date |
|---|---|---|---|---|---|---|---|---|---|---|
| Header ticket action | | | | | | | | | | |
| Price card | | | | | | | | | | |
| Session page | | | | | | | | | | |
| Footer or sticky action | | | | | | | | | | |

## Decision prompts

- Does following the link in the same tab actually lose entered form data or another necessary state? Record a tested example, not an assumption.
- If a new tab opens, does the visible link or adjacent text say so before activation, and is the notice also available to assistive technology?
- Does the label name the destination and the correct event edition? Is the public event page still clear after a failed or canceled checkout?
- After activation, can the attendee return to the event page using the expected path? Record the observed behavior on a phone and with a keyboard.
- Which owner will retest after a checkout-provider, template, or ticket-destination change?

Release decision: [ ] ready  [ ] revise  Owner: __________  Evidence URL / note: __________