How should a store watch the accessibility of third-party embeds?

Inventory every video player, review widget, chat launcher, and social embed on the storefront, test each one against the same keyboard, label, and focus checks you run on your own code, and re-verify whenever the vendor ships a change. Embeds are code you do not control on pages you are responsible for.

List what is actually embedded

Walk the storefront as a shopper and note everything that loads from someone else's servers: video players, review carousels, chat bubbles, social feeds, store locators, scheduling widgets, payment option buttons. Then check the list against the source. Iframes, third-party scripts, and embeds often load pieces the team has forgotten about. The list should name the vendor, the pages where the embed appears, and what the shopper uses it for.

Give each embed the same five checks

Test keyboard access first: every control in the embed should be reachable and operable by keyboard, with visible focus. Test names and labels: chat bubbles and video controls should be announced with clear purposes, not icon glyphs with no text. Test focus behavior: a chat widget that opens a panel should move focus into it and return focus when closed. Test contrast: vendor CSS frequently ships placeholder or caption text that fails WCAG 2.2 contrast minimums. Test captions: embedded videos need real captions, not auto-generated drafts that garble product names.

Watch for the vendor's update cadence

Vendors ship changes on their own schedule, and an embed that passed last quarter can regress silently. If a vendor offers a changelog or release notes, track it against your check dates. If not, re-run the five checks on each embed at a fixed cadence, monthly for checkout-adjacent embeds like payment buttons and reviews near the add-to-cart flow, quarterly for the rest. Keep a log of what you tested and when. The log is the difference between "we assumed it was fine" and "we verified it in September."

Use the vendor's own accessibility claims

Ask each vendor for a current VPAT or accessibility conformance report before signing, and ask again at renewal. A vendor that publishes one can be held to it. A vendor that cannot produce one is telling you something. When a check fails, file it with the vendor with a reproduction and a date, and decide what to do if they will not fix it: replace the vendor, wrap the embed with your own accessible alternative, or accept the risk in writing with the store's leadership. Accepting the risk is a decision, not an accident, and it should be written down.

Fold embeds into monitoring and the evidence log

Automated monitoring should include the pages where embeds appear, not just the theme templates. A regression in a review widget on product pages can ship at any time. When a change is found, the incident record should name the vendor, the version or date, the affected pages, and the fix or workaround. That record does double duty: it guides the next test cycle, and it shows a pattern of care if the store ever needs to explain its accessibility practice.