Accessibility Statement - Spatial Data Viewer

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 do not have accessible text or labels
• there may be some difficulties viewing the application or zooming in on mobile devices. On mobile phones, content is only visible in landscape orientation
• some users may have difficulty dragging panels, as well as dragging the map, and some focusable content may be obscured under these draggable panels
• icon buttons receiving focus have a dark border which is difficult to see against the dark panel background colour
• not all content is included within landmarks, which assists screenreading software when navigating the webpage
• some users of screenreading software may experience difficulties interacting with tabs and tables on the Attribute Table panel
• some input fields have low contrast making them harder to see
• some icons and map points are smaller than the minimum recommended target size

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 and links must have discernable text – Empty buttons(e.g. the collapse side panel toggle, arrow buttons on Attribute table tabs, input field for setting line width)(1.1.1: Non-text Content)
• SVG elements with an img role must have alternative text (images showing colour line options)(1.1.1: Non-text Content)
• Form elements should have visible label – ‘Find address or place input’ field, coordinate conversion textareas (1.1.1: Non-text Content)
• No heading structure used throughout (1.3.1: Info and Relationships, 2.4.6: Headings and Labels)
• All page content should be within landmarks – there is no main landmark or other page regions to help screenreaders identify the regions of the page (1.3.2: Meaningful Sequence)
• In portrait (mobile), the map and side panels are not visible at all. In landscape (mobile), there is some obscuring of content and functionality (1.3.4: Orientation)
• user-scalable="no" on tag disables zooming on mobile device. On laptop/desktop at 200%, content (such as icon buttons and map search functionality) is clipped. Also, the draggable panels may be truncated and not fully viewable, or require scrolling in two dimensions. (1.4.4: Resize Text)
• Elements must meet minimum colour contrast ratios (Lat, Long input fields) - Element has insufficient color contrast of 2.98 (foreground color: #8b8b8b, background color: #f0f0f0, font size: 9.8pt (13px), font weight: normal). Expected contrast ratio of 4.5:1 (1.4.11: Non-text Contrast)
• There is clipping of some of the information panels, and therefore loss of functionality, on mobile devices (1.4.10 Reflow) - however the application is not targeted to mobile device users
• The visible focus indicator is a black coloured border, which is indistinct against the dark green side panel - suggest a more vivid colour (2.4.7: Focus Visible)
• The application uses draggable panels, which may obscure other content. In this case, because the movable content is obscuring the lower icon links when in its initial position, it could be considered a fail (2.4.11: Focus Not Obscured (Minimum))
• The target size of some points/features on the map are below 24x24px (2.5.8: Target Size (Minimum))
• ARIA dialog and alertdialog nodes should have an accessible name – draggable side panels are not identified by accessible text (4.1.2: Name, Role, Value)
• 3 x Broken ARIA references - An element has an aria-labelledby or aria-describedby value that does not match the id attribute value of another element in the page ( (4.1.2: Name, Role, Value))
• 3 x Broken ARIA menu - An element with role="menu" does not contain at least one element with role="menuitem", role="menuitemcheckbox", or role="menuitemradio" (4.1.2: Name, Role, Value)
• Colour and location are used in the map functionality. Maps are exempt from the accessibility requirements, provided essential information is provided in an alternative accessible format. Similarly, green and red colours used together can be problematic for colour blind users. (1.3.3: Sensory Characteristics, 1.4.1: Use of Colour, 1.4.11 Non-text Contrast)
• 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

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. For example, we do not plan to fix [example of non-essential document].

Any new PDFs or Word documents we publish will meet accessibility standards.

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 4 April 2025. It was last reviewed on 4 April 2025.

This website was last tested on 4 April 2025 against the WCAG 2.2 AA standard.

The test was carried out by DAERA Digital Services Division.

We tested the following pages:

• Homepage
• Homepage (Information)
• Homepage (Draw)
• Homepage (Coordinate Conversion)
• Homepage (Map Layers)

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.