Guides
VPATs, explained for the people who have to write them.
Short, practical guides for product, engineering and sales teams who just got asked for an Accessibility Conformance Report.
5 min readSalesforce AppExchange ACRWhat Salesforce asks AppExchange app makers for the Accessible Solutions tag, what an accessibility report (VPAT / ACR) is, and how to make one for $49.6 min readAtlassian AEC VPAT (rule 4.1)What Atlassian’s AEC rule 4.1 asks for, the exact VPAT title format the scanner matches (VPAT - App Name (app.key)), where to publish it, and how to make one.6 min readWhat is a VPAT?A plain-English explanation of the VPAT, the Accessibility Conformance Report it produces, which edition buyers expect, and what it does and doesn’t prove.6 min readResponding to a VPAT requestA practical five-day plan for software teams who just received a VPAT or ACR request in a deal: who to ask, what to check, and what to send.8 min readHow to fill out a VPATSection-by-section instructions for completing the VPAT WCAG edition: product details, evaluation methods, conformance levels, and remarks buyers trust.7 min readChoosing conformance levelsWhat each VPAT conformance level means, how to choose between them, and example remarks for Supports, Partially Supports, Does Not Support, and Not Applicable.5 min readWCAG 2.2 vs. 2.1The six new Level A and AA success criteria in WCAG 2.2, the one that was removed, and how to decide which version your VPAT should report against.12 min readWCAG 2.2 AA checklistEvery WCAG 2.2 Level A and AA success criterion as a plain-language question your team can answer, grouped by principle. Free and printable.