Breadcrumb

Breadcrumbs

Website accessibility

Website accessibility

Website accessibility advice and our accessibility statement.

Accessibility statement

This statement applies to content published on the www.bristol.gov.uk domain. It doesn't apply to content on bristol.gov.uk sub-domains (for example maps.bristol.gov.uk).

This website is run by Bristol City Council. It's designed to be used by as many people as possible.

The text should be clear and simple to understand. You should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% and read the text
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader

We’ve made the text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

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

  • some pages and document attachments are not clearly written
  • some tables do not have row headers
  • some pages have poor colour contrast
  • some heading elements are not consistent
  • some images do not have good alternative text
  • some buttons are not correctly identified
  • some error messages are not clearly associated with form controls
  • many documents are in PDF format and are not accessible

We link to and use content provided by other websites and these are not always as accessible.

This includes:

How to request content in an accessible format

If you need information in a different format contact us and tell us:

  • the web address (URL) of the content
  • your name and email address
  • the format you need, for example, audio CD, braille, British Sign Language or large print, accessible PDF

Reporting accessibility problems with this website

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

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

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

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

Non-accessible content

Content that is not accessible is outlined below with details of:

  • where it fails the success criteria
  • planned dates for when issues will be fixed

Buttons

Some pages have buttons that don't have a correct role. This affects how they work with assistive technology.

This fails WCAG 2.1 A success criterion (Name, Role, Value). We'll find and fix these by the end of 2020.

Error messages

Some forms have error messages that aren't clear or linked to form controls.

This fails WCAG 2.1 A 3.3.1 success criterion (Error Identification). We'll find and fix these by the end of 2020.

Tables

Some tables don't have row headers when needed.

This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships). We'll find and fix these by the end of 2020.

PDF documents

Some essential service information is in PDFs.

We're identifying where information held on a PDF should be on a page on the website. We'll find and fix these by the April 2021.

Bins, recycling and street issue forms

We recently identified and have a plan to fix several accessibility issues with our bins and recycling forms.

  • There’s an issue with keyboard focus order when moving between form sub-pages that fails WCAG 2.1 success criterion 2.4.3 Focus Order.
  • The custom radio button controls fail against WCAG 2.1 success criteria 4.2.1 Name Role Value and 1.3.1 Information and Relationships.
  • Some form fields are missing autocomplete attribute value pairs which fails WCAG 2.1 success criterion 1.3.5 Identify Input Purpose. We have requested a form administration feature that will enable us to add these attributes to form fields.
  • Some link states and icon states need a higher background – foreground contrast ratio. This fails WCAG 2.1 success criteria 1.4.3 Contrast (Minimum) and 1.4.11. Non Text Contrast
  • We identified accessibility issues with the date-picker which fails on WCAG 2.1 success criteria 2.1.1 Keyboard Operability and 1.3.1 Information and Relationships.
  • We have requested an administration feature that will enable us to improve form error messaging, in order to meet WCAG 2.1 success criterion 3.3.3 Error Suggestions.
  • Some sub-headings in the forms are marked up as labels which fails success criterion 1.3.1 Information and Relationships.
  • We identified a few links that fail against WCAG 2.1 success criteria 1.1.1 Non Text Content and 2.2.4 Link Purpose

We have specified a solution to fix the accessibility issues identified for all bins, recycling and street issue forms.

We will fix some issues by end of November 2020. All issues will be fixed by February 2021.

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

The following content was published before September 2018 so it doesn't need to comply with accessibility requirements, unless it contains essential service information.

PDFs and other documents

Many documents are not accessible in a number of ways, including missing text alternatives or missing document structure

We're working to make sure that all future documents are compliant.

How we test this website

Website testing is carried out by our Web Team for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA.

We use several tools, including:

The website was also tested by the Shaw Trust before going live.

What we’re doing to improve accessibility

We aim to identify and fix issues in the timescales shown above.

This statement was last updated on 12 October 2020.