Accessibility statement
This accessibility statement applies to the Medway Adult Education website at www.medwayadulteducation.co.uk.
This website is run by Medway Council. We want as many people as possible to be able to use this website. Which 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 are not fully accessible.
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:
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 are 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.
Translating our website
There are lots of options available for you to translate pages on our website into other languages including:
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.2 AA standard, due to the known accessibility issues below.
Non-accessible content
Non-compliance with the accessibility regulations
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.
Help not presented consistently
Some help is not presented consistently. This fails WCAG A 3.2.6 (consistent help). We aim to complete this by the end of November 2024.
Ensure login is accessible
Login is not accessible and requires the user to complete a cognitive test such as remembering a password or solve a puzzle. This fails WCAG AA 3.3.8 (accessible authentication minimum). We aim to complete this by the end of November 2024.
Interactive components not far enough apart
Some interactive components are too close together. This fails WCAG AA 2.5.8 (target size minimum). We aim to complete this by the end of November 2024.
Avoid redundant entry
In some areas we ask for the same information twice. This fails WCAG A 3.3.7 (redundant entry). We aim to complete this by the end of November 2024.
Alternative to drag and drop movements
Where drag and drop movements are used, there is not an accessible alternative provided. This fails WCAG AA 2.5.7 (dragging movements). We aim to complete this by the end of November 2024.
Focus is paritally obscured
Focus is partially obscured on certain elements and users cannot see where they are on the page. This fails WCAG AAA 2.4.12 (focus not obscured enhanced). We aim to complete this by the end of November 2024.
Ensure login is accessible (without exception)
A login requre the user to remember a password or solve a puzzle. This fails WCAG AAA 3.3.9 (accessible authentication enhanced). We aim to complete this by the end of November 2024.
Ensure pages do not scroll in 2 dimensions on small screens
This fails WCAG AA 1.4.10 (reflow). We aim to complete this by the end of November 2024.
Ensure functionality for keyboard users is available
This fails WCAG A 2.1.1 (keyboard). We aim to complete this by the end of November 2024.
Lists should be marked up correctly
This fails WCAG A 4.1.2 (name, role, value). We aim to complete this by the end of November 2024.
Ensure every page contains a top-level heading
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by the end of November 2024.
Text placed over images or gradients have sufficient colour contrast
This fails WCAG AA 1.4.3 (contrast minimum). We aim to complete this by the end of November 2024.
Images must have alternative text on image gallery
This fails WCAG A 1.1.1 (non text content). We aim to complete this by the end of November 2024.
Ensure pages do not require zooming and 2D scrolling on small screens
This fails WCAG AA 1.4.10 (reflow). We aim to complete this by the end of November 2024.
Ensure HTML is in a meaningful sequence
This fails WCAG A 1.3.2 (meaningful sequence). We aim to complete this by the end of November 2024.
Each page should have an appropriate title
This fails WCAG A 2.4.2 (page titled). We aim to complete this by the end of November 2024.
Text should have sufficient contrast
This fails WCAG AA 1.4.3 (contrast minimum). We aim to complete this by the end of November 2024.
Specify the language of every page
This fails WCAG A 3.1.1 (language of page). We aim to complete this by the end of November 2024.
Check if text should be marked as a heading
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by the end of November 2024.
Add a scope to table headings
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by the end of November 2024.
Ensure alternative text is appropriate
This fails WCAG A 1.1.1 (non-text content). We aim to complete this by the end of November 2024.
Ensure links can be used by screen readers
This fails WCAG A 2.4.1 (bypass blocks). We aim to complete this by the end of November 2024.
Identify the purpose of fields programmatically
This fails WCAG AA 1.3.5 (identify input purpose). We aim to complete this by the end of November 2024.
Allow users to quickly skip to content
This fails WCAG A 2.4.1 (bypass blocks). We aim to complete this by the end of November 2024.
Legends should be added for all fieldsets
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by the end of November 2024.
Navigations should be consistent
This fails WCAG AA 3.2.3 (consistent navigation). We aim to complete this by the end of November 2024.
Headings and labels should be descriptive
This fails WCAG AA 2.4.6 (headings and labels). We aim to complete this by the end of November 2024.
Each frame should have an appropriate title
This fails WCAG A 2.4.1 (bypass blocks). We aim to complete this by the end of November 2024.
Ensure components are identified consistently
This fails WCAG AA 3.2.4 (consistent identification). We aim to complete this by the end of November 2024.
Navigation should remain consistent
This fails WCAG AA 3.2.3 (consistent navigation). We aim to complete this by the end of November 2024.
Document should have one landmark
This fails WCAG A 1.3.1 (info and relationships), WCAG 1.3.6 AAA (identify purpose) and WCAG 2.4.1 A (bypass blocks). We aim to complete this by the end of November 2024.
Ensure links explain they open in a new tab
This fails WCAG AAA 3.2.5 (help). We aim to complete this by the end of November 2024.
Content should not be too difficult to understand
This fails WCAG AAA 3.1.5 (reading level). We aim to complete this by the end of November 2024.
Ensure labels and instructions are provided when content requires user input
This fails WCAG A 3.3.2 (on input). We aim to complete this by the end of November 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 the end of November 2024.
Use text to share information where possible
This fails WCAG A 1.3.1 (info and relationships). We aim to complete this by the end of November 2024.
Hamburger menu needs 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 the end of November 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).
At 400% zoom, content within the cookie banner does not reflow correctly and information is not fully visible. This fails WCAG AA 1.4.10 (reflow).
The focus element of the cookie consent banner fails WCAG AAA 2.4.13 (focus appearance).
These are issues with our implementation of the third-party solution, Cookiebot.
We're looking into this with our supplier Cookiebot.
Exemptions: content that’s not within the scope of the accessibility regulations
Embedded Google Maps
2 embedded Google Maps do 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.
What we're doing to improve accessibility
We're auditing medwayadulteducation.co.uk to see if it's accessible.
We have formed an accessibility working group of officers from around the council. This group is helping us:
- give colleagues the tools to make accessible websites and documents
- create training courses, to raise the profile of the issue within the organisation
- communicate the importance of the issue, through newsletters, our Intranet and communication campaigns
- share developments and news through Microsoft Teams groups
- improve access to help and advice through our accessibility toolkit
Preparation of this accessibility statement
This statement was prepared on 22 September 2021. It was last reviewed on 17 October 2024.
This website was last tested on 16 October 2024. The test was carried out by Silktide. A sample of pages were tested based on user needs.
View our Silktide report of current accessibility issues
Silktide monitors accessibility issues and tracks the progress we make fixing them.
We’ll update this statement as we fix accessibility issues.