Accessibility statement

Accessibility statement for www.napier.ac.uk  

This website is run by Edinburgh Napier University. We want as many people as possible to be able to use this website and are committed to making it accessible for users with disabilities. 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 are not fully accessible. 

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: webaccessibility@napier.ac.uk 

We’ll acknowledge your request within three working days, and then provide a timescale for meeting your request, if it is possible. 

If you cannot view the map on our ‘contact us’ page, call or email us for directions. 

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: isservicedesk@napier.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)

Contacting us by phone or visiting us in person 

If you are a British Sign Language (BSL) user, you can contact Edinburgh Napier University via the national, free of charge, BSL video relay service - contactSCOTLAND-BSL

A number of our teaching spaces, libraries and some other public areas have audio induction loops, or if you contact us before your visit we can arrange a BSL interpreter.

Read more about the accessibility of our campuses 

Find out how to contact us

Technical information about this website’s accessibility 

Edinburgh Napier University 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 not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances and exemptions are listed below. 

Non-accessible content 

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

Non-compliance with the accessibility regulations 

Navigation and accessing information 
  • Some pages do not have functioning skip navigation, which means that keyboard users are unable to move easily around the page. This fails WCAG 2.1 success criteria 2.4.1 (Bypass Blocks). We plan to resolve this issue by 30 June 2021. 

  • Some pages have empty headings, meaning that people using screen readers are unable to understand the structure of a page. This fails WCAG 2.1 success criteria 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels). We plan to resolve this issue by 30 June 2021. 

  • Some pages have incorrect heading structures, so people using a screen reader and other assistive technology are unable to navigate by heading structure. This fails WCAG 2.1 success criteria 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels). We plan to resolve this issue by 30 June 2021. 

  • Some user controls presenting expanded content do so without being marked as expanded or collapsed, which means that a screen reader is unable to inform that new content has appeared. This fails WCAG 2.1 success criteria 3.2.2. (On Input) and 4.1.3 (Status Messages). We plan to resolve this issue by 30 June 2021. 

  • Some tables are missing functionality required for a screen reader to interpret the data within it. This fails WCAG 2.1 success criteria 1.3.1 (Info and Relationships). We plan to resolve this issue by 30 June 2021. 

  • Some instructions to users are missing the coding required for a screen reader to identify the action required. This fails WCAG 2.1 success criteria 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • Some sections of the site, such as the Courses drop down navigation, are inaccessible to a keyboard-only user. This fails WCAG 2.1 success criteria 2.1.1 (Keyboard). We plan to resolve this issue by 30 June 2021. 

  • People using a keyboard only are unable to tab through the site in a logical order. This fails WCAG 2.1 success criteria 2.4.3 (Focus Order). We plan to resolve this issue by 30 June 2021. 

  • Several pages have the same title as another page, giving a confusing user experience for people using a screen reader. This fails WCAG 2.1 success criteria 2.4.2 (Page Titled). Some user controls presenting expanded content do so without being marked as expanded or collapsed, which means that a screen reader is unable to inform that new content has appeared. This fails WCAG 2.1 success criteria 3.2.2. (On Input) and 4.1.3 (Status Messages). We plan to resolve this issue by 30 June 2021. 

  • Some tables are missing functionality required for a screen reader to interpret the data within it. This fails WCAG 2.1 success criteria 1.3.1 (Info and Relationships). We plan to resolve this issue by 30 June 2021. 

  • Some instructions to users are missing the coding required for a screen reader to identify the action required. This fails WCAG 2.1 success criteria 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • Some sections of the site, such as the Courses drop down navigation, is inaccessible to a keyboard-only user. This fails WCAG 2.1 success criteria 2.1.1 (Keyboard). We plan to resolve this issue by 30 June 2021. 

  • People relying on a keyboard are unable to tab through the site in a logical order. This fails WCAG 2.1 success criteria 2.4.3 (Focus Order). We plan to resolve this issue by 30 June 2021. 

  • Some pages have the same ID value as other pages, which means a screen reader will be unable to match a heading with its content. This fails WCAG 2.1 success criteria 4.1.1 (Parsing). We plan to resolve this issue by 30 June 2021. 

  • There are a number of instances where certain links in focus do not appear highlighted to keyboard-only users. This fails WCAG 2.1 success criteria 2.4.7 (Focus Visible). We plan to resolve this issue by 30 June 2021. 

Form context 
  • Some forms have unlabelled fields, so people using assistive technology are unable to understand the context of a field. This fails WCAG 2.1 success criteria 1.1.1 (non-text context), 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • There are groups of form fields missing the information needed by screen readers to understand context. This fails WCAG 2.1 success criteria 1.1.1 (Non-text Context), 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • Some fieldsets do not contain a legend, which would explain context to a person using a screen reader. This fails WCAG 2.1 success criteria 1.1.1 (Non-text Context), 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • Some form fields are missing notification that they are mandatory, so a person using screen reader technology would be unaware of mandatory fields. This fails WCAG 2.1 success criteria 1.1.1 (Non-text Context), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value). We plan to resolve this issue by 30 June 2021. 

  • Incorrectly completed forms are not returning an error message, which means screen reader users are unaware of form submission failure. This fails WCAG 2.1 success criteria 3.3.1 (Error Identification), 3.3.3 (Error Suggestion), 3.3.4 (Error Prevention – Legal, Financial, Data), and 4.1.3 (Status Messages). We plan to resolve this issue by 30 June 2021. 

Alternative text  
  • Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criteria 1.1.1 (Non-text Content) and 1.4.5 (Images of Text). We plan to resolve this issue by 30 June 2021. When we publish new content we’ll make sure our use of images meets accessibility standards. 

  • There are instances of text alternatives being present, but non-descriptive. This means that people using screen readers are not accessing the correct meaning of an image. This fails WCAG 2.1 success criteria 1.1.1 (Non-text Content) and 1.4.5 (Images of Text). We plan to resolve this issue by 30 June 2021. When we publish new content we’ll make sure our use of images meets accessibility standards. 

Links  
  • Some link text does not describe the content’s context, leaving a screen reader user unsure about clicking a link. This fails WCAG 2.1 success criteria 1.3.1 (Info and Relationships) and 2.4.4 (Link Purpose – In Context). We plan to resolve this issue by 30 June 2021. 

  • There are instances of link text fields being empty. This fails WCAG 2.1 success criteria 2.4.4 (Link Purpose – In Context). We plan to resolve this issue by 30 June 2021. 

  • Some links are not easily distinguishable from the surrounding text. This fails WCAG 2.1 success criteria 1.3.3 (Sensory Characteristics), 1.4.1 (Use of Colour) and 1.4.11 (Non-text Contrast). We plan to resolve this issue by 30 June 2021. 

Language 
  • Some pages are missing functionality that identifies the language of the page, or when text changes language within a page, so that a screen reader or other speech synthesizers are unable to use the correct accent and pronunciation. The fails WCAG 2.1 success criteria 3.1.1 (Language of Page) and 3.1.2 (Language of Parts). We plan to resolve this issue by 30 June 2021. 

Colour contrast 
  • There are instances where the colour contrast ratio between foreground and background does not meet the minimum requirements to make things easy to read for people with visual impairments. This fails WCAG success criteria 1.4.3 (Contrast - Minimum) and 1.4.11 (Non-text Contrast). We plan to resolve this issue by 30 June 2021. When we publish new content we’ll make sure our colour contrast ratio meets accessibility standards.

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

PDFs and other documents 

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. We aim to make this available in an accessible format by 31 July 2021. The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. If you require this content in a different format please contact us. When we publish new PDFs or Word documents we’ll make sure they meet accessibility standards. 


Existing video content 

We have pre-existing video on this website. This video contains captions but does not have audio descriptions or a transcript, or uses a third party captioning function that is not always accurate. The accessibility regulations do not require us to fix issues with video content published before 23 September 2020.

If you require this content in a different format please contact us. When we publish new video content we’ll make sure videos meet accessibility standards. 


Third party embedded content 

We are aware that some third party content appearing on our site does not have titles that are accessible to screen readers, for example student accommodation virtual tours. As this functionality is provided by a third party supplier, it is outside of our control. A good way to learn more about the technical accessibility of a third-party platform is to review the accessibility statement for the platform provided by the supplier searchBOX, a centralised, independent directory of third-party accessibility information. 

What we’re doing to improve accessibility 

  • We have formed a Web Accessibility Working Group to define and execute a strategic approach to accessibility across our websites 

  • Content creators and editors are being trained to ensure new content is accessible 

  • We will embed accessibility requirements in our procurement and service provision activity

Preparation of this accessibility statement 

This website was last tested on 21 September 2020. The test was carried out by Shaw Trust, using automated evaluation tools and manual testing by an experienced in-house, pan-disabled testing team. 

This statement was prepared on 17 December 2020. It was last reviewed on 31 March 2021.