Accessibility statement for flood risk, shoreline management, and coastal erosion maps

This accessibility statement applies to the following products:

  • Flood risk map
  • Shoreline management map

This website is run by Natural Resources Wales (NRW). 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
  • 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 this website is

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

  • the text will not reflow in a single column when you change the size of the browser window
  • you cannot modify the line height or spacing of text
  • some of our online forms are difficult to navigate using just a keyboard
  • you cannot skip to the main content when using a screen reader

 

Feedback and contact information

If you are unable to access information provided through a map or mapping service, or need information in a different format, such as:

  • accessible PDFs
  • large print
  • easy read
  • audio recording
  • braille


You can:

Natural Resources Wales
Customer Care Centre
Crown Buildings
Cathays Park
Cardiff
CF10 3NQ

We'll consider your request and get back to you within 5 working days.

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

NRW 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 not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content

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

 

Non-compliance with the accessibility regulations

Some images do not have an accessible text alternative, so people using a screen reader cannot access the information they convey. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: 6 April 2027

Buttons do not have appropriate labels. Buttons without labels do not provide information about the functionality of the button to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: 6 April 2027

Form input fields lack an associated text label or descriptive title. Incorrectly associated labels do not provide functionality or information about the form control to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: 6 April 2027

Headings are not always marked up appropriately which may cause screen readers to announce them incorrectly. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: 6 April 2027

Headings level 1’s are missing across the site which may cause navigational difficulties. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: 6 April 2027

ARIA landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: 6 April 2027

Some ARIA landmarks are indistinguishable which may cause navigational difficulties for screen reader users. This may cause content to be missed by screen reader. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: 6 April 2027

Some navigational links on the page are not contained within a navigational element. This stops users who navigate using landmarks from being able to directly access the navigational links. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: 6 April 2027

When styling is disabled, not all content is displayed. This may result in unexpected announcements by screen readers. This fails WCAG 2.2 success criterion 1.3.2 (meaningful sequence).

We plan to resolve this by: 6 April 2027

Information on the page is communicated only by colour. This may be difficult to understand for users with visual impairments or colour blindness. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

We plan to resolve this by: 6 April 2027

Text does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).

We plan to resolve this by: 5 August 2027

Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (resize text).

We plan to resolve this by: 5 August 2027

Applying 400% zoom with a browser width of 1280px results in a loss of content. This fails WCAG 2.2 success criterion 1.4.10 (reflow).

We plan to resolve this by: 5 August 2027

Some non-textual content lacks contrast against the background of the page. This includes toggle controls, checkboxes and various image buttons. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

We plan to resolve this by: 5 August 2027

Some non-textual content lacks contrast against the background page when focused or selected. This includes checkboxes and various image buttons. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

We plan to resolve this by: 5 August 2027

There is not enough contrast between the foreground and background within a graphical object. This includes the multiple layers used within the map and the related legend. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

We plan to resolve this by: 5 August 2027

Applying spacing or custom styling to text results in a loss of content. This fails WCAG 2.2 success criterion 1.4.12 (text spacing).

We plan to resolve this by: 5 August 2027

Content that appears on hover or focus is unable to be dismissed without moving the pointer cursor. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).

We plan to resolve this by: 5 August 2027

Content that appears on hover or focus disappears when the mouse is moved over the content. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).

We plan to resolve this by: 6 April 2027

Some content in inaccessible when using a keyboard or screen reader to navigate the site. For example, buttons or toggle controls within side panels and modals. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).

We plan to resolve this by: 6 April 2027

A ‘Skip to Main Content’ links or similar is not present within the site to allow keyboard and assistive technology users to bypass repeated navigational components. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).

We plan to resolve this by: 6 April 2027

Page titles are not sufficiently descriptive or informative which may cause navigation issues between tabs. This fails WCAG 2.2 success criterion 2.4.2 (page titled).

We plan to resolve this by: 6 April 2027

The focus order of the page is not logical. Users who rely on a keyboard for operating a page benefit from a logical, usable focus order. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

We plan to resolve this by: 6 April 2027

Links with identical text are not distinguished by their accessible labels. This could cause confusion for screen reader users. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).

We plan to resolve this by: 6 April 2027

The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).

We plan to resolve this by: 5 August 2027

The ‘Basecamp Gallery’, ‘Draw’ and ‘Print’ buttons are obscured by another element when focused. This could cause confusion for users who navigate via keyboard. This fails WCAG 2.2 success criterion 2.4.11 (focus not obscured (minimum)).

We plan to resolve this by: 5 August 2027

Some interactions cannot be easily cancelled through simple gestures. This may impact users with impaired mobility. This fails WCAG 2.2 success criterion 2.5.2 (pointer cancellation).

We plan to resolve this by: 6 April 2027

The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (label in name).

We plan to resolve this by: 6 April 2027

Dragging movements are required for some site elements which may be difficult for users with motor impairments. This fails WCAG 2.2 success criterion 2.5.7 (dragging movements).

We plan to resolve this by: 5 August 2027

Some uses of ARIA are not appropriate and may result in some incorrect content announcements by screen readers. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: 6 April 2027

Some ARIA components lack accessible labels which may result in some incorrect screen reader announcements. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: 6 April 2027

Not all components can be interacted with using the voice recognition software, Dragon Naturally Speaking. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: 6 April 2027

Status messages are not announced by screen readers. This may result in users being unable to correct input errors. This fails WCAG 2.2 success criterion 4.1.3 (status messages).

We plan to resolve this by: 5 August 2027

Preparation of this accessibility statement

This statement was prepared on 28/10/2026 It was last reviewed on 28/10/2026.

This website was last tested on 28/08/2026. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define the pages tested and test approach.

Last updated