Turas Learn accessibility statement

Add to favourites

This accessibility statement applies to the application https://learn.nes.nhs.scot/.

This application is run by NHS Education for Scotland (NES). 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 fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the application using just a keyboard
  • navigate most of the application using speech recognition software
  • listen to most of the application using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the application 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 application is

Parts of this application are not fully accessible. For example:

  • some of our older PDFs are not screen reader compatible due to lack of Alt tags on images and missing document titles
  • there are some missing styles for focus elements such as data tables and dropdown menus which make it visually difficult to see what your keyboard is focused on when tabbing through table details with action buttons
  • there are some colour contrast issues on links in the footer which might make them difficult to read for people with visual impairments
  • the date pickers are not accessible when using keyboard entry which means users cannot select a date using just the keyboard date picker
  • users have issues with the tabbed navigation using screen readers and keyboard entry
  • users with screen readers cannot access nested data tables
  • the main navigation bar and main content section on the homepage have duplicate IDs
  • some form elements are missing labels which can make it difficult for screen reader users to understand their purpose
  • some users using keyboard navigation will have issues accessing older learning modules
  • the admin area colour palette and some interface elements have low contrast
  • some videos may not have captions
  • some content is developed by third parties and may not be fully accessible

Feedback and contact information


If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact us at: support.web@nes.scot.nhs.uk

Any personal data provided as part of the request will be stored in line with our privacy notice.

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 application’s accessibility


NHS Education for Scotland is committed to making its applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status


The application has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

This application is partially compliant with WCAG 2.2 AA, due to the non-compliances listed below.

Non-accessible content
The content is non-accessible for the following reason(s):

  • Some of our PDFs may not have appropriate titles and are missing ALT tags for images. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content) and 2.4.2 (Page Titled) (Level A).
  • Some focus styles are missing from interactive elements such as data tables and dropdown menus, making it visually difficult to see which element is focused when using the keyboard. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible) and 1.4.11 (Non-text Contrast) (Level AA).
  • Some links in the footer have insufficient colour contrast, making them difficult to read for users with visual impairments. This fails WCAG 2.2 success criterion 1.4.3 (Contrast Minimum) (Level AA).
  • The date picker component cannot be operated using a keyboard, preventing users from selecting a date without a mouse. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 2.1.2 (No Keyboard Trap) (Level A).
  • Screen reader and keyboard users have difficulty using the tabbed navigation, as some tabs do not announce their state or allow proper focus movement. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value), 2.1.1 (Keyboard), and 2.4.3 (Focus Order) (Level A).
  • Screen reader users cannot access or interpret nested data tables correctly. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value) (Level A).
  • Duplicate IDs within the main navigation bar and main content on the homepage make it difficult for assistive technologies to differentiate between elements. This fails WCAG 2.2 success criterion 4.1.1 (Parsing) (Level A).
  • Some form elements are missing labels, making it difficult for screen reader users to identify their purpose. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels) (Level AA).
  • Some older learning modules cannot be accessed using only the keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard) and 2.1.2 (No Keyboard Trap) (Level A).
  • Some colour contrast issues are present in the admin area, including buttons and information panels. This fails WCAG 2.2 success criterion 1.4.3 (Contrast Minimum) and 1.4.11 (Non-text Contrast) (Level AA).
  • Some videos may not have captions. This fails WCAG 2.2 success criterion 1.2.2 (Captions – Prerecorded) (Level A).
  • Some content provided by third parties or external organisations may not meet accessibility standards.

Content that’s not within the scope of the accessibility regulations
PDFs and other documents


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.
Any new PDFs or Word documents we publish will meet accessibility standards.

Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Third-party content
Some of our content is developed by third parties or hosted on external platforms (for example, SCORM modules and social media). While we expect these to meet a reasonable level of accessibility, we cannot guarantee full compliance.

What we are doing to improve accessibility


Turas applications are currently undergoing a redesign using a new design system to align with WCAG 2.2 AA compliance.
Turas Learn is scheduled to migrate to this new design system soon, which will address many of the accessibility issues identified above.

How we tested this application


This application was last tested in October 2024 against the WCAG 2.2 AA standard.

Testing was carried out by a member of our application team using a combination of:

  • Axe Accessibility Tool
  • Lighthouse Accessibility Audit
  • Keyboard navigation tests
  • JAWS screen reader

We focused testing on the most visited pages, including:

  • Homepage
  • Course catalogue and search pages
  • Module launch and completion flows
  • Pages with forms and data tables
  • Video and PDF content