Skip to main content Skip to footer

Accessibility statement

Accessibility statement for

This accessibility statement applies to the main Coleg Cymraeg Cenedlaethol’s website at

Using the Website

This website is run by the Coleg Cymraeg.  We want as many people as possible to be able to use this website. For example, this 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
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also 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.


How accessible is this

We know some parts of this website are not fully accessible:

  • Termau is a 3rd party integration and is not fully accessible
  • not all embedded videos have captions


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: [ - *****]

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).


Technical information about this website’s accessibility

The Coleg Cymraeg Cenedlaethol is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is compliant with the Web Content Accessibility Guidelines version 2.1 – Level AA standard, due to the non-compliances and exemptions of some of the content on the website, as listed below.

Non-accessible content

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

Due to Welsh language, screen readers do not offer total language equivalence in their interpretation of content into Welsh.

Disproportionate burden

Interactive tools

Termau is based on a 3rd party API that is not fully compliant. Whilst this is outside of our control, the API is being continually improved and will ensure that the page where Termau is embedded will become accessible at the point where the 3rd party completes this work.

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

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.

Embedded video

We plan to add captions to embedded videos that we ourselves own and control, however some embedded videos are outside our control and is exempt from meeting the accessibility regulations.

What we’re doing to improve accessibility

An internal group has been established to create an accessibility roadmap in order to show how and when we plan to improve accessibility on this website.  The roadmap will be published when it is completed.

Preparation of this accessibility statement

This statement was prepared on 09 February 2023.

The website developer tests all new functions and features of the platform as a part of the sprint based user centric development process. Sprints are clusters of user stories which describe the feature/function from a user’s (or persona) perspective (e.g. As a learner I want to be able to…) . Within the sprint project cycles, user stories are include from accessible users’ perspectives. These form a part of the QA process where the following work is conducted:

  • Functional testing – Does the feature or function do what is says it needs to do in the user story
  • Technical testing – is the technical solution successfully implemented in terms of code, performance and technologies used
  • Usability testing – is the feature/function simple and intuitive to use from the end user’s perspective
  • Accessibility testing – Testing against WCAG 2.0 and 2.1 guidelines. We Strive to meet AA levels in testing against Perceivable, Operable, Understandable and Robust aspects of the guidelines.

The following tools and manual methods are used in testing.