Federal Accessibility Authority
Accessibility at 508 Audit
We hold our own website to the standard we deliver for clients: WCAG 2.1 Level AA. We publish our own Accessibility Conformance Report in both human-readable and machine-readable (OpenACR) formats — dated and signed by our evaluator of record — and we do not publish one until it has been verified against the live production site.
Our ACR — current status
Current Accessibility Conformance Report undergoing final verification
Our evaluation is being re-verified against the frozen production build of this website before release. We will not publish a conformance claim that has not been confirmed against the live site — the same standard we apply to every client ACR we author. The verified report will be posted here in Word and OpenACR YAML formats once complete.
Evaluator of record: Nicole Clayter. To request the report status or a copy for procurement review, email contact@508audit.com.
Found a barrier?
Email contact@508audit.com and we'll respond within 2 business days.
See also our Accessibility Statement.
VPAT editions, standards, and our verification timeline
Plain-language answers to the questions procurement teams ask most about VPAT editions and about the status of our own conformance report.
What is a VPAT, and how is it different from an ACR?
A VPAT (Voluntary Product Accessibility Template) is the blank template. Once an evaluator fills it in with real findings for a specific product and version, the completed document is called an ACR (Accessibility Conformance Report). Buyers ask for a VPAT; what they should actually receive is a completed, dated, signed ACR.Which VPAT edition and standards apply to my agency?
The VPAT template comes in editions that map to different legal frameworks: the 508 edition covers the U.S. Revised Section 508 standards, the EU edition covers EN 301 549, the WCAG edition covers WCAG alone, and the INT (international) edition combines all three. Federal agencies and their contractors normally need the 508 edition, which reports against WCAG 2.x Level A and AA plus the additional Section 508 software, hardware, documentation, and support requirements.Why does the edition matter if everything is based on WCAG?
WCAG covers the web content criteria only. Section 508 adds requirements that WCAG never addresses — such as accessible documentation, accessible support services, and hardware and closed-functionality provisions. An ACR built on the WCAG-only edition can look complete while omitting the very criteria a federal contracting officer is required to evaluate.Why has 508 Audit not published its own ACR yet?
We do not publish a conformance claim until it has been re-tested against the frozen production build it describes. Our evaluation is in that final verification step now. Publishing an ACR that was written against a staging or pre-release build would be exactly the practice we advise buyers to reject.What is the verification timeline for your ACR?
Verification runs in four steps: freeze the production build, re-test every reported criterion against that build, have the evaluator of record review and sign the findings, then publish in both human-readable (Word) and machine-readable (OpenACR YAML) formats. We publish the signed report here as soon as that sequence is complete, and we will state the evaluation date and the build it applies to.Can I request the report before it is published?
Yes. Procurement teams that need the current status or an advance copy for market research can email contact@508audit.com and we will respond within 2 business days with the verification status and the expected publication date.