Liverpool Website Accessibility - WCAG & Public Rules

Technology and Data England 3 Minutes Read · published February 12, 2026 Flag of England

Liverpool, England public-sector websites must follow UK accessibility rules and WCAG standards to ensure services are usable for everyone. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 set the legal baseline and require publications of accessibility statements and remediation plans; see the Regulations for obligations and legal text legislation.gov.uk[1].

Publish an accessibility statement on every public-sector site and update it after major changes.

Penalties & Enforcement

The Regulations specify duties rather than fixed fines; specific monetary penalties are not detailed on the cited regulation page. For enforcement pathways, guidance from the UK government explains compliance expectations and potential legal remedies for failures to comply gov.uk guidance[2].

  • Fines and monetary penalties: not specified on the cited page.
  • Escalation: the Regulations set remedial duties; escalation to court or judicial review is possible but specific ranges are not specified on the cited pages.
  • Non-monetary sanctions: orders to publish or amend accessibility statements, required remediation plans, and court enforcement actions are possible under civil law.
  • Enforcer and complaints: there is no single municipal fine officer named in the Regulations; complaints and enforcement can involve civil proceedings and public bodies should follow gov.uk guidance on compliance and complaints.
If a regulation does not list a fine, consider legal advice early to manage risks.

Appeals, Reviews and Time Limits

The cited Regulations and guidance do not set specific administrative appeal time limits on fines because fixed administrative fines are not specified; instead, remedies follow civil enforcement routes and judicial processes, so statutory limitation periods for civil claims may apply and are not specified on the cited pages.

Common Violations

  • Missing accessibility statement or outdated statement.
  • Failure to meet WCAG 2.1 AA success criteria for key user journeys.
  • Failure to publish a remediation plan for non-compliant content.

Applications & Forms

There is normally no separate application or permit to comply with the Accessibility Regulations; public bodies must self-assess, publish a statement and fix issues. If a local authority publishes a reporting form for accessibility faults, use that official channel; otherwise no central application form is required, as not specified on the cited regulation page.

Start with an accessibility audit and a public remediation plan.

Action Steps to Comply

  • Audit your site and apps against WCAG 2.1 AA success criteria and record findings.
  • Publish or update an accessibility statement describing compliance, known issues and a remediation timeline.
  • Prioritise fixes for key public services and document testing methods and results.
  • Provide an accessible complaints route and respond within reasonable timescales.

FAQ

Do public-sector websites in Liverpool need to meet WCAG?
Yes. UK Public Sector Accessibility Regulations require public bodies to meet WCAG standards and publish accessibility statements; see the Regulations and official guidance.[1][2]
How do I report an accessibility problem with a Liverpool City Council site?
Use Liverpool City Council’s reported contact or accessibility reporting channel listed in their website support pages; if unavailable, use the council main contact page.
Is there a standard form to apply for an exemption?
The Regulations do not provide a central exemption application form; exemptions and exceptions are described in the Regulations or guidance, and no specific municipal form is specified on the cited pages.

How-To

  1. Commission or run an automated and manual accessibility audit covering WCAG 2.1 AA.
  2. Publish an accessibility statement that lists compliance status, known issues and a remediation timetable.
  3. Prioritise fixes for critical user journeys and redeploy updates with accessibility testing.
  4. Provide a clear contact for accessibility feedback and record responses and completion dates.

Key Takeaways

  • Public bodies must publish accessibility statements and remediate non-compliant content.
  • WCAG 2.1 AA is the practical benchmark for compliance.

Help and Support / Resources

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data