Section 508 ICT accessibility preflight

Inspect supported portions of an ICT offering against the Revised Section 508 profile and prepare source evidence for procurement review. Software, hardware, support, documentation, exceptions, and the accuracy of a final Accessibility Conformance Report remain human-owned.

Scanning profileus-section-508-ict
US Section 508Technical preflight
Input
Web page, HTML, PDF, or DOCX from an ICT offering
Mapping
Revised Section 508 Standards · supported ICT assets
Boundary
Procurement evidence, not an automated ACR or acceptance
Technical base36 CFR part 1194 · Appendices A and C
Web mappingWCAG 2.0 Level A and AA incorporated
DeliverableEvidence workbook for procurement review

Use US Section 508 through the API.

Send us-section-508-ict with the asset and keep this profile’s evidence boundary in the returned result.

Explore the US Section 508 API

Build evidence around the complete ICT offering.

The profile handles supported web and document assets. The procurement record must also describe the product version, environment, functions, support, and components outside those formats.

Section 508 procurement evidence set
Offering

Name the exact product and version

Keep platform, edition, configuration, dependencies, and evaluated environment with the evidence.

Assets

Inspect supported web and documents

Attach page, PDF, and DOCX findings to the relevant requirement and product function.

Beyond scan

Evaluate the rest of the ICT

Assign hardware, software, closed functionality, documentation, support, and functional performance review.

Give each conformance statement an evidence trail.

Procurement reviewers need the tested configuration, observed result, open work, and basis for every statement. A universal pass badge omits that evidence.

Requirementautomated

Pinned Section 508 reference

Retain the applicable technical reference and the profile version used for inspection.

Observationpartial

Source-locatable technical evidence

Record the asset, state, selector or document object, engine, and observed condition.

Dispositionmanual

Supported, partial, unsupported, or not applicable

Require a reviewer to make and justify product-level conformance statements.

Remediationmanual

Owner and planned correction

Keep open barriers connected to the product backlog and procurement response.

Build an ACR input from evidence layers that can be challenged.

Each layer narrows ambiguity while leaving the final product claim and procurement decision with accountable reviewers.

  1. Configuration

    Exact ICT offering

    Product, version, platform, options, and evaluated environment

  2. Technical proof

    Supported asset evidence

    Requirement, observation, locator, coverage, and scan lineage

  3. Review

    Product-level disposition

    Unsupported ICT, functional performance, exceptions, and approval

Read the source behind this profile.

The US Section 508 source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.

Run US Section 508 where content enters the workflow.

Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.

Check a website freeCreate an account

Automated preflight is not an accessibility certification or legal determination.