Accessibility has partnered with ITS<\/a> and Contracts, Purchasing, and Risk Management<\/a> (CPRM) to develop a process for purchasing services, technology, software, and hardware, that aligns with NAU\u2019s current policies and needs. This process is under constant refinement, so we appreciate your patience as we grow and improve to better serve you.<\/p>\n Since these 3 processes are significantly intertwined you can refer to the Purchasing Technology at NAU<\/a> page for instructions on the process. This page will tell you if you need a Contract Signature Request (CSR) or just approval from ITS and Accessibility.<\/p>\n Usability is a key factor when developing products and websites. Universally designed products and websites allow as many users as possible to interact within the digital world without the need of additional technology. Designing with accessibility in mind goes one step further to ensure individuals with disabilities that use assistive technology have the opportunity to interact with products and websites in that same digital world.<\/p>\n Section 504 of the Rehabilitation Act and the Americans with Disabilities Act cover accessibility. Information and Communication Technology (ICT) purchased, developed, maintained, or used by the University must meet federally recognized accessibility guidelines. As such, we are required to follow the Web Content Accessibility Guidelines (WCAG) 2.0 at the AA level.<\/p>\n The Department of Education Office for Civil Rights (OCR) enforces compliance with accessibility requirements. OCR has created over 1,000 resolution agreements with schools around ICT accessibility.<\/p>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\n Any Information and Communication Technology (ICT) in use at Northern Arizona University (“University”) should be fully accessible to people with disabilities. If a product or service is not fully accessible, an Equally Effective Alternative Access Plan (EEAAP)<\/a> should be in place to compensate for the lack of accessible feature(s).<\/a> This plan should be developed in advance of any requests for accommodation so that in the event of a request for access, there will be minimal delay in providing the accommodation.<\/p>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\n Accessibility Documentation.<\/p>\n Ask the vendor to provide an Accessibility Conformance Report (ACR), which is a completed <\/span><\/span>Voluntary Product Accessibility Template (VPAT). <\/span><\/span>If they do not have a VPAT or an ACR, request an accessibility statement or Section 508 Statement.<\/p>\n<\/body><\/html>\n\n <\/div>\n<\/div>\n\n\nFAQ<\/h2>\n\n
Why do we do an accessibility review? Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
What happens if the software I need is not fully accessible? Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
What paperwork do I need? Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n
I have other questions not answered here. Accordion Closed<\/span><\/h4>\n <\/span>\n <\/div>\n <\/a>\n