Turas Medical ACT accessibility statement

Add to favourites

This accessibility statement applies to the Medical ACT application.

This application is run by Public Services Delivery Scotland. 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:

• modal dialogs (including sign out modals) are not announced to screen reader users

• hidden form fields are not announced to screen reader users when revealed

• required form fields are not consistently announced to screen reader users

 • form fields are not always programmatically associated with visible labels

 • dynamic content updates (such as table updates triggered by dropdowns) are not communicated to screen readers

 • guidance text is not programmatically linked to form fields

• excessive use of guidance accordions reduces clarity and navigation for screen reader users

 • keyboard focus is missing or unclear on file upload components

• file upload status changes (uploading, complete, failed) are not reliably announced to screen reader users

 • form field error messages are not announced to screen reader users

• navigation menus do not close when the ESC key is pressed

• list elements contain invalid direct children, breaking semantic structure

 • landmarks are not uniquely labelled, making them difficult to distinguish

Feedback and contact information

We’re always looking to improve the accessibility of this application.

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact us on the following email address  nes.accessibility@nhs.scot  with details of the problem that you have encountered.

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

Public Services Delivery Scotland is committed to making its application 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 the WCAG (Web Content Accessibility Guidelines) version 2.2 AA standard, due to the following non-compliances (and/or) the following exemptions.

Non accessible content

The content is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

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

Modal dialogs (including sign out modals) are not announced to screen reader users, which fails WCAG Success Criterion 4.1.3 – Status Messages.

Hidden form fields are not announced to screen reader users when revealed, failing WCAG Success Criterion 4.1.3 – Status Messages.

Required form fields are not consistently announced to screen reader users, which fails WCAG Success Criterion 3.3.2 – Labels or Instructions.

Form fields are not always programmatically associated with visible labels, failing WCAG Success Criterion 1.3.1 – Info and Relationships.

Dynamic content updates (such as table updates triggered by dropdowns) are not communicated to screen readers, which fails WCAG Success Criterion 4.1.3 – Status Messages.

Guidance text is not programmatically linked to form fields, failing WCAG Success Criterion 1.3.1 – Info and Relationships.

Excessive use of guidance accordions reduces clarity and navigation for screen reader users, which fails WCAG Success Criterion 2.4.6 – Headings and Labels.

Keyboard focus is missing or unclear on file upload components, failing WCAG Success Criterion 2.4.7 – Focus Visible.

File upload status changes (uploading, complete, failed) are not reliably announced to screen reader users, which fails WCAG Success Criterion 4.1.3 – Status Messages.

Form field error messages are not announced to screen reader users, failing WCAG Success Criterion 3.3.1 – Error Identification.

Navigation menus do not close when the ESC key is pressed, which fails WCAG Success Criterion 2.1.1 – Keyboard.

List elements contain invalid direct children, breaking semantic structure and failing WCAG Success Criterion 1.3.1 – Info and Relationships.

Landmarks are not uniquely labelled, making them difficult to distinguish, which fails WCAG Success Criterion 1.3.1 – Info and Relationships.

 

 

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.

What we are doing to improve accessibility

We are committed to making this application accessible, in line with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. We have carried out an accessibility audit to identify areas where the service does not yet meet WCAG 2.2 standards.

We are reviewing these findings and will address issues as part of planned updates and ongoing improvements to the service.

Preparation of this accessibility statement

This statement was prepared on 10th February 2026. It was last reviewed on 16th March 2026.

This application was last tested on 10th February 2026 against the WCAG 2.2 AA standard.

The audit was carried out by a member of our application team.

All the pages in the application were tested using the following:

·         AXE automated testing tool

·         Chrome, Firefox and Edge browsers

·         JAWS and NVDA screen readers

·         keyboard navigation