For everyone who comes here. On every device.

Luxe Gems builds toward the Web Content Accessibility Guidelines version 2.1, level AA. Every shipped page is reviewed against contrast, focus, label, and keyboard checks before it goes live. We do not yet claim full conformance across every legacy surface; the gap list is reviewed each release and we publish progress on request.

• Keyboard navigation. Every interactive element on the site can be reached and operated with a keyboard alone. A visible focus ring is preserved across buttons, links, form fields, and the cart drawer.
• Screen reader support. Semantic HTML throughout the catalog, with ARIA labels on icon buttons, the cart, the concierge, and the site search. Page titles update on every navigation.
• Reduced motion. The site honors the operating-system prefers-reduced-motion setting. Where animation carries meaning, a static alternative is shown when reduced motion is requested.
• Contrast. Body copy, button labels, and form-field text meet or exceed the 4.5:1 contrast ratio required by WCAG 2.1 AA against the backgrounds they sit on.
• Skip link. A Skip to content link is the first focusable element on every page, so keyboard and screen-reader users can bypass the header and site navigation.

A few legacy diamond and product images do not yet carry descriptive alt text. The ring builder is fully keyboard operable but its diamond grid relies on visual differentiation that we are actively improving for screen-reader narration. If a barrier is blocking you, please get in touch and we will route around it for you while we ship a fix.

If something on the site is hard to use with assistive technology, write to hello@luxegemsco.com with the page URL and a short description of the barrier. We reply within one business day. If the issue blocks you from completing a purchase, mention that in the subject line and we will help you place the order another way while we ship the fix.

It applies to the public catalog, the ring builder, the cart and checkout, and the account dashboard. It does not yet cover third- party services embedded inside the site (for example, payment forms served by Stripe), which carry their own accessibility statements maintained by their providers.