This accessibility statement should be read in relation to our main accessibility statement.
This statement applies to part of our online services available via our website - our Garden Waste Subscription Scheme which enables customers to subscribe to garden waste collections; the functionality is provided by Granicus UK.
We know some parts of this system are not fully accessible, see Technical information about this system's accessibility.
Feedback and reporting accessibility problems
Get more information about:
Technical information about this system’s accessibility
We are committed to making our online services accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations, 2018.
This part of our website is partially compliant with the Web Content Accessibility Guidelines (WCAG); any non-compliances are listed.
Non-compliance with the accessibility regulations
-
some heading elements are not in a sequentially-descending order and fail to convey the semantic structure of the page, making it harder to navigate and understand when using assistive technologies - this relates to WCAG (AA) success criterion 2.4.6
-
some ID attributes are not unique and may cause errors which are problematic for assistive technologies trying to parse content - this relates to WCAG (A) success criterion 4.1.1
-
some scenarios don't have a means to bypass repeated blocks meaning people who navigate sequentially through content don't have direct access to primary content - this relates to WCAG 2.1 (A) success criterion 2.4.1
-
some table headers in a data table don't refer to data cells when associated with more than one row and/or one column header, to allows screen readers to speak the headers associated with each data cell and making complex relationships perceivable when the presentation format changes - this relates to WCAG (A) success criterion 1.3.1
-
some ARIA roles may not exists inside their required context - this technique relates to WCAG (A) success criterion 1.3.1
-
some form elements may not contain labels - this relates to WCAG (A) success criterion 1.3.1
-
some text may not sufficiently contrast with its background colour, so that people with moderate visual impairments can read it - this technique relates to WCAG (AA) success criterion 1.4.3, and in some cases WCAG (AAA) success criterion 1.4.6
-
some label elements don't explicitly associate a form control with a label (whether the label element is visible or hidden using CSS), or a label is not attached to a specific form control through the use of the 'for' attribute - this technique relates to WCAG (A) success criteria 1.1.1, 1.3.1 and 4.1.2
-
some ARIA attributes do not have valid values in order to allow assistive technologies to convey appropriate information - this relates to WCAG (A) success criterion 4.1.2
-
some list items may not be contained within the parent elements, and where this hierarchy isn't in place assistive technology cannot indicate a list is present - this relates to WCAG (A) success criterion 1.3.1
-
some elements with an ARIA roles that require children to contain a specific role are missing some or all of those required children, meaning assistive technology may not function as intended - this relates to WCAG (A) success criterion 1.3.1
-
some ARIA roles are not contained by their required parent element, meaning assistive technology may not function as intended - this relates to WCAG (A), success criterion 1.3.1
What we’re doing to improve accessibility
We have identified the areas of this system that need to be addressed in order to meet accessibility standards; we're working with our suppliers to rectify known issues as soon as possible.
Preparation of this accessibility statement
This system was last tested prior to initial launch 11 June 2024; tests were carried out by our Web Services Team, and this statement prepared on 21 June 2024.
Re-assessment will be undertaken whenever this system undergoes a major modification.