Title II FAQs
What is in scope for the Title II project?
All web applications, mobile applications, training courses, web sites, vended applications and documents are included. If you can view it electronically then it is in scope for Title II.
What is the deadline for making my application fully accessible?
All applications identified as part of phase one should be tested and remediated by April 24th, 2026. As each team finishes with phase one applications, they will continue working toward meeting accessibility requirements with all other applications they support. If possible, AITS would like to have all internal applications tested by April 24th, 2026.
How do I request accessibility testing from the AITS Quality Assurance team?
Testing requests should be submitted to the Quality Assurance team use the TDX intake form.
What if my application is going to be decommissioned?
If you have a decommission date please provide that information to the Quality Assurance team. We will watch for the decommission event and remove the application from the testing list at that time. If you don’t have a date yet please provide as much detail as possible about the decommission or replacement plan for the application so that a determination can be made on the best use of our testing and development resources.
Do I need to provide use cases before testing can begin?
If your application is a one or two page form then use cases are not needed. For medium or large applications that have a lot of functionality, please create a use case document or schedule a walk through meeting with the testing team. This will ensure that testers follow a standard workflow for you application and that they have all the information needed to navigate to all sections of the application.
How will accessibility issues be tracked?
AITS QA will created a project in Reqtest for your application. This will be used to track issues found and assign issues to the person who requested testing. The requestor will work with the development team to determine the level of remediation needed and involve the UX team if design changes are required.
Once application updates have been made to correct accessibility issues, Reqtest items should be reassigned back to the QA team for retesting before application updates are promoted to production.
The QA team will follow up with regular check-ins with development teams to track progress of fixes and provide any assistance needed.
Are vended applications included in this project?
Yes. The Title II Federal regulations also include accessibility requirements for vended applications that we use and provide to staff, faculty and students for use. Every vendor that we work with has received a letter informing them of the regulations and their role in meeting accessibility requirements. We are in the process of gathering Accessibility Conformance Reports from all vendors. Those documents will be reviewed along with accessibility testing of each product to determine any remediation actions needed. The depth of testing for vended applications can vary. QA is available to answer questions and help determine what is needed.
My vended application uses an overlay. Is that considered accessible?
Overlays, sometimes also called bolt-ons or accessibility mode, present a “separate but equal” environment and experience for disabled people and are not an acceptable solution. Overlay Factsheet
The Americans with Disabilities Act and the Department of Justice state:
a. “As WCAG 2.1 defines it, a conforming alternate version is a separate version of web content that is accessible, up to date, contains the same information and functionality as the inaccessible web content, and can be reached in particular ways, such as through a conforming page or an accessibility-supported mechanism. However, the Department is concerned that WCAG 2.1 could be interpreted to permit a segregated approach and a worse experience for individuals with disabilities. The Department also understands that, in practice, it can be difficult to maintain conforming alternate versions because it is often challenging to keep two different versions of web content up to date. For these reasons, as discussed in the section-by-section analysis of § 35.202 (of Title II of the ADA), conforming alternate versions are permissible only when it is not possible to make web content directly accessible due to technical or legal limitations.” (Title II Fact Sheet)