Accessibility statement for Visit Aylesbury
This accessibility statement applies to www.visitaylesbury.co.uk
This website is run by Buckinghamshire Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts using the accessibility widget
- zoom in up to 300% 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
- Dyslexia Font can be accessed using the accessibility widget.
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website 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
This website 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 issues on linked pages
- some content not included in landmarks
- some landmarks are not distinguishable
- some duplicate link text
- some input fields do not have descriptions
- associated input elements are not grouped
- incorrect mark up is used for bold and italic text
- some element IDs are duplicated
- some empty heading elements used
- some images do not have alt text
- some of our link text doesn’t explain the purpose of the link
- some of our online forms are difficult to navigate using just a keyboard
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: communications@buckinghamshire.gov.uk
call: 01296 585 008
Write to: Visit Aylesbury, Communications, Buckinghamshire Council, The Gateway, Gatehouse Road, Aylesbury, HP19 8FF
We’ll consider your request and get back to you in 7 working days.
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, email communications@buckinghamshire.gov.uk and mark your email ‘Visit Aylesbury Accessibility’, call 01296 585 008 and ask to speak to the Place Marketing Officer or use the reporting function in the Accessibility Widget.
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).
Contacting us by phone or visiting us in person
If you can’t hear or speak on the phone we provide a text relay service: 18001 01296 395000.
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.
Compliance status
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Forms
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Non-compliance with the accessibility regulations
Some input fields do not have descriptions
Input fields such as the search bar do not have appropriate descriptions that can be interpreted by assistive technologies. (4.1.2)
Associated input elements are not grouped
Input elements, such as those in the review section of pages, have not been grouped together correctly. (3.2.2)
Incorrect mark-up is used for bold and italic text
The and tags are used to format bold and italic text. This may be a barrier to assistive technologies. (1.3.1)
Some element IDs are duplicated
Some of the attributes used to identify elements are used more than once on the same webpage. (4.1.1)
Some empty heading elements are used
On some pages there are
and
elements used that do not contain any text. (1.3.1)
Some images do not have appropriate alt text
Some images, specifically those used as image links, do not have appropriate alternative text. (2.4.4)
Some link text doesn’t explain the purpose of the link
There are examples of insufficient link text on this website. (2.4.9)
Content not included in landmarks
Content on some of our webpages is not included in the WAI-ARIA landmarks throughout the page. We are working to resolve this with help from our developers. (1.3.1)
Duplicate link text
Link text is occasionally duplicated. We are working to resolve this with help from our developers. (2.4.4)
Navigation and accessing information
It’s not possible for users to increase text size beyond 200% without some of the content overlapping.
Interactive tools and transactions
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Our forms are built and hosted through third party software and ‘skinned’ to look like our website.
Disproportionate burden
Not applicable.
Content that’s not within the scope of the accessibility regulations
Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations
What we’re doing to improve accessibility
We monitor accessibility using automated checks via Siteimprove and manual checks. We also test this website regularly with real users.
Preparation of this accessibility statement
This statement was prepared on 9 November 2020. It was last reviewed on 3 March 2021.
This website was last tested on 28 January 2021. We performed our own testing using automated checks via Siteimprove and manual checks. All pages were tested.