Rendered product interfaces
Scan representative states and preserve incorporated WCAG references, browser evidence, and coverage.
Section 508 compliance testing API
Use the Section 508 API profile to assemble technical evidence for an exact ICT product configuration. The integration supports a procurement workbook and remediation process; it does not produce a completed ACR or decide federal acceptance, exceptions, or equivalent facilitation.
For vendors, federal delivery teams, and procurement reviewers evaluating supported ICT assets
API profile
us-section-508-ict@2026.2Illustrative request
202 AcceptedPOST /v1/scans
Idempotency-Key: platform-enterprise:7.4
{
"asset": {
"type": "upload",
"upload_id": "upl_product_admin_guide_v7"
},
"profiles": [
"us-section-508-ict@2026.2"
],
"metadata": {
"product_version": "platform-enterprise:7.4"
}
}queued
id: scn_01J…profile resolved- Inputs
- URL, HTML, PDF, or DOCX
- Mapping
- Revised Section 508 supported requirements
- Output
- Procurement evidence for a human-reviewed ACR
Organize evidence by product surface and evaluation method.
A single product may need several supported scans plus manual evaluation for functions the API cannot observe.
Guides, forms, and product collateral
Inspect PDF and DOCX sources with format-native locators and separate remediation ownership.
Software, hardware, support, and closed functions
Register as declared scope and assign qualified evaluation outside the scan API.
Pin the product configuration in the scan request.
Product metadata prevents technical evidence from drifting away from the exact version and asset the procurement response describes.
POST/v1/scansIllustrative- profile
- us-section-508-ict@2026.2
- product
- platform-enterprise:7.4
- workbook
- procurement-2026-federal
The completed scan becomes evidence for a requirement review. It does not generate an ACR statement.
Automate evidence collection, not the vendor claim.
The API improves repeatability for supported assets. Product representatives and reviewers remain accountable for the complete response.
Returned by the integration
- Pinned requirement mappings and rule lineage
- Source-locatable web and document findings
- Product and asset metadata with scan history
- Explicit unsupported and manual-review work
Approved through procurement review
- Complete ICT scope and evaluated configuration
- Functional performance, support, and documentation
- Exceptions, equivalent facilitation, and best-meets analysis
- Final ACR statements and federal acceptance decisions
Inspect the policy behind the API profile.
Before US Section 508 becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the US Section 508 API in the path you already own.
Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.