Accessibility statement
This accessibility statement applies to medway.metastreet.co.uk. The online service is run by Medway Council and provided through a software platform developed and maintained by MetaStreet Limited.
How you can use this website
This website is run by Medway Council. We want as many people as possible to use this website.
- change colours, contrast levels and fonts using browser or device settings
- zoom in up to 400% without the text spilling off the screen
- navigate most of the website using a keyboard or speech recognition software
- listen to most of the website using a screen reader
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 is this website
We know some parts of this website are not fully accessible:
- you cannot skip directly to the main content when using a keyboard
- the password strength indicator relies on colour alone
- some pages do not use headings correctly
- some components do not provide a clear keyboard focus indicator
- some form fields do not have accessible labels or clear error messages
- some links and buttons have touch targets that are too small
- some PDF documents generated by the platform are not fully accessible to screen reader users.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, email hmo@medway.gov.uk.
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email hmo@medway.gov.uk.
We’ll consider your request and get back to you in 5 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).
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
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-compliance with the accessibility regulations
Content listed below is non-accessible.
- users cannot skip directly to the main content
- password strength relies on colour alone
- some pages have incorrectly structured heading hierarchies
- the OneLink payment autofill component lacks a visible keyboard focus state
- some form fields do not have accessible labels or clear error messages
- some interactive elements do not meet minimum target size requirements
- generated PDFs are untagged and may not be fully accessible for assistive technologies.
We publish this list to show the issues we know about. This helps us comply with the law and be transparent about what we're working to fix.
Users cannot skip directly to the main content
The skip to main content feature is not currently accessible to keyboard users, making it difficult to bypass repetitive navigation content. This fails WCAG A 2.4.1 (Bypass Blocks), A 2.1.1 (Keyboard), AA 1.4.3 (Contrast (Minimum)), AA 2.4.7 (Focus Visible), and AA 2.4.13 (Focus Appearance). We aim to fix this by the end of 2027.
Password strength relies on colour alone
Users who cannot perceive colour differences may not be able to determine the strength of their password. This fails WCAG A 1.4.1 (Use of Color) and A 3.3.2 (Labels or Instructions). We aim to fix this by the end of 2027.
Some pages have incorrectly structured heading hierarchies
This can make it difficult for users of assistive technologies to understand the structure and organisation of content. This fails WCAG A 1.3.1 (Info and Relationships). We aim to fix this by the end of 2027.
The OneLink payment autofill component lacks a visible keyboard focus state
This may make it difficult for keyboard users to determine which element is currently selected. This fails WCAG AA 2.4.7 (Focus Visible) and AA 2.4.13 (Focus Appearance). We aim to fix this by the end of 2027.
Some form fields do not have accessible labels or clear error messages
Users may find it difficult to understand what information is required or how to correct errors when submitting forms. This fails WCAG A 1.3.1 (Info and Relationships), A 3.3.1 (Error Identification), A 3.3.2 (Labels or Instructions), and AA 3.3.3 (Error Suggestion). We aim to fix this by the end of 2027.
Some interactive elements do not meet minimum target size requirements
Users with limited dexterity or those using touch devices may find these elements difficult to select accurately. This fails WCAG AA 2.5.8 (Target Size (Minimum)) and AAA 2.5.5 (Target Size). We aim to fix this by the end of 2027.
Generated PDFs are untagged and may not be fully accessible for assistive technologies
This may prevent users from navigating and understanding document content effectively. This fails WCAG A 1.1.1 (Non-text Content), A 1.3.1 (Info and Relationships), A 1.3.2 (Meaningful Sequence), A 2.4.2 (Page Titled), AA 2.4.6 (Headings and Labels), A 3.1.1 (Language of Page), and A 4.1.2 (Name, Role, Value). We aim to fix this by the end of 2027.
Disproportionate burden
Not applicable.
Preparation of this accessibility statement
This statement was prepared on 19 August 2026. It was last reviewed on 19 August 2026.
This website was last tested on 12 August 2026 against the WCAG 2.2 AA standard.
The test was carried out by Medway Council, with various testing methods including Axe, Lighthouse, WAVE and manual testing.