This website is run by London Councils. London Councils Freedom Pass portal allows users to apply for, replace and renew their pass online. Users can also update their personal details and upload proof of identity, residency and photograph as part of their application for the scheme.
We aim to make the Freedom Pass website easy to use and accessible to everyone. We are actively working to increase the accessibility and usability of our website.
For example, that means you should be able to:
Change colours, contrast levels and fonts
Navigate most of the website using just a keyboard
Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
Navigate most of the website using speech recognition software
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is the website
We know this website is not fully accessible because:
Change colour, font and contrast
Colour can’t be changed in Edge
Font can’t be changed in Chrome and Edge
Font size can be increased in Chrome but the text doesn’t wrap
The sub-navigation fails colour contrast level
Navigate without a mouse
The website can’t be navigated using only a keyboard. This is because users can’t rely on keyboard navigation to move through the different sections of a page, from the address bar to menus, across fields, links and other content.
There is no option to skip to main content. This means users using a keyboard to navigate the website don’t have the option to bypass the top-level navigation links and jump to the main content on a page.
Listen to the website using a screen reader
The website can’t be navigated using a screen reader. This is because some content isn’t properly formatted and the screen reader will have difficulties navigating the different sections of a page.
When a page is enlarged, the screen reader doesn’t read tabs or move along the whole screen.
Some of the link text is not unique and uses the same link phrase for links going to different destinations. This means people using a screen reader will hear the same link phrase but the links will take them to different pages.
Some links are generic and not descriptive. For people using a screen reader they will hear a list of links without additional context.
Many of our PDFs don’t meet accessibility standards and are not accessible to a screen reader.
Some images don’t have a text alternative. This means a screen reader won’t be able to identify the function of the image.
There are some images of text that a screen reader will treat as if it were a photo or logo. This will prevent users from being able to properly navigate or understand elements of the page.
Some of our interactive elements don’t have the required descriptive tags to describe what their purpose is. This means a screen reader may not be able to identify a component such as a carousel.
What to do if you can’t access parts of this website or want to report accessibility problems
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
E-mail: [email protected]
Phone: 0300 330 1433
Postal address: Freedom Pass, PO Box 6618, Arbroath, DD11 9AZ
Please make sure you provide:
The document name and/or the web address (URL) of the page the content is on and,
A description of the format you need (for example, audio CD, braille, BSL or large print)
We try to respond within three business days. Please note there may be a delay in receiving other formats as these are created when they're requested.
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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
London Councils 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some images don’t have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
Some input fields have no description and some headings are in bold to highlight text, so people using a screen reader cannot identify the information. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). We plan to identify content as headings and ensure our input fields are programmatically determined by September 2020. When we publish new content we’ll make sure headings and input fields meets accessibility standards.
Colour contrast on pages is insufficient, so that people with moderately low vision or colour deficit vision cannot read it. This fails WCAG 2.1 success criterion 1.4.6 (contrast (enhanced). We plan to provide enough contrast between text and its background by September 2020. When we publish new content we’ll make sure that the contrast meets accessibility standards.
There is no mechanism to bypass blocks of content that is repeated on multiple pages, so people with some disabilities cannot reach the main content of the web page quickly and easily. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks). We plan to create a link and group blocks of repeated material in a way that can be skipped by September 2020. When we publish new content we’ll make sure there is a mechanism to bypass blocks of content so that our web pages meets accessibility standards.
Some pages do not have section headings, so people using a screen reader or keyboard cannot use shortcuts or tab through headings to identify and access different sections and information on a page. This fails WCAG 2.1 success criterion 2.4.10 (section headings). We plan to organise our pages using section headings by September 2020. When we publish new content we’ll make sure our section headings meets accessibility standards.
Entering data or selecting a form control on some pages does not have predictable effects, so that users with visual disabilities or cognitive limitations may not be able to detect changes of context in order to navigate the web pages. This fails WCAG 2.1 success criterion 3.2.2 (on input). We plan to provide submit buttons to initiate a change of context on required pages by September 2020. When we publish new content we’ll make sure input controls meets accessibility standards.
On some pages an input error is automatically detected and the error is described to the user in text, so people using a screen reader cannot identify the error until they encounter the error indicator. This fails WCAG 2.1 success criterion 3.3.1 (error identification). We plan to provide text descriptions to identify fields that were not completed, and use ARIA (Accessible Rich Internet Applications) so that screen readers can identify fields that have failed validation by September 2020. When we publish new content we’ll make sure our use of error identification meets accessibility standards.
Some fields do not have labels or instructions when content requires user input, so people with disabilities may not know what user input is required. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions). We plan to add descriptive labels to required fields that make the user input clear by September 2020. When we publish new content we’ll make sure our use of labels and instructions meets accessibility standards.
Some pages do not enable content to be parsed into a data structure, so some assistive technologies may present content differently or be completely unable to parse it. This fails WCAG 2.1 success criterion 4.1.1 (parsing). We plan to make sure that web pages can be parsed by September 2020. When we publish new content we’ll make sure our parsing of web pages meets accessibility standards.
Some pages do not provide role, state, and value information, so not all user interface components enables compatibility with assistive technology, such as screen readers, screen magnifiers, and speech recognition software. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value). We plan to add name, role and value attributes to required pages by September 2020. When we publish new content we’ll make sure our use of name, role and value attributes meets accessibility standards.
Content that’s not within the scope of the accessibility regulations
All accessibility problems listed fall within the scope of the accessibility regulations.
How we tested this website
This website was last tested on 3 October 2019. London Councils assessed the accessibility of the Freedom Pass website by self-evaluation, using a mixture of automated and manual tests. We tested a sample of pages including Home, Adding Evidence, Adding a Photograph and Making a Payment.
What we’re doing to improve accessibility
We plan to improve accessibility on this website by resolving the identified issues by December 2020.
This statement was created on 2 September 2019.
This statement was updated on 22 July 2020.