Accessibility Statement - Field Finder

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 most of the website using a keyboard or 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 aren't fully accessible:

• some buttons and inputs do not have visible or accessible text
• some icons on the Draw panel, or key items on the Legend panel do not have alternate text
• the focus indicator, showing where the user has tabbed to on the page, is quite indistinct and of low contrast with the dark green background
• overall, navigating the map functionality may prove difficult for keyboard-only users
• the button to collapse the side panel is very narrow and may be difficult for some users to use
• on some mobile devices, the application may need to be used in landscape orientation
• there is some clipping or hiding of information when viewed on mobile devices, and it may not be possible to resize text on mobile devices

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the DAERA Helpline who will direct you towards the correct branch or division.

• email daera.helpline@daera-ni.gov.uk
• call 0300 200 7852

You can also contact the DAERA Helpline if you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille.

If you have a hearing difficulty you can contact DAERA via Text Relay using the Next Generation Text Service (NGTS). Making a call from a textphone dial 18001 + number. Making a call from a telephone dial 18002 + number.

There are also various Text to Speech applications available to use

If you cannot view the map on our contact us page, call or email us for directions.

Enforcement procedure

The Equality Commission for Northern Ireland 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 contact the Equality Commission for Northern Ireland (ECNI).

Technical information about this website’s accessibility

DAERA 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 listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

• Buttons must have discernable text – Empty buttons (the collapse side panel toggle)(1.1.1 Non-text Content, 2.4.4: Link Purpose (In Context))
• Form elements should have visible label – ‘Find address or place input’ field (1.1.1 Non-text Content, 2.4.6: Headings and Labels, 3.3.2: Labels or Instructions)
• Draw panel. SVG elements with an img role must have alt text. (1.1.1 Non-text Content)
• Draw panel. All buttons must have discernable text – the pin icons are missing alt text. (1.1.1 Non-text Content, 2.4.4: Link Purpose (In Context))
• Draw panel. Form elements must have labels (dropdown selects) (1.1.1 Non-text Content,3.3.2: Labels or Instructions)
• Legend panel. SVG elements with an img role must have alt text (1.1.1 Non-text Content)
• About panel – icon images must have alt text (1.1.1 Non-text Content)
• No heading structure used throughout (1.3.1 Info And Relationships)
• Map content and panels not visible in portrait simulation, so can only be meaningfully used in landscape on mobile device.(1.3.4 Orientation, 1.4.10 Reflow)
• Map Layers. Disabled elements do not have to pass contrast ratio – however these items can still be checked, so are not truly disabled.(1.4.3 Contrast (Minimum))
• user-scalable=no on tag disables zooming on mobile device.(1.4.4 Resize Text)
• On laptop/desktop at 200%, some content (e.g. in footer) is clipped. Also, the draggable panels may be truncated and not fully viewable or even scrollable.(1.4.4 Resize Text)
• Landscape – overlapping of content in header and footer, and scrolling required to view side panel (1.4.10 Reflow)
• When a link or icon receives focus, a darker-coloured border is observed around the user interface element. The contrast of the border should be improved as it is difficult to distinguish against the dark green side panel.(2.4.7 Focus Visible)
• The button to collapse the side panel is very narrow (12px) which is below the minimum 24x24 target size.(2.5.8 Target Size (Minimum))
• Ensure all page content is contained by landmarks (4.1.2 Name, Role, Value)
• Map layer panel - The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable – I’m not sure what this relates to (4.1.2 Name, Role, Value)
• Legend panel. Key items have broken ARIA references. An aria-labelledby or aria-describedby reference exists, but the target for the reference does not exist (4.1.2 Name, Role, Value)
• Attributes table tabs. Certain ARIA roles must contain particular children. Think this is because UL tablist contains DIVs with tablist role, but not tabs. (4.1.2 Name, Role, Value)
• Add Data panel. Broken ARIA references - An aria-labelledby or aria-describedby reference exists, but the target for the reference does not exist. (4.1.2 Name, Role, Value)
• Add Data panel. Interactive controls must not be nested. Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies (4.1.2 Name, Role, Value)
• Add Data panel. ARIA input fields must have accessible name. (4.1.2 Name, Role, Value)
• Redundant title text throughout – this is title text which duplicates the visible label.

Disproportionate burden

• Not applicable

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

This application uses mapping functionality and imagery extensively. Maps are one of the items which are excepted from the accessibility legislation, provided essential information is provided in other ways. However, we will attempt to make the functionality of map viewers as accessible as possible within these limitations.

PDFs and other documents

• Not applicable

What we’re doing to improve accessibility

DAERA is actively engaged in improving the accessibility of its applications. As part of our 'UX Checklist', we require developers to design software with accessibility compliance built in. In those circumstances where compliance cannot be met, reasons for this should be documented, along with steps for addressing issues. We also endeavour to carry out user research to ascertain user requirements and conduct usability workshopping before launching new applications.

Preparation of this accessibility statement

This statement was prepared on 22 May 2025. It was last reviewed on 22 May 2025.

This website was last tested on 22 May 2025 against the WCAG 2.2 AA standard.

The test was carried out by DAERA Digital Services Division.

We tested the following pages:

• Field Finder (About panel, Map layers panel, Legend panel, Attribute Table, Draw panel, Add Data panel)

We chose to test those pages which were most commonly used, and most representative of the general functionality and layout of the web application. Sample pages were tested for code compliance using the Axe and WAVE testing tools. The pages also underwent manual testing to ensure they adhered to the four Accessibility principles (Perceivable, Operable, Understandable, Robust). We also test using NVDA screenreader, and Adobe Acrobat Accessibility Checker (where applicable).

The full accessibility test report can be made available on request.