Edinburgh Council Accessibility Self-Assessment

This guide explains how Edinburgh, Scotland public bodies should approach a self-assessment under the Public Sector Accessibility Regulations and related duties. It summarises the legal requirements for council websites and mobile apps, the practical steps for a site-level audit, where to publish an accessibility statement, and how to report or appeal. Use the official City of Edinburgh Council accessibility statement and the UK regulations to confirm obligations and contact routes for complaints.^[1]

Scope & Legal Basis

Council websites and mobile applications operated by City of Edinburgh Council are in scope of the Public Sector Bodies - Websites and Mobile Applications (No. 2) Accessibility Regulations 2018 and related public-sector equality duties; the regulations require an accessibility statement and remediation of non-compliant content where reasonable. For statutory text and obligations, consult the original regulations and supporting guidance.^[2]

How to run a self-assessment

1. Inventory: list domains, subdomains, apps and third-party platforms supporting council services.
2. Automated audit: run WCAG 2.1 AA checks with an automated scanner and save reports.
3. Manual testing: keyboard-only, screen reader, and low-vision checks on priority user journeys.
4. Prioritise fixes: classify issues as critical, major, minor and estimate timelines to remediate.
5. Record costs and resources needed for remediation and maintenance.
6. Publish or update the accessibility statement with known issues, timelines, and contact details.

Penalties & Enforcement

The Accessibility Regulations set duties but do not set specific pecuniary fines on the face of the statutory instrument; monetary penalties are not specified on the cited page and enforcement depends on complaint routes and civil remedies. For enforcement options and practical complaint routes see the statutory guidance and equality regulator guidance below.^{[2] [3]}

• Escalation: the regulations do not specify a graduated fine schedule; enforcement is normally by complaint, regulatory engagement or court action (not specified on the cited page).
• Non-monetary sanctions: remedies commonly include compliance notices, court orders and declarations; the specific powers and procedures are set out in enforcement guidance (see regulator links).
• Enforcer: City of Edinburgh Council is responsible for its own websites; oversight and wider enforcement remedies may involve the Equality and Human Rights Commission for discrimination matters.^[3]
• Inspection & complaints: users may complain to the council web team, and unresolved matters can be taken to the equality regulator or civil court (time limits for civil claims are not specified on the cited regulator pages).

Applications & Forms

No national licence or permit is required to run a self-assessment; councils must publish an accessibility statement and provide contact details for reporting barriers. City of Edinburgh Council publishes its accessibility statement and contact route for web accessibility issues on its website.^[1]

Common violations and typical outcomes

• Missing alt text on images — often requires code changes and re-deployment.
• Poor keyboard focus order — remediation may include HTML updates and ARIA fixes.
• Unlabelled form fields — usually fixed by adding labels and aria-describedby where needed.
• Failure to publish an accessibility statement — requires immediate publication with a remediation timeline.

Action steps

• Run an automated scan and manual checks within 30 days.
• Publish or update your accessibility statement with a clear remediation plan.
• Provide a contact route for reporting accessibility barriers and respond within a stated time.
• If a complaint cannot be resolved, inform the complainant of independent regulator routes.

FAQ

Do council websites in Edinburgh have to comply with accessibility regulations?

Yes. Public sector websites and mobile apps are within scope of the Public Sector Accessibility Regulations and must publish an accessibility statement and take reasonable steps to meet WCAG 2.1 AA standards where applicable.

What if an accessibility issue cannot be fixed immediately?

Councils should record the issue in the accessibility statement, give a clear timeline for fixes, and provide reasonable alternatives or direct assistance while remediation is underway.

Who enforces accessibility for public sector websites?

Enforcement can involve the Equality and Human Rights Commission for discrimination issues and civil remedies; local disputes often begin with the council web team or the council complaints process.

How-To

1. Map all public web properties and owner contacts.
2. Run automated WCAG 2.1 AA scans and archive the reports.
3. Perform manual checks for keyboard and screen-reader access on priority pages.
4. Create a remediation plan with owners, costs and deadlines.
5. Publish or update the accessibility statement with known issues and contact information.
6. Set a review cadence (quarterly recommended) and log improvements.

Key Takeaways

• Publish a clear accessibility statement and remediation timeline.
• Combine automated and manual testing for reliable coverage.

Help and Support / Resources

• City of Edinburgh Council accessibility statement and contact
• City of Edinburgh Council contact and complaints
• Scottish Government guidance on accessible communication
• Equality Advisory and Support Service (EASS) for Scotland

1. [1] City of Edinburgh Council accessibility statement and contact
2. [2] Public Sector Bodies - Websites and Mobile Applications (No. 2) Accessibility Regulations 2018
3. [3] Equality and Human Rights Commission guidance for public sector bodies