Accessibility

This accessibility statement applies to www.sustrans.org.uk

This website is run by Sustrans. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
  • We’ve also made the website text as simple as possible to understand.

AbilityNet 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:

  • Some parts of our website are difficult to read when a user adjusts the text to 200% its current text size.
  • Some of our online forms are difficult to navigate using just a keyboard. This includes our member of the public referral form. If you need help filling in this form please contact us on the details below.
  • Not all page functionality is available using the keyboard
  • Our PDF documents are not fully accessible to screen reader software.

 

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email us at web@sustrans.org.uk

We’ll consider your request and get back to you in three 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, contact:

web@sustrans.org.uk

 

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, please contact the Equality Advisory and Support Service (EASS).

 

Technical information about this website’s accessibility

Sustrans is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

Non-compliance with the accessibility regulations

The content listed below is non-accessible for the following reasons.

  1. Some images do not have a text alternative, so people using a screen reader cannot access the information. This does not meet WCAG 2.0 success criterion 1.1.1 Non-text Content.

    We plan to add text alternatives for all images by mid 2021 When we publish new content we’ll make sure our use of images meets accessibility standards.


  2. Our video “Our story: from 1977 to present day” is missing accessible text. This can make it difficult for people using assistive technology to identify this as a video. This fails WCAG 2.0 success criterion 1.1.1 Non-text content.

    We plan to add accessible text to this video by (add date here). In future, when we publish new videos we will make sure they are easily identified by accessible text.

  3. Some pages have skipped heading levels and are missing a heading level 1. This can make it difficult for people using a screen reader to navigate around a page. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships and 2.4.1 Bypass Blocks.We plan to fix this issue by (add date here). When we publish new content we’ll make sure to structure our web pages so they meet accessibility standards.

  4. There are tables presented on our website that are for presentation purposes and don’t hold tabular data but are not marked-up appropriately for accessibility. When tables haven’t been marked up correctly for accessibility it can make it difficult for a person who uses a screen reader to understand what is being presented. This fails WCAG 2.0 success criterion 1.3.1 Info and Relationships.
    We plan to fix this issue by (add date here). When we publish new content we’ll make sure our tables are designed and coded so they meet accessibility standards.
  5. Some input fields in our online forms do not have labels programmatically associated to them. This can make it difficult for a person who uses a screen reader to understand what they should input into a field. This does not meet WCAG 2.0 success criterion 1.1.1 Non-text content, 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.

    We plan to fix these issues by (add date here). When we publish new content we’ll make sure our forms are designed and coded so they meet accessibility standards.

  6. Some text on our website does not have sufficient contrast against the background. This can make it difficult to read for people with low vision or visual impairments. This does not meet WCAG 2.0 success criterion 1.4.3 Contrast (Minimum).We plan to adjust the colour of our text or backgrounds by (add date here) to ensure there is a sufficient contrast ratio between the two.

  7. Some parts of our website are difficult to read when a user adjusts the text to 200% of its current text size. Some text overlays other text and some becomes cut off. This can make it difficult for users with low vision or visual impairments who need to scale content in order to read it. This does not meet WCAG 2.0 success criterion 1.4.4 Resize Text.

    We plan to fix this by (add date here) to ensure users can read and access all content with text adjusted to 200%.

  8. The dropdown navigation cannot be dismissed by keyboard alone. This can be difficult for keyboard only users as some of the dropdown elements obscure other content on the page. This does not meet WCAG 2.1 success criterion 1.4.13 Content on Hover or Focus

    We plan to fix this issue by (add date here) to ensure keyboard users are able to dismiss the dropdown navigation.WCAG 2.0 success criterion 2.4.7.

    We plan to fix this issue by (add date here) to ensure the focus indicator is visible for all interactive elements on our website.

  9. The accessible name for the “Continue” button on our monthly donation set-up page does not include the label of the button. This could create confusion for users of speech recognition software. This does not meet WCAG 2.1 success criterion 2.5.3 Label in Name. We plan to fix this issue by (add date here). When we publish new content we’ll make sure accessible names include the label visually presented.

  10. On our website we have some content published in the Welsh language but no language attributes have been defined for the content. This can make understanding the content for screen reader users difficult as without the language defined the screen reader may not pronunciate the content correctly. This does not meet WCAG 2.0 success criterion 3.1.2 Language of Parts. We plan to fix this issue by (add date here). When we publish new content we’ll make sure any language variations presented have the correct language attribute.


  11. There are fieldsets missing within our online forms, these help to group form inputs where there are multiple options such as radio buttons present. Without these, it can be difficult for a person who uses a screen reader to understand what is required of them (what input is needed in a form field). This does not meet WCAG 2.0 success criterion 1.3.1 Info and Relationships and 3.3.2 Labels or Instructions.

    We plan to fix these issues by (add date here) When we publish new forms we’ll make sure they have the required accessibility markup to meet accessibility standards.

Content that’s not within the scope of the accessibility regulations.

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents.

By (add date here), 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.

Any new PDFs or Word documents we publish will meet accessibility standards.

 

Preparation of this accessibility statement

This statement was prepared on the 27th of October 2020. It was last reviewed on 27th of October 2020.

This website was last tested in October 2020. The test was carried out by The Method Consulting Group Limited.

We selected a sample of webpages to test across the main page templates we use for the website, we ensured to include pages with the most traffic and any critical paths on the website. These pages and components selected are representative of the product as a whole.