Accessibility statement
This statement explains how we have designed and tested the Branch website, what remains outside our control, and how to report an accessibility problem.
Accessibility information
Our approach
We want people to be able to use this website regardless of the device, input method or assistive technology they rely on. Accessibility is part of our normal design and engineering work, and Web Content Accessibility Guidelines (WCAG) 2.2 Level AA is the standard against which we assess this site.
Assessment result
On 14 September 2026, we completed an assessment of all 30 public Branch pages and the custom error page against every WCAG 2.2 Level A and Level AA success criterion. The Branch-authored content met all 34 applicable criteria, while 21 criteria did not apply because the site has no audio, video, native form, authentication, time limit, dragging or motion-operated input.
The technologies relied upon are HTML, CSS and JavaScript. The assessment covered desktop and mobile layouts, including the shared navigation, dialogs, FAQ disclosures and screenshot viewer.
Conformance status
All content and functionality designed and maintained by Branch conforms to WCAG 2.2 Level AA. This covers the whole website apart from the optional Google Calendar appointment interface.
The booking interface is a separate service supplied and changed by Google, so its markup and behaviour sit outside our assessment and control. It is not loaded unless you choose to open the booking panel, and an accessible alternative is always available: email liam@branchagency.co.uk and we will arrange the call directly.
How the website has been built
The website has been designed to support keyboard and screen-reader use while remaining readable when text is enlarged or motion is reduced. In particular:
- Pages retain their content and core function when JavaScript is unavailable.
- Links, buttons, menus and dialogs can be reached and operated with a keyboard, with a visible focus indicator showing the current position.
- Menus and dialogs can be closed with Escape, and focus returns to the control that opened them.
- Pages use semantic landmarks, a logical heading structure and descriptive text alternatives for meaningful images.
- Colour combinations are checked for contrast against the colours with which they are actually displayed.
- The client list is static, decorative animation stops within five seconds, and motion is removed when a device is set to reduce motion.
How we assessed it
The review combined automated testing across every page with source inspection and manual checks. We tested semantic structure, accessible names and states, keyboard behaviour, focus order and return, colour contrast, reduced motion, target sizes, 320-pixel reflow and the WCAG text-spacing overrides.
The automated scan used axe-core 4.13.0 with its WCAG 2.0 A, WCAG 2.0 AA and WCAG 2.2 AA rules. Automated tools cannot identify every barrier, so their results formed one part of the evidence alongside manual checks and source inspection. The criterion-by-criterion record is maintained with the website source.
What the assessment found
We corrected narrow-screen grid overflow, removed automatic movement from the client list, limited the duration of decorative animation, added a non-colour indicator for the current navigation item and removed opacity changes that could temporarily lower text contrast.
We have not tested every combination of browser, operating system and assistive technology. Meeting WCAG does not guarantee that every person will encounter no barrier, which is why reports from people using the site remain important.
Accessibility in client projects
For client software, we agree accessibility requirements and testing scope for each project. Where a project needs to meet a particular standard or conformance level, that target and the evidence required should be stated explicitly in the proposal.
Tell us about a problem
If part of this website is difficult to use, email liam@branchagency.co.uk. Please include the page you were using, what you were trying to do and what happened. Details of your browser, device or assistive technology are helpful if you are comfortable sharing them, but they are not required.
You can also use the contact page to find our contact details.
We will acknowledge the report, investigate the problem and explain what we can do to address it or provide the information another way.
Reviewing this statement
Last reviewed: 14 September 2026.
We will repeat the relevant checks when the website changes and update this statement when the assessment scope, result or known limitation changes.