Accessibility

This statement covers eclataur.com, the website of Eclataur LLC (doing business as ÉCLATAUR). It says what we have built, how we check it, and what we know is not yet right.

This site is built and tested to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We do not call it compliant or certified. Accessibility is a standard we keep working to, page by page and release by release, not a badge earned once.

• Native controls. Links, buttons, menus and form fields are the browser's own elements, so they announce themselves correctly and work with the keyboard without extra scripts.
• Keyboard first. Every flow, from choosing a fragrance to paying for it, completes with the keyboard alone. Focus is always visible and is never trapped. A skip link at the top of every page jumps straight to the content.
• Targets you can hit. Interactive controls are at least 44 by 44 pixels.
• Contrast from the palette itself. Text and background colours come from a fixed set that is checked for contrast, including the gold on light surfaces, which is the tightest pair we use.
• Never colour alone. Stock, errors and states are always written in words as well.
• Images described. Every image that carries meaning has a text description, and decorative images are marked so screen readers pass over them.
• Forms with real labels. Fields have visible labels, and an error says what went wrong and how to fix it, in text.
• Motion that respects your settings. When your system asks for reduced motion, the site's animations stop and every page settles into its finished state.
• One outline per page. Headings run in order, with one main heading, so a screen reader's outline reads like the page.

Automated checks run with Lighthouse, which applies the axe accessibility rules, on the home, collection, product and Journal templates. The last run, on September 4, 2026, scored 100 on each. Keyboard walks of the shopping and checkout flows, and screen reader checks with VoiceOver, are part of every release that touches them.

• Payment fields. The card and wallet fields at checkout are provided by Stripe and PayPal inside their own frames. We choose the most accessible configuration they offer; what happens inside those frames is theirs.
• Emails and invoices. Order emails and PDF invoices are laid out for mail clients and print, which support fewer accessibility features than the web.
• Product photography on listing pages. The photograph on a product card is described by the product name beside it rather than by its own text, to avoid announcing every name twice.
• Other companies' marks. Payment logos and the Google mark on the preferred-source link use their owners' own colours, which do not always meet our contrast target. None of them carries information that is not also in text.

If something on this site is in your way, tell us and we will fix it. Email support@eclataur.com or call +1 (469) 434-6194. Say which page you were on and what happened, and the assistive technology you use if any. We reply within 2 business days, usually sooner, and a fix ships with the next release.

This statement was written on September 4, 2026, and is reviewed every quarter, or sooner when a page changes in a way that could affect it. The date at the top is the last time it was checked against the site.