Interaction testing
Audit a Third-Party Embed in Context
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Test an embedded widget as part of the page and the complete user process. Record its vendor, version, integration settings and frame boundaries. Separate defects the site owner can repair from defects requiring the provider.
A practical example
A support page embeds a scheduling widget that opens a time selector and then a contact form.
How to check it
- Navigate to, into and out of the embed using the keyboard. Check its frame title, entry point, reading order and exit behavior.
- Complete the embedded task, including validation and cancellation. Review zoom, mobile layout and screen-reader announcements at each boundary.
- Document failures with the host URL, widget state and vendor details. Identify an interim accessible route that accomplishes the same task while a repair is pursued.
What can be missed
A vendor accessibility statement does not verify your configured integration. An alternative route should be usable and discoverable, not merely an instruction to try another browser.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.