Accessibility Statement - Veterinary Road Traffic Accident Editor

View Veterinary Road Traffic Accident Editor

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
• some users may have 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
• there are some broken ARIA references, which may cause unpredictable instructions for users of assistive technologies (screenreaders) - especially on menus, list items or tabs
• some users of screenreading software may experience difficulties interacting with tabs and tables on the Attribute Table panel
• the application title is not very descriptive
• title text is duplicated for multiple elements, which means the same instructions may be read out twice by screenreading software

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, arrow buttons on Attribute table tabs) (1.1.1: Non-Text Content)
• Form elements should have visible label – ‘Find address or place input’ field (1.1.1: Non-Text Content)
• Ensure svg elements with an img, graphics-document or graphics-symbol role have an accessible text (symbols on the Legend panel) (1.1.1: Non-Text Content)
• Coordinate Finder: Missing form labels – X, Y coordinate fields - A form control does not have a corresponding label. (1.1.1, 1.3.1, 2.4.6, 3.2.2 )
• No heading structure used throughout (1.3.1: Info and Relationships, 2.4.6: Headings And Labels)
• Broken ARIA references on Legend: An aria-labelledby or aria-describedby reference exists, but the target for the reference does not exist. (1.3.1: Info and Relationships, 4.1.2: Name, Role, Value)
• Map layer panel checkbox tree - Ensure elements with an ARIA role that require child roles contain them (Element has children which are not allowed: [role=treegrid]) (1.3.1: Info and Relationships)
• Select Draw mode – certain ARIA roles must contain particular children: Element has children which are not allowed: div[aria-label], button[aria-busy], [role=region] (1.3.1: Info and Relationships)
• Because the link to Information Hub is not underlined, it is not obvious that it is a link (Links must be distinguishable without relying on colour) (1.4.1: Use Of Colour)
• user-scalable=no on tag disables zooming on mobile device (1.4.4: Resize Text)
• The application title is not sufficiently descriptive 'RTA Web App - NEW'. Some users may not understand the abbreviation without context (2.4.4: Page Titled)
• When a link or icon receives focus, a blue-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 blue side panel (2.4.7: Focus Visible)
• Broken ARIA references on Legend: An aria-labelledby or aria-describedby reference exists, but the target for the reference does not exist. (4.1.2: Name, Role, Value)
• Ensure all page content is contained by landmarks (1.3.1: Info and Relationships, 4.1.2: Name, Role, Value)
• Attribute Table: Ellipsis Elements must use supported ARIA attributes - ARIA attribute is not allowed: aria-expanded="false“ (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

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

This website was last tested on 24 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 (Legend)
• Homepage (Map Layer)
• Homepage (Draw)
• Homepage (Coordinate FInder)

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.