Overview Princeton University's Policy on Digital Accessibility requires that academic and administrative units conducting core educational or administrative activities align websites and other information technology with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.The University's Transaction Authority Policy requires that units contemplating agreements for websites or other information technology consult with and request reviews by the Office of Information Technology’s Digital Accessibility team to ensure compliance with the University’s Policy on Digital Accessibility.IT suppliers are expected to ensure their products are accessible to people with disabilities per the WCAG guidelines. Architecture and Security Review University offices are encouraged to discuss proposed products, and those up for contract renewals, with the Architecture and Security Review (ASR) team to help ensure they meet accessibility requirements along with those for cybersecurity and infrastructure. Suppliers are expected to bring a member of their accessibility team to ASR meetings. Accessibility Documentation Suppliers are asked to provide the following accessibility documentation:HECVAT QuestionnairePrinceton relies on the most current version of the Higher Education Community Vendor Assessment Toolkit to help it assess accessibility risk.VPAT Accessibility Conformance ReportThe University expects suppliers to have their products tested by professionals with accessibility testing expertise, using best practices, and to document the accessibility of their products using the Voluntary Product Accessibility Template (VPAT) report. Suppliers should use the 2.5 WCAG version of the report to indicate conformance to the World Wide Web Consortium's Content Accessibility Guidelines. Fill out the VPAT template in its entirety.Accessibility Roadmap Matched to Conformance ReportSuppliers are asked to provide the University with an accessibility roadmap, structured to match the findings of accessibility test results. Each accessibility issue should indicate a date by which it will be fixed.Any aspects of the product's design and functionality that do not meet WCAG criteria are considered product defects. Suppliers are expected to prioritize fixing defects ahead of feature requests.Offices should ensure the contract requires the supplier to commit to the roadmap, and should follow up with the supplier on a regular basis to ensure follow through. Third Party Testing If an IT supplier does not have expert accessibility testing staff, they are expected to have their product(s) tested and documented by an industry-recognized accessibility testing organization. Tests should prioritize:Key tasksPersistent elements, such as navigation, search, and footerTemplates and any aspects of the existing product that are based on a templateFeatures in developmentFrequently accessed contentAny function or content that has already been flagged by someone with a disability as problematic University Testing IT productsThe University may conduct its own product testing. The supplier should be prepared to provide a test account. In general, the University does not test until after the supplier has conducted its own thorough testing and attested to accessibility as described above.WebsitesUniversity offices that engage suppliers for website design should:Request an accessibility review of the initial designRequest an accessibility test during implementationAll websites are reviewed for accessibility before go-live. Suppliers are responsible for ensuring any site they deliver is accessible to and provides an equitable experience for people with disabilities. Accessibility Help Link Websites and other IT must include the Accessibility Help link in the footer or other persistent location, to allow people with disabilities to request assistance from Princeton. The link address is: https://accessibility.princeton.edu/help
