VPAT® 1.0 was discontinued January 18, 2018. Additional information provide on the Information Technology Industry Council (ITI) website.

What does the vendor report?

Note that the Texas Administrative Code (TAC) aligns its compliance standards with the United States Access Board’s compliance standards in Section 508. This makes assessing compliance for state and federal procurements easier due to their similarities.

If using VPAT® 2.0 (October 2017), please review the reports vendors are require to fill out on the VPAT® 2.0. Below is the explanation for VPAT® 1.0.

The vendor goes through the section(s) their product(s) fall under:

  • Section 1194.21 (or TAC §213.30) Software Applications and Operating Systems
  • Section 1194.22 (or TAC §206.70) Web-based Internet Information and Applications
  • Section 1194.23 (or TAC §213.31) Telecommunications Products
  • Section 1194.24 (or TAC §213.32) Video and Multi-media Products
  • Section 1194.25 (or TAC §213.33) Self-Contained, Closed Products
  • Section 1194.26 (or TAC §213.34) Desktop and Portable Computers

Additionally, the vendor must go through the following sections:

  • Section 1194.31 (or TAC §213.35) Functional Performance Criteria
  • Section 1194.41 (or TAC §213.36) Information, Documentation and Support

The vendor responds to each Criteria under the Supporting Features with the one of the following:

  • Not Applicable
  • Not Applicable – Fundamental Alteration Exception Supplies
  • Not Supported
  • Supported
  • Supported with Exceptions / Partially Supported
  • Supported through Equivalent Facilitation
  • Supported when combined with Compatible Assistive Technology

The vendor should clarify the compliance under Remarks and explanations to avoid a long assessment before the procurement process is completed.

Criteria’s Supporting Features StatusWhat to provide in Remarks and explanations
Not ApplicableDescribe why the criteria is not applicable to the product.
Not Applicable – Fundamental Alteration Exception SuppliesUse this language when you determine a fundamental alteration to the product would be require to meet the Criteria (see the Access Board’s E202.6 Undue Burden or Fundamental Alteration).
Not SupportedDescribe how the product does not support the criteria.
SupportedList what features of the product do meet the criteria and describe how they are used to support the criteria.
Supported with Exceptions / Partially SupportedList what features of the product do meet the criteria and describe how they are used to support the criteria. Then list what parts of the product do not meet the criteria and describe how they fail to support the criteria.
Supported through Equivalent FacilitationList exactly what other methods exist in the product and describe how they are used to support the criteria.
Supported when combined with Compatible Assistive TechnologyUse this language when you determine the product fully meets the letter and intent of the criteria when used in combination with compatible assistive technology. E.g., many software programs can provide speech output when combined with a compatible screen reader.

Good remarks and explanations examples:

Level of Support & Supporting FeaturesRemarks and explanations
SupportedImages are accompanied by alternative text by default.
Supported[Product] is primarily text-based, and supports keyboard navigation.
Supported[Product] does not directly enable or disable any activated accessibility features.
SupportedAll multimedia content is provide by users.
Supported[Product] includes text to describe program elements represented by images, and Voice Over can dictate the function including question labels, answer checkboxes, buttons, alerts and modals.
SupportedWhen a [product maintainer] attaches an animation, there is an additional option to embed a non-animated presentation.
SupportedDocumentation can be made available in the format of the user’s choice upon request, at no additional charge.
SupportedSupport materials are available as videos and electronic written instructional guides. [Product] support information has been designed specifically for [product users] with accessible needs. Email, chat and phone support is also available. A support line is available by calling [phone number].
Not ApplicableThis criteria does not apply to [product] functionality.
Not Applicable[Product] has no timed applications or time-based response limits.
Not SupportedOn the [vendor product roadmap] to support auto-logout warning to reasonably increase the time-limit on a time-response.

Tips for Vendor Reporting

The vendor should have their technical staff assist in the testing and reporting on the VPAT. This allows the vendor’s technical staff to be aware of the compliance standards that need to be added to their product’s roadmap as a high priority.

After completing the Voluntary Product Accessibility Template, the vendor should make their VPAT available on their website and/or by request to reduce the time require for their customers to complete procurement processes. As each product undergoes versioning, the VPAT should be updated with any changes to accessibility compliance.

References

State Rules and Guidelines