Accessibility

The standard we work to

This site aims to conform to WCAG 2.1 Level AA. We say "aims to" rather than "conforms to" deliberately: conformance is a statement about every page, and the site is still being built out. The pages that exist have been tested; the gaps are listed below rather than left for you to find.

What is built in

• Every page works without JavaScript. The navigation, the mobile menu and the ingredient-list panels are HTML elements, not scripted widgets. The forms submit and validate with scripting switched off.
• A visible focus indicator on everything focusable, at a contrast that passes against every surface used on the site. It is never removed.
• A skip link as the first focusable element on every page.
• Text contrast is measured, not guessed. Body text sits at 8.7:1 and secondary text at 5.3:1 on the page background. The two brand accent colours that do not reach 4.5:1 are barred from carrying text at all and are used only as non-text marks.
• Colour is never the only carrier of meaning. The coloured rule above a product card sits on top of a written label, not instead of one.
• Every form field has a real label, with hints and errors wired to the field so a screen reader reads them together. Required fields say "required" in words. A failed submit announces how many fields need attention and moves focus to the first one.
• Motion respects your settings. Nothing animates for a visitor whose system asks for reduced motion, and nothing moves, blinks or auto-plays regardless.
• Tables are real tables with proper header cells, so the developer-selection and development-time charts can be navigated cell by cell rather than read as a wall of numbers.

How it was tested

Automated checks with axe-core driven through a headless browser against the built pages, plus manual keyboard-only walkthroughs of the navigation and all three forms. Automated testing catches perhaps a third of real barriers, which is why the gap list below exists.

Known gaps

We would rather you read this than discover it.

• No testing with a screen reader by a person who uses one daily. Keyboard walkthroughs and automated checks are not the same thing as that, and this is the most significant gap on the list.
• Product photography is not yet in place, so the alternative text that will accompany it has not been written or reviewed. Shade descriptions currently rely on the shade name and number.
• The site is published in English only. Polish and Spanish pages exist in the codebase but are not published, so a reader who needs one of those languages is not served at all yet.
• The multi-select control on the distribution form asks you to hold a modifier key to choose more than one state. It is operable by keyboard and correctly labelled, but it is not the easiest control of its kind and it is on the list to be replaced with checkboxes.
• Documents linked from product pages — safety data sheets and ingredient PDFs supplied by the manufacturer — have not been checked for PDF accessibility and are unlikely to be tagged. If you need one of these in an accessible format, ask and we will send the content as plain text or HTML.

Tell us about a barrier

If something on this site blocks you, write to info@rosaneracosmetics.com with "accessibility" in the subject. Tell us the page and what happened; the assistive technology and browser you were using helps but is not required.

We reply within five business days. If a fix will take longer than that, we will say so and give you the information you were trying to reach by another route in the meantime — that part is not contingent on the fix.