5. Procurement and Accessibility Policy
Many organizations will have in-house developers who create and maintain web content and who can be trained to implement web accessibility in their development practices. Most organizations however, will purchase or license third-party software or Web applications for particular purposes rather than having their in-house developers create them. It is generally more economical to license than it is to create complex systems like a content management system (CMS) or a customer relationship management system (CRMS).
The accessibility of these third party tools should always be assessed before committing to a particular system. This often starts by asking vendors to describe the accessibility features of their product in a request for proposals (RFP). This request might include:
- A checklist of desirable accessibility features that the vendor completes
- A request for a Voluntary Product Accessibility Template (VPAT) if the company is in the U.S.
- A request for a third party evaluation of the product being procured
Here are some tips to follow once you receive accessibility information from vendors:
- Do some research and take the time to carefully assess the vendor’s claims for accuracy: Because vendors are often in competition to win your business, it is possible that they may exaggerate claims, word claims to work around known issues in their products, and, in the worst cases, make false claims about the accessibility of their products. It can be helpful to look at the vendor’s own website, test it with an automated checker, and look for accessibility information there. This can tell you a lot about the vendor’s accessibility knowledge. Failing to assess a vendor’s claims may have significant legal consequences, if accessibility claims are made against your organization and it can be shown that due diligence was not employed when acquiring a product.
- Think beyond “yes or no”: It is not uncommon to shortlist a product for purchase or licensing that is not fully accessibility compliant, but that does have a good variety of accessibility features. It can be counterproductive to make absolute compliance a requirement. You may find for some complex systems that there are no fully compliant offerings. A system may not be compliant, but it may be the most accessible of a class of systems. Aim to procure the system that provides the best mix of required features and accessibility.
Once your organization has decided on procuring a system, it is important to build accessibility requirements into the contract, so that if issues are later found that present significant barriers, vendors must take responsibility and provide solutions.
Some vendors will be receptive to accessibility requests, particularly those in regions where accessibility laws affect their ability to sell their products. It is not uncommon for vendors to have little knowledge of accessibility, having never had such a request (but who, when educated, may be very happy to accommodate those requests). To set yourself up for success, simply plan to work with vendors that understand the importance of accessibility.
Readings & References: For more about strategies for procuring accessible IT, review the following resources.