You are here: Home Web Team Accessibility Purchasing Software

Purchasing Software

Accessibility checklist for district offices and schools purchasing software

Accessibility? What does that mean?

  • Making it possible for all abilities and disabilities to access online information.

  • Removing barriers for anyone having difficulties using a keyboard or mouse, unable to hear or see well, using assistive devices, or finding words difficult because of fonts, styles, and colors.

  • Accessibility overview


Purchasing business and curricular software for use by APS students, parents, and employees can streamline clunky processes and offer a boost in productivity, as well as learning. 

However, due to some recent changes that affects all district online content, we must be extra mindful about how we purchase software.

According to our resolution agreement with the Office of Civil Rights (OCR), August 2016:

All existing content, "including online content and functionality developed by, maintained by, or offered through a third-party vendor or open source", must meet federal requirements for online accessibility.

Unfortunately, sales representatives may not know if their products are accessible to all users or not. So, before you buy, you will first need to make sure that software meets accessibility compliance by asking questions and getting documented verification from the software vendor.

We have prepared a checklist to help you when considering software for your department or school.


Need help?

Contact  Procurement or the Web Team

For the vendor:

  • How long has the company been implementing accessibility into their business practices?
  • Is their focus on both web and mobile accessibility?
  • Does the company employ people with disabilities as testers, engineers and consultants?
  • Is their own website compliant with WCAG 2.0 Level AA and WAI-ARIA 1.0?
  • Are consulting and support services provided to clients to help with accessibility issues on their websites and applications?
  • Can you provide documentation on how it is accessible?

For the product:

  • Is the software interface/program accessible?
  • Can this be used across all browsers, such as Internet Explorer, Safari, Firefox, Chrome, etc.?
  • Do you perform regular testing to check if the product is accessible after it's launched?