|Last updated:||13 May 2021|
This statement applies to content published on the www.buckscc.gov.uk domain. Other websites managed by Buckinghamshire Council will have their own separate accessibility statements.
As a minimum, you should be able to:
- zoom in up to 300% without problems
- navigate most of the website using just a keyboard
- operate most of the website using a screen reader
We’ve also tried to make the website text as simple as possible to understand.
For advice on making your device easier to use if you have a disability, visit AbilityNet.
Other Buckinghamshire Council websites
Specific issues relating to our other core websites can be found on their individual accessibility statements:
- www.buckinghamshire.gov.uk accessibility statement
- www.buckscc.gov.uk accessibility statement
- www.chiltern.gov.uk accessibility statement
- www.southbucks.gov.uk accessibility statement
- www.wycombe.gov.uk accessibility statement
How accessible this website is
www.buckscc.gov.uk is partially compliant with WCAG 2.1 AA standards. However, we are constantly working to improve both our compliance and the experience of our users.
We know some parts of this website are not fully accessible:
- Some online maps and mapping services cannot be easily navigated
- Some pages and documents are not clearly written or structured
- Some online tools may be difficult to use for assistive technologies
- Some videos do not have captions
- Some content such as images do not have good text alternatives
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email firstname.lastname@example.org.
We will consider your request and get back to you within 20 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’re not meeting accessibility requirements, contact: email@example.com
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 contact us with a complaint and you’re not happy with our response contact the Equality Advisory and Support Service (EASS).
Technical Information about this website’s accessibility
Buckinghamshire Council is committed to making its website 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, due to the following issues:
Parts of the website link to legacy county and district council websites. Some of these websites are not fully accessible.
Non-compliance with the accessibility regulations
Skip to main content link is missingSome pages can be reformatted for print. This template does not have a skip to main content link. This fails WCAG 2.1 Technique G1: Adding a link at the top of each page that goes directly to the main content area
Colour contrast is not sufficientText is too faint on some pages and can cause problems for users who are colour blind or have low vision. This fails WCAG 2.1 success criterion 1.4.3 Contrast (Minimum)
Link without a text alternativelinks to our Twitter feed on some pages do not have alternative text. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose in Context)
Headings are not structuredSome heading structures have been skipped on some pages. This fails WCAG 2.1 best practice.
Links are not clearly identifiableSome links are highlighted only by colour on some pages. Some people may be unable to a link if colour is its only distinguishing feature. This fails WCAG 2.1 success criterion 1.4.1 (Use of Colour)
No data cells assigned to table headerTables on some pages are missing headers. Users of assistive technologies may not have access to this information. This fails WCAG 2.1 success criterion 1.3.1 (Information and relationships)
Inline frame without a text alternativeInline frames on some pages are missing alternative text. Users of assistive technologies may not understand the iframe's purpose on the page. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value)
Container element is emptyContainers on some pages do not contain their required roles. This fails WAI-ARIA 1.1: 2.5 (Required Owned Elements)
Button without a text alternativeButtons on search pages do not have alternative text. Users of assistive technology may not have access to this information. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).
Role not inside the required contextOn the Waste Wizard, some roles are not presented correctly. This fails WCAG 2.1 success criterion 5.2.6 (Required Context Role)
Unhelpful image descriptionsImages 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).
Missing captions on videosSome videos do not have captions which can make them difficult to understand. This fails WCAG 2.1 success criterion 1.2.2 (Captions).
Inaccessible documentsMany documents are in less accessible formats, for example PDF. Non-HTML documents published on or after 23 September 2018 must have an accessible format.
Content that’s not within the scope of the accessibility regulations
Documents published before 23 September 2018
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or other documents we publish will meet accessibility standards. Where we are unable to publish accessible documents we will provide alternative methods to access this information.
We plan to fix any remaining issues with documents or replace them with accessible HTML pages as we migrate content over to our new website.
Third party content
Where we choose to feature third party content or functionality on our website, we are responsible for ensuring it meets accessibility standards. However, we are not responsible for the accessibility of third party platforms or content that is neither funded nor developed by us, or under our control. This includes:
- third party websites that we link to from this website and any of our other digital channels
- social media platforms
- data we supply to national databases
- third party content we are legally required to publish but is not in the control of Buckinghamshire Council
What we're doing to improve accessibility
We are working with our website developers to make this website as accessible as it can be. Large scale improvements have been made in recent months, however, we still have issues remaining that we are working to find solutions for.
We monitor our accessibility through Siteimprove, which helps us check our website and displays any accessibility issues against accessibility standards. Our web team will continue using Siteimprove to make improvements where necessary.
As part of the reorganisation of local government for Buckinghamshire, the county and district councils have been replaced by Buckinghamshire Council as of 1 April 2020.
Content currently hosted on the legacy council websites will be gradually transferred over to the new Buckinghamshire Council website where it will be republished as fully accessible content. Once this is complete, the current area websites for the district councils and county council will be decommissioned.
This is a gradual process and will take place over the next couple of years. In the meantime, we plan to improve the accessibility of our existing content alongside the migration of content to the new website. Furthermore, all new content published will be fully accessible.
We have begun hiring the team that will be carrying forward this content migration and hope to see significant improvements in the near future.
Preparation of this accessibility statement
This statement was prepared on 1 April 2020. It was last reviewed on 11 May 2021.