UK public-sector accessibility testing API
Integrate a current UK public-sector profile into publishing and supplier acceptance for assets declared to fall within England, Scotland, or Wales. The API gives each scan a technical lineage and sample identity; the organization still owns representative monitoring, mobile apps, feedback, and statement accuracy.
For UK public bodies, digital agencies, and suppliers maintaining accessible services
uk-psbar-current@2026.2202 AcceptedPOST /v1/scans
Idempotency-Key: housing-service:key-journey:application
{
"asset": {
"type": "url",
"url": "https://council.example/housing/apply"
},
"profiles": [
"uk-psbar-current@2026.2"
],
"metadata": {
"sample_id": "housing-service:key-journey:application"
}
}id: scn_01J…profile resolved- Technical target
- Current WCAG 2.2 AA operational profile
- Asset scope
- Website, HTML, PDF, or DOCX
- Boundary
- One asset is not representative monitoring
Keep the sample plan attached to every result.
An asset-level scan becomes more useful when the monitoring team can place it within a service, template, journey, supplier, and review period.
- Profile
- uk-psbar-current@2026.2
- Body
- Customer-declared public-sector organization
- Service
- Housing applications
- Sample
- Key journey · application start
- Supplier
- delivery-partner:release-31
- Review period
- 2026 Q3 monitoring cycle
Move from supplier preview to statement evidence.
Use stable identifiers so the same technical result can support delivery checks, remediation tracking, and periodic statement review.
- Accept
Check the supplier release candidate
Scan agreed page and document states before publication and return new blockers with evidence.
- Monitor
Repeat the selected technical sample
Keep profile and source changes visible across monitoring periods rather than comparing scores alone.
- Reconcile
Review statement and feedback records
Join scan history to manual tests, mobile coverage, known issues, requests, and remediation plans.
Show the monitoring team what changed in the selected sample.
A pinned comparison makes remediation progress inspectable without presenting one sampled asset as a representative audit.
- Baseline
- 2026 Q2 sample
- Current
- 2026 Q3 sample
Sample requires remediation and statement reconciliation
Inspect the policy behind the API profile.
Before UK public sector becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.
Put the UK public sector 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.
Automated preflight is not an accessibility certification or legal determination.