Accessibility statement for University of Strathclyde

This website is run by University of Strathclyde. 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 (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

We know some parts of this website aren’t fully accessible:

  • Some of the forms and search functions on our website are not labelled appropriately.
  • Some pages on our website use a legacy page layout that is not consistent with other pages and is not responsive.
  • Some images have missing or inappropriate alt text.
  • The colour contrast on some block level links is not sufficient.
  • Our link text does not always make sense when removed from the context of the page e.g. "Read more".
  • Headings do not appear in a logical order on some pages.
  • Some of our ARIA labelling is not valid or is used incorrectly.
  • Some of our PDFs and Word documents are not correctly structured.

What to do if you cannot access parts of this website

If you need information on this website in a different format, please email help@strath.ac.uk.

We’ll consider your request and get back to you in five working days.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website and our services. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact: help@strath.ac.uk.

Any issues reported will be reviewed by the University Web and Data Services team. To contact the Web and Data Services team, please email help@strath.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

University of Strathclyde is committed to making strath.ac.uk accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the the non-compliances and exemptions listed below.

Non-accessible content

We know that some parts of the website aren't fully accessible:

Non-compliance with the accessibility regulations: Issues with content

  • The navigational drop-down menus in the website header are not consistent between the website’s current and legacy page designs. This does not meet WCAG 2.1 success criterion 3.2.3.
  • Headings on some of our pages do not appear in a logical order. This does not meet WCAG 2.1 success criterion 2.4.10.
  • Some of our links do not make sense or are unhelpful when removed from the context of surrounding content. This does not meet WCAG 2.1 success criterion 2.4.4.
  • Some of our list items - <li> - do not have a <ul> or <ol> parent element. This does not meet WCAG 2.1 success criterion 1.3.1.
  • Some of our ARIA attributes do not have valid values. This does not meet WCAG 2.1 success criterion 4.1.2.

Non-compliance with the accessibility regulations: Issues with images, video and audio

  • Some of the alt tags for our images are missing or not appropriate. This does not meet WCAG 2.1 success criterion 1.1.1.
  • Some of the pages using the legacy design include images with embedded text. This does not meet WCAG 2.1 success criterion 1.4.5.
  • Some <video> elements do not have captions.This does not meet WCAG 2.1 success criterion 1.3.1.

Non-compliance with the accessibility regulations: Issues with interactive tools and transactions

  • Some of the forms and interactive search pages on our website are not appropriately labelled or do not have labels. This does not meet WCAG 2.1 success criterion 3.3.2.
  • Some of our interactive elements such as tabs and accordions are not functional using a keyboard and/or do not use appropriate mark-up to identify relationships. This does not meet WCAG 2.1 success criterion 2.1.1 and 4.1.2.
  • Some of our tab elements with role="tablist" do not have child elements with role="tab" present. Some of our tab elements with role="tab" do not have a parent with role="tablist" present. This does not meet WCAG 2.1 success criterion 1.3.1.
  • Some of our search pages and interactive elements do not utilise status messages to update screen readers of a change in state. This does not meet WCAG 2.1 success criterion 3.2.2.
  • The button to open the Hotjar survey does not contain screen-readable text. This does not meet WCAG 2.1 success criterion 4.1.2.

Non-compliance with the accessibility regulations: PDFs and other documents

  • Many of our 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. This doesn’t meet WCAG 2.1 success criterion 4.1.2.

How we aim to resolve these issues

We have a Digital Accessibility project currently running which aims to fix these issues, and to establish an ongoing monitoring and reporting schedule to ensure that compliance is maintained beyond the life of the project. The project also provides training to staff to improve knowledge, skills and understanding of digital accessibility across the institution. The project runs until Autumn 2024. 

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

  • 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. Any new PDFs or Word documents we publish will meet accessibility standards.
  • Maps are exempt from the accessibility regulations, but where we have a map on a page, we will provide other information in an accessible format, such as an address or directions
  • Live video streams don’t have captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 (captions - live). We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

How we test our website

Our website is crawled daily using the search software Funnelback. This provides us with accessibility reports against WCAG 2.1. We use Siteimprove to constantly identify and fix accessibility issues.

Our web developers and web content team use Deque Axe and WAVE browser plugins and manual testing techniques to ensure the pages they are working on are accessible.

When we design and develop new features for our website we test against a number of checkpoints that help us conform to WCAG 2.1 accessibility standards, and use these as part of our standard testing procedure.

What we’re doing to make our website more accessible

The University is committed to providing accessible digital content, and has initiated a two-year project to resolve outstanding accessibility issues with our websites and to provide training to staff to ensure we meet the highest standards going forward.

Digital Accessibility Project

An accessibility audit was conducted on our website by Jim Byrne Accessible Web Design in July 2019. This consisted of a manual audit using a browser and various assistive technologies on a sample set of pages that were broadly representative of the website as a whole. This included the website homepage, interactive functionality and search pages, and legacy page designs. The results of this audit were used to put forward a business case to run a full-scale project with dedicated staff to improve accessibility.

The project has ten dedicated members of staff, including developers, content creators, a tester and a trainer.

As part of the project, we are migrating content from the legacy website templates so that the website is consistent and accessible. As the migration is happening in sections, this means that some of the issues identified above will exist until the last of the legacy sections is migrated, but we are making good progress in reducing instances of these issues.

As well as migrating content, we are also fixing technical issues with the new templates and addressing content issues. These actions are reducing the instances of issues identified above.

We have a dedicated tester as part of the project who is manually testing migrated content, identifying issues that cannot be automatically detected. These are resolved by developers, improving accessibility on an ongoing basis.

Preparation of this accessibility statement

This statement was prepared on 23rd September 2019. It was last updated on 3rd August 2023.

This website is being tested regularly using the range of tools described above. Monthly reports are shared with the Digital Accessibility project board and stakeholders.

We used this approach to decide on a sample of pages to test: we chose a selection of page formats that represent a broad selection of developments and pages that represented key areas of the website. This includes our website homepage, course pages, news, opportunities, and interactive search pages. The URLs we audited are as follows: 

Accessibility Statement history

DateActivity
23rd September 2019  Accessibility Statement prepared 
2020 Accessibility Statement reviewed and updated
2021 Accessibility Statement reviewed and updated
27th May 2022 Accessibility Statement reviewed and updated
3rd August 2023 Accessibility Statement reviewed and updated