How we are making our website more accessible

This accessibility statement applies to https://www.Imperial.nhs.uk, https://www.cc4c.imperial.nhs.uk/, https://www.careinformationexchange-nwl.nhs.uk/ and https://www.nwl-acute-provider-collaborative.nhs.uk/accessibility.

This website is run by Imperial College Healthcare NHS Trust. We want as many people as possible to be able to use this website. For example, that means you should be able to:

The website can be converted using the toggle switches below – these will apply the update to all pages throughout your website session.

  • Grayscale:
    Grayscale switch On Off
    High contrast:
    High contrast switch On Off
    Regular text size:
    Normal switch On Off
    Large text size:
    Larger switch On Off
    Extra large text size:
    Largest switch On Off
    Change page colours and contrast levels 
    • Change font size
  • 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

[Note: use this section to provide information that a disabled user can act on - for example, avoid a particular section of the website, or request an alternative version rather than waste time trying to make it work with their assistive technology. Try to list in order of most impact to least impact.]

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

  • the text will not reflow in a single column when you change the size of the browser window
  • you cannot modify the line height or spacing of text
  • most older PDF documents are not fully accessible to screen reader software
  • live video streams do not have captions
  • some of our online forms are difficult to navigate using just a keyboard
  • you cannot skip to the main content when using a screen reader
  • there’s a limit to how far you can magnify the map on our ‘contact us’ page

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

  • email [email address]
  • call [phone number]
  • [add any other contact details]

We’ll consider your request and get back to you in [number] days.

If you cannot view the map on our ‘contact us’ page, call or email us [add link to contact details page] for directions.

Reporting accessibility problems with this website

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, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].

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

[Note: if your organisation is based in Northern Ireland, refer users who want to complain to the Equalities Commission for Northern Ireland (ECNI) instead of the EASS and EHRC.]

Contacting us by phone or visiting us in person

In order to make our services more accessible to people who are D/deaf, hearing impaired or have a speech impediment we have three numbers which can be used to reach a member of staff directly without having to encounter an automated menu selection via the UKRelay service (Relay UK - homepage | Relay UK (bt.com).

Outpatient appointments/admissions

0203 3111598
i.outpatientappointments@nhs.net
i.admissions@nhs.net

 Available Monday to Friday 8am to 8pm

Main Switchboard

 0203 3111599
i.switchboard@nhs.net

 Available 365 days per year 24 hours per day.

Patient advice and liaison service (PALS)

020 3311 1596
imperial.PALS@nhs.net

Available from Monday to Friday 10am to 4pm

Please do not use these numbers if you are not D/deaf, hearing impaired or have a speech impediment since our staff members will be expecting a UKRelay member of staff to join the call and misuse will be preventing those in need from accessing services.

Our offices have audio induction loops, or if you contact us by email imperial.interpreting@nhs.net before your visit we can arrange a British Sign Language (BSL) interpreter. 

Technical information about this website’s accessibility

[Note: this form of wording is legally required, so do not change it.]

[Name of organisation] 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

[Note: say that the website is fully compliant if the website meets WCAG 2.1 AA standard in full. Say that it’s partially compliant if it meets most requirements of the WCAG 2.1 AA standard. If it does not meet most requirements of the WCAG 2.1 AA standard, say that it’s not compliant.

If your website is either partially compliant or not compliant WCAG 2.1 AA standard, you’ll need to explain why. This will be due to one or both of the following:

  • non-compliances - this means the content in question is in scope of the regulations, but there’s an accessibility problem with it
  • an exemption - this means the inaccessible content is out of scope of the regulations, or it’d be a disproportionate burden for you to make it accessible

There’s a legally required way of expressing the compliance status of your website, so do not change it. The 3 options are as follows:]

This website is fully compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The [insert one of the following: ‘non-compliances’, ‘exemptions’ or ‘non-compliances and exemptions’] are listed below.

[Note: delete the options that do not apply.]

Non-accessible content

[Note: if the website is fully compliant with the WCAG 2.1 AA standard, you can leave the ‘Non-accessible content’ section out.

Otherwise, do not change the ‘Non-accessible content’ heading or the ‘The content listed below is non-accessible for the following reasons’ sentence - they’re legally required.

Do not change the ‘Non-compliance with the accessibility regulations’, ‘Disproportionate burden’ and ‘Content that’s not within the scope of the accessibility regulations’ subheadings: they’re also legally required.

But if you need to list a lot of problems, you can break these subsections up with further subheadings - for example, ‘Navigation and accessing information’ or ‘Interactive tools and transactions’.]

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

[Note: In this subsection, list:

  • accessibility problems
  • which of the WCAG 2.1 AA success criteria the problem fails on
  • when you plan to fix the problem

Do not include any problems where you’re claiming disproportionate burden, or where the problem is outside the scope of the accessibility regulations (those should go in the subsections below).]

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.

Disproportionate burden

[Note: in this subsection list accessibility problems you’re claiming would be a disproportionate burden to fix

Bear in mind that something which is a disproportionate burden now will not necessarily be a disproportionate burden forever. If the circumstances change, your ability to claim disproportionate burden may change too.]

There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option).

It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.

It’s not possible for users to change text size without some of the content overlapping.

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.

Our forms are built and hosted through third party software and ‘skinned’ to look like our website.

We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in [rough timing].

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

[Note: in this subsection list accessibility problems that fall outside the scope of the accessibility regulations.]

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document].

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

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

What we’re doing to improve accessibility

[Note: publishing an accessibility roadmap is optional. It’s a good idea to publish one if you want to be specific about the order you’re planning to tackle accessibility issues, and there’s no space to do so in the accessibility statement itself.]

Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.

Preparation of this accessibility statement

[Note: the wording about when the statement was prepared is legally required, so do not change it.]

This statement was prepared on [date when it was first published]. It was last reviewed on [date when it was last reviewed].

This website was last tested on [date]. The test was carried out by [add name of organisation that carried out test, or indicate that you did your own testing].

We used this approach to deciding on a sample of pages to test [add link to explanation of how you decided which pages to test].

[Note: you do not have to use this approach to sampling, but you should link to a full explanation of what you tested and how you chose it. If you get a third party auditor to test your website for you, they should include sampling details in test report - so you can just to link to that.]

You can read the full accessibility test report [add link to report].

[Note: publishing the test report is optional, but doing so may allow you to make your accessibility statement shorter and more focused.]

Accessibility standard

We follow the Web Content Accessibility Guidelines 2.0 (WCAG) published by the World Wide Web Consortium (W3C) and aim to meet WCAG’s Level AA recommended level of conformance standards across our website.

We regularly measure and review the accessibility of our website using a variety of browser plug-ins and external vendor assessments

Screen readers

We have run tests to ensure all page types on this website are accessible via a NVDA screen reader.

Text size

You can can choose to make the text larger (or smaller) by changing the text size option using the toggle switches displayed above.

Keyboard navigation

We have run tests to ensure users can navigate the website by using a keyboard.

Google translation

We have added Google translation to our site so you can view our content in different languages. Imperial College Healthcare NHS accepts no liability for the accuracy of translations on this site or reliance upon information contained in those translations.

How accessible is this website?

While this website strives to adhere to the accepted guidelines and standards for accessibility and usability, we know some parts of this website are not fully accessible. Known issues that we are seeking to address are as follows:

Home page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

A visible focus helps users know which element has keyboard focus and where they are on the page.

When an element gets focus there should be a visible border around it. Highlighting the element that has keyboard focus or is hovered over can provide information like whether the element is interactive or the scope of that element.

Operating systems have a native indication of focus, which is available in many browsers. The default display of the focus indicator is not always highly visible and may even be difficult to see especially on coloured backgrounds.

There is no visible focus around the hamburger menu at 200% zoom and above.

 

2

WCAG 1.4.10 Reflow

Reflow or ‘responsive web design’ helps users with low vision who may need to enlarge text on a webpage and read it in a single column without scrolling in more than one direction. It also helps users who are viewing the page on a mobile device.

If a page does not support reflow it can appear smaller and more difficult to use or content may be cut off.

Navigation menus often collapse into fewer items or into a single menu button to take up less space. All content and functionality must still be fully available.

The page does not reflow at 400% zoom.

 

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

Issue found using Deque Axe.

Screen readers tell users if a list is present and how many items are in the list. This helps users to know what they are reading and what to expect. It is important to use the correct semantic hierarchy for lists.

Ordered, unordered and description lists must contain semantically correct parent and child elements. When lists contain other elements or they are ordered incorrectly, screen readers are not able to read the lists accurately.

This is an issue in relation to the menu items in the header and top panel.

4

WCAG 4.1.2 Name, Role, Value: Buttons must have discernible text.

Issue found using Deque Axe.

All buttons must have a descriptive accessible name so that screen reader users can understand the destination, purpose, function, or action of the button.

If an image is used as a button, screen readers may not understand the use without a clear and accessible name. The title of an active image may not give enough information. Unnamed active images will have no details of the destination, purpose or action.

This is an issue in relation to the magnifying glass which does not have accessible text.

Get in touch page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

There is no visible focus around the hamburger menu at 200% zoom and above.

2

WCAG 1.4.10 Reflow

The page does not reflow at 400% zoom.

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

This is an issue in relation to the menu items in the header and top panel.

4

WCAG 4.1.2 Name, Role, Value: ARIA attributes must conform to valid values.

Issue found using Deque Axe.

Incorrect use of ARIA attributes can cause conflicts with semantic HTML elements which may cause errors in assistive technology and make accessibility worse for a user. ARIA defines which attributes are allowed and where.

ARIA attributes can cause issues where:

· an invalid attribute or attribute value is used

· attribute names or values are spelt incorrectly

· an invalid role has been assigned

· an attribute is missing when it is required

This is an issue in relation to the accordion headings. This is an issue because of the invalid ARIA attribute value: aria-controls="accordion-content-0-0."

 

5

WCAG 4.1.2 Name, Role, Value: Elements must only use allowed ARIA attributes.

Issue found using Deque Axe.

Incorrect use of ARIA attributes can cause conflicts with semantic HTML elements which may cause errors in assistive technology and make accessibility worse for a user. ARIA defines which attributes are allowed and where.

ARIA attributes can cause issues where:

· an invalid attribute or attribute value is used

· attribute names or values are spelt incorrectly

· an invalid role has been assigned

· an attribute is missing when it is required

This is an issue in relation to the accordion headings. This is an issue because the ARIA attribute is not allowed: aria-selected="true"

 

6

WCAG 4.1.2 Name, Role, Value: Buttons must have discernible text.

This is an issue in relation to the magnifying glass which does not have accessible text.

Services page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

There is no visible focus around the hamburger menu at 200% zoom and above.

2

WCAG 1.4.10 Reflow

The page does not reflow at 400% zoom.

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

This is an issue in relation to the menu items in the header and top panel.

GPs and referrers page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

There is no visible focus around the hamburger menu at 200% zoom and above.

2

WCAG 1.4.10 Reflow

The page does not reflow at 400% zoom.

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

This is an issue in relation to the menu items in the header and top panel.

4

WCAG 4.1.2 Name, Role, Value: Buttons must have discernible text.

This is an issue in relation to the magnifying glass which does not have accessible text.

Visiting us page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

There is no visible focus around the hamburger menu at 200% zoom and above.

2

WCAG 1.4.10 Reflow

The page does not reflow at 400% zoom.

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

This is an issue in relation to the menu items in the header and top panel.

4

WCAG 4.1.2 Name, Role, Value: Buttons must have discernible text.

This is an issue in relation to the magnifying glass which does not have accessible text.

Accessibility page issues

#

Issue and description

Where the issue was found

1

WCAG 2.4.7 Focus Visible

There is no visible focus around the hamburger menu at 200% zoom and above.

2

WCAG 1.4.10 Reflow

The page does not reflow at 400% zoom.

3

WCAG 1.3.1 Info and Relationships: <li> elements must be contained in a <ul> or <ol>.

This is an issue in relation to the menu items in the header and top panel.

4

WCAG 4.1.2 Name, Role, Value: Buttons must have discernible text.

This is an issue in relation to the magnifying glass which does not have accessible text.

 

Alternative formats

Our content can be provided on request in large print or easy read, as a sound recording, audio-description, in Braille or in alternative languages. Please email the communications team: imperial.communications@nhs.net

Reporting accessibility problems with this website

Although we have taken steps to make this site accessible, we would still welcome your comments on how we can improve it. To report an accessibility issue with the website, please contact us at imperial.Web@nhs.net.

If you need a foreign language interpreter or sign language interpreter, please tell your GP. They will advise us when they refer you to our services. 

When the referral is triaged the clinician will decide on the method they will use for the interpretation. This may be via telephone, video or face to face.

Find out what interpreting services are available for your appointment