Accessibility
Accessibility statement
We aim for the Guavas website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We build and test new pages against that standard, but the site does not meet it everywhere yet. This page lists the problems we know about. If something does not work for you, email info@guavas.co.uk.
Last updated: November 2026
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. These guidelines, published by the W3C, set out how to make websites easier to use for people with a wide range of needs, including people who use a screen reader, a keyboard instead of a mouse, or magnification.
We do not claim the site meets that standard in full. Where we know it falls short, we say so below.
What we have built in
On the pages of our new website:
- a "Skip to main content" link is the first thing on every page, and it works with JavaScript switched off
- every link, button and form field shows a clear outline when you move to it with the keyboard
- if your device is set to reduce motion, animations and transitions are switched off
- pages use real headings, lists and tables, so screen readers can read their structure
- tables have proper header cells
- images carry text descriptions
- every field on our quote form has a label, error messages are announced to screen readers, and the form still works when the page is zoomed to 200%
- body text is dark charcoal on a light background, well above the minimum contrast the standard asks for
- we write in plain English
How we test it
We check pages with axe, an automated accessibility tester, against the WCAG 2.2 AA rules. Our build rules say a page must have no critical or serious problems in that scan, apart from the known issues listed below. Where part of a page only appears after you interact with it, such as the company search on the quote form, the test carries out that step first and then scans.
We also review each new page by eye at desktop and phone widths, and check by hand for problems the automated scan rates as less serious.
Automated testing finds many problems but not all of them, so we also rely on you telling us when something does not work.
Known problems
These are the parts of the site we know do not meet WCAG 2.2 AA.
- Button text contrast. Our main buttons, including "Get a quote", have white text on our brand green, and our second-tier buttons have white text on peach. The contrast is about 2 to 1 on green and about 2.1 to 1 on peach. WCAG 2.2 AA asks for at least 4.5 to 1 for normal-sized text. This was a design decision and the buttons are excluded from our automated contrast check.
- Peach accent text. Some short accent words and labels in peach on a light background have a contrast of about 2 to 1. This affects the highlighted word in the main heading on the home page, some accent text on the quote page, and the labels in the facts list on the contact page.
- Link hover colour. When you hover over a link in body text, it changes to a darker green with a contrast of about 3.4 to 1, below the 4.5 to 1 minimum. The link stays underlined.
- The home page is not yet covered by our automated scan.
- Older pages. Some pages from our previous website are still being served while we move them across. They were not built or tested to the standard on this page.
- Documents. Pages on the new website do not link to PDF documents. Older pages from our previous website may; we have not tested those documents.
Changing colours and text size
You can make text larger with your browser's zoom (Ctrl and + on Windows, Cmd and + on a Mac). If you find our colours hard to read, your device's own contrast and colour filter settings work on this site; we do not add our own colour modes.
Tell us about a problem
If you have trouble using any part of this site, or you need something from it in a different format, email info@guavas.co.uk.
Please tell us:
- the page, or what you were trying to do
- what went wrong
- the device, browser and any assistive technology you were using
If you would rather speak to someone, our phone number is on our contact page.