Accessibility Statement - Staff Risk 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
• some users may have difficulty dragging panels, as well as dragging the map
• 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 buttons open in a new tab without alerting the user

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

• There are some empty buttons without discernable accessible text (1.1.1: Non-text Content)
• On mobile, when turned to portrait view, the map is not visible at all. On mobile (landscape), map panels are visible but with some loss of functionality or hidden content (1.3.4: Orientation, 1.4.10 Reflow)
• Zooming and scaling must not be disabled in the meta tags – this prevents users from zooming on mobile devices (1.4.4 Resize Text)
• There is no mechanism to bypass blocks of links, such as the main icon menu or the listings of locations. However, there are only a small number of main menu items, so less of an issue (2.4.1 Bypass Blocks)
• A visible focus indicator is generally shown as a dark outline around buttons and links. However, the visible focus indicator is hard to see around the main icon buttons (black outline against dark green). (2.4.7 Focus Visible)
• When a modal window (Welcome panel) is open, the contents of the modal window should be tabbable, but not the content of the parent window (3.2.1 On Focus)
• Some links (in top menubar) open in new tab - the user is alerted but the text '(opens in new tab)' should be part of the link. Some 'Details' buttons open in new tab but the user is not alerted (e.g. under Map Layers) (3.2.2 On Input)
• All page content should be contained within landmarks (4.1.2: Name, Role, Value)
• Lists (OL and UL) contain the correct li elements, but because these have role=“button”, they are being treated as buttons rather than list elements. ARIA 'role=button' is not allowed for given element (li) (Increase/decrease capacity, Details) (4.1.2: Name, Role, Value)
• Panels do not have accessible name (ARIA dialog and alertdialog nodes should have an accessible name) (4.1.2: Name, Role, Value)
• Attribute Table: ARIA attributes must be used as specified for the element’s role. Aria-level is supported with treegrid rows but not with table or grid (4.1.2: Name, Role, Value)
• Attribute Table: Certain ARIA roles must contain particular children. The tablist element contains children which are not allowed (appears to include child DIVs with role=“tablist) (4.1.2: Name, Role, Value)

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 12 December 2024. It was last reviewed on 15 November 2024.

This website was last tested on 12 December 2024 against the WCAG 2.2 AA standard.

The test was carried out by DAERA Digital Services Division.

We tested the following pages:

• Homepage
• Homepage (Map Layers)
• Homepage (Legend)
• Homepage (Attribute Table)
• Homepage (About)

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.