Accessibility

Gwynedd Council Accessibility Statement

This accessibility statement applies to Gwynedd Council’s website, www.gwynedd.llyw.cymru and to Gwynedd Council’s self service portal: https://diogel.gwynedd.llyw.cymru/

The website is run by Gwynedd Council and 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
  • listen to most of the website using a screen reader (for example NVDA).

 

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:

We’ll consider your request and get back to you in 5 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 gwefan@gwynedd.llyw.cymru

 

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS) (external link)..


Contacting us by phone or visiting us in person

There are a number of different ways you can contact us: www.gwynedd.llyw.cymru/contactus

Audio induction loops are available at all Siop Gwynedd receptions



Technical information about this website’s accessibility

Gwynedd 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 (external link) AA standard, due to the non-compliances listed below.

  1. The colour contrast is insufficient in some areas of the site. This fails WCAG 2.1 AA success criteria 1.4.3 (Contrast). This is considered a high priority on our accessibility roadmap to improve accessibility across this website.
  2. Some input fields do not have a visible label indicating the purpose of the input field. This fails WCAG 2.1 A success criteria 3.3.2 (Labels or Instructions). This is considered a high priority on our accessibility roadmap to improve accessibility across this website.
  3. Some input fields have no description. This fails WCAG 2.1 A success criteria 3.3.2 (Labels or Instructions). This is considered a priority on our accessibility roadmap to improve accessibility across this website.
  4. Heading is missing text on some pages. This fails WCAG 2.1 A success criteria 1.3.1 (Info and Relationships). We will correct these issues over time as we review each page.
  5. The same link text is used for links going to different destinations. This fails WCAG 2.1 A success criteria 2.4.4 (Link Purpose). This is considered a priority on our accessibility roadmap to improve accessibility across this website.
  6. Some links identified only by colour. This fails WCAG 2.1 A success criteria 1.4.1 (Use of Colour). This is considered a priority on our accessibility roadmap to improve accessibility across this website.
  7. HTML is used to format some content such as tabular data. This fails WCAG 2.1 A success criteria 1.3.1 (Info and Relationships). This is considered a priority on our accessibility roadmap to improve accessibility across this website.
  8. Local link destination does not exist on some pages. This fails WCAG 2.1 A success criteria 1.3.1 (Info and Relationships). We will correct these issues over time as we review each page.
  9. Some element IDs are not unique. This fails WCAG 2.1 A success criteria 4.1.1 (Parsing). This is considered a priority on our accessibility roadmap to improve accessibility across this website.
  10. The iFrame is missing a title. This fails WCAG 2.1 A success criteria 4.1.2 (Name, Role, Value). This is considered a priority on our accessibility roadmap to improve accessibility across this website.


Disproportionate burden

Some older content uses the 'bold' to highlight text. This fails WCAG 2.1 A success criteria 1.3.1 (Info and Relationships). An update to our CMS means that newer content should use the 'strong' tag instead. We consider it a disproportionate burden to change the tag on all the historic pages.

We are also aware that many of our older PDFs are not fully accessible to screen reading software. We are trying to reduce the use of PDFs on the website in general, and are ensuring that all new PDFs published meet the accessibility standards.


What we’re doing to improve accessibility

We have a roadmap in place to greet the issues raised in this statement. Priority will be given to the issues identified as a high priority. We will then move on to resolve the issues with lower priority. Some of the issues will be fixed as part of the day to day work of reviewing all the webpages on the site.

This statement will be reviewed regularly to report on our progress.

 

Preparation of this accessibility statement

This statement was prepared on 21 September 2020.

All the webpages were last tested by Siteimprove.com on 14 October 2020. During October 2020 Silktide.com also tested 125 pages from the site.

We tested: