Mobile Application Accessibility Statement

This accessibility statement applies to Gwynedd Council’s Mobile Application.

Our mobile application is maintained by Gwynedd Council and we want as many people as possible to be able to use it. 


How accessible this mobile application is

We know some parts of this mobile application are not fully accessible:

  • Some sections and forms are difficult to navigate using just a keyboard and screen reader software – you can contact us using the details below to ask for alternative formats
  • some links and images on the mobile application are not accessible. 

 

Feedback and contact information

If you need information on this mobile application in a different format such as 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 our mobile application

We’re always looking to improve the accessibility of our mobile application. If you find any problems 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 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 audio induction loops at all Siop Gwynedd receptions. 

Find out how to contact us: www.gwynedd.llyw.cymru/contactus

 

Technical information about the mobile application's accessibility

Gwynedd Council is committed to making its mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This statement is based on a full accessibility review of our ap by The Digital Accessibility Centre (DAC).

 

Compliance Status

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 (external link) AA standard. 

 

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations: 

  1. Focus is not always sent to the correct area when a page loads. This fails the WCAG 2.2 A success criterion 2.4.3 Focus Order. We aim to resolve this issue by March 2025.
  2. When the menu is opened, content that is placed on the page underneath is picked up via VoiceOver. This fails the WCAG 2.2 A success criterion 2.4.3 Focus Order. We aim to resolve this issue by March 2025.
  3. Some form elements do not have labels. This fails the WCAG 2.2 A success criterion 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value. We aim to resolve this issue by March 2025.
  4. There are some links present on pages that are not marked up as links. This fails the WCAG 2.2 A success criterion 2.4.4 Link Purpose (In Context) and 1.3.1 Info and Relationships. We aim to resolve this issue by March 2025.
  5. There is some content present on the page that cannot be accessed via VoiceOver.This fails the WCAG 2.2 A success criterion 1.3.1 Info and Relationships 2.1.1 Keyboard. We aim to resolve this issue by March 2025.
  6. Text content cannot be resized via the accessibility features or content overlaps where text can be enlarged. This fails the WCAG 2.2 AA success criterion 1.4.4 Resize text. We aim to resolve this issue by March 2025.
  7. Some form elements are present that are not descriptive of their function or purpose.This fails the WCAG 2.2 AA success criterion 2.4.6 Headings and Labels. We aim to resolve this issue by March 2025.

 

Disproportionate burden

Not applicable. We are not claiming that any of our accessibility issues are disproportionate to fix. 

 

What we’re doing to improve accessibility

We are urgently fixing content which fails to meet the Web Content Accessibility Guidelines version 2.2 A and 2.2 AA standard. We will update this accessibility statement as issues are fixed.

 

Preparation of this accessibility statement

This statement was prepared on 15 June 2021. 

The mobile application was tested by The Digital Accessibility Centre (DAC) during October 2021.

This statement was last reviewed and updated on 12 September 2024.