Accessibility Statement - Private Water Supplies

This website is run by Department of Agriculture, Environment and Rural Affairs (DAERA), Northern Ireland. 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 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 parts of this website are not fully accessible.

• low contrast on legacy page buttons may make it hard for some users to read
• text is small on mobile devices and may not be resizable
• On the Master Schedule and Admin - Parameters pages, the search functionality updates the listings table without warning the user first
• it's sometimes hard to know when the user has successfully updated information due to lack of status messages
• tables are used for layout on some older screens
• datepickers are not fully accessible but users can still enter dates manually 

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

• There are a some instances where a visible label is missing and should be used e.g. search parameters functionality on Master Schedule, Admin Parameters (1.3.5 Identify Input Purpose)
• Contrast of buttons and alert messages on legacy screens falls below the minimum ratio. (1.4.3: Contrast (Minimum))
• There appears to be some issues with resizing text on mobile devices. (1.4.4: Resize text)
• On the Master Schedule and Admin Parameters pages, the search may be considered a change of context as the returned results are filtered based on what is input. Users should either be prewarned as to what will happen on inputting text, or a button should accompany the input (3.2.2: On Input)

The following points should also be considered for best practice:

• All pages should have an H1 heading and not start with an H2 - skipped heading levels can be disorienting for users of assistive technologies (1.3.1: Info and Relationships)
• Tables are used for layout in some legacy screens - this should be avoided (1.3.1: Info and Relationships)
• Legacy screens have a generic title for all pages - the title should be specific to the page the user is viewing (2.4.2: Page Titled)
• Ambiguous link text can make it harder for screenreader users to understand what it refers to. Including visually hidden context to a 'Details' button will assist users (e.g. Details for ACL002) (2.4.4: Link Purpose (In Context))
• Some elements of the legacy screens have very faint visible focus indicators (2.4.7: Focus Visible)
• More use of status messages may give users a better understanding of when updates have been successful, particularly where information in tabular format has been updated (4.1.3: Status Messages)
• Where a field is required, add aria-required="true" or 'required', so it can be identified by screenreaders (1.3.1: Info and Relationships)
• Page content should be contained in landmarks – there should be at least one main landmark. Banner landmarks should not be contained in another landmark (new screens). Ensure landmarks are unique (have unique role or role/label/title combination) (4.1.3 Name, Role, Value)

Disproportionate burden

• Not applicable

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

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 10 July 2020. It was last reviewed on 6 August 2025.

This website was last tested on 6 August 2025 against the WCAG 2.2 AA standard.

The test was carried out by DAERA Digital Services Division.

The following pages were tested:

• Sites
• Site details - Edit
• Risk assessment records
• Upload monitoring results
• Scheduling - Master schedule
• Scheduling - Details
• Admin - Parameters
• Site monitoring results
• Users
• User details

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.

 

-----------------------------------------------------------------

This website is run by Department of Agriculture, Environment and Rural Affairs (DAERA), Northern Ireland. We want as many people as possible to be able to use this website. For example, that means you should be able to:

• zoom in up to 200% without the text spilling off the screen
• navigate most of the website using just a keyboard
• navigate most of the website using speech recognition software
• clearly understand the content and instructions of the website.

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:

• Contrast of buttons and alert messages on legacy screens may make it hard for some users to read (1.4.3: Contrast (Minimum))
• There are some issues with resizing text on mobile devices (1.4.4: Resize text)
• users may be timed out of the application without warning, and need to sign in again (2.2.1: Timing Adjustable)
• On the Master Schedule page, the search functionality updates the listings table without warning the user first (3.2.2: On Input)
• it's sometimes hard to know when the user has successfully updated information due to lack of status messages (4.1.3: Status Messages)
• tables are used for layout on some older screens (1.3.1: Info and Relationships)
• datepickers are not fully accessible but users can still enter dates manually (1.4.13: Content on Hover or Focus)

What to do if you can't access parts of this website

If you need further information or assistance in using parts of this website, you can contact a DAERA Direct Regional Office.

• email DAERA Direct Regional Offices
• call 0300 200 7840

A DAERA member of staff will be able to help you with your request.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems that aren't listed on this page or think we're not meeting the requirements of the accessibility regulations, contact the DAERA customer helpline on 0300 200 7852 or email daera.helpline@daera-ni.gov.uk.

If you are unhappy with the quality of service received, in the first instance, you can make a complaint to DAERA.

Enforcement procedure

If you remain dissatisfied with the Department's final response to your complaint, you can refer your case to the Equalities Commission for Northern Ireland (ECNI), which is responsible for enforcing accessibility regulations. You can contact them.

Contacting us by phone or visiting us in person

Department of Agriculture, Environment and Rural Affairs
Dundonald House
Upper Newtownards Road
Ballymiscaw
Belfast BT4 3SB

DAERA Headquarters map location

Call DAERA customer helpline on 0300 200 7852 or email daera.helpline@daera-ni.gov.uk.

If you have a hearing difficulty you can contact the Department 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.

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.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Issues with technology

• Contrast of buttons and alert messages on legacy screens falls below the 4.5:1 ratio (1.4.3: Contrast (Minimum))
• There is no observed method for extending the session time, and no warning to users that their session is about to run out (2.2.1: Timing Adjustable)
• There are a number of instances of non-unique IDs on datagrids (mostly on legacy screens) (4.1.1 Parsing)
• On the Master Schedule page, the search may be considered a change of context as the returned results are filtered based on what is input. Users should either be prewarned as to what will happen on inputting text, or a button should accompany the input (3.2.2: On Input)
• Some elements of the legacy screens have very faint visible focus indicators (2.4.7: Focus Visible)
• More use of status messages may give users a better understanding of when updates have been successful, particularly where information in tabular format has been updated (4.1.3: Status Messages)

Issues with text

• There appears to be some issues with resizing text on mobile devices (1.4.4: Resize text)
• All pages should have an H1 heading and not start with an H2, as skipped heading levels can be disorienting for users of assistive technologies (1.3.1: Info and Relationships)
• Tables are used for layout in some legacy screens (1.3.1: Info and Relationships)
• Legacy screens have a generic title for all pages - the title should be specific to the page the user is viewing (2.4.2: Page Titled)
• Ambiguous link text, such as 'Details' or 'can be found here' can make it harder for screenreader users to understand what it refers to (2.4.4: Link Purpose (In Context))
• Avoid using form labels where they are not associated with an input as they will be reported as 'orphaned form labels' with WAVE.

Issues with PDFs and other documents

• Excel documents are generated and exported as part of this application. Those tested report no accessibility issues.
• Any new PDFs or Word documents we publish will meet accessibility standards.

Issues with images, video and audio

• Icons which are purely decorative should not have title or alt attributes set. Or you can add role="presentation" so they are ignored by assistive technologies (1.1.1 Non-text Content)

Issues with interactive tools and transactions

• Datepickers can be difficult to make accessible - the datepicker on legacy screens does not appear to be fully accessible to keyboard-only users. However a date can be entered manually (1.4.13: Content on Hover or Focus)
• Drag and drop functionality should be used with some caution (and will be further addressed in WCAG2.2).

How we tested this website

This website was last evaluated on 24 April 2023. The evaluation was carried out by DAERA Digital Services Division.

We chose to sample those pages which were most commonly used, and most representative of the general functionality and layout of the web application. The sample pages were tested for code compliance using the Axe testing tool and WAVE (Web Accessiblity Evaluation Tool). The pages also underwent manual testing to ensure they adhered to the four Accessibility principles (Perceivable, Operable, Understandable, Robust). We use the Chrome browser and NVDA screenreader software. Where PDFs are included with the application, we test using Adobe Accessibility Checker.

We tested:

• User / Edit User details
• Reports / Site Report
• Admin Parameters / Admin Parameter Details
• Master Schedule / Master Schedule Details
• Monitoring - Upload monitoring results
• Risk Assessment Records
• Risk Assessment/Current Risk Assessment
• Registration Detail
• Monitoring results
• Landing Page
• Create PWS Registration
• Risk assessment - section selection
• Risk assessment – source: General catchment
• Risk assessment – review details
• Risk assessment – risk review page
• Create PWS Registration
• Risk Assessment Records

What we're doing to improve accessibility

The Department is actively engaged in improving the accessibility of its applications. As part of our 'Development 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 carry out user research to ascertain user requirements and conduct usability workshopping before launching new applications.

This statement was first prepared on 10 July 2020. It was last updated on 24 April 2023.