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.
Compliance status
This part of our website is partially compliant with the Web Content Accessibility Guidelines (WCAG); non-compliances are listed.
Non-compliance with the accessibility regulations
Currently:
- some image elements inside hyperlinks have alternative text that duplicates the content of a text link inside or beside it - this relates to success criterion (A) 1.1.1
- we need to check the use of <noscript> elements; this element needs to be checked to ensure the scripted content is accessible - this relates to success criterion (A) 1.1.1
- 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 using the 'for' attribute; this means that screen readers, for example, cannot announce field purposes and therefore causes confusion - this relates to success criterion (A) 1.1.1, (A) 1.3.1 and (A) 4.1.2
- some ARIA roles may not exist inside their required context; this impacts users of assistive technologies who depend heavily on the correct structure and semantics provided by ARIA to understand and navigate the content - this relates to success criterion (A) 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 success criterion (A) 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 success criterion (A) 1.3.1
- We need to ensure that aria-expanded is used correctly (typically on a button that controls expandable content) and that the value (true or false) reflects the expansion state; this ensures that assistive technologies understand dynamic states of content which makes interactive elements navigable and understandable - this relates to success criterion (A) 1.3.1 and (A) 4.1.3
- some broken ARIA references appear in the code; this means that those who use screen readers to convey information will find it difficult because the user will lose essential context, labels or descriptions - this relates to success criterion (A) 1.3.1, (A) 2.4.4 and (A) 3.3.2
- Some ARIA labels need checking to make sure that non-text content and controls have accessible names; this means that assistive technologies can convey their purpose clearly - this relates to success criterion (A) 1.3.1 and (A) 4.1.2
- Some instances of inappropriate colour contrast exist, meaning potential reduced readability if you have low vision (if not using contrast-enhancing assistive technology) - this relates to success criterion (AA) 1.4.3
- At 400% some items are not responding appropriately; they do not reflow correctly, meaning users with low vision will not have the same options available to them - this relates to success criterion (AA) 1.4.10
- Some links cannot be reached by keyboard; this means that not all information can be reached by users who require a keyboard to operate the interface - this relates to success criterion (A) 2.1.1
- Some ARIA tabindex needs to be checked; ensuring that all functionality of the content can be operated by a keyboard and navigate it in the correct order – this relates to success criterion (A) 2.1.1 and (A) 2.4.3
- some redundant title text is present; meaning a confusing and repetitive user experience for users of assistive technologies - this relates to success criterion (A) 2.4.2
- Some links do not have discernible text; this means that the destination or the function of the link is not always clear to users - this relates to success criterion (A) 2.4.4
- some redundant links are present; this means that users may hear the same link multiple times or keyboard users may have to navigate through redundant links which is inefficient - this relates to success criterion (A) 2.4.4 and (A) 3.3.7
- some heading elements are not in a sequentially descending order and fail to convey the semantic structure of the page; this makes it harder to navigate and understand content when using assistive technologies - this relates to success criterion (AA) 2.4.6
- some ID attributes are not unique and may cause errors; this is problematic for assistive technologies trying to parse content - this relates to success criterion (A) 4.1.1
- some ARIA attributes do not have valid values; this means that assistive technologies cannot convey the appropriate information - this relates to success criterion (A) 4.1.2
- some ARIA attributes need checking to ensure the name and role can be programmatically determined by assistive technologies, and that states, properties, and values that can be set by the user can be programmatically set and notification of changes to these items is available; this means that assistive technologies can gather appropriate information about, activate (or set) and keep up to date on the status of user interface controls in the content - this relates to success criterion (A) 4.1.2
- elements with role=”button” need to be checked to ensure that buttons work properly even if they are a <div> or <span>; this ensures that all users can interact with the page properly and understand when there is a selection to be made - this relates to success criteria (A) 4.1.2
- we need to ensure interactive elements are programmatically identified and operable; this informs assistive technologies about the type of popup and therefore improves navigation and comprehension of content – this relates to success criterion (A) 4.1.2
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 in December 2025; tests were carried out by our Web Services Team, and this statement prepared on 5 January 2026.
Re-assessment will be undertaken whenever this system undergoes a major modification.
Also see
Comment on this page