The University procures ICT that is universal in design and accessible to all individuals, including individuals with disabilities. In the event this is technically infeasible or imposes undue burden, the University ensures an equally effective accessible alternative. All ICT must meet the applicable accessibility standards set forth in Section 508 of the Rehabilitation Act of 1973, as amended (Sec. 508), the Americans with Disabilities Act of 1990, as amended (ADA), and University of Nevada, Reno Benchmarks for Measuring Accessibility
Please send questions or comments to firstname.lastname@example.org and the Software Accessibility team will respond as soon as possible.
ICT Procurement Process
STEP ONE: Gather Information and Required Documents
- Obtain compliant accessibility documentation from the vendor.
- The Voluntary Product Accessibility Template (VPAT) Version VPAT2.2WCAG - July 2018 can be found at the bottom of the Information Technology Industry Council Accessibility web page.
- If the VPAT lists some items as "partially supports" or "does not support", you must provide documentation from the vendor indicating their intent to remediate those barriers including a time line for expected completion of remediation.
STEP TWO: Submit for ICT Review
- Complete and submit the Information and Communication Technology (ICT) Software Accessibility Review form and attach accessibility documentation from step one above.
STEP THREE: ICT Review Process
- If the product is student- or public-facing, it may also require internal UNR ICT Software Accessibility Review Committee testing to identify any potential critical barriers to access and clarify any questions regarding the VPAT. You will be contacted with more details if such testing is necessary. You will receive a written report of findings and a recommendation of next steps once the VPAT review and the internal test, if applicable, are complete.
- The Committee has the discretion to choose not to test some student- or public-facing software. Examples of instances that may preclude testing include;
- Software that has limited impact (relatively low number of users)
- Committee has prior knowledge of the product accessibility (tests performed by other institutions)
- Provided documentation clearly satisfies all Committee interests
What to do if your ICT request is not accessible?
If your accessibility review documentation indicates the product or service is not accessible, you can do any of the following:
- Develop an Equally Effective Alternative Action Plan (EEAAP). Work with your vendor to develop an Equally Effective Alternate Access Plan (MS Word) and submit to the ICT Software Accessibility Review Committee for approval.
- Submit an Alternative Option. Select a more accessible solution.
- Submit an Exception Request. Submit an ICT Accessibility Exception Request (MS Word) form.