Third Party Plugin
Accessibility & ADA Compliance
Third Party Plugin Accessibility & ADA Compliance
Most websites today use plugins and third party components to deliver functionality that extends the capabilities of the native content management system. CMSs such as WordPress, Drupal, Expression Engine, Shopify, Magento and many many others all rely on external third parties to create plugins that provide specific functions such as events calendars, email capture, appointment scheduling, ecommerce, and an endless number of features.
Some are plugins and some are more extensive systems that don’t plugin to your CMS, but run independently. A lodging room booking system, an ecommerce system, or a spa reservation system would be good examples.
Most plugins and third party systems were not designed or built to be accessible however. And it can be very frustrating for website owners and their developers to make these systems on their websites accessible, because these providers typically offer limited degrees of access for your developers to modify them. In most cases, one can only modify style sheets to control colors and fonts. But most often that stops there, leaving the elements that affect accessibility behind locked doors to your developers.
What is the standard for website accessibility?
The de facto standard for ADA compliance is to meet the requirements of the Web Content Accessibility Guidelines. The WCAG has been created by the W3C, an international digital standards consortium, and it is currently in version 2.1. 2.2 is expected to be published at the end of 2021. The WCAG is broken down into 3 levels: A, AA, AAA. The current minimum requirement is to meet WCAG 2.0, A, AA.
Do third party components and plugins need to be ADA compliant?
The short answer is yes. The website owner takes on the liability of every element of a website that lives within www.yourcompany.com domain. And that’s a key determining factor. Does the third party component or system live on your domain, or on a separate domain from the provider?
In the hospitality space for example, you may have a booking engine that includes a booking widget that takes the guest’s initial arrival, departure, and number of guests and sends the user to the provider’s domain to see room availability and place the booking. In this case, the arguable limit of liability would be just the initial booking intake widget. Once the user leaves your domain, your technical liability ends. But that doesn’t mean that consumers will see it that way.
Disclaimer: This post and the headline is my opinion. I provide facts throughout to inform that opinion. I am also not a lawyer and this post does not constitute legal advice.