Accessibility
Accessibility statement for edinburgh.gov.uk/tramstonewhaven
This website is run by the City of Edinburgh Council. We want as many people as possible to be able to use this website.
has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible:
- most older PDF documents are not accessible to screen reader software
- some videos do not have captions and rely on auto-captions, which are not accurate
- the chat cannot be used without a mouse or with assistive technology.
What to do if you cannot access parts of this website
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille
We’ll consider your request and get back to you in 10 working days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, .
Technical information about this website’s accessibility
Сòòò½APP is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the .
Non accessible content
The content listed below is non-accessible for the following reasons.
Non-accessible content
Many of our PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.
By January 2021, we plan to either fix these or replace them with accessible HTML pages.
The chat cannot be accessed without a mouse as it does not receive focus. This fails success criterion 2.1.1 keyboard.
The chat does not announce its responses properly, so cannot be used with a screen reader. This fails success criterion 4.1.3 status messages.
Content that’s not within the scope of the accessibility regulations
Our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.
The accessibility regulations if they’re not essential to providing our services.
How we tested this website
This website was last tested on 9 November 2020. We tested the website manually to ensure compliance with each criteria of the WCAG 2.1.
We tested all HTML web pages on the site at this date and a random selection of 10 documents.
Statement details
This statement was prepared on 20 November 2019. It was last updated on 18 November 2020.
Preparation of this accessibility statement
This statement was prepared on 20 November 2019. It was last updated on 18 September 2020.
This website was last tested on 9 November 2020. Сòòò½APP's web team tested the website.
Our web team are experienced in
- web technologies
- validation tools for web technologies
- WCAG 2.1 and techniques
- web accessibility
- assistive technologies.
We conducted manual testing, aided by automated tools (WAVE Evaluation Tool) and a screen reader (NVDA).
We tested all HTML web pages on the site on 9 November and a random selection of 10 documents. We tested the chat functionality on 9 November 2020.