Effective from: 25 July 2025 • First published and last reviewed on: 25 July 2025

1.0 Why this matters
1.1 We believe technology should welcome everyone. When our site is hard to use, that’s on us—not on you. This statement is our promise to keep improving and an open door to tell us where we fall short.

2.0 What is in scope
2.1 This statement covers what you use every day on GeiG.co.uk: the public pages, the signed-in account areas, and our browser-based cloud dashboards.
2.2 It also covers shared interfaces—navigation, forms, cookie banners, and our embedded 24/7 web chat.
2.3 It does not yet cover downloadable PDFs or manuals. If you need something we publish in another format, tell us (see 10.0) and we will make it happen.

3.0 The standard we aim for
3.1 We design and build to WCAG 2.2 Level AA. That’s the bar we set for new work and the lens we use to review existing pages.
3.2 When we ship something new, we check it against this standard before it reaches you.

4.0 Who is responsible and how to reach us
4.1 Our Web Platform team owns accessibility at GeiG.
4.2 You can contact us at support@geig.co.uk  or via 24/7 web chat on GeiG.co.uk.
4.3 We aim to respond to accessibility messages within 7 business days. If it’s urgent, say so—we’ll try to move faster.

5.0 How we build for access
5.1 We start with semantic HTML, clear labels, predictable focus, and keyboard-first journeys.
5.2 We pick colours for contrast, not just style, and we keep visible focus so you never lose your place.
5.3 Where motion exists, we respect “reduce motion” preferences.
5.4 Accessibility checks are part of our CI/CD gates—no passing tests, no shipping changes.

6.0 How we test and learn
6.1 We combine manual audits with automated checks, because people catch what tools miss and tools catch what people miss.
6.2 Our automated toolkit includes Ally and Elementor accessibility checks where applicable.
6.3 We also schedule third-party reviews to challenge our assumptions and validate fixes.

7.0 What you can expect to work
7.1 We support the latest two versions of Chrome, Edge, Safari, and Firefox.
7.2 We test with NVDA and JAWS (Chrome/Edge), VoiceOver (Safari), and TalkBack (Chrome).
7.3 On mobile, we rely on the same browsers where available. If you hit a blocker, tell us the device and browser and we’ll investigate.

8.0 Where we know we need to be better
8.1 Some legacy components may still have colour contrast that needs refinement.
8.2 A few complex forms may show missing or duplicate labels.
8.3 In some flows, focus order could better match the visual order.
8.4 The embedded web-chat may occasionally present keyboard traps or heading issues.
8.5 None of this is acceptable to us. We track these issues and fix them by priority (see 11.0).

9.0 About third-party embeds
9.1 We use third-party content (videos, maps, marketplace widgets). We configure what we can, but some embeds may not fully meet WCAG.
9.2 When possible, we add titles, captions, or alternatives so you still get the information.

10.0 If you need a different format or hit a barrier
10.1 Email support@geig.co.uk or use web chat and tell us what you need. Large-print or plain-text versions are available on request.
10.2 Please include the page link, the issue you faced, and your browser or assistive tech—this helps us fix things quickly.

11.0 How we prioritise fixes
11.1 Critical (you can’t complete a key task, no workaround): target fix within 10 business days.
11.2 Major (significant impact, but a workaround exists): target fix within 30 business days.
11.3 Minor (limited impact or cosmetic): grouped and shipped in our quarterly releases.
11.4 If we mis-scored your issue, tell us—we will re-grade it.

12.0 Improving every quarter
12.1 Accessibility is part of design and code review, not an afterthought.
12.2 Our designers, developers, and content authors complete annual accessibility training.
12.3 We review our accessibility backlog every sprint and formally re-check this statement quarterly.

13.0 The legal bit (kept simple)
13.1 We align our efforts with the Equality Act 2010 and UK guidance on digital accessibility.
13.2 This statement does not create extra legal rights beyond those laws and our other posted terms—but it does create a commitment from us.

14.0 If you’re not satisfied
14.1 Ask for an escalation to the Web Platform accessibility owner and we will review your case.
14.2 We do not list an independent mediation/ADR route in this statement. If that changes, we will update this section.

15.0 Dates and updates
15.1 First published and last reviewed: 25 July 2025.
15.2 We keep this statement current. When we make meaningful changes, we’ll update this page and the date above.

End of Accessibility Statement