Accessibility

Accessibility Statement

This website is run by the Borough of Broxbourne Council. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:

• zoom in up to 300% without problems
• navigate most of the website using just a keyboard
• navigate most of the website using speech recognition software
• use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

Parts of this website are not fully accessible. For example:

• some pages and document attachments are not written in plain English
• some tables do not have row headings
• some heading elements are not consistent
• some images do not have image descriptions

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

Enforcement procedure

If you contact us with a complaint and you’re not happy with our response contact the Equality Advisory and Support Service (EASS).

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

Technical information about this website’s accessibility

The Borough of Broxbourne Council is committed to making its websites 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.1 AA standard.

Non-accessible content

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

1. some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships)
2. images on some pages do not always have suitable image descriptions. Users of assistive technologies may not have access to information conveyed in images. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)
3. some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.4.2 success criterion (Page Titled)
4. the change in the default written language is not correctly identified on some pages. This means screen readers will not read content correctly. This fails WCAG 2.1 success criterion 3.1.2 (Language of Parts)
5. translation Navigation is inconsistently named. This fails WCAG 2.1 success criterion 3.2.4 (Consistent Identification)
6. some pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways)
7. some pages have inconsistently-placed language navigation. This fails WCAG 2.1 success criterion 3.2.4 success criterion (Consistent Identification)
8. some content looks like headings but is not. This makes it difficult for screen reader users to navigate the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
9. some pages have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.1 (Use of Colour)

Content that’s not within the scope of the accessibility regulations

Non-HTML documents published before September 2018 do not need to be accessible – unless users need them to use a service.

How we tested this website

We used the Web Content Accessibility Guidelines V2.1 level A and level AA to test our website’s accessibility.

We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to decide on a sample of pages to test.

We also tested a sample of pages involved in applying for licences.