This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Accessibility Statement
Please see below for accessibility considerations in creating this website. If you find any accessibility issues, or think we are not meeting your accessibility requirements, please contact us.
All accessibility considerations
Screen-reader compatible web pages: Web pages are readable by electronic “screen readers” — which are devices commonly used by the visually impaired to surf the internet.
Links should be visually identifiable: Links are visually identifiable and distinguishable from the standard copy.
Correct semantic HTML element structure is used for content: The correct element for the current context has been chosen to create a good web experience. Correct heading tags are used to create a comprehensible page structure. Headings do not skip a level. All pages have a <h1> tag which describes the page.
Alt-tagged Images: Images should have “alt tags” (a type of metadata) which help visually-impaired users to identify the image via text or via a screen reader. Some archive images migrated from the Bristol Bites Back Better website may not have alt-tags, but these will be updated by January 2024.
Style sheet independence: Web pages should not need a stylesheet to display in a way that is understandable. They should be readable to screen readers, most of which cannot load style sheets.
Accessible forms: Web forms are usable even without a mouse, and each field is labeled. Descriptive error explanations are used close to the invalid input.
Text and background colour should have sufficient contrast: Text and background colour has an optimal contrast ratio so that it can be read by people with moderately low vision. Text has a contrast ratio of at least 4.5:1 with the background. Colour contrast passes WCAG AA success criterion (AAA for mobile).
Content scales properly when zoomed/enlarged: Content should be readable when a page is zoomed up to 200% and the page should not visually break when using these constraints.
Using a descriptive title tag: Web pages have a title tag that accurately describes the page function or purpose. The title is typically the first content read by screen readers when the page is loaded.
Keyboard-friendly browsing: The Bristol Good Food 2030 website isn’t reliant on the usage of a mouse or touchpad. Users who wish to navigate using only keyboard keys should be able to do so.
Harmless website design: The website does not serve images or videos that can cause seizures.
Use ARIA landmarks where applicable: Accessible Rich Internet Applications (ARIA) allow assistive technologies to convey appropriate information to people with disabilities. ARIA in HTML is a combination of ‘roles’ (which identify an element’s purpose) and ‘aria’ attributes (which describe things about it and what it’s up to).
Links should be descriptive and provide intent: Links with non-descriptive text (for example ‘Click Here’) have been avoided – however, there may still be examples of migrated legacy content that uses non-descriptive text. The link should describe where the user will go when clicking (or tapping on a mobile device).
Use the HTML lang attribute: The HTML lang attribute (<html lang=”en”>) is used to identify the language of text content on the web. This information helps screen readers switch language profiles to provide a better user experience.
Limit or remove any flashing elements.
Avoid mouse only interactions: The website does not rely on hover states to convey information as this approach is not screen reader, keyboard or mobile accessible.
The Bristol Good Food 2030 website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. Non-compliance is as follows:
- Some form inputs are not keyboard operable (date picker).
- Some legacy videos do not contain captions.
- There may be legacy documents that are hard to read or navigate.