But here’s the catch: if these tools are part of your digital experience and serve EU customers, they need to comply with the EAA’s accessibility standards.
Do third-party tools need to be accessible?
Absolutely. If a third-party tool is visible to or used by your customers, it must meet the same accessibility standards as your core website or app. Simply put, you’re responsible for ensuring all integrated tools provide an inclusive user experience.
Why third-party accessibility matters
Even the most accessible website can fall short if a third-party tool creates barriers.
For example, an accessible e-commerce site can become unusable if its payment gateway doesn’t support screen readers or keyboard navigation.
These gaps can frustrate users, violate the EAA, and result in penalties.
What kind of third-party tools are covered under the European Accessibility Act?
Here’s a non-exhaustive list of common third-party tools that need to meet EAA accessibility standards:
- E-commerce platforms (e.g., Shopify, WooCommerce): Ensure checkout and product navigation are accessible.
- Payment gateways (e.g., PayPal, Stripe): Transactions must be smooth for all users, including those using assistive technology.
- Live chat widgets (e.g., Intercom, Zendesk Chat): Provide accessible customer support channels.
- Video players (e.g., YouTube, Vimeo): Include captions, audio descriptions, and accessible controls.
- Pop-ups and modals (e.g., Mailchimp pop-ups): Ensure they are keyboard-navigable and easy to dismiss.
- Booking systems (e.g., Eventbrite, OpenTable): Make forms and navigation accessible.
- Interactive maps (e.g., Google Maps embed): Provide text alternatives and ensure usability without a mouse.
- Cookie banners: Allow easy consent management for all users.
How to ensure third-party tools are compliant
Making sure your tools comply might seem tricky, but these steps can help:
- Research accessibility claims: Check for accessibility statements or documentation from providers. If accessibility isn’t mentioned, ask questions.
- Request a VPAT: A Voluntary Product Accessibility Template (VPAT) details how a tool meets WCAG standards. Ask vendors for this document to assess compliance.
- Test the tools yourself: Use screen readers, keyboard navigation, or automated tools like Silktide to verify accessibility claims.
- Prioritize accessible options: When choosing new tools, opt for providers with a strong track record in accessibility.
- Monitor updates: Re-test tools regularly to ensure updates haven’t introduced new barriers. Continuous monitoring tools can simplify this process.