You are here: Home | Medway Safeguarding Children Partnership (MSCP) Accessibility statement

Medway Safeguarding Children Partnership (MSCP) Accessibility statement

This accessibility statement applies to the MSCP website at www.medwayscp.org.uk.  

This 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’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 this website is 

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

  • most older PDFs and Word documents are not fully accessible to screen reader software  
  • <html> elements do not have a lang attribute 
  • documents do not have one main landmark 
  • page content is not contained by landmarks  
  • pages do not contain one level 1 (H1) heading  
  • some elements do not have sufficient colour contrast 
  • some links do not have discernible text 
  • some links with the same name do not have a similar purpose.

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 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 or 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.2 AA standard, due to the known accessibility issues below. 

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.

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 fix this by the end of June 2025.

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 fix this by the end of June 2025.

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 fix this by the end of June 2025.

Help not presented consistently

Some help is not presented consistently. This fails WCAG A 3.2.6 (consistent help). We aim to fix this by the end of June 2025.

Focus is partially 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 fix this by the end of June 2025.

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 fix this by the end of June 2025.

Ensure every page contains a top-level heading

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Specify alternative text for images inside links.

This fails WCAG A 1.1.1 (non-text content). We aim to fix this by the end of June 2025.

Ensure PDFs have a title

This fails WCAG A 2.4.2 (page titled). We aim to fix this by the end of June 2025.

Ensure PDFs are all tagged

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Ensure PDFs are machine readable

This fails WCAG A 1.1.1 (non-text content). We aim to fix this by the end of June 2025.

Ensure PDFs specify a default language

This fails WCAG A 3.1.1 (language of page). We aim to fix this by the end of June 2025.

Ensure PDF headings follow a logical order

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Check PDFs have sufficient colour contrast

This fails WCAG AA 1.4.3 (contrast minimum). We aim to fix this by the end of June 2025.

Specify headings for every PDF

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Ensure the first heading in a PDF is a heading 1

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Ensure PDFs have a strong title

This fails WCAG A 2.4.2 (page titled). We aim to fix this by the end of June 2025.

Ensure long PDFs use bookmarks to aid navigation

This fails WCAG AA 2.4.5 (multiple ways). We aim to fix this by the end of June 2025.

Each page should have an appropriate page title

This fails WCAG A 2.4.2 (page titled). We aim to fix this by the end of June 2025.

PDFs should be in a meaningful sequence

This fails WCAG A 1.3.2 (meaningful sequence). We aim to fix this by the end of June 2025.

Ensure links explain they open in a new tab

This fails WCAG AAA 3.2.5 (change on request). We aim to fix this by the end of June 2025.

Ensure headings include text

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

Ensure images are correctly defined as decorative

This fails WCAG A 1.1.1 (non-text content). We aim to fix this by the end of June 2025.

Alternative text should be appropriate

This fails WCAG A 1.1.1 (non-text content). We aim to fix this by the end of June 2025.

Adjacent links with the same destination

This fails WCAG A 1.1.1 (non-text content). We aim to fix this by the end of June 2025.

Avoid using the same link text for different destinations

This fails WCAG A 2.4.4 (link purpose in context).We aim to fix this by the end of June 2025.

<html> element must have a lang attribute 

This fails WCAG A 3.1.1 (language of page). We aim to fix this by the end of June 2025.

Pages should contain at least one heading

This fails WCAG AA 2.4.6 (headings and labels). We aim to fix this by the end of June 2025.

Heading levels should only increase by one

This fails WCAG AA 2.4.6 (headings and labels). We aim to fix this by the end of June 2025.

Ensure links explain their purpose

This fails WCAG A 2.4.4 (link purpose in context). We aim to fix this by the end of June 2025.

Search this site text needs to have sufficient colour contrast

This fails WCAG AA 1.4.11 (non-text contrast). We aim to fix this by the end of June 2025.

All page content should be contained by landmarks

This fails WCAG A 1.3.1 (info and relationships). We aim to fix this by the end of June 2025.

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 fix this by the end of June 2025.

Check context sensitive help is available for forms

This fails WCAG AAA 3.3.5 (help). We aim to fix this by the end of June 2025.

Ensure text is used to convey information where possible

This fails WCAG AA 1.4.5 (images of text). We aim to fix this by the end of June 2025.

Labels and heading should be descriptive

This fails WCAG AA 2.4.6 (headings and labels). We aim to fix this by the end of June 2025.

Labels and instructions should be provided when content requires user input

This fails WCAG A 3.3.2 (on input). We aim to fix this by the end of June 2025.

Each frame should have an appropriate title

This fails WCAG A 2.4.1 (bypass blocks). We aim to fix this by the end of June 2025.

Most older PDFs and Word documents are not fully accessible to screen reader software   

We aim to fix this by the end of June 2025.

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. 

Exemptions: content that’s not within the scope of the accessibility regulations

Not applicable.

Disproportionate burden 

Not applicable. 

Preparation of this accessibility statement 

This statement was prepared on 8 September 2020. It was last reviewed on 30 May 2025.

This website was last tested on 30 May 2025. The test was carried out by Silktide. A sample of pages were tested based on user needs.