Find out what we are doing to make our website as accessible as we can and where we have identified areas for improvement.

This statement covers our website at www.rushmoor.gov.uk 

The purpose of our website is to provide our customers with online services and information.  

We are committed to making our website as accessible as possible for people with visual, hearing, cognitive and motor impairments.  

You are able to: 

  • Change colours, contrast levels and fonts 
  • Zoom in up to 200% without the text spilling off the screen 
  • Navigate most of the website using just a keyboard 
  • Navigate most of the website using speech recognition software 
  • Navigate the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver) 

We have also made the website text as simple as possible to understand. 

The My Computer My Way  website has advice on making your device easier to use if you have a disability. 

How accessible the website is

Although we regularly test our online platform to the WCAG 2.1 guidelines to ensure it works on both desktop and mobile devices, currently there are some barriers that may prevent disabled users’ access to the website, such as: 

  • On forms, changes to content are not updated for screen reader users 
  • On forms, radio buttons that form a natural group are not grouped programmatically 
  • Menu navigation buttons do not convey their state to users 
  • Some PDF documents are not fully accessible to screen reader software 

Feedback and contact information

If you need information on this website in an alternative format, such as accessible PDF, large print, easy read, audio recording or braille: please contact us by: 

We will look into your request and get back to you within 10 working days. 

Reporting accessibility problems with this website

We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please contact webteam@rushmoor.gov.uk. 

Enforcement procedure

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’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS). 

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, please contact us by sending an email using the contact details on this page.   

Enforcement procedure

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').

If you're not happy with how we reply, you can Equality Advisory and Support Service

Technical information about this website’s accessibility

We are committed to making our website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance status

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances are listed below.

Page content and design 

  • Content images don’t have appropriate alt text.  This fails under: 1.1.1 Non-text Content (Level A). 
  • Heading order is illogical. This fails under 1.3.1 Info and Relationships (Level A) and 2.4.6 Headings and Labels (Level AA) 
  • Text cannot be resized without loss of content. This fails under 1.4.4 Resize text (Level AA)
  • Colour contrast on UI elements is insufficient for users with low vision. This fails under 1.4.11 Non-text Contrast (Level AA) 
  • Content becomes lost or obscured at low resolution or scrolling in 2 dimensions is required (reflow 320 x 256) This fails under 1.4.10 Reflow (Level AA)
  • Focus order is incorrect or illogical. This fails under 2.4.3 Focus Order (Level A) 
  • Email addresses or phone numbers are not linked. This fails under 1.3.1 Info and Relationships (Level A) 
  • Code quality issues (parsing) mean that some of the content may not be accessible via software used by people with disabilities. This fails under 4.1.1 Parsing (Level A) 

Side menu

  • Keyboard access is possible but it's not intuitive. This fails under 2.1.1 Keyboard (Level A) 
  • Expanding controls need appropriate name, role and value. This fails under 4.1.2 Name, Role, Value (Level A) 

Search results page

  • There are some problems with the consistency and operation of components. This fails under 3.2.3 Consistent Navigation (Level AA) and 3.2.4 Consistent Identification (Level AA) 

Home Page

  • Colour contrast of text is insufficient for users with low vision. This fails under 1.4.3 Contrast (Minimum) (Level AA) 
  • Text cannot be resized without loss of content. This fails under 1.4.4 Resize text (Level AA) 
  • Hidden elements gain keyboard focus. This fails under 2.4.7 Focus Visible (Level AA) 
  • Focus order is incorrect or illogical. This fails under 2.4.3 Focus Order (Level A) 
  • Content becomes lost or obscured at low resolution or scrolling in 2 dimensions is required (reflow 320 x 256) This fails under 1.4.10 Reflow (Level AA) 

Find my councillor

  • Text and images that are found together and that serve the same purpose should be combined. This fails under 1.1.1 Non-text Content (Level A) 
  • Content becomes lost or obscured at low resolution or scrolling in 2 dimensions is required (reflow 320 x 256) This fails under 1.4.10 Reflow (Level AA) 

Accordions

  • Neutral markup is used for interactive elements this fails under 1.3.1 Info and Relationships (Level A) and 4.1.2 Name, Role, Value (Level A) 
  • Focus order is incorrect or illogical. This fails under 2.4.3 Focus Order (Level A) 

Forms

  • Fieldset and Legend are being used inappropriately. This fails under 3.3.2 Labels or Instructions (Level A) and 4.1.2 Name, Role, Value (Level A) 
  • (HTML) Groups of related form fields are not grouped using Fieldset and Legend. This fails under 1.3.1 Info and Relationships (Level A), 3.3.2 Labels or Instructions (Level A) and 4.1.2 Name, Role, Value (Level A) 
  • (ARIA) Radio button choices are not grouped using ARIA radiogroup. This fails under 1.3.1 Info and Relationships (Level A), 3.3.2 Labels or Instructions (Level A) and 4.1.2 Name, Role, Value (Level A) 
  • Instructions for completing the form are marked up inappropriately. This fails under 1.3.1 Info and Relationships (Level A) and 3.3.2 Labels or Instructions (Level A) 
  • When a user submits a form and an error is detected, non-sighted users aren't aware of the error notification. This fails under 3.3.1 Error Identification (Level A), 3.3.3 Error Suggestion (Level AA) and 4.1.3 Status Messages (Level AA) 

Recycling directory

  • List markup is misused. This fails under 1.3.1 Info and Relationships (Level A) 
  • Labels for form fields are missing or are not accurate. This fails under 1.3.1 Info and Relationships (Level A), 2.4.6 Headings and Labels (Level AA) and 3.3.2 Labels or Instructions (Level A) 
  • Dynamic changes or status updates are not being conveyed to assistive technologies. This fails under 1.3.3 Sensory Characteristics (Level A) and 4.1.3 Status Messages (Level AA) 

Find my bin collection day

  • Focus order is incorrect or illogical. This fails under 2.4.3 Focus Order (Level A) 

Download a copy of your bin calendar 

  • Content images don’t have appropriate alt text.  This fails under: 1.1.1 Non-text Content (Level A). 
  • Tabular data is provided using list markup. This fails under 1.3.1 Info and Relationships (Level A) 
  • Colour contrast across borders of interactive elements is insufficient for users with low vision. This fails under 1.4.11 Non-text Contrast (Level AA) 
  • The primary language of the page has not been identified. This fails under 3.1.1 Language of Page (Level A). 

Houses in multiple occupation list

  • Too much interactive content is grouped. This fails under 1.3.1 Info and Relationships (Level A) 

Find my polling station

  • Links are not visually distinct. This fails under 1.4.1 Use of Color (Level A)

What we are doing to improve accessibility

We are doing the following to improve the accessibility of our website: 

  • We have conducted an external audit (with Dig Inclusion) to evaluate the current state of our website 
  • We have had accessibility training to better understand existing accessibility issues that are present on our website
  • We are planning to fix the issues based on the external audit by November 2022
  • When we publish new content, we will make sure all features meet accessibility standards

Preparation of this accessibility statement

This statement was prepared on 9 May 2022. It was last reviewed on 9 May 2022. 

This website was last tested on 5 May 2022. The test was carried out by  Dig Inclusion Ltd (diginclusion.com).  

You can read the full accessibility test report on the DigInclusion website. 


Contact us