Accessibility
We build to WCAG 2.1 Level AA. We are not claiming to have met it, because no one has yet tested this site with a screen reader. Here is what is done and what is not.
The target
Web Content Accessibility Guidelines 2.1, Level AA. That is the standard this site is built against and measured against.
This is a statement of target and current state, not a claim of conformance. Some of the checks below are automated and run on every build. Others — the ones that need a person and a screen reader — have not been done. Both are listed honestly.
What is built and checked
These are enforced by automated gates that fail the build, not by good intentions:
- Contrast. Every text and background pairing in the palette is recalculated on every build. Body text clears 4.5:1 and the focus ring clears 3:1 on every ground the site uses. A colour change that drops a pairing below the threshold fails the build.
- Line length. Body text is capped at 70 characters, measured with the real glyph widths of the typeface rather than estimated.
- Touch targets. Controls are at least 44 by 44 pixels on touch devices, keyed on whether the pointer is coarse rather than on screen width — so a tablet or a landscape phone gets the same treatment as a phone held upright.
These are built in and verified by hand:
- A skip link to the main content, as the first focusable element.
- Visible keyboard focus on every interactive element. Focus is never removed without a replacement.
- One
h1per page and headings in order, with no levels skipped. - The Fit Ruler is operated by number inputs. The draggable rulers are a pointer enhancement layered on top. Everything the tool can do is available from the keyboard, and the tool still teaches its rule with JavaScript switched off.
- Page scrolling is never trapped. No element blocks a vertical swipe to capture a horizontal drag.
- Contact form fields are labelled, errors are tied to their field, and the outcome is announced. Focus moves to the first field that needs attention.
- Frequently asked questions use native disclosure elements, and every answer is in the page source whether or not it is open.
- Legal pages are never collapsed behind a control you have to find and expand.
- All motion is removed for anyone whose system asks for reduced motion. There is very little to begin with.
- With JavaScript off, navigation is fully visible and the contact page offers a working email route rather than a form that cannot submit.
Known gaps
These are real and we would rather write them down than let you find them:
- No screen reader testing yet
- The site has been checked programmatically — roles, labels, live regions, focus order — but nobody has yet worked through it with NVDA, JAWS or VoiceOver. That is the single biggest gap on this list.
- No independent audit
- No third party has assessed this site. Everything here is our own assessment of our own work.
- High contrast and forced colours modes untested
- We have not verified how the site renders under Windows High Contrast or a forced-colours setting.
- 400% zoom untested
- Text is set in relative units and the layout is built to reflow, but we have not confirmed behaviour at 400% zoom on a small viewport.
- The spam check is a third-party widget
- The contact form uses Cloudflare Turnstile. Its own accessibility is Cloudflare's to determine, not ours. If it blocks you, use the email address below — it reaches the same inbox.
- Product photography is not in place
- The product is currently shown as technical line drawings, which carry text descriptions. When photographs replace them, their alternative text will be written and this note removed.
Deliberate decisions worth explaining
Two elements are hidden from assistive technology on purpose, because they repeat information that is already available as text:
- The Fit Ruler's draggable tracks duplicate the number inputs beside them. Announcing both would present one control twice.
- The Fit Ruler's two-axis chart restates the verdict that is written out in full underneath it, naming which measurement caused it.
If either decision makes the tool harder rather than easier for you, we want to know — that judgement is ours and it may be wrong.
Telling us about a problem
Email contact@gemnyestore.com with "Accessibility" in the subject, or use the contact form. Tell us the page, what you were trying to do, and what got in the way. Your browser and any assistive technology you use helps, if you are willing to say.
We reply within one business day, Monday to Friday. If something on this site stops you reaching us, that is the most serious kind of bug here and we will treat it that way.