Accessibility Non-Compliance

---

Note for site owners

This page details areas of non-compliance with accessibility guidelines that have been identified in the CMS platform.  All non-compliances will be added to our development plan as items to fix. Please check this page regularly and update your local digital accessibility statements to reflect any updates.  You will need to add any issues that are a result of your content.

Admins can manually copy & paste the non-compliances listed on this page to their own website’s accessibility statement or pull this detail in through a Shared Component. The Shared Content function will allow site admins to draw in specific pieces of content, that the CMS Support Team provide and manage, which includes the Non-compliance Part 1 and Part 2 lists. The shared content guide shows admins how to apply this to their site and has screenshots of each step.

The list is in two parts:

Part 1 contains a general description of the issues and is intended to be placed in the "How Accessible this Website is" section. 

Part 2 provides more detailed/technical information and a reference to the specific WCAG 2.2 success criterion and is intended to be placed in the "Non-accessible content" section under the "Non-compliance with the accessibility regulations" heading.

When we update the list of non-compliances, we will increment the version number, so you can keep track of when you need to update your local statements.

---

Part 1

1. Some pages contain text that has poor colour contrast 
2. Some pages contain headings that are not logically ordered
3. Some pages are not fully usable with the keyboard
4. Some pages have an illogical focus order

Part 2

1. At 200% zoom and more in mobile view, the keyboard focus is not visible on the radio buttons and next buttons under both sliders on the multi content display 1 layout. This fails WCAG 2.2 success criterion WCAG 2.4.7 Focus Visible
2. At 200% zoom and more, once the hamburger menu has been expanded, the keyboard tabs onto the cookie icon at the bottom of the webpage rather than onto links within the menu. This fails WCAG 2.2 success criterion WCAG 2.4.3 Focus Order
3. Links must be distinguishable without relying on colour. This fails WCAG 2.2 success criterion WCAG 1.4.1 Use of Color
4. When navigating the page with a keyboard, it's not possible to tab to, and interact, with the links on some pages because this particular content lazy loads after the tab has already gone past that section. You can only tab backwards to access it. This fails WCAG 2.2 success criterion WCAG 2.4.7 Focus Visible

---

Rhan 1

1. Mae rhai tudalennau yn cynnwys testun sydd â lliwiau gwrthgyferbyniol gwael
2. Mae rhai tudalennau yn cynnwys penawdau nad ydynt wedi’u trefnu mewn modd rhesymegol
3. Nid oes modd defnyddio rhai tudalennau’n llawn gyda’r bysellfwrdd
4. Nid yw rhai tudalennau wedi’u trefnu mewn modd rhesymegol o ran ffocws

Rhan 2

1. Pan fydd wedi chwyddo 200% a mwy mewn golwg symudol, nid yw ffocws y bysellfwrdd yn weladwy ar y botymau radio a’r botymau nesaf o dan y ddau lithrydd ar y gosodiad arddangos aml-gynnwys 1. Nid yw hyn yn bodloni maen prawf llwyddiant WCAG 2.2 WCAG 2.4.7 Ffocws yn Weladwy
2. Pan fydd wedi chwyddo 200% a mwy, unwaith y bydd y ddewislen hambyrgyr wedi’i ehangu, mae’r bysellfwrdd yn tabio ar yr eicon cwci ar waelod y dudalen we yn hytrach nag ar ddolenni o fewn y ddewislen. Nid yw hyn yn bodloni maen prawf llwyddiant WCAG 2.2 WCAG 2.4.3 Trefn Ffocws
3. Rhaid bod modd gwahaniaethu rhwng dolenni heb ddibynnu ar liw. Nid yw hyn yn bodloni maen prawf llwyddiant WCAG 2.2 WCAG 1.4.1 Defnyddio Lliw
4. Wrth lywio’r dudalen gyda bysellfwrdd, nid yw’n bosibl tabio i, a rhyngweithio â’r dolenni ar rai tudalennau oherwydd bod y cynnwys penodol hwn yn ‘llwytho’n ddiog’ ar ôl i’r tab eisoes fod wedi mynd heibio’r adran honno. Dim ond drwy dabio yn ôl y gallwch chi ei gyrchu. Nid yw hyn yn bodloni maen prawf llwyddiant WCAG 2.2 WCAG 2.4.7 Ffocws yn Weladwy