Third Party Vendors
Although many of our third party vendors don't have to be WCAG 2.1 AA compliant, as a college offering these services to our students and community, we must ensure they are compliant or find another vendor.
Please review the guidelines below and integrate them in your workflow.
Who is responsible?
Any employee who works with a third party vendor in their department must ensure the platform is WCAG 2.1 AA compliant.
Tools for Accessibility
Find or ask for WCAG 2.1 AA compliance statements from the third party vendor.
Third Party Vendor Best Practices
Services Already in Use
There are many websites, apps and other digital tools provided by third party vendors already in use at MCC. To ensure compliance, we need to:
Look for a WCAG 2.1 AA compliance statement from the vendor. If they do not have one readily available online, please request one.
While having a compliance statement is extremely helpful, we still need to make sure the content we are uploading or adding to the third party site, app, etc., is compliant.
Accessible Procurement Process
If you're considering purchasing a new digital product, please use the information below to guide the process. The IT department will also need to be involved in the purchase or use of any new digital product.
Research the product and find/ask for a digital accessibility statement from them before continuing the process. If it isn't WCAG 2.1 AA compliant, we will not be able to utilize it.
Along with a digital accessibility statement, vendors will likely have a HECVAT (Higher Education Community Vendor Assessment Toolkit) and a VPAT (Voluntary Product Accessibility Template).