Accessibility statement for www.exeter.ac.uk

Source: https://www.exeter.ac.uk/about/oursite/accessibility/compliance/ Parent: https://www.exeter.ac.uk/about/oursite/dataprotection/request/#a4

• Accessibility
• Accessibility statement
• Changing page appearance

Accessibility statement for www.exeter.ac.uk

This accessibility statement applies to content published by the University’s Web Content Management System (Web CMS) to www.exeter.ac.uk and associated university department sub domains:

University of Exeter Departments\ This table lists the academic departments and related units within the University of Exeter. Each cell contains a link to the department’s website. The table is structured as four columns per row, grouping departments alphabetically across multiple rows for easier scanning and navigation.

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. For example, that means you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 170% 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)

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 accessibility-related issue, 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

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. Link text must have sufficient contrast against the background so users with low vision or contrast sensitivity can read it. This fails WCAG 2.2 success criterion 1.4.3 (Contrast Minimum).
• Text fails minimum contrast requirements. Text must meet minimum contrast ratios to remain readable for users with visual impairments. This fails WCAG 2.2 success criterion 1.4.3 (Contrast Minimum).
• Links inside text are difficult to see or identify. Links must be visually distinguishable and not rely on colour alone. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color).

2. Content structure and semantics

• An image is missing alternative text. Images must have appropriate alt text so users who cannot see them understand their purpose. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
• A heading is missing an accessible name. Headings must include clear descriptive text so screen reader users can identify and navigate the page structure. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Elements intended as presentation-only contain focusable content. Presentational elements must not be interactive, as this confuses keyboard and screen reader users. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
• Incorrect use of ARIA states or properties. ARIA attributes must be valid and used correctly, as incorrect ARIA can mislead assistive technologies. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

3. Forms, buttons and interactive controls

• A button is missing an accessible name. Buttons must include meaningful names so users of assistive technologies understand their purpose. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
• A form field is missing an accessible name. Form inputs must include labels or accessible names so users know what information is required. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
• A link is missing an accessible name. Links must include descriptive names so screen reader users understand the destination or purpose. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

An iframe is missing an accessible name. Iframes must have titles or accessible names to explain their purpose. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

4. Tables and data relationships

• A complex data table is missing ID and/or header attributes to associate headers with data cells. Data tables must include semantic associations so assistive technologies convey relationships correctly. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• A table header is not associated with any data cells. Table headers must be programmatically connected to their data cells so users understand table structure. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• A layout table includes a summary attribute. Layout tables must not include summary information as this misleads screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• A layout table contains a caption element. Captions must only be used for real data tables, not layout tables. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).

5. Page-level attributes and language

• The page is missing a language attribute. Pages must declare a default language so screen readers can apply correct pronunciation rules. This fails WCAG 2.2 success criterion 3.1.1 (Language of Page).
• An element language attribute has an invalid language tag. Language codes must follow valid standards so assistive technologies announce them correctly. This fails WCAG 2.2 success criterion 3.1.2 (Language of Parts).
• The page is missing a title. Web pages must have descriptive titles to help users understand the purpose of the page. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).

6. Keyboard access and focus management

• Scrollable content is not accessible using the keyboard. All interactive content must be operable without a mouse to support keyboard-only users. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
• An element marked as hidden is included in the tab navigation. Hidden elements must not receive keyboard focus as this disrupts navigation. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

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 11 September 2020. It was last reviewed on 5 March 2026.

This website was last tested on 6 March 2026 against the WCAG 2.2 AA. The test was carried out using the Acquia Web Governance and the Axe browser extension.