Section 508 accessibility testing for federal procurement.

Depending on the product, it can include software, hardware, electronic documents, support information, and other applicable ICT provisions. The Revised 508 Standards incorporate WCAG 2.0 Level A and AA requirements, but WCAG coverage alone does not settle every requirement. We review the product and solicitation to identify the relevant provisions before defining the evaluation.

Receiving federal money alone does not describe the scope of Section 508. The law addresses ICT that federal agencies develop, procure, maintain, or use. Vendors encounter its requirements through federal acquisitions and contract terms. Other accessibility obligations can arise under different laws or policies. Send the specific requirement so we can identify the technical evaluation needed instead of applying a blanket rule.

It may supply relevant evidence, but the scope still needs to address the Revised 508 Standards and any additional requirements in the request. A newer WCAG version does not automatically replace the standard incorporated into Section 508. Hardware, non-web software, documentation, and support can require additional consideration. We map the requested coverage before deciding whether existing test results are sufficient.

Provide the solicitation or questionnaire, product description, user roles, supported configurations, and deadline. Include existing ACRs, test reports, and instructions for accessing the product. Identify related documents, devices, and support materials. These inputs allow us to scope the actual procurement requirement. Our Section 508 procurement guide explains how to prepare the evidence for review.

Yes, we can scope an ACR and supporting technical findings for the evaluated product. The requested format, VPAT edition, standards, and evidence need to be confirmed first. Some buyers also request demonstrations, issue details, or answers to follow-up questions. VPAT and ACR support can be included with testing so the deliverables match the request.

No. An ACR is evidence for the buyer's evaluation, not an approval from the government. The agency considers the report alongside its requirements and other procurement information. Clear limitations, current test results, and specific explanations help the reviewer understand the product. Promised future fixes should be distinguished from functionality that has already been evaluated.

Not automatically. Section 508 is a federal ICT requirement, while state and local entities have their own applicable obligations, including the ADA, and may specify additional procurement standards. A public-sector buyer may expressly require Section 508 or a particular WCAG version. Use the actual solicitation and organizational requirements to determine coverage rather than assuming every government project has the same scope.

The scope depends on the ICT being evaluated, applicable provisions, available access, and the documentation required. A software-only assessment differs from one involving physical devices and extensive manuals. We identify any device logistics, document work, reporting, and retesting before confirming a quote and schedule. Share the submission deadline early so the plan allows time for technical questions and review.