This website is run by Cardiff and Vales Safeguarding Board. We want as many people as possible to be able to use this website. For example, that means you should be able to:
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:
What to do if you cannot 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:
We’ll consider your request and get back to you in ten working days.
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 us by e-mailing email@example.com
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 can provide a text service for people who are D/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.
Find out how to contact www.cardiffandvalersb.co.uk.
Technical information about this website’s accessibility
Cardiff and Vales Safeguarding Board 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 listed below.
Non accessible content
PDF documents on our website
Many of the PDFs on our website are non-accessible because:
Technical errors on several pages of the website
There are a number of technical errors on our website that make some parts of our content non accessible. We have listed below the non-accessible parts and the following reasons.
Non compliance with the accessibility regulations
Some images and icons do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
PDF documents on our website
PDF documents are non-accessible to screen readers. This fails WCAG 2.1 success criterion criterion 1.3.1 (Info and Relationships)
The majority of the PDFs referenced in the content have been developed by external agencies there are not possible to make accessible.
For all new PDF documents added to the app, we plan to develop HTML templates for new documents so as we publish new content we’ll make sure our documents meet accessibility standards by March 2020.
Local link destination does not exist 1.3.1 – this error is caused by tooltips, they are links which by design do not link anywhere but instead trigger a popup glossary definition in the content. The tooltip content is included within the link element as a screen reader accessible label and should be accessible to impaired users.
Technical issues on our website
There are a number of technical errors on our website that make some parts of our content non accessible. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships)
We plan to fix all technical issues listed by September 2020.
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
Some PDFs and other documents
Many of our 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).
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 do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. Nor does it require us to fix PDF documents published by external agencies.
Any new PDFs or Word documents we publish will meet accessibility standards.
We tested: www.safeguarding.wales
This statement was prepared on 27 January 2020.