This accessibility statement relates to all web content on the Improving our Digital Channels blog website located at https://blog-digitalparliament.scot.
This blog is run by the Scottish Parliament Corporate Body (SPCB). 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.
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 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’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 this website is
We know some parts of this website are not fully accessible:
- Element Description: Lack of accurate alternative text for image description and use of incorrect or no titles for headings. Some elements have not been named. This leads to confusion about the content of the element.
- Use of colour and styling: Lack of contrast between text and background colours and lack of efficient element outlines eg underlining and borders to allow accurate visual focus.
- Language : Some parts of the website contains sentences that are too long; including the use of jargon and acronyms and uses language that is not fully understandable to the general audience.
- Links: Some links do not provide an accessible name for an image which is the only content in the link.
- Keyboard: The position of the navigation is not clear on some elements and some of the website features cannot be used with anything other than a keyboard.
- Navigation: Some main elements appear as a descendant of a section element and the website is unable to bypass blocks of content that are repeated on multiple Web pages.
What to do if you cannot access parts of this website
Get content in other formats
We will do our best to provide you with the content you need in a format that is suitable for you. Please get in touch.
- Email us at email@example.com
- Describe the format you need, for example audio CD, braille, BSL or large print.
- Provide your name and email address.
We’ll aim to reply within 2 working days.
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems that are not listed on this page or think we’re not meeting accessibility requirements, please contact us by doing the following:
- Contact firstname.lastname@example.org.
- Add the web address (URL) of the page the content’s on or choose the whole site.
- Let us know your issue.
- Provide your name and email address if you want a response, or leave this blank if you want to remain anonymous.
If you request a response, we'll aim to reply within 2 working days.
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
SPCB is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. This blog is partially conformant with WCAG 2.1 level AA, due to the non-compliances listed below.
Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
The page titles do not specifically refer to blogs. This fails WCAG 2.1 AA success criterion 2.4.2 (page titles).
We’ll fix this issue as part of the continuous-improvement work we're committed to as part of our new web operating model. We are also currently reviewing our policy for parliamentary blogs and expect to move those that are still required onto a new more accessible platform in 2021.
Content that’s not within the scope of the accessibility regulations
Some articles may have uploaded files in PDF format. Older PDFs documents may not meet accessibility standards. For example, they may not be structured to be accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2.
However, it passed on manual and automated tests, presenting a good level of accessibility with bookmarks, tab support, and reading order.
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 we publish will meet accessibility standards.
How we tested this website
This website was last tested in March 2020. The test was carried out by accessibility Passion4Social CIC (third-party), not involved in the design and development process.
We used this approach to test:
- Automated tests: We used 6 software tools to identify accessibility and navigation issues across the entire website;
- The web pages with most issues were added to the manual testing;
- Using Google Analytics, we selected the pages most accessed by the users since January 2020 and added to manual testing;
- Manual tests: performed by three people with disabilities (blindness, global learning disabilities, and motor disabilities) and one professional web developer that run 3 simulation tools for dyslexia, low or partial vision, colour blindness, trembling movements, and keyboard navigation;
As all pages are based on the same platform and template, they have not been tested individually but some samples have been selected from all of them.
Compatibility with browsers and assistive technology
The Improving our Digital Channels blog is designed to be compatible with the following assistive technologies:
- Internet Explorer (from version 10)
- Microsoft Edge
Accessibility of the Improving our Digital Channels blog relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
These technologies are relied upon for conformance with the accessibility standards used.
This statement was prepared on 15 September 2020.