Legal
Accessibility Statement
Last updated August 16, 2026. What we have done, what we know is imperfect, and how to tell us if something blocks you.
Where we are aiming
We build toward WCAG 2.2 Level AA, the standard US courts and regulators generally reference. We test as we build rather than auditing once and forgetting.
We are not claiming perfection. A statement that claims full conformance and is wrong is worse than one that is honest about the gaps.
What has actually been done
Every one of these was verified in a browser, not assumed:
Content does not depend on JavaScript to be visible. If scripts fail, the page still shows. This was a real bug here once and it is now guarded in CSS.
Motion respects your settings. Everything that animates stops if your system asks for reduced motion — including the rotating emblem, which is exactly the kind of movement that triggers vestibular symptoms.
Keyboard usable. Every link, button and form field is reachable by tab and shows a visible focus ring. There is a skip link to jump past the navigation.
Touch targets are at least 44 pixels. Measured on a 375-pixel screen.
Text does not zoom the page on iOS. Form fields are 16 pixels or larger, which prevents the forced zoom that traps people on mobile.
Images carry alternative text, and decorative images are marked as decorative so a screen reader skips them rather than reading a filename.
Real headings, in order, so a screen reader user can navigate by structure instead of reading everything. Every page has one h1 and no skipped levels.
Colour contrast is measured, not eyeballed. Body text is 17.5:1 against the page, secondary text 6.75:1 and the gold 9.5:1 — AA asks for 4.5:1. The borders on form fields and outline buttons are 3.1:1 or better, which is the separate threshold that applies to the edge of a control.
Known limitations
Automated testing is not the same as human testing. Our checks run on every page and currently pass. They are not a substitute for someone using this site with a screen reader every day, and we do not claim they are.
Third-party components. Scheduling and payment are embedded from Calendly and Stripe. We chose vendors that take accessibility seriously, but we do not control their markup. If either blocks you, email us and we will complete your booking or payment by phone.
Tell us about a barrier
If any part of this site stops you doing something, email goldencoterie@gmail.com with the page and what happened.
We aim to reply within two business days and to fix genuine barriers rather than argue about them. If a fix will take time, we will give you another way to get what you needed in the meantime.