The original Hatton Garden directory
List Your BusinessAdvertising Opportunities
HATTON GARDEN JEWELLERS
Directory
HATTON GARDEN JEWELLERS

The original Hatton Garden directory, est. 2003

Legal

Accessibility Statement

Last updated: 23 April 2026. Our commitment to making this website usable by everyone, including people with disabilities, in line with the Equality Act 2010 and WCAG 2.1 Level AA.

Hatton Garden Jewellers (operated by Teksyte LTD) is committed to making the Hatton Garden Jewellers website accessible to the widest possible audience, regardless of ability or technology. This statement explains our accessibility commitments, the standards we target, known limitations, and how you can report issues or request content in an alternative format.

01

Our Commitment

We believe the internet should be open and accessible to everyone. We are committed to providing a website that is usable by all visitors, including those using assistive technologies such as screen readers, screen magnifiers, switch devices, voice input and keyboard-only navigation. We treat accessibility as an ongoing programme of work, not a one-time audit.

This commitment is informed by our obligations under the UK Equality Act 2010, which requires service providers to make reasonable adjustments so that disabled people are not substantially disadvantaged when using a service. Although Hatton Garden Jewellers (operated by Teksyte LTD) is a private-sector publisher and not subject to the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, we choose to align voluntarily with the same standards.

02

Standard We Target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This standard covers the four principles of accessible web content:

  • Perceivable — information and interface components are presented in ways users can perceive (alt-text on meaningful images, captions, adequate colour contrast).
  • Operable — the interface can be used with keyboard alone, does not rely on timing, and avoids content that could trigger seizures.
  • Understandable — text is readable, behaviour is predictable, and errors are clearly explained.
  • Robust — content works with current and future assistive technologies.

Where WCAG 2.2 introduces new success criteria (e.g. 2.4.11 Focus Not Obscured), we adopt them as our baseline for new development.

03

Features We Provide

  • Semantic HTML landmarks (<header>, <main>, <nav>, <footer>, <aside>) so screen-reader users can jump directly to the main content.
  • A single, unique <h1> per page and a logical heading hierarchy.
  • Keyboard focus rings are visible on all interactive elements and are never suppressed by CSS.
  • Text on background colour meets WCAG AA contrast (≥ 4.5:1 for body text and ≥ 3:1 for large text / UI components). Our design tokens are reviewed for contrast before any new skin ships.
  • Meaningful images include descriptive alt text; decorative images use empty alt="" so assistive technologies can skip them.
  • Form inputs have associated labels; error messages are programmatically linked via aria-describedby.
  • Links are descriptive ("View listing", "Read full article") rather than generic ("click here").
  • Responsive layout that reflows at 400% zoom and 320 px viewport width without horizontal scroll, per WCAG 1.4.10 Reflow.
  • Respect for prefers-reduced-motion — animations and transitions are disabled for users who have set that preference in their operating system.
  • No autoplay audio or video.
  • Skip-to-content link available at the top of every page for screen- reader and keyboard users.
04

Known Limitations

Despite our best efforts some limitations remain. We are actively working on them:

  • Third-party embeds. Embedded maps (OpenStreetMap), payment widgets and some social-media previews are provided by third parties and their accessibility is outside our direct control. Where possible, we provide a text equivalent (e.g. full street address alongside the map).
  • Legacy imported content. Some blog posts migrated from our earlier WordPress installation may have incomplete alt-text or heading hierarchy. We are auditing and fixing this content on a rolling basis as we re-publish it.
  • User-supplied content. Listing owners submit their own business descriptions, logos and photographs. We prompt for alt-text at upload time but cannot guarantee that every submitted image has a meaningful description.
  • PDF documents. Where we publish PDF brochures, older PDFs may not be fully tagged for screen readers. A text-equivalent web page is provided alongside each PDF where feasible.

If any of these limitations prevents you from using a specific feature, please contact us (see section 08) and we will provide the information you need in an accessible format within 5 business days.

05

How We Test

Accessibility testing is integrated into our development process through a combination of:

  • Automated scanning (axe-core, Lighthouse) as part of the build pipeline — any page scoring below 95 on accessibility triggers a manual review;
  • Manual keyboard-only navigation testing on every new template;
  • Screen-reader verification with NVDA (Firefox) and VoiceOver (Safari) for the main user journeys: browse directory → open a listing → submit a contact form;
  • Colour-contrast verification using WCAG-compliant tooling on every new design;
  • Quarterly full-site audits covering random sample pages and the latest editorial content.
06

Assistive Technology Support

We have tested the Service with the following combinations and aim to support them:

  • Latest two versions of Chrome, Firefox, Safari and Microsoft Edge on desktop;
  • Latest two versions of Mobile Safari (iOS) and Chrome for Android;
  • NVDA + Firefox, JAWS + Chrome, VoiceOver + Safari, Narrator + Edge, TalkBack + Chrome for Android;
  • Dragon NaturallySpeaking for voice input;
  • Keyboard-only navigation in all supported browsers.
07

Requests & Alternative Formats

If you need information from this website in a different format — such as large print, easy read, audio recording or braille — please contact us. We will try to respond within 7 days. Where the requested content is complex (for example a long legal document), we may need more time but will keep you informed.

08

Report an Accessibility Problem

We welcome feedback. If you find something on the Service that is not accessible, please tell us what happened, which page you were on and what device/browser/assistive technology you were using:

09

Enforcement Procedure

If you contact us with a complaint and you are not satisfied with our response, you can contact the Equality and Human Rights Commission (EHRC), which is responsible for enforcing the Equality Act 2010. They can be contacted via the Equality Advisory and Support Service (EASS), the UK government's equality-law advice line.

10

Preparation & Review

This statement was originally prepared on 1 March 2025 and is reviewed at least every 12 months, and whenever we make a significant change to the Service. The last review was conducted on 23 April 2026 using a combination of automated tooling (Lighthouse, axe-core, WAVE) and manual testing with NVDA and VoiceOver.

Our Featured Partners

We use cookies and analytics to understand how the site is used and to keep the service free. Choose Accept All to allow this, or Essential Only to use just the cookies we need to keep the site working. You can change your choice any time in our Cookie Policy