ACCESSIBILITY LIBRARY

Third-Party Components and Accessibility Requirements

Third-party components can introduce accessibility barriers in embeds, payments, bookings, chat, maps, authentication, video players, cookie banners and widgets.

Third-party components can be part of the user journey even when your team does not own their source code.

Review embeds, payment systems, booking systems, chat, maps, authentication providers, video players, cookie consent systems and widgets. The assessment should identify barriers, dependencies, ownership and possible remediation paths.

Do not turn this into a legal conclusion about responsibility. Treat it as technical evidence: what users encounter, where it happens and what options exist.