Recently a client asked for a quote on a VPAT (ACR) for his web app, but he was concerned that he wouldn’t have an opportunity to fix accessibility issues before we issued his ACR; he thought we would just audit his web app and then immediately issue the ACR.
And, by the way, the terms VPAT and ACR are used interchangeably in the marketplace. A VPAT is simply the standard template we use and once we fill in and complete the VPAT, then the resulting document is an ACR or Accessibility Conformance Report.
We let the client know that, absolutely, he would have as much time as he needed to remediate issues before we issue the ACR.
Not only that, we even provide technical support hours to help with remediation and validate the fixes pre-ACR issuance. We assured the client the audit and VPAT process is completely straightforward and there are no surprised.
Here’s how our VPAT services typically flow:
- Client request for a VPAT
- Details are agreed to
- Audit begins
- Audit is delivered
- Client begins remediation
- We answer questions
- We validate fixes
- Once client is satisfied, we issue ACR
We basically pause the VPAT service so that the client has a chance to fix the issues. We still validate all issues to make sure the fixes are actually made correctly, but there’s no reason you can’t fix the issues before we start filling in the VPAT.
Now clients do sometimes just request us to directly go from audit to filling in the VPAT and issues an ACR, with no remediation in between. This is often because either 1) they’re comfortable with the state of accessibility and/or 2) they just need to provide an ACR to their purchaser (often by a certain deadline).
But this is always the client’s choice.
Our primary concern is ensuring that the final ACR is comprehensive, detailed, and accurate; it needs to mirror the state of accessibility of the product or service identified in the ACR.
If you’d like help with VPAT services, we’d love to help. Just send us a message and we’ll be right back with you.
