Search the site
Search the site
We are committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability.
We are actively working to increase the accessibility and usability of our website.
We aim to make sure our website is:
Clear - presented to our users in a clear and concise format
Adaptable – content can be presented in different ways without losing the key information or structure.
Readable – content is readable and understandable (e.g. using simple plain English and Welsh*)
*Please note that the Welsh translation if provided by a Google Translate plugin.
The site displays correctly in current browsers and using standards compliant HTML/CSS code means any future browsers will also display it correctly.
To increase or decrease the size of the text displayed on this website - hold the Ctrl key and the "+" or "-" (or scroll mouse wheel) to adjust the size.
Whilst we try to adhere to the accepted guidelines and standards for accessibility and usability, it is not always possible to do so in all areas of the website
We are continually seeking solutions that will bring all areas of the site up to the same level of web accessibility overall. In the meantime if you experience any difficulties accessing our website please don’t hesitate to contact us: email@example.com
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 please email us with your:
We’ll consider your request and get back to you within 7 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: firstname.lastname@example.org
Content that’s not within the scope of the accessibility regulations
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.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs and Word documents. By September 2020, we plan to 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.
Any new PDFs or Word documents we publish will meet accessibility standards.