Accessibility

We are committed to making our services accessible to everyone who could benefit from them, irrespective of any disability they may have.

Our standards

This website is delivered in partnership by Scottish Enterprise (SE), Highlands and Islands Enterprise (HIE), Skills Development Scotland (SDS) and Business Gateway (BG).

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
  • zoom in up to 300% without the text spilling off the screen
  • navigate the website using just a keyboard
  • navigate the website using speech recognition software
  • listen to 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 is this website?

We know some parts of this website aren’t fully accessible, we are working to resolve these issues. A list of know issues can be found under the ‘non-accessible content’ section of this page.

What to do if you can’t access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

  • Email enquiries@scotent.co.uk
  • Call 0300 013 3385 - calls charged at local rates
  • Call 0141 846 0200 - from mobile phones or if outside Scotland
  • Minicom 0800 023 2071 - if you are deaf or hard of hearing (BT helpline 0800 731 1888)
  • Use our online contact form

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.

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

Reporting a problem

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements, contact: enquiries@scotent.co.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).

Technical information about this website’s accessibility

Scottish Enterprise (SE), Highlands and Islands Enterprise (HIE), Skills Development Scotland (SDS) and Business Gateway (BG) are committed to making the PrepareforBrexit.scot website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

Actions listed below will be taken to make non-accessible content accessible by March 2020.

Web developer actions

All pages

The website is using static font sizes, meaning a user cannot increase the size of fonts on the page, via browser settings.

  • We will switch all fonts from px, to em, allowing them to scale
    Success story panels, call to action link text, is often repeated and provides no useful information to assistive techs.
  • We will pull in the title of the success story block, after the link text, using accessible hidden text, so tech like screen readers and braille devices can get a better understanding of the purpose of these links

The partner logos in the footer are all missing alt text.

  • Add the partner name as alt text for each partner logo 

Add an aria landmark role to the footer, for backwards compatibility.

  • The role of contentinfo will be added to the footer tag to support older versions of assistive technologies that don’t automatically infer this from the HTML5 footer tag itself

There is no option to skip repeated content across pages, such as the main header navigation links.

  • We will add a skip to main content and skip to accessibility statement option to the site.

Resources page

The telephone number link destination, includes text within it, causing it to fail when attempting to dial it.

  • We will fix the links target to include the telephone number only whilst allowing the text on screen to remain the same

Events page

Images used on event blocks are for decorative purposes only but have varying and often confusing alt text defined.

  • We will hide these decorative images from the view of assistive technologies that parse the accessibility tree (e.g. screen readers, braille devices)

The event block link text is often repeated and provides no useful information to assistive techs.

  • We will pull in the title of the event block, after the link text, using accessible hidden text, so tech like screen readers and braille devices can get a better understanding of the purpose of these links

The heading structure of the events page does not correctly feedback its importance.

  • We will switch the main page header from a h2 to a h1. This issue also appears on the Resources page
  • Event block headers are h2 currently and should be reduced to a h3
  • The webinar section title is currently a h3 and will be increased to a h2

Events page and Resources page

The jump to top link has some accessibility issues associated with it.

  • We will fix the aria label, which currently says “jump-to-top”, we will remove the dashes from this
  • We will remove the title attribute which causes issues for some assistive techs
  • We will set focus to the top of the page, after the use activates the jump to top link

Self-assessment pages

We use using colour only to convey positive messages. The negative and positive messages are also impacting what’s being sent to assistive techs.

  • Accessible visually hidden text will pre-fix negative and positive messages to portray they’re meaning
  • An SVG icon will display left of the messages highlighting if it’s a positive or negative message
  • We will add an ARIA live region with a polite update to the messages, to stop them blocking form information from being sent to users

The results page has a few links which open in a new tab window, but don’t give an indication to assistive techs that they do so.

  • We will append visually hidden but accessible text to these links, highlighting that they open in a new window
  • We will place a visual indicator next to the links, which will highlight they open in a new window. This indicator will be consistent for external links throughout the site.

The PDF documents which can be downloaded at the end of a self-assessment are not tagged in an accessible manner.

  • We will tag areas of the document to make them accessible
  • We set the document language type, which is currently blank

Contact page

The contact us page does not include a header 1.

  • The main page header will be increased from a header 2 to a header 1 

Content editor actions

Readability

We will focus on the pages that return an ARI score of 11 and higher (15 years+) as best practice guidance.

  • To keep content short and to the point
  • Provide users with bulleted lists, number lists or summary sections for easier scanning
  • Use meaningful subheadings
  • Avoid exaggerations and corporate marketing
  • Avoid polysyllabic words
  • Avoid tables
  • Alt text for non-decorative images
  • Captions & transcripts for any video content

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Our forms are built and hosted through third party software and ‘skinned’ to look like our website. This doesn’t meet WCAG 2.1 success criterion 1.3.1 (information and relationships).

We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in [rough timing].

PDFs and other documents

Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).

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. By September 2020, we plan to either fix these or replace them with accessible HTML pages.

The accessibility regulations don’t 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. 

How we tested this website

This website was last tested between the 19-23 August. The test was carried out by SE Digital QA Team.

We tested our main website platform, available at https://www.prepareforbrexit.scot/

This statement was last updated on 25 September 2019.