# Event website embed dependency and fallback register

Copy one row for each external map, video, social post, schedule, form or ticket widget. Test the actual attendee task with the embed working and unavailable. A static alternative may inform the attendee but cannot substitute for a functioning booking or payment.

**Event / edition:** [ ]  **Register owner:** [ ]  **Review date:** [ ]

| Page and embed | Attendee task / criticality | Provider and content/account owner | Official source URL / status contact | On-page key facts and accessible alternative | Failure fallback and activation owner | Last check / next review |
| --- | --- | --- | --- | --- | --- | --- |
| Map | Find venue | [ ] | [ ] | Address + written directions | [ ] | [ ] |
| Video or stream | Watch session | [ ] | [ ] | Description, captions/transcript where needed | [ ] | [ ] |
| Schedule or social feed | Learn current details | [ ] | [ ] | Authoritative event date/time text | [ ] | [ ] |
| Registration / ticket widget | Apply or buy | [ ] | [ ] | Clear status and official provider identity | Official tested route or support contact | [ ] |

## Failure exercise

**Scenario and date:** [embed blocked / permission revoked / third-party outage / content removed].

**Can the visitor still identify the event, date and venue?** [ ]  **Can keyboard users reach the direct link?** [ ]

**For booking or payment: is the alternative official, tested and accurately described?** [ ]  **Who approves activation?** [ ]

**Affected pages, observed result, evidence and follow-up:** [ ]

Recheck after provider account changes, privacy-setting changes, event date/location edits and before on-sale. Keep performance work separate so loading changes do not remove the fallback.

Sources: [UMKC embedded-content guidance](https://www.umkc.edu/digital-accessibility/website-remediation/embedded-content.html) and [web.dev third-party embed practices](https://web.dev/articles/embed-best-practices).