Birmingham digital accessibility bylaw and WCAG guide
Birmingham, England public bodies must follow accessibility requirements that implement WCAG standards for websites and apps; this guide explains the local obligations, enforcement pathways and practical steps for council services and contractors.
Standards & Legal Basis
Public sector accessibility in England is governed by the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, which require conformity with WCAG 2.1 AA for most content and set rules for accessibility statements and remediation plans[1]. Central government guidance on making public sector websites and apps accessible provides practical compliance steps and timelines for legacy content[2].
Local Responsibilities
Birmingham City Council is the local public body responsible for its own digital services and for contractors working on behalf of the council; the council publishes an accessibility statement describing its current compliance position and contact routes for issues reported by users[3].
Penalties & Enforcement
Legal and enforcement responsibilities are split between national enforcement bodies and local duty-bearers: the primary legal instrument is the 2018 Accessibility Regulations, and enforcement actions for failure to comply are managed under the Equality Act 2010 framework and by the Equality and Human Rights Commission (EHRC) rather than a named local fine schedule.
- Fines or monetary penalties: not specified on the cited page; enforcement is typically through compliance measures and legal action rather than a published fixed fine on the regulation page[1].
- Escalation: first action commonly includes written notice and requirement to publish an accessibility statement and remediation plan; specific escalation amounts or tiered fines are not specified on the cited regulation page[1].
- Non-monetary sanctions: compliance notices, court proceedings, orders to make content accessible and judicial remedies under the Equality Act are available to enforcing authorities (details as per national guidance)[2].
- Enforcer and complaints: individuals may complain to Birmingham City Council via the contact details in the council accessibility statement; the EHRC can investigate and take legal action for systemic breaches[3].
- Appeal and review: routes are via judicial review or responding to statutory compliance notices; time limits for legal challenges depend on the notice or court timetable and are not specified on the cited regulation page[1].
- Defences and discretion: reasonable adjustments, published exemptions for content unverifiable or disproportionate to fix, and recorded remediation plans are permitted where justified; the specific tests for ‘disproportionate burden’ are set out in national guidance[2].
Common violations
- Missing alt text for images — often remedied through content updates.
- PDFs and documents not tagged or without accessible structure — common legacy issue.
- Inaccessible forms or controls that prevent keyboard navigation.
- Absence of an up-to-date accessibility statement and remediation plan.
Applications & Forms
There is no dedicated national licence or permit form to certify compliance; organisations usually publish an accessibility statement and remediation plan. For Birmingham City Council digital services, the council’s website provides contact details to report issues but does not publish a separate formal “accessibility permit” form on the cited page[3].
How to comply in practice
Local steps for Birmingham public bodies and suppliers include auditing content against WCAG 2.1 AA, prioritising fixes for high-impact pages, updating procurement clauses to require accessibility, and publishing an accessibility statement with a remediation plan and contact point.
- Audit schedule: perform regular automated and manual accessibility testing and document results.
- Remediation: prioritise core transactional pages and documents for repair.
- Procurement: include accessibility requirements in contracts and acceptance testing.
- Reporting: publish a clear contact route for users to report barriers.
FAQ
- How do I report an inaccessible page on a Birmingham council website?
- You can report issues using the contact details in Birmingham City Council’s accessibility statement; include the page URL, browser and assistive technology used and screenshots where possible.
- Does the council have to meet WCAG 2.1 AA?
- Yes, public sector bodies are required by the 2018 Accessibility Regulations to meet WCAG 2.1 AA where applicable, subject to permitted exceptions and remediation timelines.
- Can I take legal action if the council does not fix accessibility faults?
- Individuals may complain to Birmingham City Council and to the Equality and Human Rights Commission or seek judicial remedies; enforcement options include compliance notices and court action.
How-To
- Run an automated site scan and identify key failing pages and documents, then prioritise by traffic and service impact.
- Carry out manual testing with keyboard-only navigation and at least one screen reader to confirm user impact.
- Create and publish an accessibility statement listing issues and a remediation timetable, and provide a clear contact for reports.
- Update procurement and supplier contracts to require WCAG compliance and acceptance testing before go-live.
- Respond to reported issues promptly, record actions, and notify the reporter when fixes are implemented.
Key Takeaways
- Public bodies must follow the 2018 Accessibility Regulations and aim for WCAG 2.1 AA.
- Publish an accessibility statement, remediation plan and a clear contact route.
- Enforcement focuses on compliance and remedies; monetary fines are not detailed on the regulation page.
Help and Support / Resources
- Birmingham City Council accessibility statement and contact
- GOV.UK guidance: make your public sector website or app accessible
- The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
- Equality and Human Rights Commission - advice and complaints