What is an accessibility statement?
An accessibility statement tells people how accessible your website is. It is useful for people who rely on assistive technology. It helps people understand if they can use the site and how to get help if they experience any issues.
It’s good practice to add an accessibility statement to every website.
How to add this accessibility statement to your website
- Create a new basic page if you have a Drupal site
- Use the exact wording in the statement. Some of the text must be included for legal reasons.
- Use the same heading styles on your webpage. For example, ‘Accessibility statement’ should be H1 (heading style one) and ‘How accessible this website is’ should be H2 (heading style 2).
- Update any areas in square brackets [EXAMPLE].
- Write your examples in plain language. Do not use technical language.
- Explain which success criterion the issue affects. For example, ‘Many 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).’
- Email assistedmigration@admin.cam.ac.uk to add a link to the statement in your local site footer, if you're using the new Cambridge Web Platform.
Get support
- Read the Web Content Accessibility Guidelines (WCAG) 2.2
- Find out about accessible content on the Content Community SharePoint site.
If you have any questions or need advice, email accessibility@cam.ac.uk or contentdesign@uis.cam.ac.uk.
-----------------------------------------------------------
Accessibility statement
This website is run by the University of Cambridge and this accessibility statement applies to [INSERT URL].
This website is published using the Cambridge Web Platform. The Cambridge Web Platform Accessibility Statement contains information about the accessibility of features common to platform websites.
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
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
All pages should comply with WCAG 2.1 Level AA and where possible comply with WCAG 2.2 Level AA.
We know some parts of this website are not fully accessible:
[LIST HIGH-LEVEL DETAILS]
[example: Most older PDF documents are not fully accessible to screen reader software]
[example: Many images do not have text descriptions]
Requesting information in a different format
If you need information on this website in a different format, email [INSERT CONTACT]. We’ll consider your request and get back to you in 5 business days.
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 email accessibility@cam.ac.uk and give details of the URLs and the problems you encountered.
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/2022 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS) (link opens in a new window).
Technical information about this website’s accessibility
The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018/2022 (the ‘accessibility regulations’) do not apply to the University of Cambridge. However, the University of Cambridge is committed to making its websites and mobile applications accessible and in this regard to complying voluntarily with the accessibility regulations. This accessibility statement is published in that context.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 Level AA standard, due to the following non-compliances.
Non-accessible content
The content listed is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
[INSERT DETAILS – enter each reason on a separate line and in plain language. Do not use technical language. For each reason you list, include the WCAG criterion that is not met]
[EXAMPLE: Many 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).]
What we’re doing to improve accessibility
We’ll continue to address the accessibility issues identified in this accessibility statement. Our aim is to resolve or significantly improve issues within our control by [INSERT DATE – MONTH AND YEAR]. We’ll report issues beyond our control to the software provider to consider. As we implement changes, we’ll review and retest the accessibility of this website.
Preparation of this accessibility statement
We have listed all known accessibility issues in this statement.
We tested this website in [INSERT DATE – MONTH AND YEAR] using both manual and automated testing tools on desktop and mobile devices.
Browsers
On desktop, we used:
- [LIST WEB BROWSER AND OPERATING SYSTEM, for example, Google Chrome 130 on Windows 11]
On mobile, we used:
- [LIST DEVICE AND WEB BROWSER, for example, Apple Safari 18]
Assistive technology
On desktop, we used
- [IF APPLICABLE, LIST ASSISTIVE TECHNOLOGY USED IN TESTING, for example, NVDA 2024]
On mobile, we used:
- [IF APPLICABLE, LIST ASSISTIVE TECHNOLOGY USED IN TESTING, for example, Apple VoiceOver]
Automated testing tools
We used:
- [LIST AUTOMATED TOOLS USED IN TESTING, for example, axe DevTools]
This statement was prepared on [INSERT DATE – MONTH AND YEAR]. It was last reviewed on [INSERT DATE – MONTH AND YEAR].