Research and analysis

Riverine Natural Capital Condition and Ecosystem Service Mapping Project: accessibility statement

Published 11 May 2026

Applies to England

1. Ecosystem Service Map Explorer Accessibility Statement

1.1 Accessibility statement for the Ecosystem Service Map Explorer

This accessibility statement applies to the Ecosystem Service Map Explorer (ESME) web application. This statement is also available in HTML format from GOV.UK.

This web application is run by the Environment Agency.

We want as many people as possible to be able to use this website. For example, that means you should be able to:

• use browser settings or other software to zoom in up to 150% without the text spilling off the screen

We’ve also made the website text as simple as possible to understand and provided additional user guidance in multiple formats. AbilityNet has advice on making your device easier to use if you have a disability.

1.2 How accessible this website is

We know some parts of this web application are not fully accessible, largely because of technology constraints. This is likely to impact users with low vision who require audio feedback or screen readers, and mobility impaired or keyboard users. These elements include:

• it doesn’t work without JavaScript, so if you have a JavaScript disabled preference the web application will appear blank.
• it will not work on mobile devices and reflow may not work well on narrow screens or when using screen magnifiers. It works best for screen size settings of 1024 x 768 and above and when zoomed in no more than 150%.
• it is not possible to fully interrogate the maps with a just a keyboard.
• the map tab interface order is not logical for keyboard users.
• the keyboard order focus is not always logical.
• some element and function settings are not optimal for screen readers.
• charts are not meaningful for screen readers, but data within them can be exported to CSV or other formats to explore in a user’s own software.
• it is not possible to change between a light or dark colour theme preference, but the data can be exported to CSV or spatial formats to explore in a user’s own software.
• the format of some content cannot be modified to suit a user’s preference.
• you cannot modify the line height or spacing of text.
• the scroll image is still animated when a user has chosen reduced motion preference.
• default software warning dialog boxes have insufficient colour contrast.

This web application helps visualise spatial data and information but is not the primary or only way to access it. The underlying data and accompanying reports and guidance are available in accessible formats from the Defra Data Services Platform and GOV.UK for a user to view in their preferred software.

1.3 Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: NaturalCapital@environment-agency.gov.uk.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

• email NaturalCapital@environment-agency.gov.uk

We’ll consider your request and get back to you within 10 working days.

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

1.5 Technical information about this website’s accessibility

The Environment Agency 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

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

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

The web application does not work without JavaScript, so for users with a JavaScript disabled preference the web application will appear blank. This fails WCAG 2.2 success criterion 4.1.1 (Compatibility). This web application helps visualise data and information but is not the primary or only way to access it. The underlying data and accompanying reports and guidance are available in accessible formats from the Defra Data Services Platform and GOV.UK. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

The web application does not respect Prefers-Reduce-Motion and moving content is present, so for users who have prefers-reduce-motion enabled scroll animations will still be present on some pages. This fails WCAG 2.2 success criterion 2.3.3 (Animation from Interactions) and 2.2.2 (Pause, Stop, Hide). In addition, the user guidance page includes video GIFs which cannot be paused. However a user must choose to expand a guidance step to see these, and a user warning is clearly displayed to highlight they contain animations and to signpost an alternative downloadable static user guide. It is not currently possible to disable scroll and GIF animations where users have prefers-reduce-motion enabled in Esri ArcGIS Experience Builder software, but we have minimised where they are used and taken steps to reduce their impact. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

In the web application keyboard focus and tab order is not always logical. Some buttons and dialog boxes cause bleed through or obscure page content when the wrong element receives focus, making it hard to interpret information. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order), 2.4.11 (Focus Not Obscured), 2.1.1 (Keyboard), 1.3.1 (Info and Relationships) and partially fails WCAG 2.2 success criterion 2.4.7 (Focus Visible). Keyboard focus is visible in the web application, but the focus order and tab order is not always logical, and it does not always match the visual layout. Keyboard focus and tab order enhancements were implemented in Esri ArcGIS Experience Builder by Esri partway through build of the tool, however it is not possible to change the order of the keyboard focus or tab focus without completely rebuilding the tool. Further improvements to keyboard focus, navigation and automated tab order are on Esri’s roadmap of future improvements so these are likely to improve over time. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible to re-order keyboard focus and or tab order retrospectively. The web application is being released initially as a Beta product with the intention of building upon it in the future and eventually releasing an alpha, improved, version if there is demand. If and when the tool has a major re-build this functionality will be built in if technology allows.

In this web application the content of the interactive charts is not meaningful for screen readers. This fails WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence). Screen reading is enabled within the tool but there are currently limitations to fully meaningful narration of interactive chart contents by screen readers in Esri ArcGIS Experience Builder software. Esri’s roadmap of future improvements include enhancing screen reader support and widget-level accessibility settings, so these are likely to improve over time. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible. In the meantime, the chart contents can be exported into CSV or other formats by selecting the Action button next to them to explore in a user’s own software.

In the web application it is not possible to fully interact with the map with just a keyboard. Users can zoom but not pan or select features. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard). The map ‘Select’ widget requires dragging movements for operation which some users of assistive technology may not be able to perform. This fails WCAG 2.2 success criterion 2.5.7 (Dragging Movements). It is not currently possible for a user to fully interact with an interactive map with just a keyboard in Esri ArcGIS Experience Builder software. However, it is possible to select a feature on the map and zoom to it by typing a feature name into the ‘Search’ widget instead. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible. In the meantime, data can be exported to CSV or spatial formats, or downloaded from the Defra Data Services Platform, to explore in a user’s own software.

The function and location of some visual icons in the web application are described by text however, users who experience vision impairments may not be able to understand information conveyed by location alone. This fails WCAG 2.2 success criterion 1.3.3 (Sensory Characteristics). We plan to review and improve descriptions where possible by April 2027 through our improvement roadmap.

Some warning dialog boxes in the web application have insufficient colour contrast which some users may find hard to read. This fails WCAG 2.2 success criterion (1.4.3 Contrast). Warning text uses standard settings within Esri ArcGIS Experience Builder software, and it is not currently possible to change this. Esri do have a roadmap of future improvements which include accessibility enhancements so this may become possible in the future. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

Some labels and instructions are truncated when the page is magnified up to 200% which may make it more difficult for users who experience visual impairments that might rely on high levels of browser magnification to read text content. This fails WCAG 2.2 success criterion 1.4.4 (Resize text). The web application is best suited to larger screen sizes due to the large amount of information shown (charts, text, maps). If the application is viewed on a mobile screen, or when zoomed in beyond 400% a warning message will appear stating to load the application on a larger screen. A screen size of 1024 x 768 and above is recommended, as is zooming in no more than 150%. Outside of these recommendations overlapping elements and vertical scrolling conflicts may occur. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible. In the meantime, the underlying data and accompanying reports and guidance are available in accessible formats from the Defra Data Services Platform and GOV.UK, and the data can be exported for use in a user’s own software.

Some text information is presented in images and cannot be adjusted for a user’s required presentation. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text). Meaningful alternative text has been added to images to mitigate this impact for now, but restructuring some of the information may further help. We plan to review and improve content like this where possible by April 2027 through our improvement roadmap.

Navigation links are at the bottom of the homepage meaning a keyboard user has to tab through other content to reach them. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks). It’s not possible to add a ‘skip to main navigation’ button. Page navigation was added to the bottom of the page to prevent overcrowding of tabs at the top of the page, but we will consider re-structuring navigation tabs in future iteration of tool. We plan to review and improve structure where possible by April 2027 through our improvement roadmap.

Some widgets are not programmatically associated with the information they provide or provide overly long instruction, which can make it hard for users of screen readers to determine the element’s purpose. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels) and 1.3.1 (Info and Relationships). The web application uses standard Esri ArcGIS Experience Builder widgets, and we have limited control over the settings, for example we cannot programmatically determining headings, but will consider where additional supporting text may help. Esri do have a roadmap of future improvements which include accessibility enhancements so this may become possible in the future. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

Some hyperlinks open in a new window without informing a user which could be disorientating for screen reader users who may not know that the window has opened. This fails WCAG 2.2 success criterion 3.2.5 (Change on Request). We plan to review and improve content like this where possible by April 2027 through our improvement roadmap.

The function or purpose of some widgets is unclear because they contain elements with no instruction (such as check lists to toggle map layers on) or because they rely on placeholder text alongside them. This can make it hard for some users to interpret the instruction, and some users who cannot view page content simultaneously may be unable to reliably perceive a change in content triggered by an action. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions). The web application uses standard Esri ArcGIS Experience Builder widgets, and we have limited control over the settings. The user guides in the guidance tab do provide widget instructions to a assist a user, but we will consider where additional supporting text may help. Esri do have a roadmap of future improvements which include accessibility enhancements so further control of widget settings may become possible in the future. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

Accessible Rich Internet Applications (ARIA) roles are not fully or correctly defined for some elements within the web application. ARIA roles act as labels to tell a screen reader what an element represents to support user understanding. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). The web application uses standard Esri ArcGIS Experience Builder software settings for elements and we have no control over ARIA attributes. Esri do have a roadmap of future improvements which include accessibility enhancements so further control of element settings may become possible in the future. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible.

Disproportionate burden

N/A

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

This web application does not respect Prefers-Colour-Scheme, so for users who have prefers-colour-screen enabled the colour scheme will not default to their preferred dark or light colour theme. This does not directly fail any WCAG 2.2. success criterion, but is best practice, and can indirectly impact compliance with WCAG success criterion 1.4.3 (Contrast) and 1.4.11 (Non-text Contrast). It is not currently possible for a user to change between dark and light themes in Esri ArcGIS Experience Builder software. It is however on Esri’s roadmap of future improvements. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible. In the meantime, data can be exported to CSV or spatial formats, or downloaded from the Defra Data Services Platform, to explore in a user’s own software.

This web application will not work on mobile devices and reflow may not work well on narrow screens or when using screen magnifiers. This fails WCAG 2.2. success criterion 1.4.10 (Reflow). However, interactive maps are exempt from the reflow requirement under this success criteria as they inherently require two-dimensional scrolling for meaningful use. The web application is best suited to larger screen sizes due to the large amount of information shown (charts, text, maps). If the application is viewed on a mobile screen, or when zoomed in beyond 400% a warning message will appear stating to load the application on a larger screen. A screen size of 1024 x 768 and above is recommended, as is zooming in no more than 150%. Outside of these recommendations overlapping elements and vertical scrolling conflicts may occur. We plan to revisit technology constraints annually and will address this issue through our improvement roadmap if it becomes technically feasible. In the meantime, the underlying data and accompanying reports and guidance are available in accessible formats from the Defra Data Services Platform and GOV.UK, and the data can be exported for use in a user’s own software.

1.6 What we’re doing to improve accessibility

This web application is a Beta release product, and we intend to build and improve on it over time, including improving its accessibility to users. We will revisit technology constraints annually through our accessibility roadmap and will address non-compliant WCAG2.2 success criterion as and when it becomes technically feasible and resources allow.

1.7 Preparation of this accessibility statement

This statement was prepared on 11/03/2026.

It was last reviewed on 11/03/2026.

This website was last tested on 11/02/2026.

The test was carried out by the Digital Accessibility Centre (DAC) user/technical team who undertook an expert independent accessibility audit for each user journey within the web application. It was assessed against the WCAG 2.2 AA standard to identify issues and areas for improvement. Some of the issues documented in this statement were identified in a previous test carried out by the Defra Accessibility Team who undertook an expert accessibility mini audit of each page within the draft version of the web application on 19/12/2025.