Accessibility

Contents

This page explains how we ensure our NHS website and service sites are usable and accessible to all users. This applies to:

Kent Community Health NHS Foundation Trust
- Beside You
- Clover Street
- Discovery Orthotics
- East Sussex School Health and CITES
- Kent family (0 to 19 services)
- Kent Youth Health
- New Street Dental Practice
- Quality Improvement
- SHIFT.

We want to ensure that we make reasonable adjustments to enable our patients and service users to receive information in formats that they can understand and appropriate support to help them communicate. It is our duty under the Equality Act 2010.

Accessibility statement for Kent Community Health NHS Foundation Trust

This website and our service sites are run by Kent Community Health NHS Foundation Trust. We want as many people as possible to be able to use these websites. For example, that means you should be able to:

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 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 (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.

You can use our Recite Me accessibility toolbar to:

read the website text aloud (including PDFs)
download the text as an MP3 file to play it where and when it suits you
change font sizes and colours
customise background-colours
translate text into more than 100 different languages
access a fully integrated dictionary and thesaurus.

If you find information on our site that you think should be clearer, please tell us by emailing kchft.comms@nhs.net. We will need to know the details of the page your were looking at; information you thought should be clearer and anything else you think would help us to improve this.

How accessible our websites are

We know some parts of websites aren’t fully accessible:

most older PDF documents aren’t fully accessible to screen reader software
some videos don’t have captions
you can’t modify the line height or spacing of text
some of our online forms are difficult to navigate using just a keyboard.

Closed captions for video content

We host our videos on Vimeo or YouTube, who use auto-generated closed captions for people who ae deaf or have hearing loss.

Closed captions can be turned on/off by clicking on the icons shown in the video toolbars below.

Vimeo

YouTube

What to do if you can’t access parts of our websites

If you need information on our websites in a different format like translations, accessible PDF, large print, easy read, British Sign Language (BSL), audio recording or braille:

0800 030 4550
kentchft.PALS@nhs.net

We’ll consider your request and get back to you within 14 days.

Reporting accessibility problems with our websites

We’re always looking to improve the accessibility of our websites. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact our Communications Team at kchft.comms@nhs.net.

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

Kent Community Health NHS Foundation Trust is committed to making its websites 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 version 2.1 (WCAG) AA standard.

Our websites are partially compliant with the WCAG AA standard, due to the non-compliances listed below.

Non-accessible content

We have listed checks identified from our accessibility scanner that are non-accessible.

We have outlined the checks for our Kent Community Health website and our service sites separately below.

Non compliance with the accessibility regulations

Kent Community Health (this website)

A standard

Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure links explain their purpose WCAG 2.0 A 2.4.4
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Fix missing ARIA description IDs WCAG 2.0 A 1.3.1
Specify a title for all frames WCAG 2.0 A 2.4.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Write lists or groups of links semantically WCAG 2.0 A 1.3.1
Ensure headings include text WCAG 2.0 A 1.3.1
Avoid alternative text that is the same as adjacent text WCAG 2.0 A 1.1.1
Ensure lists are marked up correctly WCAG 2.0 A 4.1.1
Add a scope to table headings WCAG 2.0 A 1.3.1
Add headers to tables WCAG 2.0 A 1.3.1
Fix duplicate IDs WCAG 2.0 A 4.1.1
Add a legend for all fieldsets WCAG 2.0 A 1.3.1
Combine adjacent links with the same destination WCAG 2.0 A 1.1.1
Avoid linking to anchors that do not exist WCAG 2.0 A 2.4.1
Ensure links are distinguished by more than just colour WCAG 2.0 A 1.4.1
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Ensure custom tabbing order makes sense WCAG 2.0 A 2.4.3

AA standard

Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Identify the purpose of fields programmatically WCAG 2.1 AA 1.3.5
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5

Beside You

A standard

Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure links explain their purpose WCAG 2.0 A 2.4.4
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Ensure lists are marked up correctly WCAG 2.0 A 4.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Ensure links are distinguished by more than just colour WCAG 2.0 A 1.4.1
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Combine adjacent links with the same destination WCAG 2.0 A 1.1.1
Add headers to tables WCAG 2.0 A 1.3.1
Ensure headings include text WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Specify a title for all frames WCAG 2.0 A 2.4.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1

AA standard

Ensure pages don't scroll in two dimensions on small screens WCAG 2.1 AA 1.4.10
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Identify the purpose of fields programmatically WCAG 2.1 AA 1.3.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5

Clover Street

A standard

Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure links explain their purpose WCAG 2.0 A 2.4.4
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Add headers to tables WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Specify a title for all frames WCAG 2.0 A 2.4.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1

AA standard

Ensure pages don't scroll in two dimensions on small screens WCAG 2.1 AA 1.4.10
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure pinch-to-zoom is enabled WCAG 2.0 AA 1.4.4
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure pages don't require zooming and 2D scrolling on small screens WCAG 2.1 AA 1.4.10
Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Identify the purpose of fields programmatically WCAG 2.1 AA 1.3.5
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4

Discovery Orthotics

A standard

Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Ensure links are distinguished by more than just color WCAG 2.0 A 1.4.1
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Avoid alternative text that is the same as adjacent text WCAG 2.0 A 1.1.1
Add headers to tables WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Write lists or groups of links semantically WCAG 2.0 A 1.3.1
Ensure labels in the document point to valid IDs WCAG 2.0 A 1.3.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1
Ensure custom tabbing order makes sense WCAG 2.0 A 2.4.3
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2

AA standard

Ensure pages don't scroll in two dimensions on small screens WCAG 2.1 AA 1.4.10
Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Identify the purpose of fields programmatically WCAG 2.1 AA 1.3.5
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3

East Sussex Children

A standard

Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Ensure links are distinguished by more than just color WCAG 2.0 A 1.4.1
Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Avoid alternative text that is the same as adjacent text WCAG 2.0 A 1.1.1
Add headers to tables WCAG 2.0 A 1.3.1
Ensure headings include text WCAG 2.0 A 1.3.1
Add a scope to table headings WCAG 2.0 A 1.3.1
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Fix duplicate IDs WCAG 2.0 A 4.1.1
Specify a title for all frames WCAG 2.0 A 2.4.1
Ensure pre-recorded media has a description or text alternative WCAG 2.0 A 1.2.3
Ensure pre-recorded video has text alternative WCAG 2.0 A 1.2.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1
Include audio controls where necessary WCAG 2.0 A 1.4.2

AA standard

Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure prerecorded media has a description WCAG 2.0 AA 1.2.5
Ensure captions are provided for all live audio WCAG 2.0 AA 1.2.4
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5

Kent Family

A standard

Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure links are distinguished by more than just colour WCAG 2.0 A 1.4.1
Ensure lists are marked up correctly WCAG 2.0 A 4.1.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Add a submit button to all forms WCAG 2.0 A 3.2.2
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Specify alternative text for images inside links WCAG 2.0 A 1.1.1
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Combine adjacent links with the same destination WCAG 2.0 A 1.1.1
Avoid alternative text that is the same as adjacent text WCAG 2.0 A 1.1.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Specify alternative text for appropriate images WCAG 2.0 A 1.1.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1
Ensure custom tabbing order makes sense WCAG 2.0 A 2.4.3

AA standard

Ensure pages don't scroll in two dimensions on small screens WCAG 2.1 AA 1.4.10
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5

New Street Dental Practice

A standard

Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure lists are marked up correctly WCAG 2.0 A 4.1.1
Ensure links are distinguished by more than just color WCAG 2.0 A 1.4.1
Add a scope to table headings WCAG 2.0 A 1.3.1
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Add headers to tables WCAG 2.0 A 1.3.1
Ensure links can be used by screen readers WCAG 2.0 A 4.1.2
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2

AA standard

Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3

Quality Improvement

A standard

Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Ensure links explain their purpose WCAG 2.0 A 2.4.4
Tag all PDFs WCAG 2.0 A 1.3.1
Check PDFs have sufficient text contrast WCAG 2.0 A 1.4.3
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure PDF content is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Fix duplicate IDs WCAG 2.0 A 4.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Specify headings for every PDF WCAG 2.0 A 1.3.1
Combine adjacent links with the same destination WCAG 2.0 A 1.1.1
Ensure links are distinguished by more than just color WCAG 2.0 A 1.4.1
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Specify a title for all frames WCAG 2.0 A 2.4.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1

AA standard

Ensure text has sufficient contrast (AA) WCAG 2.0 AA 1.4.3
Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Ensure long PDFs use bookmarks to aid navigation WCAG 2.0 AA 2.4.5
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4

SHIFT

A standard

Ensure functionality is available to keyboard users WCAG 2.0 A 2.1.1
Ensure form controls have labels WCAG 2.0 A 1.3.1
Ensure every page contains a top-level heading WCAG 2.0 A 1.3.1
Check PDFs have sufficient text contrast WCAG 2.0 A 1.4.3
Tag all PDFs WCAG 2.0 A 1.3.1
Check that each page has an appropriate title WCAG 2.0 A 2.4.2
Ensure HTML is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure PDF content is in a meaningful sequence WCAG 2.0 A 1.3.2
Ensure alternative text is appropriate WCAG 2.0 A 1.1.1
Ensure users can pause or hide animated content WCAG 2.0 A 2.2.2
Specify headings for every PDF WCAG 2.0 A 1.3.1
Ensure links are distinguished by more than just color WCAG 2.0 A 1.4.1
Check if text should be marked as a heading WCAG 2.0 A 1.3.1
Avoid using the same link text for different destinations WCAG 2.0 A 2.4.4
Check images have been correctly defined as decorative WCAG 2.0 A 1.1.1
Ensure PDFs specify a default language WCAG 2.0 A 3.1.1
Fix duplicate IDs WCAG 2.0 A 4.1.1
Specify a title for all frames WCAG 2.0 A 2.4.1
Check pages for three flashes (Level A) WCAG 2.0 A 2.3.1
Ensure labels or instructions are provided when content requires user input WCAG 2.0 A 3.3.2
Check that each frame has an appropriate title WCAG 2.0 A 2.4.1

AA standard

Ensure controls change appearance when they are selected WCAG 2.0 AA 2.4.7
Ensure text placed over images or gradients has sufficient contrast WCAG 2.0 AA 1.4.3
Ensure form controls contrast sufficiently with their surroundings WCAG 2.1 AA 1.4.11
Ensure long PDFs use bookmarks to aid navigation WCAG 2.0 AA 2.4.5
Ensure components are identified consistently WCAG 2.0 AA 3.2.4
Ensure that navigation remains consistent WCAG 2.0 AA 3.2.3
Use text to convey information where possible WCAG 2.0 AA 1.4.5
Ensure suggested corrections are provided where applicable WCAG 2.0 AA 3.3.3
Check that headings and labels are descriptive WCAG 2.0 AA 2.4.6
Ensure there are multiple ways to access a page WCAG 2.0 AA 2.4.5
Check if an error prevention mechanism is required (for legal, financial, data) WCAG 2.0 AA 3.3.4

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services.

Older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, board papers.

We do not generally add new PDFs to our site. There are some exceptions:

we add some PDFs as downloads of reports or publications
our annual reports and other reports, which must, by law, be laid before parliament in a printed version, and then appear unaltered
downloads intended for print purposes, such as posters.

Is there anything I can do to make PDF documents more accessible?

Useful information about ways to make Acrobat documents more accessible is provided on Adobe’s website.

Online maps

Maps embedded from digital mapping services such as Google Maps, and maps made available in formats such as PDF - are exempt from meeting the accessibility regulations where they are used for non-navigational purposes. However, we will always attempt to provide as much related information as possible in text, for example, postcodes and directions.

Video content

We do not plan to add captions to existing pre-recorded video content that was published before the 23 September 2020. This content is exempt from the regulations. All new video content we produce will have appropriate captions, audio descriptions and transcripts as necessary.

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Third party content

Some of the content hosted on our website or linked to by us is created by third parties. We have no control over the accessibility of these documents and encourage third parties we work with to make their documents as accessible as possible. If you need accessibility adjustments for a document that may be controlled by a third party, please contact us using the methods below.

This is not a comprehensive list as we are still identifying some accessibility issues.

What we’re doing to improve accessibility

We plan to identify and fix issues on a regular basis.

We are working to identify content/documents and where information is still required, we plan to update, fix the document or republish it in HTML format.
We are aware we have a number of other non-accessible documents such as board and council of governors papers, staff guidance and policies. We are currently working on fixing these documents and the work will be completed by end of December 2024.
If you require one of these documents in an accessible format, please contact kentchft.PALS@nhs.net
There are some documents designed for printing. This includes our Community Health magazine.

Accessibility toolbar

We have digital inclusion software from Recite Me, on our website. This makes our content more accessible with reading and translation support*. This service is free for site users.

* The language translation service should only be used to translate general information on our website. As this is a Google translation tool, it is not intended to replace human or traditional translation methods. To ensure patient safety please continue to use our service providers to translate information relating to personal treatment and care.

Click on the light blue accessibility icon (located bottom right) on your screen to launch the support toolbar.

All the features are accessed from an easy-to-use toolbar.

Dictionary, translation, and magnifier

Dictionary, translation and magnifying buttons

Dictionary: Highlight and click on this to view the definition of the word
Translation: Translate text into a different language
Magnifier: Click and drag the magnifying glass to magnify text on the screen.

Play audio

Text to speech buttons

Back: Rewind to the previous paragraph of text.
Play: Click the Play button to read the text aloud.
Forward: Skip forward to the next paragraph of text.

Text options

Text size and font buttons

Decrease: This will decrease the text size.
Font: You can change the font that displays on the page
Increase: This will increase the text size

Colour, ruler and mask

Colour, ruler and mask buttons

Colour: Change the background, text, and link colours
Ruler: Click to enable the reading ruler
Screen mask: Will create a letterbox for focused viewing of a section of the page.

Margins, plain text mode, and download audio

Margins, text only and download buttons

Text mode: Remove images to view content in plain text mode
Margins: Change the text dimensions by narrowing the width of the text column
Download audio: Highlight the text then click the button to download the text as an audio file.

Settings

Settings buttons

Settings: Adjust your Recite Me toolbar settings
Reset: This will restore the default settings
User guide: This will give you an overview of the Recite Me toolbar features.

Toolbar FAQs

Do I need to download anything to enable Recite Me?

How do I launch the Recite Me toolbar?

Does Recite Me work across different operating systems and mobile devices?

Can I save my settings?

How do I turn Recite Me off?

Interpreting and translation

We can provide communication and language support to help with your care.

If English is not your first language, we will book an interpreter for your appointment and send written information in your preferred language.

We offer:

video, telephone and face-to-face interpreting
British Sign Language interpreting and other support for the Deaf community
translation of letters and leaflets
Braille
audio
large print
Easy Read.

If you want to make sure we know your preferred language, please contact the service you are seeing. Their details will be included on appointment letters or you can search for a service at www.kentcht.nhs.uk/our-services/.

Contacting us by phone or visiting us in person

If you contact the relevant service before your visit we can arrange a British Sign Language (BSL) interpreter and/or arrange appropriate accessibility needs.

For help or more details please speak to our Patient Advice and Liaison Service (PALS):

0800 030 4550
Text 07899 903499
kentchft.PALS@nhs.net

Preparation of this accessibility statement

Last updated on 12 August 2024.

This statement was prepared on 20 December 2023.

Our websites were last tested on 24 May 2024 against the WCAG 2.1 AA standard. The tests were complete in-house using an automated accessibility scanner.

A representative sample of pages of the website were tested along with a sample of the documents from each area of the website.