Procurement
Review Accessibility Responsibilities for a Third-Party Service
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Map who can repair each part of an integrated service and how defects will be escalated. Work with the organization's procurement or legal owner for contract terms. This workflow prepares operational evidence, not a legal contract.
A practical example
A website embeds a payment service while the merchant controls the surrounding labels, instructions and error presentation.
How to check it
- Draw the boundary between host content, integration code and vendor interface. Record versions, configuration choices and support contacts for each area.
- Review available accessibility evidence against the deployed integration. Identify unresolved barriers and the party able to change the affected behavior.
- Document the reporting route, interim user support and expected retest evidence. Confirm how updates will be communicated and checked after release.
What can be missed
A supplier's report can exclude the integration layer. Assigning responsibility does not make an inaccessible dependency disappear from the user's process.
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.