This site is in development. Help us improve it using our feedback form.

National Library of Scotland

This accessibility statement applies to the National Library of Scotland (NLS) website.

This website at www.nls.uk and auth.nls.uk, is run by the National Library of Scotland. 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 using a browser or device settings

  • zoom in up to 400% without the text spilling off the screen

  • navigate most of the website using a keyboard or 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 to understand as we can.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know that some parts of this website, and some of the forms and services it links to, are not fully accessible:

  • Some icons are not coded correctly, which means that screen readers may misidentify them or overlook them altogether.

  • Some links and controls do not have unique, accessible names describing their purpose. In some places, multiple links on a single page use the same name and may have different purposes, and some link names do not convey where they lead. Some labels may not be available to assistive technologies.

  • Some of the content is not organised in a way that communicates its information structure. Some groups of items with a list-type relationship are not defined and presented as lists, some parts of the site have multiple top-level headings, some parts skip heading levels, and some elements have the visual appearance of headings but are not coded as such.

  • Some pages support resizing only up to 200%.

  • The focus order does not always make sense, focus states are not always indicated consistently, some pages do not provide a way to skip repetitive content, and some functions cannot be operated by keyboard.

  • Some pages contain duplicate links.

  • Some interactive elements are not used for their intended purposes, and some are too small for adequate access via pointing device.

  • Autocomplete is missing or invalid in some form fields in which users would normally expect it, and some form fields remove previously entered data when focus returns to them.

  • Some error messages fail to describe the problem or give adequate guidance for correcting it. Some interactions fail without producing an error message at all. Some forms load with error messages showing even when the user has not entered any data.

  • Some components may not behave as expected with assistive technology.

More information on the accessibility issues appears in the section on non-accessible content.

Feedback and contact information

If you:

  • find any problems

  • think we're not meeting accessibility requirements

  • need information on this website in a different format, such as accessible PDF, large print, easy read, audio recording or Braille

contact the Digital Engagement Team via our Contact us page. We'll consider your request and get back to you within five 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).

Technical information about this website's accessibility

The National Library of Scotland is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website and auth.nls.uk have been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard. This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

Non-compliance with the accessibility regulations

This section lists the ways in which this website fails to meet the WCAG 2.2 success criteria. It includes all violations of levels A and AA success criteria and all issues that the independent audit found to be more than minor. It includes minor issues only if they relate to a Level A or AA criterion. The issues appear in sequential order of the applicable success criteria.

Some icons on the 'join' form are incorrectly coded, which may cause screen readers to identify them incorrectly or overlook them altogether. This fails the following WCAG 2.2 success criterion: 1.1.1 (Non-text content, Level A). We will ensure that all icons are correctly coded by 13/07/2026.

Some buttons and other interactive elements do not have labels on the 'contact us', donation, and 'join' forms. Some labels are not associated with form elements, some labels are empty, some labels are duplicated on a page, and some legends are empty or missing. This fails the following WCAG 2.2 success criteria: 1.1.1 (Non-text Content, Level A); 1.3.1 (info and Relationships, Level A); 2.4.4 (Link Purpose (In Context), Level A); 2.4.6 (Headings and Labels, Level AA); 3.3.2 (Label or Instructions, Level A). We plan to ensure that all interactive elements have labels by 13/07/2026.

Some groups of links in the footer on the auth.nls.uk domain, are not identified as lists. This fails the following WCAG 2.2 success criterion: 1.3.1 (Info and Relationships, Level A). We plan to ensure that all groups of items are accurately identified as groups by 13/07/2026.

Some headings on the 'contact us', donation, and 'join' forms are empty or are duplicated, and some pages skip heading levels. This fails the following WCAG 2.2 success criteria: 1.3.1 (info and Relationships, Level A); 2.4.1 (Bypass Blocks, Level A); 2.4.6 (Headings and Labels, Level AA). We plan to ensure that all headings contain unique, meaningful content by 13/07/2026.

On 'join' and donation forms, some text elements have the appearance of headings but are not coded as headings. This fails the following WCAG 2.2 success criteria: 1.3.1 (info and Relationships, Level A); 2.4.6 (Headings and Labels, Level AA). We plan to ensure that all elements that look like headings are coded as headings by 13/07/2026.

Autocomplete is missing or invalid in some fields on the contact, donation, and join forms, where users would normally expect it. This fails the following WCAG 2.2 success criterion: 1.3.5 (Identify Input Purpose, Level AA). We plan to ensure that all elements for which autocomplete would be expected will have autocomplete by 13/07/2026.

In some places on the 'join' form, resizing the text beyond 200% disrupts functionality. This fails the following WCAG 2.2 success criterion: 1.4.4 (Resize Text, Level AA). We plan to ensure that, by 13/07/2026, resizing text up to 200% will cause no loss of functionality.

Some forms including 'join', 'contact us', and donation, cannot be operated via keyboard, and some within-page links are broken. This fails the following WCAG 2.2 success criteria: 2.1.1 (Keyboard, Level A); 2.4.1 (Bypass Blocks, Level A); 3.2.2 (On Input, Level A). We plan to ensure that all content and functionality can be accessed and operated by keyboard by 13/07/2026.

Forms including 'join', 'contact us', and donation, do not provide a way to skip repetitive content. This fails the following WCAG 2.2 success criterion: 2.4.1 (Bypass Blocks, Level A). We plan to ensure that all pages provide for skipping repetitive content by 13/07/2026.

The focus order on online donation forms, does not always make sense, and focus states are not always indicated consistently. This fails the following WCAG 2.2 success criteria: 2.4.3 (Focus Order, Level A); 3.2.4 (Consistent Identification, Level AA). We plan to ensure that the focus order will be logical by 13/07/2026.

Some interactive elements on online donation forms, do not indicate when they have focus. This fails the following WCAG 2.2 success criteria: 2.4.7 (Focus Visible, Level AA). We plan to ensure that all elements clearly indicate when they have focus by 13/07/2026.

Some interactive elements on online donation forms, are too small for easy access via pointing device. This fails the following WCAG 2.2 success criteria: 2.5.8 (Target Size, Level AA). We plan to ensure that all interactive elements have adequate size by 13/07/2026.

Some form fields on online donation forms, removes previously entered data when focus returns to them. This fails the following WCAG 2.2 success criterion: 3.2.1 (On Focus, Level A). We plan to ensure that, by 13/07/2026, all data entered into form fields remains there when focus returns to the field.

Some changes to a component's settings on online donation forms, cause an unexpected change of context. This fails the following WCAG 2.2 success criteria: 3.2.2 (On Input, Level A). We plan to ensure that all changes to component settings maintain the existing context.

On the 'contact us', donation, and ''join' forms, some error messages fail to describe the problem or give adequate guidance for correcting it. Some interactions fail without producing an error message at all, and some forms load with error messages showing even when the user has not entered any data. This fails the following WCAG 2.2 success criteria: 3.3.1 (Error Identification, Level A); 3.3.2 (Label or Instructions, Level A). We plan to update all error messages by 13/07/2026, so that they clearly indicate and describe the error, provide guidance for correcting it, and remain visible until the error has been corrected.

Some non-interactive elements on the donation and 'join' forms appear within the tab order. This fails the following WCAG 2.2 success criterion: 4.1.2 (Name, Role, Value, Level A). We plan to ensure that only interactive elements appear in the tab order by 13/07/2026.

Some components on the donation and 'join' forms may not behave as expected with assistive technology. This fails the following WCAG 2.2 success criterion: 4.1.2 (Name, Role, Value, Level A). We plan to ensure that all components behave as expected by 13/07/2026.

Some components in the donation and 'join' forms have labels that may not be available to assistive technologies. This fails the following WCAG 2.2 success criterion: 4.1.2 (Name, Role, Value, Level A). We plan to ensure that all component labels are available to assistive technologies by 13/07/2026.

Additional accessibility issues found through inclusive usability testing

Inclusive usability testing (IUT) conducted on this website found a small number of additional accessibility issues that the WCAG success criteria do not explicitly cover. Although these are not necessarily WCAG compliance issues, we list them here because we found them to present accessibility problems for some participants in our testing.

Search can return an overwhelming number of results.

Some terminology can be confusing — for example, the differences between archives, manuscripts, and special collections, and the meaning of "education affiliation". This is especially relevant for people with cognitive impairments or certain kinds of neurodivergence.

Links or buttons that go to the same place (e.g., multiple instances of "Join") can be confusing, especially when they appear on the same page.

Some form fields on auth.nls.uk (title, in particular) offer a large number of choices. Additionally, the options may not appear in a logical order that helps people find the one they want. This is especially relevant for people using screen readers and/or keyboard navigation.

Large header images on many of the pages can make it difficult for some people to find relevant content. This is especially relevant for people who have visual or motor impairments.

The pages change backgrounds between dark/black and light/white. This requires some people using certain assistive technologies to change their settings as they go between these pages.

Some pages display text on top of images. This makes that text harder to read.

Some areas of the site use nonspecific language. For example, the filter options under "where" for events within "What's on" do not offer an address or even a city, to help people identify where the events are. Although This can make it harder for anyone, it could be even more relevant for people with cognitive impairments or certain kinds of neurodivergence.

What we're doing to improve accessibility

This website underwent a full third-party accessibility audit on 1 July 2025. This accessibility statement has been prepared to reflect the results of those assessments. We are working to correct the issues found.

We are continually working to improve the accessibility of this website. We conduct regular accessibility audits and inclusive usability testing, and we act on their findings. We learn from these audits and other accessibility information, and we continually apply new knowledge to all updates we make.

Preparation of this accessibility statement

This statement was prepared on 14/07/2025. It will next be reviewed on 13/07/2026.

This website was last tested via audit on 01/07/2025 against the WCAG 2.2 AA standard, and via inclusive usability testing (IUT) between 26/06/2025 and 08/07/2025. The audit and testing were carried out by Nexer Digital Ltd.

Accessibility audit

We chose the pages to audit on the basis of four user journeys:

1. Visit and find out what's on

2. Support us (donate)

3. Join the library

4. Search

The audit assessed the following pages and functions:

The audit used the Web Content Accessibility Guidelines V2.2, levels A and AA, to determine how well the selected pages meet accessibility requirements.

Inclusive usability testing

The July 2025 testing also included inclusive usability testing, a practical, observed process that involves people with disabilities and with specific technology access needs.

The testing uncovered some accessibility issues that do not map directly to the WCAG 2.2 criteria but affect the ability of people with disabilities and/or special access needs to use the site. We have listed those issues in this statement in addition to the audit findings.