Skip to content

Accessibility

Accessibility at Quoin

Our target is WCAG 2.2 AA. Here is the current state, the known gaps, and how to tell us about barriers you encounter.

The standard we target

We build the Quoin website to conform with Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level, the guidelines published by the W3C for making web content usable by people with visual, auditory, motor, and cognitive disabilities.

What is in place today

  • Semantic HTML with a logical heading order (one H1 per page, nested H2 / H3).
  • Real landmarks: <header>, <nav>, <main>, <footer>.
  • A skip-to-content link, available as the first focusable element on every page.
  • Visible focus indicators on every interactive element (2 px accent outline, 2 px offset).
  • Color contrast verified at WCAG AA or better for body text and UI.
  • prefers-reduced-motion is respected. Scroll-entry fade animations are disabled for visitors who request reduced motion.
  • Responsive layouts from 320 px through 1440 px; zoom to 200 % supported without loss of content.
  • Meaningful images have descriptive alt text; decorative images are marked as such.
  • Form fields have visible labels (not placeholder-only) and clear validation messages.
  • Navigation works end-to-end with a keyboard; no mouse-only interactions.

Known gaps

As of April 2026:

  • No automated accessibility regression tests in CI yet. We run manual audits with axe DevTools and VoiceOver/NVDA before each deploy.
  • Some third-party content (e.g., embedded LinkedIn links) inherits the accessibility posture of the source site, which we do not control.

We update this page when gaps are fixed or new ones are found.

If you hit a barrier

Email accessibility@quoinbuildings.com. Tell us what you were trying to do and what went wrong. A page URL and a short description are enough. We will acknowledge within two business days and tell you when we expect to have it fixed.

If you need the content of this site in a different format (larger text, plain document, a phone call), ask at the same address.

How we review

We audit the site manually at least once per quarter and whenever we ship a significant change to a shared layout, component, or navigation pattern. Results are not published, but we will share audit findings on request.