Accessibility statement for DataLoch
Website accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This accessibility statement applies to this website, referred to as DataLoch, which is run by DataLoch and is on the domains www.dataloch.org and app.dataloch.org.
We want as many people as possible to be able to use this website. For example, that means that you should be able to:
- change colours, contrast levels and fonts.
- zoom in to up to 200% without text spilling off the screen.
- navigate most of the website using just a keyboard.
- navigate most of the website using speech recognition software.
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA, and VoiceOver).
We have also tried to ensure that the website text is as simple as possible to understand.
Customising the website
AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible.
Further guidance on how to improve accessibility and customise settings for specific internet browsers can be found here:
How accessible this website is
We know some parts of this website are not fully accessible:
- some text may not reflow in a single column when you change the size of the browser window.
- you cannot modify the line height or spacing of text.
- most older PDF documents are not fully accessible to screen reader software.
- some of our online forms are difficult to navigate using just a keyboard.
- some of our online forms are not linked together using aria-landmarks.
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:
- call us on 0131 658 5325
- connect with us here
We’ll consider your request and get back to you as soon as possible.
Reporting accessibility problems with this website
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, contact:
- call us on 0131 658 5325
- connect with us here
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) here.
Contacting us by phone using British Sign Language
contactSCOTLAND-BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates 24 hours a day, 7 days a week.
Technical information about this website’s accessibility
DataLoch is committed to making its 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 and exemptions listed below.
Non-compliance with the accessibility regulations
The following items do not comply with the WCAG 2.1 AA success criteria for the following reasons.
- 1.2.1 - Audio-only and Video-only (Prerecorded) (https://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded) - Not all prerecorded audio-only or video-only media will have alternative media that presents equivalent information e.g. audio track with description of the action in a video with no sound.
- 1.2.5 - Audio Description (https://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded) - Videos do not have an alternative audio description. We believe that the video visual elements are purely visual and are not required for an understanding of the video content.
- 1.3.5 - Identify Input Purpose (https://www.w3.org/TR/WCAG21/#identify-input-purpose) - It might not be possible for all form fields to be programmatically determined. This means that when using auto-fill functionality for forms not all fields will identify the meaning for input data accurately.
- 1.4.11 - Non-text Contrast (https://www.w3.org/TR/WCAG21/#non-text-contrast) - Visual information to identify user interface components, such as keyboard focus, do not always have a sufficient contrast ratio.
- 1.4.13 - Content on Hover or Focus (https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus) - Most tooltips disappear as soon as the cursor moves. Also tooltips are not always present for all icons and images.
- 1.4.3 - Contrast (Minimum) (https://www.w3.org/TR/2008/REC-WCAG20-20081211/#visual-audio-contrast-contrast) - We've worked hard to ensure that text always meets minumum contrast requirements, but there may not be sufficient colour contrast between font and background in certain circumstances (such as on infographics or documents).
- 2.1 - Keyboard Accessible (https://www.w3.org/TR/WCAG21/#keyboard-accessible) - We have worked hard to make all content keyboard accessible, but some content may be either difficult to navigate or not possible to access using a keyboard.
- 2.4.3 - Focus Order (https://www.w3.org/TR/WCAG21/#focus-order) - The cookie acceptance banner is currently at the bottom of the page and a user must tab through the page to access it.
- 2.4.4 - Link Purpose (In Context) (https://www.w3.org/TR/WCAG21/#link-purpose-in-context) - Some external links open in new tabs but do not contain text informing the user of this.
- 3.3.2 - Labels or Instructions - (https://www.w3.org/TR/WCAG21/#labels-or-instructions) - Some form elements are not linked together. This is due to an issue caused by Drupal CMS. We’re looking into solutions, but this may require waiting for an update from Drupal.
- 4.1.2 - Name, Role, Value (https://www.w3.org/TR/WCAG21/#name-role-value) - The projects page search field and the projects page sort by field don't have associated labels. In these cases we have provided aria-labels and clear hint text for screen readers. We do not believe this to be an accessibility issue, but it does mean that the site will fail some automated accessibility tests.
We aim to improve our websites accessibility on a regular and continuous basis. Please see the 'Reporting accessibility problems with this website' section above if you would like to reach out about any of the above issues.
Interactive tools and transactions
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form elements are not grouped together and some controls must be controlled using the arrow keys rather than the tab and enter keys.
Our forms are built to Drupal standards and would require further work to rebuild fully accessible forms that work with the Drupal interface.
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 after future updates from Drupal.
Content that's not within the scope of the accessibility regulations
PDFs and other documents
It's possible that we may upload older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
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. For example, we do not plan to fix archive material such as news articles published before 2018.
What we’re doing to improve accessibility
- We maintain an active relationship with our web developer to ensure that our website accessibility is up to date.
- Future work on the site is being carried out with an accessibility first approach.
- Regular updates to the Drupal CMS and implementation of any updates to accessibility best practice.
Preparation of this accessibility statement
This statement was prepared on 16/05/2022. It was last reviewed on 16/05/2022.
This website was last tested on 04/05/2022. The test was carried out by our web developers, Starbit Ltd.
We use a number of different approaches to testing the accessibility of DataLoch, which includes both manual testing using assistive technology and automated testing. We test all static pages on the site and select a random sample of article and project pages to test each time. Testing is carried out immediately after any work altering the structure of the site has taken place.