Accessibility Statement

Last updated: [23/04/2026]

The short version: We believe a website that can't be used by everyone is a website that isn't finished. We build BuildForLeads.com - and every site we build for clients - with accessibility as a core requirement, not an afterthought. This page explains what we've done, where we fall short, and how to tell us when we get it wrong.

1. Our commitment

Roughly one in five people has a disability that affects how they use the web. We believe your website should work for all of them - and that means ours should too. Accessibility isn't a checkbox we tick at the end; it's part of how we design, build, and test every page.

2. The standard we aim for

We design and build to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is the internationally recognised standard for web accessibility and the benchmark referenced by the UK Equality Act 2010 and the US ADA.

Level AA means the site should be usable by people who:

- Use screen readers (such as NVDA, JAWS, or VoiceOver)

- Can't use a mouse and navigate with a keyboard only

- Have low vision and need high contrast or larger text

- Are colour-blind

- Have cognitive differences that benefit from clear, predictable layouts

- Are Deaf or hard-of-hearing and rely on captions for video

3. What we do to meet it

- Semantic HTML — proper headings, landmarks, and labels so screen readers can navigate the page

- Colour contrast — our dark green on cream and mint on dark green palette is tested to meet or exceed 4.5:1 contrast for body text

- Keyboard navigation — every link, button, form field, and interactive element can be reached and operated using a keyboard

- Alt text on images — every meaningful image has a text description; decorative images are marked so screen readers skip them

- Captions and transcripts — our videos include captions, and we provide transcripts on request

- Clear language — we write in plain English, avoid jargon where we can, and explain industry terms when we use them

- Focus indicators — when you tab through the page, the currently focused element is visibly highlighted

- Form labels — every form field has a proper label associated with it, not just placeholder text

- Responsive design — the site works at any screen size and supports browser zoom up to 200% without breaking

4. Known limitations

We're honest about where we're not perfect. At the time of this statement's last update, we're aware of the following:

- Some third-party embedded content (such as booking widgets) may not be fully WCAG AA compliant. We've raised this with the vendor and are monitoring their progress.

If you find a barrier we haven't listed, please tell us - see section 6.

5. Compatible assistive technologies

We test our site with:

- Screen readers: NVDA on Firefox (Windows), VoiceOver on Safari (macOS and iOS)

- Browsers: current versions of Chrome, Safari, Firefox, and Edge

- Keyboard-only navigation across all major browsers

- Automated tools: axe DevTools and Lighthouse accessibility audits

We don't claim compatibility with every assistive technology, but if something doesn't work for yours, we want to hear about it.

6. How to tell us about problems

If you come across a page that's hard to use, a video without captions, a form that won't submit with your screen reader, or anything else - email us.

Email info@buildforleads.com with:

- The page URL

- What were you trying to do

- What went wrong

- What assistive technology were you using (if any)

We aim to acknowledge within 2 business days and fix confirmed issues within 10 business days.

7. Our approach to client sites

Because BuildForLeads is an agency, our approach matters beyond this site. Every website we build for a client is developed to WCAG 2.2 AA. We use the Duda platform, which provides an accessible foundation, and we layer our own standards on top. Clients receive an accessibility check as part of every build.

8. How do we keep this current

We review this statement at least once a year, and any time we make a significant change to the site. The "last updated" date at the top of the page is always accurate.