Accessibility Statement for Neuraé

This is an accessibility statement from SISLEY UK Ltd.

Measures to support accessibility

SISLEY UK Ltd. takes the following measures to ensure accessibility of Neuraé:

• - Integrate accessibility into our procurement practices.
• - Appoint an accessibility officer and/or ombudsperson.
• - Employ formal accessibility quality assurance methods.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Neuraé is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Feedback

We welcome your feedback on the accessibility of Neuraé. Please let us know if you encounter accessibility barriers on Neuraé:

• - Phone: +44 020 304 852 80
• - E-mail: customerservicesuk@neurae.com
• - Postal Address: 33 Foley Street, 5th Floor, London, W1W 7TL United Kingdom

We try to respond to feedback within 2-3 business days.

Compatibility with browsers and assistive technology

Neuraé is designed to be compatible with the following assistive technologies:

• - Google Chrome with NVDA on Windows
• - Mozilla Firefox with NVDA on Windows
• - Google Chrome with Jaws on Windows
• - Mozilla Firefox with Jaws on Windows
• - Microsoft Edge with Narrator on Windows
• - Safari with VoiceOver on Mac OS
• - Safari with VoiceOver on iOS
• - Google Chrome with Talkback on Android

Neuraé is not compatible with:

• Browsers and assistive technologies that do not support JavaScript and WAI-ARIA, or only partially

Technical specifications

Accessibility of Neuraé relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• - HTML
• - WAI-ARIA
• - CSS
• - JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and alternatives

Despite our best efforts to ensure accessibility of Neuraé, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for Neuraé:

1. General statement: We have identified accessibility issues that have been filed for fixes as part of our continuous improvement process. Our content and development teams work conjointly, with the help of an external consultant, to resolve these issues, prioritizing the most impacting ones. Please contact our customer care service if you encounter accessibility issues that are not listed below.
2. Images, icons, and pictures: Certain graphic files might be output to assistive technologies, whereas they bear no specific information.
3. Interactive elements: Some items like buttons, selection widgets, or the main menu, don't correctly communicate their purpose and statuses to assistive technologies. Known defects are being evaluated for correction.
4. Structured texts: Most text content is structured with headings, paragraphs, landmarks, and lists, to ease their navigation with assistive technologies like screen readers. However, we have identified parts of the content that need rework in this regard.
5. Routine finder - keyboard navigation: The second step of the routine finder cannot be operated with the keyboard currently. You can reach out to our beauty consultants to advise you about the products that suit you best.
6. Routine finder - screen reader support: The final form includes controls to agree to receive our marketing messages, or not. Due to a configuration error, the associated question is incorrect for screen readers users. Until this is fixed, please know that the actual label for this field is "By selecting YES, I also consent to receive NEURAÉ communications".
7. Tutorials - keyboard navigation: Under certain conditions, it might not be possible to return to the first steps using the keyboard only. If you need to consult these steps again, we advise you to reload the page to return to the first steps of the component.
8. Tutorials - use of voice control devices: Although the actionable items are visually presented as "steps", the underlying code makes them known to assistive technologies as "slides". This is due to the code library that has been used, and that we will fix in this regard. In the meantime, voice control users may use the term "slide" to refer to these buttons, or use other means to reach them with their assistive software.
9. Pop-up dialogs: Some dialog windows, for special offers, may appear while browsing. This occurs mainly during your first visits to the site, as the system detects this and pushes these offers to new visitors essentially. We are looking into getting a better balance between the drawbacks and the benefits of this feature. We recommend that you accept cookies on the website to avoid being flagged as a newcomer on each of your visits.
10. Keyboard navigation: Some items, like the log in window, need additional key presses to be reached, due the keyboard cursor landing on hidden items in the menu. We are working on a fix to avoid this phenomenon. Pressing the keys until you reach a visible item should allow you to proceed, as we have not found any occurrence where the keyboard cursor is completely trapped.
11. Skip link: All pages include a link that allow to go directly to the main content area, effectively avoiding the need to move the keyboard cursor through the links of the menu and the header. However, on some pages, this link is broken. This is due to missing elements in these pages, that we are working on adding in a future version.
12. Terms in French: Our products ranges bear French names that recall the origins of our company. This may cause difficulties to understand the content output by screen readers. We are working on providing to assistive technologies the information they need to read out these terms correctly, if they support this language. There is only a small number of these terms, however, and they shouldn't affect your ability to use the main features of the website.
13. Color contrasts - texts: Some texts are displayed over pictures and videos, which may affect their visibility, depending on the underlying image composition. We are working on a solution to limit the occurence of this unfortunate effect, while preserving the brand identity. We also try to choose color combinations and pictures that don't cause the issue.
14. Color contrasts - non-text content: The dot that denotes the fact that the current user is logged in, is not visible enough. In a future version, the chosen color will be darker, and thus more visible against the white background. In doubt, you may check your logging status by clicking on the icon. You will be prompted to enter your e-mail and password if you are not logged in.
15. Moving images: Some videos are played in a loop, in the background or in a frame. While they participate to the appeal of our website's design, they can also be troublesome to some people. We are working on a feature that allow users to pause these animations if they prefer to. These videos can be found mainly on the home page, and in select places in the product pages. Other parts of the website without these animations provide the same information.
16. "Read more" links: Some of the "Read more" links may not be usable with the keyboard only, in certain circumstances. We are assessing ways to fix this code issue. Although this prevents access to parts of the content, this doesn't prevent from using the main features of our website.
17. Slideshows: The slideshow that present our N|3™ technology can be read with a screen reader, but the output can be mixed up, and confusing. Besides, it can't be operated with a keyboard only. We are working on a version that better works with assistive technologies. These inconveniences, that we take seriously, shouldn't affect your ability to use the main features of the website.
18. Tab systems: In the product pages, the ingredients and other information are organized under tabs that can be operated with assistive technologies. However, they do not exactly follow the recommended interaction patterns for these components, as they are accessed with the Tab key instead of the arrow keys. A future version of this component will better adhere to these recommendations. In the meantime, you can use the Tab key to navigate between tabs in this component.
19. Promotional code: If a wrong code is entered in the promotional code field, the error message may not be easily found by users with low or no vision, who rely on screen reader to navigate. The message is actually placed after the submission button, which makes it more difficult to notice for them. Until this is fixed, users concerned by this issue are encouraged to read past the submission button to check if the code was accepted.
20. E-mail verification: Before checking out, non-identified users are required to enter a valid e-mail. The validity and the existence of the entered e-mail is checked on the fly. But instead of displaying an error message, the interface seems unresponsive, and doesn't allow to proceed to the next step. We are investigating this issue with our service provider. In the meantime, if your e-mail doesn't seem to allow you entrance to the checkout process, we advise you to check its validity, and avoid the use of temporary e-mail services.
21. Phone number verification: Errors in phone numbers are detected, but the expected format is not detailed, and the message may incorrectly ask to remove spaces. We are working on ways to provide more accurate information in our error messages. In the meantime, ensure that you enter 10-digit numbers for phone numbers operated inside the US territory.
22. Page titles: Some page titles are broken, due to incorrect configuration. Whenever such a page is identified, the faulty parameter is fixed.
23. Link tooltips: Certain tooltips on links are incorrect, or contain unusable information. The issues have various origins, as per our current analysis. Until all of them are fixed, you might rely on the link texts and their context for appropriate information.
24. Birthdate input widget: Currently, the selection lists for birthdates items (month, day, year) don't communicate their accessible name to assistive technologies - only their current value. This issue is being under investigation. In the meantime, here is the order of the date components in the US version of our website: month, day, year.
25. Password management page: Each field to enter passwords has a button to display the obscured password. However, the buttons for the "new password" and the "confirm new password" reveal buttons have incorrect names. Until this is fixed, you may rely on the field label to know the actual function of each button, knowing that the buttons come immediately after their respective field in reading order.
26. Payment methods removal feature: In their profile pages, users can manage their payment methods, and remove them if they wish. If there are several payment methods, it can be difficult to know which Remove button is related to which method, as they all bear the same accessible name. In a future version, the controls will have more specific names. In the meantime, please note that the Remove button associated to a payment method immediately follows its description. Also, the confirmation dialog lacks some accessible names, however it is understandable and operable with assistive technologies, albeit with a degraded experience, that we are working on improving.
27. Checkout - address edition: When an error is detected in the form, the keyboard focus remains on the submission button. We are working on fixing this feature, that is already active on other forms on our website. Until then, if the form seems unresponsive when you have hit the submission button, you may navigate back into it to check which fields have an error message.
28. Checkout - zip code for shipping options: Once the field has been confirmed, it loses its accessible name. Until the issue is fixed, note that this is the only text field in this part of the page.
29. Checkout - credit card form: Our third party payment solution to enter credit card details may feel unusual to users of screen reader. Unfortunately this is not something we can act upon, due to security concerns. However, it should be usable. Please reach out to us if you experiment issues with this form.
30. Contact form - visual test: To protect our website from spam, a visual or audio test may occasionally be imposed when you try to use the contact form. If you experience issues with both the audio and visual tests, you may use other means of contact, like those provided in this page.
31. Contact forms - labels: Unlike other forms on our website, this form has no visible labels, and the indications inside the fields are not contrasted enough. The selection list also lack information for assistive technologies. This form hasn't been updated yet, and doesn't follow our current design principles. This is being addressed internally. If you experience issues with form, you may use other means of contact, like those provided in this page.

Assessment approach

SISLEY UK Ltd. assessed the accessibility of Neuraé by the following approaches:

• External evaluation

Date

This statement was created on 4 April 2024 using the W3C Accessibility Statement Generator Tool.