Electronic Information Technology and Software Accessibility
The clause below must be included in all contracts involved in the purchase or subscription use of electronic information technology (EIT).
Compliance with Laws/Policies. Other Party warrants and certifies that in performance of this Agreement, it will comply with all applicable statutes, rules, regulations, including laws and regulations pertaining to the subject matter of this Agreement. Other party also agrees to maintain compliance with WCAG 2.0 AA accessibility standards.
This procedure applies to all purchases of EIT goods and/or services that fall into one of the following ten categories:
- Telecommunications products
- Information kiosks
- Transaction machines
- World Wide Web sites
- Software and mobile applications
- Computer operating systems
- Electronic Office Equipment (such as copiers and multi-function devices)
- Any device or system that is used in the creation, conversion, or duplication of data or information
Demonstrating Accessibility - What We Need To Know
In order to demonstrate software accessibility within the College community, suppliers may be asked to complete our Information Security Posture & Accessibility Compliance Questionnaire. Below are examples of questions we ask:
- Does your company have a Voluntary Product Accessibility Template (VPAT) for a current version of your product that documents product conformance with WCAG standards?
- If your company has a VPAT, please provide it to your College contact (example: Google's VPAT for Gmail). If your company does not have a VPAT, please describe your perspective on accessibility and any exceptions you believe are applicable.
- Please describe your accessibility conformance testing process.
- Does your company have an Accessibility Roadmap to remediate any accessibility gaps in a reasonable period of time? An Accessibility Roadmap can be a list and description of accessibility gaps, including current resolution status of each gap and a specific timeline for remediation. An Accessibility Roadmap also lists any known workarounds to provide end-users access until the vendor has resolved each of the accessibility gaps. If an Accessibility Roadmap is available, please provide it as an attachment in response to this email.
- Can you share with us your company's Accessibility Mission Statement or equivalent?
- To whom in your company should we direct our accessibility questions should we have any (name and contact information)?
- Could you show us how your application works using only the keyboard to navigate. In other words, please do not use the mouse to get to the various sections of the page - use only the keyboard to do so. If this is not possible, can you show us how it works using a screen reader? Acceptable screen readers are JAWS and NVDA for windows or VoiceOver for Macs.
Tools We Use When Testing for Accessibility
- * Testing without a mouse
- Navigating using screen reader technology (e.g. NVDA, JAWS, VoiceOver)
- Browser based tools
- Browser Developer Tools
- Disabling Cascading Style Sheets (CSS)
* these tools are ones we have found most informative
If you are interested or need to know more about how to apply WCAG standards, the W3C has a very useful reference guide that provides a good starting point. The other resource we have found useful when learning about web accessibility is WebAIM.
In the United States, approximately 1 in 4 persons have an identified disability. In addition, the World Health Organization estimates that about 15% of the world's population lives with a disability. WebAIM has gathered several simulations which you may find useful to gain a general understanding of challenges some people face.