Licensing

Accessibility statement for the Idox Cloud Regulatory Services Online Portal

This accessibility statement applies to the Idox Cloud Regulatory Services Online Portal (RSOP).

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 300% without the main text spilling off the screen
• navigate most of the webforms using only a keyboard
• listen to most of the webforms using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

 

We’ve also made the Idox Cloud Regulatory Services Online Portal as simple as possible to understand by using clear and plain language.

AbilityNet (opens in a new tab) has advice on making your device easier to use if you have a disability.

 

How accessible the Idox Cloud Regulatory Services Online Portal is

We know some parts of the webforms are not fully accessible. For example:

• You cannot modify the line height or spacing of text.
• On the main home page, the tab focus is automatically set to the main first link, so you would have to tab all the way through to get back to the navigation menu.
• The RSOP has not been fully optimised for screen readers – they still work, but some content may not be identified and announced exactly as expected.
• Some content is not useable with only a keyboard (e.g. calendars).

 

Feedback and contact information

If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille, contact the council.

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

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the Council.

Enforcement procedure

If you contact us with a complaint about the accessibility of this website and you are not satisfied with our response, the Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). You can report any concerns to the EHRC. If you are in Northern Ireland, contact the Equality Commission for Northern Ireland. If there is an issue with how a complaint is handled, contact the Equality Advisory and Support Service (EASS) (opens in a new tab).

Technical information about this website’s accessibility

Idox is committed to making the 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.2 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons:

• Some input fields do not have a label.
• Screen reader users may not be told what information is required in a field, making it impossible to complete the form without sighted assistance.
• This is found in the Title field on the Registration form and some checkboxes in My Submissions.
• This is also flagged in the reCAPTCHA form on authentication pages, but this is a 3rd party application which we cannot control.
• This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (opens in a new tab), WCAG 2.2 Success Criterion 2.4.6 Headings and Labels (opens in a new tab), WCAG 2.2 Success Criterion 3.3.2 Labels or Instructions (opens in a new tab), and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).
• There are labels not correctly related to an input field.
• Screen reader users may hear the wrong label read out for a field, or no label at all, which could cause them to enter incorrect information or be unable to complete a form.
• This is found in the Address field group in Registration, a button in the Building Control Application form, and some filters in Planning Applications.
• This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (opens in a new tab) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).
• Some input fields that collect personal information do not have a valid autocomplete attribute value.
• Users who rely on autofill — including people with memory difficulties, motor impairments, or cognitive disabilities — may need to re-enter personal information manually each time.
• This is found in the log in form, where it was disabled for security reasons; and a couple of forms in Planning Submissions.
• This fails WCAG 2.2 Success Criterion 1.3.5 Identify Input Purpose (opens in a new tab).
• Some table column headings do not contain any text label.
• Screen reader users will not be told what a column contains, making it difficult or impossible to interpret the data in that table.
• This is found in the Actions column in Building Control Requests History, the Appeals Register, and Planning Applications.
• This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (opens in a new tab) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).
• There are fieldsets without a clear legend, and some radio button and checkbox groups that are not wrapped in a fieldset.
• Screen reader users may not be told the question or context that a group of radio buttons or checkboxes relates to, which could lead to them answering incorrectly or being unable to complete the form.
• This is found in Building Control forms, a couple of Planning forms, the Caravan licence form, a couple of Register item pages, and one Admin area.
• This fails WCAG 2.2 Success Criterion 1.3.1 Info and Relationships (opens in a new tab).
• There are some links with unclear text labels, including within content configured by council administrators.
• Users who navigate by links — including screen reader users who browse a list of links out of context — may not be able to tell where a link leads.
• This affects links within content configured by council administrators; guidance has been provided to reduce new instances, and existing content is under review.
• This fails WCAG 2.2 Success Criterion 2.4.4 Link Purpose (In Context) (opens in a new tab).
• There are some links that are missing a destination URL or that are used to trigger actions rather than navigate.
• Keyboard-only users may be unable to reach or activate these elements, and screen reader users may be told a control is a link when it behaves as a button, causing confusion about how to interact with it.
• This is found in a couple of Register item pages, and a couple of Planning Submission forms.
• This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard (opens in a new tab) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).
• There are duplicated IDs on some elements.
• Assistive technologies rely on unique element IDs to correctly identify and describe content. Where IDs are duplicated, screen readers may announce incorrect information, skip content, or behave unpredictably.
• This is found in Planning Submissions, Building Control Submissions, and the Admin area.
• This fails WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).
• Some menus and interactive elements driven by JavaScript are not fully operable via keyboard.
• Users who do not use a mouse — including keyboard-only users, screen reader users, and people using switch access devices — may be unable to open, navigate, or close these menus.
• This is found in the table on the Licensing home page.
• This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard (opens in a new tab).
• There is an element incorrectly marked up with an ARIA menu role that does not contain the required menu item children.
• Screen readers will announce this element as a menu and apply menu keyboard behaviour, but the expected keyboard interactions will not work, leaving the element unusable for screen reader users.
• This is found on one button in the Planning Application details page.
• This fails WCAG 2.2 Success Criterion 2.1.1 Keyboard (opens in a new tab) and WCAG 2.2 Success Criterion 4.1.2 Name, Role, Value (opens in a new tab).

Disproportionate burden

We have not made any disproportionate burden claims.

Content that is not within the scope of the accessibility regulations

Some of our web forms include third-party content or widgets that are not funded, developed, or controlled by Idox or the Council. For example, the reCAPTCHA widget used on the registration page is provided by Google. We cannot guarantee the accessibility of this third-party content, but we will raise any known issues with suppliers and seek accessible alternatives where possible.

 

How we tested the Idox Cloud Regulatory Services Online Portal

The Regulatory Services Online Portal was last tested on 14 May 2026. The Idox web team carried out the testing, using manual and visual tests and with the help of accessibility testing software including WAVE and Silktide.

As there are a large number of similar pages and webforms, we manually tested a representative selection of forms and pages within the RSOP.

 

How we prepared this Accessibility Statement

Following testing of the software, this statement was prepared with any outstanding non-compliances. This statement was last updated on 15 May 2026.

 

What we’re doing to improve accessibility

We’re using reports from accessibility software, including WAVE and Silktide and following WCAG guidelines to work towards being fully compliant with WCAG 2.2 AA success criteria.

We are working to address the non-compliances listed in this statement, with a target date of December 2026 for further remediation. We will also address any issues raised by users and continue to review accessibility as part of any future updates to the Idox Cloud Regulatory Services Online Portal.