In this article
What are third-party applications?
A third-party application is a web-based technology not exclusively owned, operated, or controlled by an entity that uses it on its website.
While third-party applications can enhance functionality, they can create accessibility barriers for users with disabilities.
Examples of Third-Party Applications
Calendars
Social Media Feeds
Maps
Lead Generation Services
News Services
Are you responsible for the accessibility of embedded third-party content?
Yes. If the content lives on your domain, i.e. the content can be reached at yourorganization.com or yourschool.edu, then you are responsible for the accessibility of that content.
For this reason, it is recommended to link to the third-party site directly for any content that isn’t accessible that you cannot edit yourself.
What responsibility is there if the third party does not have a VPAT, but we disclose the violations?
Your level of responsibility remains the same regardless of the presence of a Voluntary Product Accessibility Template, (VPAT). Essentially, including the third party's VPAT in your accessibility statement reduces risk while you work on its remediations. It does not absolve you of responsibility.
An existing VPAT could also open up a conversation with the third party about changes that need to be made to comply with accessibility standards. However, even if you don't have their VPAT, you can and should still disclose the violations. Making your accessibility plan known is always a great strategy.
Accessibility Barriers that Third-Party Applications can Introduce
Lack of keyboard navigation: Many applications rely on mouse clicks, excluding users who navigate with keyboards or assistive technologies.
Keyboard traps: Many embedded applications cause the keyboard focus to get "trapped" within the content and offer no way to release the focus.
Missing or incorrect ALT text: Applications like maps or social media feeds may lack alternative text descriptions for images or non-text content.
Color contrast issues: Third-party applications might not follow the same color contrast standards as your website, making the content difficult for visually impaired users.
Incompatible with assistive technologies: Screen readers or other assistive technologies might not be able to interact effectively with the application.
Dealing with Inherited Third-Party Software
One of the downsides to using third-party software is the inability to update the HTML behind the page.
If the vendor’s product does not meet your criteria, consider letting them know and ask if they are willing to make the adjustments. Many vendors are being pressured to update their applications or risk losing out on business, so many are willing to accommodate these requests.
You can use DubBot's feature to Ignore an Issue based on the Source.
For Accessibility and Best Practices issues, you can select a single occurrence of an issue on a page and ignore just that issue for the site, account, or only the current page. This is particularly helpful when dealing with third-party embeds that have issues over which you have no control. You should ensure there is an alternative method for interacting with the third-party content, you may be then able to ignore the error specific to that third-party embed.
Learn more in our Ignoring and Resolving Issues article.
Before You Start Using Third-Party Software
Clearly state the level of accessibility compliance your organization adheres to in all contracts and Requests for Proposals.
Research accessibility features and test third-party applications before integrating them.
Look for vendors who provide an Accessibility Conformance Report (ACR) using a Voluntary Product Accessibility Template (VPAT) to outline their accessibility compliance.
Have no choice but to use a particular piece of software? Require remediation (along with a deadline for completion) from the vendor as part of the sales agreement. You will also want to add a penalty for non-remediation or a "bonus" of some type for prompt compliance.
Consider alternative solutions: Based on the results of the first two bullet points, ask yourself: Can I achieve the desired functionality with a more accessible option? Can this opt-in be built in-house?
Provide alternative content or information for inaccessible third-party application features. For example, if the application is a calendar, provide a link to an accessible webpage with the details on current events at your organization.
Learn More
If you have questions, please contact our DubBot Support team via email at help@dubbot.com or via the blue chat bubble in the lower right corner of your screen. We are here to help!