Accessibility statement for

This accessibility statement applies to the website.

This website is run by Arun District Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:

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 are not fully accessible:

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read or audio recording:

We’ll consider your request and get back to you.

If you cannot view the map on our ‘contact us’ page, call or email us for directions Contact Us | Arun District Council

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:

Enforcement procedure

Contacting us by phone or visiting us in person

Technical information about this website’s accessibility

Arun District Council 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

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.
In certain areas the following non-compliance issues and exemptions arose:

Non-compliance with the accessibility regulations

The Non-compliances outlined below are outstanding accessibility problems affecting limited areas of the NIHMO portal which are due to be resolved by the dates below.

WCAG Guideline Accessibility Problem Plan date for resolution
WCAG 2.1 A F68 A label needs to be linked (or name) linked to the control allowing screen readers to voice the label correctly when reading the control. 26 March 2021
WCAG 2.1 AA 1.4.4 Setting user-scalable=no or maximum-scale to less than 2.0 prevents zooming small text to make it readable. 26 March 2021
WCAG 2.1 A F54 Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. 26 March 2021
WCAG 2.1 A F2 Amend the strong element instead of the span element for bold text. 26 March 2021
WCAG 2.1 A 4.1.1 Element input not allowed as child element in this contex 26 March 2021
WCAG 2.1 A 4.1.1 Duplicate id - the same ID is used on more than one element. 26 March 2021
WCAG 2.1 A F54 Controls that respond to clicks should be given an ARIA role such as role=button or role=link. 26 March 2021
WCAG 2.1 A F15 Add tab index=0 to allow keyboard users to tab to the control. 26 March 2021
WCAG 2.1 A F49 Add role='presentation' if the inner table is a layout table, otherwise modify the inner table to present the same data without nesting tables 26 March 2021
WCAG 2.1 A H71 The first child element inside a field set must be a legend element, which provides a label or description for the group 26 March 2021
WCAG 2.1 AA F78 The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. 26 March 2021
WCAG 2.1 A 4.1.1 No space between attributes 26 March 2021
WCAG 2.1 A F73 Removing the underline from links makes it hard for colour-blind users to see them. 26 March 2021
WCAG 2.1 A F25 Some pages have the same title, so the title cannot be used to distinguish pages. 26 March 2021
WCAG 2.1 A 1.3.1 'h1' to 'h6' elements should not contain elements with 'role=heading' and vice versa. Remove the nested headings or replace them with span elements. 26 March 2021
WCAG 2.1 A 4.1.1 The interactive element input must not appear as a descendant of the a element. 26 March 2021
WCAG 2.1 A 4.1.2 The role attribute changes how screen readers voice content. Invalid values can result in content being misread. 26 March 2021
WCAG 1.1.1 & 2.4.4 When navigating to a button, descriptive text must be presented to screen reader users to indicate the function of the button 26 March 2021
WCAG 2.1 AA 2.4.6 Form field labels should be unique on a page, or be close to text providing context 26 March 2021
WCAG A 4.1.2 Ensure Registration change address link can be read by screen readers 26 March 2021
WCAG 2.1 1.4.11 Arun District Council will review after inhouse testing 26 March 2021

Preparation of this accessibility statement

This statement was prepared on 06 October 2020, based upon testing a sample number of pages, using auditing software ‘OnDemand Web Suite’ by Power Mapper (recommended by W3C Web Accessibility Initiative), and the Chrome Dev Tool extension ‘Lighthouse’. It was last reviewed on 13 October 2020.

This website was last tested on 09 September 2020. The test was carried out by Idox.