Manage third-party content accessibly

Inventory the whole user journey

List every external service in the page or document workflow: a YouTube or Vimeo player, registration form, project gallery, map, document portal, payment step, chat widget, or analytics-driven component. Record the provider, URL, embed or link method, data collected, owner, and the task it supports. A page can be visually simple while its most important action is trapped inside an inaccessible iframe.

Test the experience as a visitor who is keyboard-only, zoomed in, using a screen reader, or using captions. Check headings, labels, focus order, error messages, contrast, language, time limits, downloads, mobile layout, and whether the service works without a mouse. Review the provider's accessibility statement or VPAT as evidence to investigate, not as a substitute for testing the configured experience.

Choose and integrate with an equivalent path

Before procurement or renewal, ask whether the provider supports keyboard operation, accessible names and roles, captions and transcripts, zoom and reflow, accessible form errors, and a documented issue process. Keep the required information in your own page when practical. For example, introduce a registration form with an HTML heading and instructions, then provide a plain link to the vendor form and a downloadable accessible alternative if the embed fails.

Label an iframe with a meaningful title, give the external link descriptive text, and do not place an essential notice only inside a player or widget. An accessible alternative must provide the same information or task, not merely a screenshot or a sentence telling people to call someone. Keep the alternate path current when the vendor changes its URL or workflow.

Monitor and escalate changes

Set a review cadence based on risk and change frequency. Recheck the first task after a provider release, embed-code update, or new content upload. Record the URL, date, browser and assistive technology used, result, and issue reference. If an uncontrolled service introduces a barrier, make the equivalent path prominent while the provider investigates. Remove, replace, or isolate a component that blocks a core task.

WCAG 2.2 describes a statement of partial conformance for uncontrolled third-party content, but that statement acknowledges non-conformance and does not turn inaccessible content into an exemption. Do not publish a broad claim that the site is conformant while a known vendor barrier remains in a covered user journey. Describe the tested scope and limitations accurately.

Hand off provider issues with a reproducible case

Send the vendor a short reproduction: page or embed URL, exact task, keyboard steps, focus or announcement observed, browser and assistive technology, date, and a recording or screenshot only when it does not expose personal information. Include the accessibility requirement or WCAG success criterion that explains the barrier. Keep the page owner, procurement contact, and content editor aligned on the workaround and next review date.