Accessibility statement

This accessibility statement applies to the Scottish Borders Council's website at www.scotborders.gov.uk and includes all prefixes to this page.

Throughout our site we link to other external websites and third-party applications. These are not covered by this statement.

This website is run by Scottish Borders Council. 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 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 as possible to understand.

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

You can see how our website is performing against other local authority websites using the Silktide Index.

How accessible is this website?

We know some parts of this website are not fully accessible:

  • Older PDF documents are not fully accessible to screen reader software.
  • Some templates and forms may present additional navigational challenges to visitors using screen reader software and/or keyboards.
  • This site uses Microsoft Power BI dashboards to visualise data and move through different areas of interest. Visitors using screen reader software or a keyboard will not be able to interact with them in the same way.
  • Some features, including mapping, where there is the ability to zoom in to data or other areas of interest do not have an equivalent for keyboard only or screen reader users.
  • Some components on the website need clearer labels to work with assistive technologies and convey the page structure correctly.

We are committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.  

Compliance status

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.

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

  • Alt text: Some images do not have an appropriate text alternative, so people using a screen reader cannot access the correct information. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content)
  • Incorrect heading structure: Multiple pages contain illogical heading structures, such as multiple H1 headings or skipped heading levels. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships); 2.4.6 (Headings and labels)
  • Incorrect table coding: Some data tables lack proper markup, making them inaccessible to screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships)
  • Empty headings: Some pages contain empty headings, causing confusion for screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships); 2.4.6 (Headings and labels)
  • Magnification:  There’s a limit to how far you can magnify maps that we use within our site. This fails WCAG 2.2 success criterion 1.4.4 (resize text)
  • Online forms: Some of our online forms are difficult to navigate using just a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard)
  • Empty buttons: Certain buttons lack descriptive text, making it difficult for screen reader users to understand their function. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content); 1.3.1 (Info and relationships); 1.3.5 (Identify input purpose); 3.3.2 (Labels or instructions); 4.1.2 (Name, role, value)
  • Ambiguous button labelling: Some buttons have non-descriptive labels, hindering navigation. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content); 1.3.1 (Info and relationships); 1.3.5 (Identify input purpose); 3.3.2 (Labels or instructions); 4.1.2 (Name, role, value)
  • Unlabelled form fields: Several form fields are missing labels, making it challenging for users to input information correctly. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content); 1.3.1 (Info and Relationships); 1.3.5 (Identify input purpose; 2.5.3 (Label in name); 3.3.2 (Labels or instructions); 4.1.2 (Name, role, value)
  • Non-descriptive link text: Links with vague text do not provide sufficient context for users. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships); 2.4.4 (Link purpose – in context)
  • Untitled or incorrectly title frames: Frames without titles make it difficult for screen reader users to understand their purpose. This fails WCAG 2.2 success criterion 1.3.1 (Info and relationships); 2.4.1 (Bypass blocks)
  • Mouse dependant areas: Some areas are only accessible via mouse, excluding keyboard-only users. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard); 1.4.13 (Content on hover or focus)
  • Illogical tab order: The tab order on some pages is unpredictable, causing confusion for keyboard-only users. This fails WCAG 2.2 success criterion 2.4.3 (Focus order)
  • Element markup: Non-standard markup is used for elements, making them inaccessible to assistive technologies. This fails WCAG 2.2 success criterion  3.2.3 Consistent navigation; 3.2.4 Consistent identification; 4.1.2 (Name, role, value)
  • Button and link markup/styling: Incorrect use of elements and inconsistent styling hinder accessibility. This fails WCAG 2.2 success criterion 1.4.11 (Non-text contrast); 3.2.4 (Consistent identification); 4.1.2 (Name, role, value)
  • Conveying information using colour alone: Some graphs and charts within PowerBI dashboards rely solely on colour to convey information. This fails WCAG 2.2 success criterion 1.4.1 (Use of colour); 1.3.3 (Sensory characteristics)
  • Video and audio missing text alternatives: Some videos lack transcripts and accurate captions. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content); 1.2.1 (Audio-only and video only [prerecorded]); 1.2.2 (Captions [prerecorded]); 1.2.3 (Audio description of media alternative [prerecorded])
  • Video missing audio description: Videos do not have audio descriptions for visually impaired users. This fails WCAG 2.2 success criterion 1.2.3 (Audio description or media alternative [prerecorded]); 1.2.5 (Audio description [prerecorded])
  • Users unaware of content change: Dynamic content changes are not announced to screen reader users. This fails WCAG 2.2 success criterion 3.2.1 (On focus); 3.2.2 (On input); 4.1.3 (Status messages)
  • Inaccessible non-HTML documents: Most PDF documents are not fully accessible to screen reader software. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content); 1.3.1 (Info and relationships); 1.3.2 (Meaningful sequence); 2.4.2 (Page titled); 3.1.1 (Language of page)
  • Insufficient colour contrast: Text and background colour combinations do not meet minimum contrast requirements. This fails WCAG 2.2 success criterion 1.4.3 (Contrast minimum); 1.4.11 (Non-text contrast)
  • Colours preference overwrite: User colour preferences are overwritten by the website's specified colours. This fails WCAG 2.2 success criterion 1.4.1 (Use of colour); 1.4.3 (Contrast [minimum])
  • Obscured text: Text resizing causes content to be obscured. This fails WCAG 2.2 success criterion 1.4.4 (Resize text)

What we’re doing to improve accessibility

We are working to fix the issues identified wherever possible and are committed to ensuring our website is accessible to all users. We are also working with third-party suppliers to improve the accessibility of elements of our site which are externally managed.

We aim to achieve full compliance with WCAG 2.2 AA standards. Our actions include:

  • Correcting heading structures and ensuring logical order.
  • Providing descriptive text for all buttons and form fields.
  • Ensuring all links have descriptive text and context.
  • Adding titles to all frames and proper markup to data tables.
  • Improving accessibility for keyboard-only users.
  • Ensuring dynamic content changes are announced to screen reader users.
  • Making all new non-HTML documents accessible or providing accessible alternatives and remediating existing documents which are essential to providing our services
  • Improving colour contrast and respecting user colour preferences.
  • Providing text and audio alternatives for all video content.

We plan to complete these improvements by 31 March 2026.

Disproportionate burden

We have not identified any content that meets the criteria for disproportionate burden.

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

PDFs and other documents published before 23 September 2018 are not within the scope of the accessibility regulations. However, we aim to ensure that any new PDFs or Word documents we publish meet accessibility standards and are actively working to improve the accessibility of documents across the platform.

Non-accessible content

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

  • We use Power BI and maps to visualise data. We do however describe trends in associated research reports or consider alternative format requests.

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: accessibility@scotborders.gov.uk
  • Call: 0300 100 1800
  • Address: Scottish Borders Council, Newtown St Boswells, Melrose, TD6 0SA

We’ll consider your request and get back to you in 10 working days.

Reporting accessibility problems with this website to us

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

Someone from our Communications and Marketing or Digital Innovation and Systems teams will look into the issue and respond promptly.

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

We provide a text relay service for people who are deaf, hearing impaired or have a speech impediment. Our offices have audio induction loops, or if you contact us before your visit, we can arrange a British Sign Language (BSL) interpreter.

Technical information about this website’s accessibility

Scottish Borders Council is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.  As of autumn 2024, local authorities in the UK are required to meet the WCAG 2.2 AA standard. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 have been updated to reflect this new requirement.  This update ensures that websites and mobile applications are perceivable, operable, understandable, and robust for all users, including those with disabilities.

How we tested this website

This website was last tested on 7 January 2025. The test was carried out by Shaw Trust Accessibility Services. We used a combination of automated evaluation tools and manual user testing with assistive technologies to conduct a comprehensive accessibility audit.

Preparation of this accessibility statement

This statement was prepared on 29 May 2025. It will be reviewed regularly, and at least before 29 May 2026.

The website was last tested in January 2025. The test was carried out by Shaw Trust at the request of Scottish Borders Council.

We used website analytics to evaluate pages on metrics such as most visited, repeat visitors and bounce rate and tested these pages along with those that provided an opportunity to test special characteristics, such as images, video, data dashboards and map content. This approach was designed to provide a representative sample of pages to provide a comprehensive overview of improvements.

You can download the full accessibility test report from our website.