Accessibility Statement - Hazel Court HWRC online booking system

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 'Hazel Court Household Waste Recycling Centre (HWRC) online booking system', which allows customers of York Register Office to:

The functionality is provided by Stopford Information Systems.

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-compliances and non-accessible content

Currently:

  • there is some redundant title text which impacts screen reader users as it repeats information and therefore causes confusion - this relates to success criterion (A) 1.1.1 and (A) 4.1.2
  • there is an instance of an orphaned form label which means that there is a <label> element present but it’s not correctly associated with a specific input field (for example, text field) which makes it inaccessible for screen reader users - this relates to success criterion (A) 1.3.1
  • legends may not be included for all fieldsets, therefore information about content structure may not be conveyed to users of assistive technology - this relates to success criterion (A) 1.3.1
  • not all heading text is marked as a heading, therefore information about content structure may not be conveyed to users of assistive technology - this relates to success criterion (A) 1.3.1
  • there are instances of poor colour contrast which makes text difficult to understand for those who suffer from colour blindness - this relates to success criterion (AA) 1.4.3
  • not all functional elements are operable by keyboard due to the incorrect use of ARIA tabindex. This means that keyboard-only users cannot navigate the web pages sequentially - this relates to success criterion (A) 2.1.1, (A) 2.4.3 and (A) 4.1.2
  • there is an instance of a redundant link which impacts screen reader users as it repeats the link text and therefore causes confusion - this relates to success criterion (A) 2.4.4 and (A) 2.4.9
  • a noscript element has been used to define alternate content for users who have JavaScript disabled in their browsers or use a browser which doesn’t support JavaScript, this element should be applied correctly - this relates to success criterion (A) 3.2.1
  • some instances of ARIA live region or alerts may not successfully help notify assistive technologies when an input error occurs, this ensures all users are receiving real time updates - this relates to success criterion (A) 3.3.1
  • some ARIA buttons need to be checked to ensure that they function the same way as an HTML button element - this is especially important for keyboard only users - this relates to success criterion (A) 4.1.2
  • some ARIA labels may not provide a descriptive, accurate label. This makes it difficult for users of assistive technology to understand the function and meaning of the labelled item - this relates to success criterion (A) 4.1.2
  • some focusable elements, like buttons or links, are hidden using aria-hidden=”true”, this creates confusion for screen reader users as it removes the elements from the accessibility tree but not from the visual display, used for hiding icons and decorative text - this relates to success criterion (A) 4.1.2
  • some elements use incorrect ARIA roles, states and properties which means that the name, role and value cannot be programmatically determined and updated. This impacts those who use assistive technologies as some user interface components will not be compatible with their assistive technology because of this error - 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 statement was prepared on 27 February 2026.

This system was tested prior to launch in February 2026; tests were carried out by our Web Services Team.

Also see