ºìÐÓÊÓÆµ

Sunlight shines through clouds onto the pond at Emereti Park.
Making Accessible IT Purchases

Accessible IT Purchases

Technology should work for everyone. At ºìÐÓÊÓÆµ, we’re taking steps to ensure that the IT products and services we purchase, or use (including free products) meet our legal obligations and reflect our commitment to accessibility and inclusion.

The Technology Review Process helps departments assess accessibility risk before purchases are finalized — replacing the former EEAAP system (Equally Effective Alternate Access Plan) with a more streamlined, scalable, and transparent process.

Why Do Purchases Need an IT Review?

Technology reviews are necessary to comply with several University policies (91.00691.00404.001) and state law.

ºìÐÓÊÓÆµ created the IT Accessibility Policy 04.001 to align the institution with the non-discrimination provisions of the Americans with Disabilities Act (ADA), as amended, and Section 508 of the Rehabilitation Act as well as OHIO's commitment to inclusivity in August of 2017. 

ºìÐÓÊÓÆµ's IT Accessibility Policy 04.001 requires all purchases and created digital products and services to adhere to OHIO's digital accessibility guidelines. OHIO's guidelines are based on the World Wide Web Constortium's (W3C) Web Content Accessibility Guidelines .

Benefits of the IT Purchase Review process:

  • Aligns with Title II of the ADA (), requiring accessible digital tools and systems.
  • Replaces the EEAAP process with a risk-based approach focused on accountability and defensibility.
  • Integrates accessibility earlier in the purchasing cycle, with support for departments throughout the process.
  • Knowledge Base: Technology Review

    To learn more about Technology Reviews, what the reviews check, how the process works, and to view more technology review resources, visit the Knowledge Base Technology Review article.

  • Request a Technology Review

    As soon as you have selected the product you wish to purchase or renew, you can request a technology review. We encourage you to familiarize yourself with the Technology Review process by reviewing the Knowledge Base: Technology Review page.

Who Should Use This Process?

This process applies to:

  • Departments purchasing new or renewing existing IT tools
  • Faculty or staff submitting software/hardware purchasing request
  • Budget approvers and project sponsors
  • Procurement and IT governance stakeholders

IT Purchasing Process Frequently Asked Questions

When considering a new IT service or product for purchase, how can I ensure it is accessible?

Please visit thefor complete requirements for purchasing IT services or products. Accessibility is part of the full review process and there are a few things you can do and that OIT can help you with when considering a product or service:

  • Solicit accessibility information. ºìÐÓÊÓÆµ bidders and vendors shall be required to demonstrate that information technology provided to ºìÐÓÊÓÆµ conforms to or addresses each of the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.1, Level AA success criteria whenever this is possible. Vendors may do so by providing any of the following:  
    • An independent third party evaluation from a qualified accessibility professional  
    • An up to date (not older than 2 years) Voluntary Product Accessibility Template (VPAT). If a VPAT is used, the vendor must use the .
  • Validate accessibility information received. Wherever practicable, OIT's digital accessibility staff, or other qualified staff with expertise in digital accessibility, will attempt to validate the information provided by bidders and vendors, by  
    • obtaining additional information from the bidder or vendor to develop a complete and thorough understanding of the accessibility of the product or service; 
    • consulting with independent third parties who have evaluated the product or service for accessibility; or 
    • conducting an internal evaluation of the accessibility of the product or service  
  • Include accessibility assurances in contracts. The following contractual language should be inserted in contracts for the procurement of websites, web applications, software systems, electronic documents, e-learning, multimedia and programmable user interfaces wherever practicable:  
    • Contractor acknowledges and understands that its software is being licensed by Customer to be provided to its students.  Contractor acknowledges and understands that as a public institution of higher education that receives federal funding, Customer is required to comply with the Americans with Disabilities Act, 42 U.S.C. 12101 et seq. and Section 504 of the Rehabilitation Act 29 USC 701 et. Seq.  Contractor agrees that its software will comply with the Americans with Disabilities Act, 42 U.S.C. 12101 et seq. and Section 504 of the Rehabilitation Act, 29 USC 701 et seq. as those laws apply to Customer, will be accessible to individuals with disabilities, and will meet current ºìÐÓÊÓÆµ Digital Content Accessibility Guidelines.  Contractor agrees that failure to provide an accessible product is a breach of Agreement. Contractor acknowledges that certain services will not be ADA accessible until [DATE] and that Service Provider has committed to accessibility in their [DATE] version. Service Provider agrees that failure to provide an accessible product is a breach of this agreement beginning [DATE]. 
What is the Review Process?

The accessibility review process for information and communications technology (ICT) purchases and websites or web apps built by OIT begins with an  submitted by the OHIO employee making the purchase. Visit the for more details.

This form will help the accessibility and security teams determine the risk level and business use for the product. If further review is needed, OIT will send a more detailed form to the vendor to begin the review process.

Those products that do not pass accessibility review at any level can request an exception from the IT Accessibility policy. For full documentation of this process, please visit the ºìÐÓÊÓÆµ Accessibility website.

What is an Automatic Exception?

Under certain circumstances, an automatic exception to ºìÐÓÊÓÆµ policy 04.001 IT Accessibility may be granted based on the cost of the information and communication technology (ICT) and the number of students using it. 

However, no automatic exceptions to the review process will be granted to any ICT regardless of cost or number of students, if that ICT is required for a student to complete their academic requirements or if the ICT is used for critical/important transactions. Examples include:

  • Learning Management Systems and integrations
  • Standalone instructional support *
  • ICTs Used for critical or important transactions like 
    • Campus housing
    • Dining
    • Registering for classes
    • Paying bills
    • Obtaining transcripts
    • or to complete required training like AlcoholEDU.

* "Instructional support application" means a software application, whether used 

  • in a single course 
  • by a department 
  • by a college or by a school 
  • or University wide 

which OHIO makes available to students, and which is designed and dedicated to the purpose of collecting or delivering course content or assignments, or assessing student performance.

An instructional support application is peripheral to a learning management system and is not necessarily used alongside a learning management system.  

Instructional support applications are either "non-standalone," because they contain supplementary digital content provided (either directly or through third parties) by the publishers of texts and book-length course materials, or "standalone," because they do not contain such content.  Non-standalone content is not subject to accessibility review at this time

Examples of standalone instructional support applications include:

  • Turnitin
  • LearnSmart
  • Vista Higher Learning
  • Pearson MyLab Mastering
  • WebAssign
What is the exception process?

The IT Accessibility Policy allows for limited exceptions in certain cases. Information about the full review process and links to the exception request form can be found on the Office for Accessibility website

The language explaining the exception process can be found on the Information Technology Accessibility Policy webpage.

How can I speed up the process?

You can help move your request along quickly by doing three things:

  1. Submit early – Don’t wait until the last minute. Reviews often take 3-5 business days, and high-risk products can delay purchases up to three business weeks.
  2. Provide documentation – Include a VPAT or ACR from the vendor if you have one.
  3. Describe the use case – Tell us who will use the tool and what it will do as part of the IT risk review form. Be sure to tell us the specific solution you are purchasing (for example, if the vendor has many products, tell us exactly which one you are purchasing). This helps us assess risk more accurately.

We’re here to help, not slow things down. The more information you can provide up front, the faster we can complete your review. 

Our Commitment

This process supports our obligations under ºìÐÓÊÓÆµâ€™s Information Technology Accessibility Policy, State of ºìÐÓÊÓÆµ , and . It also ensures that our digital environment works for all students, faculty, staff, and visitors.