How to interpret VPATs

One way software tools convey their accessibility is through the Voluntary Product Accessibility Template (VPAT). A VPAT will describe accessibility standards that a software tool meets systematically. VPAT documents are helpful in determining whether a tool is accessible, but there are some issues in relying solely on a VPAT for establishing accessibility.

• Software developers often complete VPATs internally. The company may or may not have expertise in properly evaluating accessibility standards.
• VPATs have no required cycle. With most software developers utilizing continuous development (AGILE), new features and interfaces are added all the time. A VPAT may be out-of-date a week after the company publishes it.
• VPAT describes technical accessibility. Companies can (and have) created products that recognize the technical requirement without meeting the spirit of accessibility. This is done both intentionally and unintentionally and often depends on whether the company has accessibility expertise on their technical staff.

A VPAT is a good start to knowing how seriously a software company takes accessibility, but it is not a final determinant of accessibility for a product.