Accessibility statement for EdWeb 2 Content Management System (Drupal 10)

This accessibility statement applies to: https://web-training.is.ed.ac.uk/ 

This website is run by the University of Edinburgh. We want as many people as possible to be able to use this application. For example, that means you should be able to:

• Change colours, contrast levels and font size
• Use the website without encountering any flashing, scrolling or moving text

We’ve also made the website text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording we could use without changing what the text means.

Customising the website

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:

AbilityNet - My Computer My Way

With a few simple steps you can customise the appearance of our website using your browser settings to make it easier to read and navigate:

Additional information on how to customise our website appearance

If you are a member of University staff or a student, you can use the free SensusAccess accessible document conversion service:

Information on SensusAccess

How accessible this website is

We know some parts of this website are not fully accessible:

• There are some areas where the colour contrast could be improved
• Not all non text content has a text alternative
• There are pop-ups that appear and links that open a new tab without notifying user
• Some text may be overlapping
• Links are not underlined by default
• Some links do not have meaningful hypertext  
• Some content is cut, hidden or overlapping with increasing magnification levels
• Reflow is not enabled to 400%
• Some information is conveyed by colour only
• Not all content can be reached by keyboard
• Keyboard focus indicator does not always have sufficient colour contrast
• Not all tooltips are shown when navigating by keyboard or assistive technologies
• Although rarely used, there is a case of dragging functionality that does not have a keyboard alternative
• Compatibility with screen-readers (such as JAWS) may be limited, for example, some text may be read repeatedly
• Some heading levels may be skipped
• Some video content does not have transcripts, audio descriptions and human-corrected captions
• Not all audio visual content has an audio description
• Users are automatically logged off after some time of inactivity
• Users are not always given information on errors and how to resolve them
• There are moving icons that indicate loading and cannot be stopped or paused by the user

Feedback and contact information

If you need information on this website in a different format, including accessible PDF, large print, audio recording or braille:

• Email: website.support@ed.ac.uk
• Telephone: Information Services Helpline - +44 (0)131 651 5151
• Address: Website and Communication team, Argyle House, 3 Lady Lawson St, Edinburgh, EH3 9DR
• British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

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

Reporting accessibility problems with this website

We are 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, please contact:

• Complete our web form: Report an accessibility problem
• Email: website.support@ed.ac.uk
• Telephone: Information Services Helpline - +44 (0)131 651 5151
• Address: Website and Communication team, Argyle House, 3 Lady Lawson St, Edinburgh, EH3 9DR
• British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

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

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 please contact the Equality Advisory and Support Service (EASS) directly:

Contact details for the Equality Advisory and Support Service (EASS)

The government has produced information on how to report accessibility issues:

Reporting an accessibility problem on a public sector website

Contacting us by phone using British Sign Language

British Sign Language service

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week.

Contact Scotland BSL service details.

Technical information about this website’s accessibility

The University of Edinburgh is committed to making its websites and applications 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 (WCAG) 2.2 AA standard, due to the non-compliances listed below.

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard

Non accessible content

The content listed below is non-accessible for the following reasons.

Noncompliance with the accessibility regulations

The following items to not comply with the WCAG 2.2 AA success criteria:

• Not all non text content has a text alternative
• 1.1.1 Non Text Content
• Not all video will have captions or captions that identify all speakers as well as noting other significant sounds, e.g., laughter.
  • 1.2.2 - Captions (Prerecorded)
• An alternative for time-based media or audio description of the prerecorded video content is not always provided
  • 1.2.3 - Audio Description or Media Alternative (Prerecorded)
• Not all audio visual content has an audio description
• 1.2.5 Audio-description-prerecorded
• Lists are not always structured correctly
  • 1.3.1 - Info and Relationships
• The way the content is presented affects its meaning, and a correct reading sequence is not always programmatically determined
  • 1.3.2 - Meaningful Sequence
• The purpose of each input field collecting information about the user can not always be programmatically determined e.g Autocomplete attribute is not used correctly
  • 1.3.5 - Identify Input Purpose
• Toggle buttons and links in the text should be clearly identifiable (color alone is not enough to distinguish links from the surrounding text)
  • 1.4.1 - Use of Color
• There may not be sufficient colour contrast between font and background colours especially where the text size is small
  • 1.4.3 - Contrast (Minimum)
• Text cannot always be resized without assistive technology up to 200 percent without loss of content or functionality
  • 1.4.4 - Resize Text
• A lot of the pages reflow well and do not require horizontal scrolling, but some content is cut from different magnification levels
  • 1.4.10. - Reflow
• There are cases of overlapping text
  • 1.4.12 - Text Spacing
• Some tooltips disappear as soon as the cursor moves or may not be accessible by other means than mouse
  • 1.4.13 - Content on Hover or Focus
• Not all content is reachable by keyboard
  • 2.1.1 - Keyboard
• Users are automatically logged off after some time of inactivity and there is not a warning
  • 2.2.1 - Timing Adjustable
• Headings or heading levels are sometimes missed
  • 2.4.6 - Headings and Labels
• It is not always clear where the user has reached via keyboard navigation
  • 2.4.7 - Focus Visible
• When a user navigated by keyboard, focus states are sometimes hidden by other content
  • 2.4.11 - Focus Not Obscured (Minimum)
• There is a case where are no keyboard alternatives to a dragging movement
  • 2.5.7 - Dragging Movements
• Pop ups appear without the user being alerted when the user interacts with an item and some links open new tabs
  • 3.2.2 - On Input
• Users are not always given information on errors and how to resolve them
• 3.3.3 Error Suggestion
• Not all content may be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies
  • 4.1.2 - Name, Role, Value

We aim to improve our websites accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our site accessibility. 

We are working towards solving these problems and expect several improvements by February 2026 for those items under our control. For those issues under the control of the supplier Drupal we will continue to highlight these and push for resolution.

Disproportionate burden

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

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

At this time, we believe no content is outwith the scope of the accessibility regulations.

What we’re doing to improve accessibility

We will continue to address and make adequate improvements to the accessibility issues highlighted. Unless specified otherwise, a complete solution or significant improvement will be in place by February 2026 for those items are under our control. For those issues under the control of the supplier Drupal we will continue to highlight these and push for resolution.

While we are in the process of resolving these accessibility issues, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this website.

Preparation of this accessibility statement

This statement was prepared on 25^th February 2025. It was last reviewed on 20^th August 2025. 

The website was last tested in February 2025. The testing was carried out by Disability Information Team at the University of Edinburgh using both automated and manual methods. The site was tested on a PC, primarily using Microsoft Edge alongside Mozilla Firefox and Google Chrome.

Recent world-wide usage levels survey for different screen readers and browsers shows that Chrome, Mozilla Firefox and Microsoft Edge are increasing in popularity and Google Chrome is now the favoured browser for screen readers:

WebAIM: Screen Reader User Survey

The aforementioned three browsers have been used in certain questions for reasons of breadth and variety.

We ran automated testing using AXE browser extension (for Google Chrome) and then manual testing that included:

• Spell check functionality;
• Scaling using different resolutions and reflow;
• Options to customise the interface (magnification, font, background colour, etc);
• Keyboard navigation and keyboard traps;
• Data validation;
• Warning of links opening in new tab or window;
• Information conveyed in the colour or sound only;
• Flashing, moving or scrolling text;
• Use with screen reading software (for example JAWS);
• Assistive software (TextHelp Read and Write, Windows Magnifier, ZoomText, Dragon Naturally Speaking, TalkBack and VoiceOver);
• Tooltips and text alternatives for any non-text content;
• Time limits;
• Compatibility with mobile accessibility functionality (Android and iOS);
• Any drag functionality and alternatives;
• Consistent help function;
• No need to re-enter data already submitted;
• Any cognitive tests.