Accessibility statement for news.exeter.ac.uk
This statement applies to content published on the news.exeter.ac.uk website. It does not apply to content on subdomains or other platforms.
Separate accessibility statements are available for other University platforms and websites.
This website is run by the University of Exeter.
How you should be able to use this website
We want as many people as possible to be able to use this website. 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 also make the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
On this page
- How accessible this website is
- Feedback and contact information
- Reporting accessibility problems with this website
- Enforcement procedure
- Technical information about this website's accessibility
- Compliance status
- Non-accessible content
- What we're doing to improve accessibility
- Preparation of this accessibility statement
How accessible this website is
Parts of this website are not fully accessible. For example:
- some pages and document attachments are not written in plain English.
- some tables do not have row or column headers.
- some documents have poor colour contrast.
- some heading elements are not consistent.
- some images do not have image descriptions.
- some images used to convey information have poor colour contrast.
- some information in tables cannot be reached with a keyboard.
- many documents are in PDF format and are not accessible.
Feedback and contact information
If you:
- experience problems whilst using assistive software to access our site.
- need information on this website in a different format like accessible PDF or Word document, audio recording or braille.
- have any other feedback.
Please contact the digital team at digitalteam@exeter.ac.uk.
In your message, please include any of the following:
- the web address (URL) of the content
- your email address and name
- the format you need.
Our Contact page lists other departments you can call for information.
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 the digital team - digitalteam@exeter.ac.uk.
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
The University of Exeter 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 non-compliances and exemptions listed below.
Non-accessible Content - non-compliance with regulations
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
1. Contrast and Visual Design
- Link text fails minimum contrast requirements. Some link text does not meet required contrast ratios, making it difficult for users with low vision or contrast sensitivity to read. This fails WCAG 2.2 success criterion 1.4.3 (Contrast Minimum).
2. Accessible Names
- Link is missing an accessible name. Some links do not include a clear and descriptive accessible name, making it difficult for screen reader users to understand their purpose. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Button is missing an accessible name. Certain buttons lack accessible names, which prevents users of assistive technologies from understanding what the button does. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Iframe element is missing an accessible name. Some iframe elements do not include an accessible title or name, making embedded content unclear to screen reader users. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
3. Images and Alternative Text
- Image is missing alternative text. Several images are missing descriptive alt text, preventing users of assistive technologies from accessing the meaning or purpose of the image. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
4. Link Visibility and Identification
- Link inside text is difficult to see or identify. Some inline links are not visually distinct from surrounding text, making it difficult for users to recognise that the text is clickable. This fails WCAG 2.2 success criterion 1.4.1 (Use of Colour).
Disproportionate burden
At present we do not claim disproportionate burden for anything. However this may change, following further review and testing.
Content that’s not within the scope of the accessibility regulations
- Non‑HTML documents published before September 2018 do not need to be accessible unless they are required for users to access or use a service.
- Live video streams are exempt from the accessibility regulations, so we do not plan to add captions to live video content.
What we’re doing to improve accessibility
Training for staff
- Since Winter 2025, staff who are new to publishing web content are required to complete accessibility training so they understand how to meet WCAG 2.2 AA standards.
- Staff already involved in web publishing before this date are encouraged to take the same training to help maintain a consistent approach to accessibility across our websites.
TerminalFour Version 8 Migration Project
As part of the University’s Web Team Strategy, work began in Spring 2022 on the TerminalFour Version 8 Migration Project. This programme includes a wide range of activity to improve website accessibility. Any issues that cannot be fixed immediately will be addressed through the relevant parts of this project.
The aim of the project is to improve the experience for our users by making our digital services clearer, easier to use and more accessible.
How this work will support accessibility
- Digital tools and applications will be reviewed for accessibility, and accessibility is a key focus within our updated technology roadmap.
- Bringing more of our websites and services onto common platforms will help us manage and monitor accessibility more effectively.
- Updated guidance and training for staff editing web content, along with regular reviews and annual accessibility audits, will support ongoing improvements.
- Removing outdated or unnecessary content will reduce the amount of inaccessible material across the site.
- Accessibility will be a core requirement for all new web services and solutions, and a more consistent approach will help us maintain accessible standards across the digital estate.
Preparation of this accessibility statement
This statement was prepared on 26 September 2024. It was last reviewed on 17 March 2026.
This website was last tested on 13 March 2026. The test was carried out using the Acquia Web Governance and the Axe browser extension.