---
# System prepended metadata

title: Accessibility statement for pct.bike

---

# Accessibility statement for pct.bike
<!--
Example statement: 
https://www.gov.uk/government/publications/sample-accessibility-statement/sample-accessibility-statement-for-a-fictional-public-sector-website

Accessibility statement for [website name]


[Note: start with a brief explanation of which websites or mobile apps the statement covers.

You can have a single accessibility statement that covers multiple domains, or a separate statement for each domain or subdomain. As long as the user can access relevant accessibility information easily from any page on your website.]


-->

This statement covers the website hosted at www.pct.bike.

This website is run by [the Universities of Cambridge, Leeds and Westminster](https://www.pct.bike/tabs/about.html).
See https://www.pct.bike/tabs/about.html for details.

The web tool was developed in close collaboration with the DfT, to support delivery of the Cycling and Walking Infrastructure Strategy (CWIS): https://www.gov.uk/government/publications/cycling-and-walking-investment-strategy


We held multiple stakeholder workshops which led to improvements in the user interface.
The tool is map based because it displays geographical information and therefore relies on a map.

The main target audience is professional transport planners working for local authorities, so a level of technical knowledge is assumed when using the tool - we assume users have a PC, for example, although the tool can also work on tablets to some extent.

Users can zoom-in to 300% on the main landing page and on the 'regions' pages such as https://www.pct.bike/m/?r=west-yorkshire . 
At this high zoom level, the drop-down levels spill off the screen on some screens.

We use the Leaflet.js library which allows panning and zooming using standard keystrokes such as Ctl+`+` for zooming in.
However, there are known issues around around keyboard navigation and interaction with of popups in Leaflet maps that would require upstream development work on a [third party library](https://github.com/Leaflet/Leaflet/issues/3210#issuecomment-96056122).
The text of the landing page is available as HTML.
There are text summaries for the regions.
None of the site has been tested with a screen reader.

We’ve also made the website text as simple as possible to understand with use of headings.


## How accessible this website is


We know some parts of this website are not fully accessible:

- The regions content cannot be accessed without use of a mouse.
- The manuals are provided as PDF documents. In future work provision of the manuals in HTML could improve accessibility.
- There is no site map.
- The video on the landing page lacks captions, many images lack alt tags.
- It is not immediately clear how to get to regional results or regional summaries which will be of most interest to many users

Our maps are intended for transport planning, not for navigational purposes, and thus are exempt.


## Feedback and contact information

We do not have the resources to provide phone or in-person contact details.

There is a contact email at the bottom of the About page: pct@pct.bike.


## Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website, subject to funding. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: pct@pct.bike.


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


## Technical information about this website’s accessibility

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

## Disproportionate burden

We’ve assessed the resources required for fixing the issues with navigation and accessing information, and with interactive tools and transactions.
It would require substantial input from an experienced developer, beyond the resources we have available in the current contract, to improve the accessibility of the site in the following key areas:

- work to provide a downloadable report as HTML/Word/PDF, providing a summary of the tool, it's key findings.
- make the regional summary findings more accessible, as self-standing HTML pages and add a site map
- improve the navigability of the site by reducing reliance on JavaScript and creating more links between website section and improving heading structure throughout the site.


We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in 2021.

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


The PDFs and Word documents, including the user manuals, are not essential to providing our services of informing evidence-based investment in cycling.
The provision of regional summaries provide an overview of the findings.
The case study PDFs provide a good overview of how the services are used in practice but are not essential.


We do not plan to add captions to the video on the landing page because video recorded before September 2020 is exempt from meeting the accessibility regulations.

## What we’re doing to improve accessibility

<!--
[Note: publishing an accessibility roadmap is optional. It’s a good idea to publish one if you want to be specific about the order you’re planning to tackle accessibility issues, and there’s no space to do so in the accessibility statement itself.]
-->

Subject to funding we plan to provide a downloadable report as HTML/Word/PDF, providing a summary of the tool, it's key findings.


We would also like to make the regional summary findings more accessible, as a sitemap.
<!--
We would like to improve the navigability of the site by reducing reliance on JavaScript and creating more links between website section and improving heading structure throughout the site.
-->
Reproducing the functionality of the map using text-based user interfaces would be a larger challenge, requiring a fundamental change to the codebase.
It may be more cost effective to address this issue by creating new web services than by adapting the current PCT codebases, which is based on the web framework shiny.

<!--

You can read the full accessibility test report [add link to report].

[Note: publishing the test report is optional, but doing so may allow you to make your accessibility statement shorter and more focused.]
-->





