This website is run by West Dunbartonshire Council. We want as many people as possible to be able to use this website.
We’ve have 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.
We know some parts of this website are not fully accessible:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact the relevant team (via the Contact details on that page). If there are no contact details then please contact the web team,
We’ll consider your request and get back to you.
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
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).
Sign Language users can use the service provided by contactSCOTLAND-BSL, the online British Sign Language interpreting service, to contact the Council. Further information is available from contactSCOTLAND.
West Dunbartonshire Council 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.
The content listed below is non-accessible for the following reasons.
Some images 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.
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 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.
Some standalone maps were created have been created that fail WCAG 2.1
We will be updating these maps to a new system by September 2020
The colour of the text and the colour of the background are not in sufficient contrast to each other that fail WCAG 1.4.3 Contrast (Minimum)
We plan to fix these by September 2020
With keyboard navigation it is important that the focused component can be visually identified. If the focused component is not somehow highlighted, the user cannot be sure which component has focus. that fail WCAG 2.4.7 Focus Visible
We plan to fix these by September 2020
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.
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live).
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
This website was last tested on 17 February 2020. We performed automated and manual accessibility tests. We use Siteimprove, an automated testing system, to help us monitor and fix accessibility issues as they occur on west-dunbarton.gov.uk
We performed our own manual tests on the website
We have a range of third party websites and forms. They provide some of our online services and most of them are skinned to look like our main website. We excluded them from this testing, but we are engaging with teams to assess what is required to make them accessible: