Accessibility Statement

Effective date: 21 July 2026

We build software for other people, so it would be a poor showing if our own site were hard to use. This statement sets out where codebunnies.com stands against the Web Content Accessibility Guidelines, how we tested it, and what we know is imperfect.

The standard we hold ourselves to

We target WCAG 2.1 Level AA. As of the date above, automated and manual testing found no Level A or AA failures on the pages listed below. We are not claiming formal certification, and no third party has audited us; this is our own testing, described honestly so you can judge it.

How we tested

• Automated testing with axe-core against the WCAG 2.1 A and AA rule sets, across fourteen pages: the home page, About, Services, Work, Contact, Start a project, Our stack and its explainer pages, Blog, Careers, Areas we serve, and the Privacy, Cookie and Security policies.
• Manual keyboard testing: tab order, focus visibility, and reaching every interactive control without a mouse.
• Reflow testing at 320px width, checking no page requires horizontal scrolling.
• Verification that the site honours prefers-reduced-motion, so animations are suppressed for visitors who ask their operating system to reduce motion.
• These checks run as part of our automated test suite, so a regression fails the build rather than waiting to be noticed.

What that gives you

• Every page has a skip link, so keyboard users can jump straight past the navigation.
• Text meets or exceeds the 4.5:1 contrast minimum, and larger text and interface elements meet their thresholds.
• Headings describe the structure of each page rather than being chosen for their size.
• Images carry alternative text, and decorative images are hidden from screen readers instead of being announced as noise.
• Every interactive element shows a visible keyboard focus indicator.
• Pages reflow to a 320px viewport without horizontal scrolling, and remain usable when text is enlarged.

Where we fall short

We would rather list these than let you find them.

• Automated testing has limits. Tools such as axe reliably catch perhaps a third to a half of accessibility problems. Judgements about whether alt text is genuinely useful, or whether the reading order makes sense, need a person, and we have not commissioned an independent audit.
• The embedded map on our contact page is a Google Maps iframe. We do not control its markup or its keyboard behaviour. Our full address and telephone number are given in text directly beneath it, so nothing depends on being able to use the map.
• Code samples use syntax colouring, and dimmer tones such as comments can fall below the contrast threshold within those samples. They illustrate our work and never carry information you need; the surrounding prose explains everything.
• Faint watermark numerals sit behind some cards and process steps, and the large "404" on our not-found page. These are well below the contrast threshold by design. WCAG exempts text that is purely decorative, and nothing depends on reading them: the ordering is already carried by the page structure and the headings beside them. They are hidden from screen readers and excluded from our automated checks, which is why we are telling you about them here.
• The editable code snippet on our home page is a decorative easter egg. It is reachable by keyboard and labelled, but nothing is lost by skipping it.
• We have not yet assessed the site against WCAG 2.2, which adds further criteria.

Telling us about a problem

If any part of this site is difficult to use, please tell us and we will fix it. We would genuinely rather hear about it than not.

Email info@codebunnies.com or call 0333 015 6610, Monday to Friday, 9:00 AM to 5:00 PM. We aim to reply within one business day. If you need anything on this site in another format, ask and we will provide it.

Legal position

The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to public sector organisations rather than to private companies such as ours, so this statement is voluntary. We also have duties under the Equality Act 2010 to make reasonable adjustments, which we take seriously.

Keeping this current

We review this statement whenever the site changes materially, and update the effective date above when it does.