Accessibility Statement

Projects Website accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Website accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to and

This site is managed by Project Services, which is part of the Information Services Group (ISG) at the University of Edinburgh. 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 via settings in your web browser
  • zoom in up to 200% without the text spilling off the screen
  • navigate most of the website using just a keyboard
  • listen to most of the website using a screen reader (including the most recent versions of Job Access with Speech (JAWS), NonVisual Desktop Access (NVDA) and VoiceOver)
  • Not be timed out of the site

We’ve also made the website text as simple as possible to understand.

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 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:

  • Some parts may not be fully compatible with screen readers.  For example, some images do not have alternative text
  • You may not be able to access all content by using the keyboard alone. For example, some headings skip levels and it is not possible to access all links
  • There are some areas of the site that do not meet the required standard for contrast.  For example, there are some coloured buttons and labels that do not meet requirements, and the ‘admin’ menu
  • Some older PDF documents are not fully accessible to screen reader software
  • There are some abbreviations used in the site that are not explained
  • Spell check is not enabled in certain areas, such as ‘find’ fields or page titles

Feedback and contact information

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

  • Email 
  • Call our Information Services Helpline 0131 651 5151
  • British Sign Language (BSL) users can contact us via contactSCOTLAND-BSL, the on-line BSL interpreting service.

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

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 Information Services Project Management Office (PMO):

  • Email
  • Call our Information Services Helpline 0131 651 5151
  • British Sign Language (BSL) users can contact us via contactSCOTLAND-BSL, the on-line BSL interpreting service.

We’ll consider your request and get back to you within 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, 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

contactSCOTLAND-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 24 hours a day, 7 days a week.

contactSCOTLAND-BSL service details

Technical information about this website’s accessibility

The University of Edinburgh 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.1 AA standard, due to the non-compliances listed below.

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.1 AA standard

Non-accessible content

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

Non-compliance with the accessibility regulations

  • Not all non-text content has a text alternative e.g.
    • There are some embedded images for charts or screen captures which do not have a suitable text alternative and so are inaccessible to screen-readers.
    • Some images and icons do not have alternative text
  • Information, structure, and relationships conveyed through presentation can not always be programmatically determined  e.g.
    • There is no <h1> on the homepage and two identical headings, one visible and one for screen readers, on all other pages. 
    • On project home pages the nested headings jump from h1 in the title bar to h3 in the panel titles.
    • Some tables added in user-generated content are lacking mark up for headings, especially when the headings are the first column.
    • Required text input fields do not make use of the required attribute. 
    • Heading navigation was complicated by skipping heading levels on pages.
  • Colour contrasts do always meet recommended guidance e.g.
    • There are some minor contrast issues with some coloured buttons and labels, mainly the colour green. 
    • There is insufficient contrast with the blue link text and grey background for the collapsed vertical tabs when editing content.
    • The contrast on the “Skip content” link does not meet requirements 
    • The autocomplete option on the TypeAhead plugin used for the search block is does not meet the contrast requirements on text.
  • The contrast for non –text items does not always meet recommend guidance e.g.
  • Not all content can be accessed by a keyboard only e.g. 
    • It is not possible to access all links on the “insert files” modal dialogue, notable the “close”.
  • Where content is repeated on multiple pages there is not always a way to bypass it e.g.
    • Navigation to the columns for related information on project homepages could be improved. 
    • The main landmark is missing so it is not possible to use that method to jump to content.
  • The purpose of each link is not always clear from  the link text alone e.g. 
    • Where files have been uploaded as attachments it should be clearer what the file type is by giving the file a filename appropriate to use as link text.
    • The default link text used when inserting a link to an uploaded file on a Project Page should be more meaningful.
    • There are some links in the Latest News Panel which do not have unique and meaningful link text.
    • There are other instances of duplicate link text used across panels, such as “review all…”.
  • The keyboard focus indicator is not always visible e.g.
    • On the homepage, while it is possible to navigate the “Find…” input suggestions in the drop-downs, there is no focus highlighting.
  • There are unexplained acronyms across the site.
  • Input fields with validation errors should include the aria-invalid attribute.
  • Not all navigational mechanisms occur in the same order on every page e.g.
  • Spellcheck is not enabled on all free text boxes e.g.
    • the search or the “Find” fields on the homepage.  Spellcheck is enabled for the rich text areas for content input, but not for other fields such as the page title.
  • For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role cannot always  be programmatically determined e.g. 
    • Expanding and collapsing panels on the homepage does not set the correct ARIA attributes to announce the change in state.
    • The date field calendar popup does not announce its presence nor the keyboard shortcuts it uses.
    • When using the editor page, the vertical tabs do announce when they are expanded, but not what region has changed.
  • Status messages are not always pragmatically determined e.g.
    • Navigating the vertical tabs on the edit page screen, expanding a tab is announced, but not the content area which has changed as a result.

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

There is no known content that is not within the scope of the accessibility regulations.

What we’re doing to improve accessibility

As part of the accessibility audit, a list of follow-up actions has been compiled to address areas of non-compliance in the website. These action points will be added to our existing log of improvements and fixes that are reviewed on a regular basis. Where issues exist that are within our direct control, we will work to make some improvements by August 2021. As changes are made, we will continue to review accessibility and retest the accessibility of this website and update the accessibility statement.

Preparation of this accessibility statement

This statement was prepared on 11th August 2020. It was last reviewed on 01st September 2020.

This website was last tested in August 2020. The test was carried out by the Information Services Group Software Development Team.

A combination of manual and automated testing was done, including using assistive technologies to access the site.

A sample of pages were tested with the WAVE WebAim accessibility evaluation tool to help identify any issues with the page structure and some visual issues such as text sizing and contrast.  The sample included the homepage, project pages, programme pages and the form for creating new project content.

The site was primarily tested using Chrome and Internet Explorer.  The screen-readers used to test the site were NVDA (with Chrome) and JAWS (with Internet Explorer) as well as ZoomText (with Chrome) and TextHelp Read&Write (with Internet Explorer).

We tested:

  • Spellcheck functionality
  • Scaling using different resolutions
  • Options to customise the interface (magnification, font, background colour et. cetera)
  • Keyboard navigation
  • Data validation
  • Warning of links opening in a new tab or window
  • Information conveyed in colour or sound only
  • Flashing or scrolling text
  • Operability if JavaScript is disabled
  • Use with screen reading software (eg. JAWS)
  • Assistive Software (TextHelp Read and Write, ZoomText)
  • Tooltips and text alternatives for any non-text content
  • Time limits