Below are some of the frequently asked questions regarding digital accessibility and diversity.
What is included in digital accessibility compliance requirements?
Find out on our digital accessibility program page.
Who is impacted by non-compliant electronic and information resources (EIR)?
Visit this digital diversity page to find out.
What are some examples of assistive technology devices and tools, and who are they used for?
Find out more on our digital diversity page.
Who is responsible for accessibility compliance?
The short answer is we all play a part in digital accessibility.
- Leadership shall approve all exceptions and alternative-accommodation processes.
- The Texas A&M Engineering Experiment Station (TEES) Chief Information Officer (CIO), as policy sponsor in collaboration with key stakeholders, approves all work group initiatives and changes to policy.
- The Digital Accessibility Officer monitors procurement of hardware and software accessibility documentation requirements and coordinates the training, reporting, and overall digital accessibility program maturity.
- Communications designs, monitors, and manages digital content and websites and provides guidance on developed, maintained, or published accessible communications by or on behalf of the institution.
- Procurement ensures the Technology Access Clause (TAC) is included for all procurements of software and hardware, and the specification or statement of work includes language to address compliance with accessibility standards.
- All other employees, contractors, and vendors who create digital content shall support compliance with this policy as appropriate to their specific work functions and be trained on how to create accessible digital content.
How is accessibility compliance documented?
Accessibility compliance documentation is gathered in many ways. When procuring or renewing hardware or software, one or more of the following may be gathered from the vendor:- Voluntary Product Accessibility Template (VPAT) – Completed by Vendor. Every hardware/software contract should have a recently completed VPAT called an Accessibility Compliance Report. (Some exceptions apply)
- Vendor Accessibility Development Services Information Request (VADSIR) (if required) – Provided by vendor during solicitation responses to document skills and processes used internally related to development.
- Policy Driven Adoption for Accessibility (PDAA) Vendor Assessment (if required) – Used as part of vendor solicitation responses describing how they are currently implementing accessibility policy and practices within their organizations.
When custom development on a user interface is part of the project, the following accessibility compliance reporting should be done on new ICT development prior to launch:
- Manual testing – Audits of a sampling of pages or end-to-end testing of custom-built products including multiple tools and assistive technologies to ensure the interface works for everyone. (This is conducted during build and testing, prior to deployment). When items are discovered during manual testing.
- Remediation prior to launch – High priority compliance defects should be corrected prior to launch (they will be identified in the manual testing report)
- Compliance plan – Needed for items found to be not in compliance but are not as urgent; need to be planned into future project modifications/updates.
- Automated scanning tools – Monitors HTML code to provide list of issues that need to be fixed and warnings for areas that need review.
Some applications or product of high value or high impact can also require:
- User Acceptance or Quality Assurance Testing – Experts navigate the environment to ensure it meets with all project requirements and functional performance criteria.
- Usability Testing – Conducted with external representatives or customers to determine if the product is usable and meet the user's expectations. (Optional)
Does being a Department of Information Resources (DIR) Vendor or TXRAMP-approved mean the vendor has completed the accessibility compliance documentation?
No, being a DIR vendor does not imply that the products in the cooperative contracts program are accessible. Vendors provide limited to no accessibility compliance documentation to DIR. Per the TAC rules, it is the procuring institution’s responsibility to obtain credible evidence of accessibility compliance in hardware and software procurements.
What are some examples of situations that do not require accessibility compliance documentation?
Out of scope - Operational technology like high-voltage systems, servers, networking equipment, and equipment behind locked doors.
Plugins - if the plugin does not impact the user interface, then an accessibility conformance report (ACR) may not apply. The ACR for the standard application should mention the accompanying plugin. Check areas that relate to the plugin's functionality. ACRs for plugins are not common.
Servers - Back-end systems or hardware located behind a secure or locked door do not require an ACR.
What is the difference between an accessibility exception and an exemption?
Exception - The TEES Digital Accessibility Officer has determined compliance with a provision of EIR accessibility law or administrative rules imposes a significant difficulty or expense to the institution and the documented non-conformance has been approved by the institution head.
Exemption - EIR accessibility exemptions can only be made by the DIR. The following EIR currently has an exemption file for Geographic Information Systems (GIS) Software.
Texas A&M TEES maintains records of approved exceptions in accordance with the records retention schedule.