Requestor selects a product and follows steps outlined below.
Software / SaaS Requests
- Request a VPAT (2.x or higher) from the vendor
- Request demo, sample or trial version of software from vendor for accessibility testing
If the VPAT indicates that the product is compliant ('Supports' for all checkpoints)
- Review Compliant Software Acknowledgement page
- Submit VPAT along with a VPAT 2.x Validation Checklist
- An informational notification is sent to the AAC via OrangeTracker
- Acknowledgement of receipt is sent to requestor
- Accessibility procurement process ends
If the vendor does not have a VPAT, or if the VPAT does not indicate that the product is compliant
Review Non-Compliant Software Request page
- Submit VPAT (if available), procurement form, results of local assessment, and vendor roadmap (if available)
Accessibility Assessment Committee (AAC) begins review with a two week turnaround time
AAC provides response to requestor: Approved, Conditionally Approved or Denied
If Request is Conditionally Approved:
AAC shares findings with requestor
Requestor addresses findings and coordinates with all relevant parties
- If Request is Denied:
- Requestor seeks a more accessible product and begins from the start of the Accessibility Procurement process, or
- Submits an Exception Appeal Request to the Accessibility Compliance Committee (ACC), or
- Accessibility procurement process ends
Hardware Requests
- Request a VPAT 2.x or higher from the vendor
- Request a roadmap to address accessibility issues identified in VPAT from the vendor (if applicable)
- Review Hardware Procurement Request page and submit with required documentation
- Accessibility Assessment Committee (AAC) begins review with a two week turnaround time
- AAC provides response to requestor: Approved, Conditionally Approved or Denied
- If Request is Approved or Conditionally Approved:
- AAC shares findings with requestor
- Requestor addresses findings and coordinates with all relevant parties
- If Request is Denied:
- Requestor seeks a more accessible product and begins from the start of the Accessibility Procurement process, or
- Submits an Exception Appeal Request to the Accessibility Compliance Committee (ACC)
- Accessibility procurement process ends
Policy Exclusion Acknowledgements
- Review Policy Exclusion Acknowledgement page and submit with required documentation
- An informational notification is sent to the AAC
- Accessibility procurement process ends
Exception Appeal Requests
- Review Exception Appeal Request page and submit with required documentation
- Accessibility Compliance Committee (ACC) begins review
- If Exception Request is approved:
- AAC shares findings with the requestor, and
- Requestor addresses findings and coordinates with all relevant parties
- If Exception Request is denied:
- Requestor seeks a more accessible product and begins from the start of the Accessibility Procurement process, or
- Accessibility procurement process ends