This accessibility statement applies to the Cardiff Development and Regeneration website.
This website is run by Cardiff Council. 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 using browser or device settings,
- zoom in up to 400% without the text spilling off the screen,
- navigate the website using a keyboard or speech recognition software, and
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
We have 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.
Feedback and contact information
Please contact us if you:
- find any problems not listed on this page,
- think we are not meeting accessibility requirements, or
- need information on this website in a different format.
Email: devandregen@cardiff.gov.uk
We will consider your request and get back to you as soon as possible.
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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
Cardiff Council 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 partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
| Reason | Success Criterion | Progress |
|---|---|---|
| Add a legend for all fieldsets | WCAG 2.0 A 1.3.1 |
32.65% |
| Ensure form controls have labels | WCAG 2.0 A 1.3.1 |
36.86% |
| Ensure labels in the document point to valid IDs | WCAG 2.0 A 1.3.1 |
48.63% |
| Ensure labels in the document fragment point to valid IDs | WCAG 2.0 A 1.3.1 |
48.97% |
| Remove obsolete scope attribute for table cell | WCAG 2.0 A 1.3.1 |
92.96% |
| Avoid using the same link text for different destinations | WCAG 2.0 A 2.4.4 |
94.90% |
| Ensure headings include text | WCAG 2.0 A 1.3.1 |
96.13% |
| Identify the purpose of fields programmatically | WCAG 2.1 AA 1.3.5 |
98.46% |
| Fix duplicate IDs | WCAG 2.0 A 4.1.1 |
98.98% |
| Add headers to tables | WCAG 2.0 A 1.3.1 |
99.54% |
| Write lists or groups of links semantically | WCAG 2.0 A 1.3.1 |
99.66% |
PDFs and other documents
| Reason | Success Criterion | Progress |
|---|---|---|
| Specify headings for every PDF | WCAG 2.0 A 1.3.1 |
24.49% |
| Ensure PDFs specify a default language | WCAG 2.0 A 3.1.1 |
35.71% |
| Tag all PDFs | WCAG 2.0 A 1.3.1 |
39.80% |
| Ensure PDFs have a title | WCAG 2.0 A 2.4.2 |
66.33% |
| Ensure long PDFs use bookmarks to aid navigation | WCAG 2.0 AA 2.4.5 |
72.45% |
| Ensure PDF headings follow a logical order | WCAG 2.0 A 1.3.1 |
88.78% |
| Ensure PDFs are machine readable | WCAG 2.0 A 1.1.1 |
97.96% |
| Ensure the first heading in a PDF is a H1 | WCAG 2.0 A 1.3.1 |
98.98% |
| Improve weak PDF titles | WCAG 2.0 A 2.4.2 |
98.98% |
Some plans, maps and design documents are produced by a third party. We are working with these to improve accessibility of these 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.
What we are doing to improve accessibility
Our aim is to work through the outstanding issues listed above to achieve full compliance wherever possible. We provide support and training to those who administer the website, to ensure standards are retained when updating the website. We will review the site periodically.
Preparation of this accessibility statement
This statement was prepared on 20 January 2022.
It was last reviewed on 29 August 2025.
This website was last tested on 26 August 2025 by Silktide with additional manual checks performed by our website team.
This statement was last updated on 29 August 2025.