Our goal is to ensure our website is accessible to all users whatever type of device they are using and whatever their disability, including those with impaired vision, motor difficulties, cognitive impairments or learning disabilities, deafness or impaired hearing.
Our goal is to ensure our website is accessible to all users, whether they are accessing the site using a PC, a mobile phone, a tablet or other internet device.
We aim to adhere to current best practice, such as the W3C's Web Content Accessibility Guidelines and the RNIB's "See It Right" guidelines and of course Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
Help With Multimedia
If you are having difficulty accessing MP3 audio files, try downloading one of the following players:
Using this website
This website is operated by Scotland’s Rural College (SRUC). We want the site to be as accessible as possible and we are committed to ensuring digital accessibility for people with disabilities.
Users should be able to:
- Zoom text to 500% with it remaining fully readable
- Use a screen reader to browse the website
- Modify spacing of text using an appropriate browser extension (for example Easy Read in Chrome)
AbilityNet has advice on making your device easier to use if you have a disability. AbilityNet is a UK charity that exists to change the lives of disabled people by helping them to use digital technology at work, at home or in education.
Measures To Support Accessibility
We are using the following measures to ensure accessibility of the SRUC website:
- We are using third party software to assess the accessibility of our website
- We include accessibility within our internal policies
- We tested our website for accessibility during the design process, and we carry out similar testing on the live site
- There is a ‘skip to main content’ button so users can access what they really need quickly
- All elements should have sufficient colour contrast ratio. We use a scroll reveal effect which can trick accessibility audit tools into thinking otherwise
How accessible is our website?
We know some parts of this website aren’t fully accessible:
- You can’t modify line height of text
- PDF documents aren’t fully accessible to screen reader software
- Some of our videos don’t have edited captions
- Some of our buttons don’t show focus for keyboard-only users
- Some images have blank alternate text because they are decorative (majority of images on SRUC site) meaning they will be ignored by a screen reader (which is the preferred option), having alternative text for all images (which aren't necessary to understanding the information) will overwhelm a screen reader user with irrelevant content
What to do if you can’t access parts of this website
We’re always looking to improve the accessibility of this website. Please contact us using our website accessibility information form if you:
- Find any problems that are not listed on this page
- Think we are not meeting the requirements of the accessibility regulations
We’ll consider your request and get back to you in three working days.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing 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 our website’s accessibility
SRUC is committed to making its website 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 non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
While text can be zoomed or magnified, and text can be spaced out using an extension such as Easy Read in Chrome, it is not possible for users to modify text spacing or line height. This doesn’t meet WCAG 2.1 success criterion 1.4.12 (text spacing). We are looking at a solution to this issue.
Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader. This doesn’t meet 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.
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This doesn’t meet WCAG 2.1 success criterion 2.4.1 (bypass blocks).
Content that’s not within the scope of 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 marked up so they are accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value). The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential for active administrative processes. Any new PDFs or Word documents we publish will meet accessibility standards.
Some of our videos don’t have accurate edited captions or transcripts. This doesn’t meet WCAG 2.1 success criterion 1.2.1 (audio-only and video-only pre-recorded), 1.2.2 (captions pre-recorded), 1.2.3 (audio description or media alternative pre-recorded) and 1.2.5 (audio description pre-recorded). The regulations do not apply to recorded videos published before 23 September 2020.
Additional accessibility considerations
The Web Content Accessibility Guidelines (WCAG) define three levels of conformance: level A, level AA and level AAA. Although our goal is WCAG 2.1 Level AA conformance, we have also applied some level AAA success criteria:
Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed
The purpose of each link can be identified from link text alone, except where the purpose of the link would be ambiguous to users in general
Functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes
Information about the user’s location within a set of web pages is available
How we tested this website
We carried out a mixture of automated and manual tests on using Monsido.
What we’re doing to improve accessibility
We have a rolling programme of updating content in accordance with the guidelines set out by the WCAG.
Accessibility statement updates log
This statement was first prepared on 2nd June 2020. It was last updated on 9th June 2020. We are logging every change we make to this page.