During these difficult and uncertain times it is our top priority is to protect and care for all residents, visitors and employees in our borough. After careful consideration, we have decided to cancel all workshops and events which are running alongside the Knife Angel here in Telford. Thank you for your understanding.
This accessibility statement applies to www.telfordknifeangel.com, which is managed by Telford & Wrekin Council on behalf of Telford Knife Angel.
We want as many people as possible to be able to use this website. For example, that means you should be able to:
We also use the 'browsealoud' assistive technology app to help users navigate our site and we use plain English as much as we can to make the content easier to understand.
Parts of this website are not fully accessible. For example:
If you would like to comment on the accessibility of this website, or request any of the information in a different format, such as accessible PDF, large print, easy read, audio recording or braille, please contact us using our website feedback form.
We aim to get back to you within 14 days.
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, contact the Web Services team using our website feedback form.
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, contact the Equality Advisory and Support Service (EASS)
We provide a text relay service for people with hearing impairent or speech impediment. The number is 18001 (01952) 380000. Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Telford & Wrekin Council 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 Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed on this page.
The content listed below is non-accessible for the following reasons.
Some images don’t have a text alternative (alt text), so the information in them isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (Non-text Content). We plan to resolve this issue by September 2021. When we publish new content we’ll make sure our use of images meets accessibility standards.
Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This doesn't meet WCAG success criterion 1.4.5 (Images of Text). We plan to resolve this issue by September 2021. When we publish new content we’ll make sure our use of images meets accessibility standards.
On some pages the same link text is used for different link destinations. This doesn’t meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan to resolve this issue by September 2021. When we publish new pages we’ll make sure link text meets accessibility standards.
On some pages the purpose of each link can't be determined from the link text alone. This doesn't meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan to resolve this issue by September 2021. When we publish new pages we’ll make sure link text meets accessibility standards.
On some pages tables do not have a description set using the caption element. This doesn't meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan to resolve this issue by September 2021. When we publish new tables we’ll make sure they meet accessibility standards.
PDFs and other documents
Some of our PDFs and other documents are not formatted so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (Name, role value). Any new documents we publish should meet accessibility standards where they are required for essential services or users who are likely to have disabilities or impairments. Essential documents will be reviewed and made accessible by September 2021.
On some pages there isn't sufficient contrast between the colour of the text and the background, making it hard to read the information. This doesn’t meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). We plan to resolve this issue by September 2021.
On some pages the language has not been set in a way that can be understood by a screen reader. This doesn’t meet WCAG 2.1 success criterion 3.1.1 (Language of Page). We plan to resolve this issue by September 2021.
On some pages the tabbing order is not logical when navigating using a keyboard. This doesn’t meet WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to resolve this issue by September 2021.
On some pages HTML is used to format content rather than CSS. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Information and Relationships. We plan to resolve this issue by September 2021.
On some pages headings don't cascade inside the features on the page. This fails WCAG 2.1 success criterion 2.4.10 (Section Headings). We plan to resolve this issue by September 2021.
PDFs and other documents
Some of our PDFs and Word documents are essential to providing services e.g. PDFs that give users complex information in a clear format, using illustrations etc, or forms that were published as Word documents. By September 2021, we plan to either fix these or replace them with accessible HTML pages.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example annual reports or documents used as an archive reference for work conducted in that year. Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams, because live video is exempt from meeting the accessibility regulations. All of our pre-recorded and edited film clips will feature subtitles/captions or a transcript. By September 2021 we plan to ensure all our pre-recorded videos meet the required standard.
Embedded clips from YouTube
When embedding Youtube content, it automatically generates non-compliant HTML5 code. We’re currently monitoring this to see if it has a negative effect on the overall user experience. At the time of publication that is not the case, but linked film clips will not function without the non-compliant code.
Embedded images from Flickr
We have a selection of photo albums on the site, some of which are only hosted on the photo-sharing website, flickr.com. The code used to embed an image or album can create non-compliant elements.
Maps and mapping services are exempt as long as essential information is provided in accessible digital manner for maps intended for navigational use. By September 2021 all maps will be presented alongside text equivalent information, where appropiate, for example, address/location details.
We aim to meet the needs of all visitors to our site, but we don’t yet have a way of presenting geographical information (maps and site plans etc.) in a fully achievable and accessible format. Currently all accessible map solutions would be impossible to implement for all residents due to both resource and installation issues. As new technologies emerge we will revaluate this topic.
We plan to identify and fix issues according to the timescales shown for each area above.
This statement was prepared on 22 September 2020. It was last reviewed on 22 September 2020. This website was last tested on August 2020. The test was carried out by Telford & Wrekin Council. We tested a large sample size of page types and varieties from our site, with the aim to make sure all types of user journey and the most popular tasks were represented, e.g. the main homepage and also the content listed under service landing pages.
We complete our accessibility audits by testing how the site performs when accessed using accessibility tools such as Siteimprove (to test coding elements) and WebAIM Contrast Checker (to test the contrast levels between colours with hexadecimal accuracy).