Does the evidence represent the service estate?
Include templates, key journeys, documents, authenticated areas, mobile apps, and content owned by suppliers.
UK public-sector website accessibility checks
Inspect an asset declared to belong to a public-sector body in England, Scotland, or Wales. The result can strengthen a monitoring sample and remediation workflow, but it is not an official GDS audit, a representative site assessment, or a complete accessibility statement.
Scanning profile
uk-psbar-currentUK public sectorTechnical preflight
- Input
- Public-sector URL, HTML, PDF, or DOCX
- Mapping
- UK 2018 accessibility regulations · current technical target
- Boundary
- Single-asset preflight inside a wider monitoring program
Declared scopeEngland, Scotland, or Wales public body
Technical targetCurrent GOV.UK guidance · WCAG 2.2 AA
Program workSampling, statement, feedback, and mobile review
Use UK public sector through the API.
Send uk-psbar-current with the asset and keep this profile’s evidence boundary in the returned result.
Put technical preflight on the same calendar as statement review.
Repeatable checkpoints keep delivery evidence current while preserving the broader sampling and governance work a single scan cannot complete.
- Supplier preview
Stop new deterministic failures
Scan representative candidate states before acceptance.
- Publication
Archive the released evidence
Retain source, mapping, findings, and review ownership.
- Monitoring cycle
Repeat the selected sample
Compare like-for-like assets with pinned profiles.
- Statement review
Reconcile the complete record
Combine technical, manual, mobile, feedback, and remediation evidence.
Ask what the accessibility statement must be able to support.
A statement cannot be generated reliably from one scan. Use the result to find evidence gaps before the organization reviews and publishes its statement.
Are known barriers described accurately?
Reconcile technical findings, manual testing, disproportionate-burden assessments, and planned fixes.
Can people request information and report problems?
Test that the published contact route works and that ownership and response processes exist behind it.
Make accessibility evidence part of the publishing cycle.
A current profile is most useful when it is repeated at predictable checkpoints and paired with scheduled human review.
- Before release
Preflight templates and priority pages
Block new deterministic failures and retain review tasks for the release owner.
- After change
Rescan affected services and documents
Compare against pinned evidence rather than relying on a new aggregate score.
- At review
Reconcile the statement and feedback record
Combine technical history with manual, user, mobile, and organizational evidence.
Read the source behind this profile.
The UK public sector 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 UK public sector 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.