Accessibility Statement - N Max for Grassland Calculator

Before you start

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.

• There is content loss when orientation is changed or text is resized to 200%
• orphaned form labels have been identified
• missing form labels have been identified
• skipped heading level

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

• Orphaned form label - Properly associate the label with its corresponding form control. If there is no corresponding form control, remove the label. (1.1.1)
• Missing form label – If a text label for a form control is visible, use the element to associate it with its respective form control. (2.4.6)
• Empty table header – If the table cell is a header, provide text within the cell that describes the column or row. (2.4.6)
• Missing fieldset - Determine whether the grouping of check boxes or radio buttons has or needs text that explains the purpose of the check boxes or radio button grouping. (1.1.1)
• Possible heading - If the paragraph is a section heading, use a heading element instead (< h1 >-< h6 >). (2.4.6)
• Link to PDF document - Ensure the PDF document is natively accessible.
• Device dependent event handler - Ensure that critical functionality and content is accessible by using a device independent event. (2.1.1)
• JavaScript jump menu - If the onchange event handler triggers a new web page, eliminate the JavaScript jump menu and allow the user to change the select menu, then activate an adjacent button to trigger the new page. When dropdown is selected it causes change of context without the user submitting. (3.2.2)
• Redundant title text - In most cases the title attribute can be removed, otherwise modify it to provide advisory, but not redundant information. (2.4.2)
• Layout table - In almost every case, layout tables can be replaced with other HTML elements and styled with CSS to achieve the desired visual presentation.
• Document should contain one main landmark – Ensure the document has a main landmark. (1.3.1)
• Landmarks should have a unique role or role/label/title (i.e accessible name) combination – Ensure landmarks are unique. (4.1.2)
• All page content should be contained by landmarks – Ensure all page content is contained by landmarks. (1.3.1)
• Very low contrast – Increase the contrast between the foreground (text) color and the background colour. (1.4.3)
• Frames must have an accessible name – Ensure < iframe > and elements have an accessible name. (2.5.3)
• < ul > and < ol > must only directly contain < li >, < script > or < template > elements – Ensure that lists are structured correctly. (1.3.1)
• 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. (1.3.1)
• Loss of content when orientation is changed. (1.3.4)
• Loss of content on the side navigation when text is increased to 200%. (1.4.4)
• 'Skip to main content' link has been provided but can only be indeitifed when using a screen reader, this is also presented after the navigation where it should be presented before. (2.4.1)
• Status messages have not been provided, these would be useful for when the user add/deletes data to confirm this action has been successful. (4.1.3)
• Skipped heading level - Restructure the document headings to ensure that heading levels are not skipped. (2.4.6)
• Keyboard indicator can be difficult to see on certain components such as the add/delete buttons. (2.4.7)
• Select element must have an accessible name – Ensure select element has an accessible name. (2.5.3)

Disproportionate burden

• Application links to PDF documents - ensure that these documents are accessible. An accessibility report has been provided showing the failures within a smapled PDF.

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

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

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 27 June 2025. It was last reviewed on 27 June 2025.

This website was last tested on 26 June 2025 against the WCAG 2.2 AA standard.

The test was carried out by DAERA Digital Services Division.

The following pages were tested:

• Homepage
• Land details
• Chemical fertilisers
• Organic other manure
• Report

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.