Web accessibility
Medway Tickets Live accessibility statement
This accessibility statement applies to the Medway Tickets Live website at www.medwayticketslive.co.uk
The website is run by Medway Council. 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 have 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 provided by third parties are not fully accessible:
- elements must have sufficient colour contrast
- id attribute values must be unique
- select element must have an accessible name.
Web Content Accessibility Guidelines (WCAG) 2.2
We will be testing our site against the new success criteria to become compliant with this standard.
We'll be using a combination of tools and manual testing to ensure we become compliant.
How to get information in an accessible format
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille you can fill in our online form:
Request information in an accessible format
Or you can phone 01634 333 333.
We’ll consider your request and get back to you in 20 working days.
Reporting accessibility problems
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, then please let us know by filling in our online form.
Report accessibility problems with this website
Or you can phone 01634 333 333.
We’ll consider your request and get back to you in 20 working days.
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).
Feedback and contact information
We provide a text relay service for people who are deaf, hearing impaired or have a speech impediment. The number is 18001 01634 333 333.
Our offices have audio induction loops. Or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.
Find out how to contact us and visit us in person.
Technical information about this website’s accessibility
Medway Council 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 known accessibility issues below.
We're beginning to test for WCAG.2.2. We will update our non-accessible content once we have completed testing.
Non-accessible content
The content that is not accessible is outlined below with details of:
- where it fails the success criteria
- planned dates for when issues will be fixed.
We have completed accessibility reports on third-party applications and are working with our suppliers to improve accessibility.
Aria role description on elements with a semantic role
This fails WCAG A 1.3.1 (info and relationships).We aim to complete this by 1 May 2024.
Ensure links explain their purpose
This fails WCAG A link purpose (in context). We aim to complete this by 1 May 2024.
Combine nearby links with the same destination
This fails WCAG A 1.1.1 (non-text content). We aim to complete this by 1 May 2024.
Specify alternative text for images inside links
This fails WCAG A 1.1.1 (non-text content). We aim to complete this by 1 May 2024.
Avoid using the same link text for different destinations
This fails WCAG A 2.4.4 link purpose (in context).We aim to complete this by 1 May 2024.
Ensure links explain their purpose
This fails WCAG A 2.4.4 Link purpose (in context). We aim to complete this by 1 May 2024.
Fix inaccessible link text
This fails WCAG A 2.4.4 Link purpose (in context). We aim to complete this by 1 May 2024.
All page content should be contained by landmarks
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by 1 May 2024.
Hamburger menu need to slide out and be a navigation list on page
This fails WCAG AA 2.4.11 (focus not obscured). We aim to complete this by 1 May 2024.
Third-party Cookiebot issues
At 400% zoom on first visit to the website, the cookies banner appears and covers the whole page and it is not appear to be accessible via keyboard.
This fails WCAG AA 2.4.7 (focus visible). This is an issue with our implementation of the third-party solution, Cookiebot.
We're looking into this with our supplier Cookiebot.
Third-party supplier fixes
Our third-party supplier aims to fix the following accessibility problems by the end of April 2024:
- elements must have sufficient colour contrast
- id attribute values must be unique
- select element must have an accessible name.
Exemptions: content that’s not within the scope of the accessibility regulations
Embedded Google Maps
1 embedded Google Map does not define explicit text labels for each form control. Form controls without labels do not meet WCAG A success criterion 1.3.1 (info and relationships).
Our content management and forms system provider, Jadu, have advised us that Google Maps will need to address this. However, whenever we show an address on a map, we also show the address as text on the web page.
Disproportionate burden
Not applicable.
Preparation of this accessibility statement
This statement was prepared on 2 December 2020. It was last reviewed on 9 April 2024.
This website was last tested on 21 September 2023. The test was carried out by Silktide. A sample of pages were tested based on user needs.