Skip to main content

Independent Accessibility Assurance

Accessibility at 508 Audit

We hold our own website to the standard we deliver for clients: WCAG 2.2 Level AA. We will not publish a conformance claim for this website that our own testing does not yet support, so this page describes what has been tested and what has not.

Our ACR — current status

No Accessibility Conformance Report is published for this website

Testing completed on this website to date is automated rule scanning, keyboard navigation, visible focus, contrast, heading and landmark structure, alternative text, and form label and error checks. Documented screen reader testing with NVDA, JAWS, VoiceOver, and TalkBack has not been completed. Because that evidence is not in place, we do not publish a conformance report or name an evaluator of record for this site, and we do not promise a publication date.

Procurement teams needing current accessibility information for this website can email contact@508audit.com. Full testing details are in our accessibility statement.

Found a barrier?

Email contact@508audit.com with the information needed and any relevant deadline.

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 template published by ITI. A completed VPAT for a specific product version is commonly called an ACR (Accessibility Conformance Report). The required edition, evidence, review, and sign-off depend on the procurement.
  • 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 currently provide a public ACR download for this website. Procurement teams can request current accessibility information through the contact page.
  • What is the verification timeline for your ACR?
    Any future ACR would identify the evaluated build, scope, methods, applicable standards, evaluation date, and documented limitations. Publication timing is not promised until that work is completed and approved.
  • Can I request the report before it is published?
    Yes. Procurement teams can email contact@508audit.com for current accessibility and procurement information. Response timing depends on the request and current availability.