Electronic Information Accessibility Frequently Asked Questions (FAQs)

These FAQs supplement the standard on Electronic Information, Communication and Technology Accessibility (S-5).

Web Pages

  1. What should be included in the contact information for each Web page?
  2. Where should contact information be located on each Web page?
  3. Do archived Web pages have to be in compliance with WCAG 2.0 Level AA?
  4. Do Web pages created prior to the effective date of the University’s accessibility requirements (March 15, 2010) need to be made Accessible?
  5. Who is responsible for making legacy and archived pages Accessible?
  6. What if a webpage cannot be made accessible?
  7. Does the standard apply to internal staff webpages that may only be in use for a short duration (e.g., summer instructional labs)?
  8. I have been notified that my website will be audited. What happens if something is found not to be in compliance?

Video/Captioning

  1. My department has a video posted online that is several years old, but still available because the information is relevant. Does it have to have captions?
  2. I will be using a video as part of a course. How do I get it captioned and how do I make sure the captions work when I show it?
  3. My department doesn’t have the resources to update all of our videos with captioning and audio descriptions. Can we request an exception?

Software, Hardware and IT Systems

  1. What are examples of software, hardware and IT systems?
  2. Is there language that should be included in RFPs, purchase orders and/or contracts for software, hardware and IT systems?
  3. How does my department know if we’re purchasing a product that is in compliance with the standard?
  4. I have received confirmation from multiple bidders that their products are in compliance with the standard. Is there anything else I should do?
  5. A vendor is upgrading an IT product that my department uses. Should we be worried about accessibility compliance?


Q1. What should be included in the contact information for each Web page?       

A1. Provide a phone number and/or e-mail address that puts the user in touch with someone responsible for the content and function of the page who can usually reply within one business day. Suggested language:

If you have trouble accessing this page because of a disability, please contact [insert job title] at [insert phone number and/or e-mail address].

Q2. Where should contact information be located on each Web page?

A2. The contact information described in the above answer should be indicated in plain text in the footer of each page, typically in the same place where the copyright and EAEOU statement are put.

Q3. Do archived Web pages have to be in compliance with WCAG 2.0 Level AA?

A3. Not generally, but websites containing core administrative or academic information, official records, and similar information must be made available in an Equally Effective format to individuals needing access to the information.

Q4. Do Web pages created prior to the effective date of the University’s accessibility requirements (March 15, 2010) need to be made Accessible?

A4. Legacy pages must be updated in a timely manner to be in compliance with the WCAG 2.0, Level AA, or the content must be made available in an Equally Effective format to any individual requesting access.

Q5. Who is responsible for making legacy and archived pages Accessible?

A5. The unit responsible for the creation and maintenance of the information is responsible for making it accessible.

Q6. What if a webpage cannot be made accessible?

A6. Requests for exceptions to the standard must be made in writing to the Equal Opportunity Compliance Officer for your campus. Requests for exceptions must provide a reason based on issues other than cost alone and will be evaluated on a case-by-case basis. Refer to the Contacts section of the standard for the appropriate contact.

Q7. Does the standard apply to internal staff webpages that may only be in use for a short duration (e.g., summer instructional labs)?

A7. Yes, the standard applies to all websites and pages, no matter the duration of their intended use, and even if they are available only to faculty, staff and/or students behind a login.

Q8. I have been notified that my website will be audited. What happens if something is found not to be in compliance?

A8. The Equal Opportunity Compliance Officer will first attempt to secure voluntary compliance by working with the owner of the website and with campus resources to remediate any area of noncompliance. The officer will determine on a case-by-case basis whether the website should be disabled until such time as it is brought into compliance or until an Equally Effective alternative is made available. If efforts to secure voluntary compliance are unsuccessful, the Equal Opportunity Compliance Officer will consider whether to file a complaint under the policy on Equal Opportunity, Equal Access and Affirmative Action (III.C.2)

Back to Top

Q9. My department has a video posted online that is several years old, but still available because the information is relevant. Does it have to have captions?

A9. Yes. Any non-captioned and non-described video still in use, whether on a website, in Blackboard, or for in-class display, must be updated to have captions and be audio-described.

Q10. I will be using a video as part of a course. How do I get it captioned and how do I make sure the captions work when I show it?

A10. Your campus Equal Opportunity Compliance Officer can direct you to the resources available for captioning and playing video, including training on AV equipment and vendors to perform captioning. Refer to the Contacts section of the standard for the appropriate contact on your campus.

Q11. My department doesn’t have the resources to update all of our videos with captioning and audio descriptions. Can we request an exception?

A11. Lack of sufficient funding, in and of itself, is not considered justification for an exception. You may discuss options with your campus Equal Opportunity Compliance Officer (see the Contacts section of the standard).

Back to Top

Q12. What are examples of software, hardware and IT systems?

A12. Examples include learning and content management systems, library and email systems, and administrative management systems such as finance, registration and human resources, and all software, hardware and software services used for student services, employment purposes, and customer service purposes. Software includes freeware, shareware, desktop, enterprise, subscription and remotely-hosted options.

Q13. Is there language that should be included in RFPs, purchase orders and/or contracts for software, hardware and IT systems?

A13. The following language is recommended for RFPs, purchase orders and contracts:

The University is committed to purchasing products and solutions that meet the applicable standards of Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.  This is predominantly applicable to the following:

  • Software applications and operating systems
  • Web-based intranet and Internet information and applications
  • Video or multimedia products

Bidders shall indicate whether the product or solution they will be providing meets WCAG 2.0 Level AA. If so, the bidder will provide the results of a compliance audit or test results that document the testing methodology utilized to determine the product or solution's compliance and the results of the accessibility audit. They will also specify whether the testing was conducted by the vendor or an independent third party auditor (independent third party preferred).

Finalists may be expected to allow Purdue University to test their product/solution and assess their compliance with WCAG 2.0 Level AA. It is preferred that vendors notify Purdue University in advance of an upgrade or patch, and provide information demonstrating the upgrade or patch will not negatively affect accessibility. Purdue University also reserves the right to periodically test the product/solution throughout the contract period to make sure as upgrades or patches are implemented, that accessibility is not negatively affected.

Q14. How does my department know if we’re purchasing a product that is in compliance with the standard?

A14. Vendors may show proof that the product or solution they will be providing meets WCAG 2.0 Level AA in the form of results from a compliance audit or test results that document the testing methodology utilized to determine the product or solution's compliance and the results of the accessibility audit. Ask the vendor also to specify whether the testing was conducted by the vendor or an independent third party auditor (independent third party preferred).

Q15. I have received confirmation from multiple bidders that their products are in compliance with the standard. Is there anything else I should do?

A15. You may request that each vendor allow the University to test the product/solution and assess their compliance with WCAG 2.0 Level AA. If you need assistance with this, please contact your campus Equal Opportunity Compliance Officer to be put in touch with appropriate resources (see the Contacts section of the standard).

Q16.  A vendor is upgrading an IT product that my department uses. Should we be worried about accessibility compliance?

A16. In advance of an upgrade or patch, ask the vendor to provide information demonstrating that it will not negatively affect accessibility. The University reserves the right to periodically test products throughout the contract period to make sure accessibility is not negatively affected as upgrades or patches are implemented.

Back to Top

Purdue University, 610 Purdue Mall, West Lafayette, IN 47907, (765) 494-4600

2015 Purdue University | An Equal Access/Equal Opportunity University | Copyright Complaints | Maintained by: Office of Institutional Equity

If you have trouble accessing this page because of a disability, please contact the Office of Institutional Equity at equity@purdue.edu or (765) 494-7255