UK Equality Act accessibility API

Use the Equality Act digital-context profile to connect page and document findings to service-access work in England, Scotland, or Wales. The API identifies and tracks supported technical barriers; people determine disadvantage, reasonable adjustments, alternatives, and the legal outcome.

For UK service providers connecting accessibility engineering to service operations

API profileuk-equality-act-digital-context@2026.2

Check a website free Book a demo

Illustrative request202 Accepted

POST /v1/scans
Idempotency-Key: application:identity-check

{
  "asset": {
    "type": "url",
    "url": "https://service.example/apply/identity"
  },
  "profiles": [
    "uk-equality-act-digital-context@2026.2"
  ],
  "metadata": {
    "service_path": "application:identity-check"
  }
}

queuedid: scn_01J…profile resolved

Evidence: Supported WCAG 2.2 technical conditions
Context: Customer-declared digital service
Boundary: No automatic reasonable-adjustment decision

Turn a technical barrier into explicit next ownership.

The integration can route observable facts while keeping service impact and adjustment decisions outside the automated verdict.

Signal	Disposition	Owner
Deterministic failure	Block release and repair	Engineering
Complete-task impact	Assess disadvantage	Service owner
Proposed alternative	Validate effectiveness	Accessibility lead
Verified remediation	Retain evidence	Governance

Connect engineering evidence to an adjustment workflow.

The scan record should make the next responsible action obvious without allowing a code-level result to stand in for a service decision.

Engineering

Repair the observed condition

Use source evidence, requirement mapping, fingerprint, and baseline status to fix and verify the asset.

Service owner

Assess the affected path

Review task impact, existing alternatives, support routes, frequency, and urgency across the whole service.

Accessibility review

Validate the adjustment

Test the remediated path with relevant users and retain the human decision outside the machine verdict.

Let the API preserve facts without inventing the conclusion.

The technical and organizational records can share identifiers while remaining different kinds of evidence.

Machine-observable record

Asset, state, locator, and observed condition
WCAG mapping, profile, engine, and confidence
New, recurring, resolved, and suppressed status
Manual checks disclosed by the technical profile

Human-owned service record

Affected users and substantial disadvantage
Anticipatory and individual adjustment options
Alternative-channel effectiveness and operational impact
Approval, validation, and legal assessment

Inspect the policy behind the API profile.

Before UK Equality Act becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Read the UK Equality Act profile Equality Act 2010 Equality Act 2010, section 20 Equality Act 2010, section 29 W3C Recommendation: WCAG 2.2

Put the UK Equality Act 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 free Create an account

Automated preflight is not an accessibility certification or legal determination.