ACCESSIBILITY STATEMENT

last update 21/04/2026
ACCESSIBILITY STATEMENT

ACCESSIBILITY STATEMENT

last update 21/04/2026

FRED Paris is committed to making its website accessible, in accordance with Article 47 of French Law No. 2005-102 of February 11, 2005.

To this end, FRED Paris is implementing:

  • An audit to assess compliance with version 4.1.2 of the Référentiel Général d’Amélioration de l’Accessibilité (RGAA)—France’s General Framework for Improving Accessibility—conducted in March 2026

  • A multi-year accessibility strategy and an accompanying three-year action plan, currently in development

This accessibility statement applies to the FRED website, found at the address https://www.fred.com

COMPLIANCE STATUS

The FRED Paris website is not compliant with the Référentiel Général d’Amélioration de l’Accessibilité (RGAA), version 4.1.2, due to the non-compliances and exemptions listed below.

TEST RESULTS

The RGAA 4.1.2 compliance audit conducted by the LVMH Accessibility Center reveals that:

  • 38.81% of RGAA 4.1.2 criteria were met.

Specifically:

  • Number of criteria met: 26

  • Number of inapplicable criteria: 39

  • Number of criteria failed to be met: 41

NON-ACCESSIBLE CONTENT

Non-compliances

Examples:

  • 1.2 – Some images were incorrectly acknowledged by assistive technology.

    • Example: decorative images on editorial pages or at certain steps in the checkout process are picked up by screen readers despite containing no information.

  • 1.3 – Some informative images have absent or irrelevant text alternatives.

    • Example: information embedded in visuals containing editorial content or product details was not correctly rendered by screen readers.

  • 1.6 – Some images containing complex information do not have an accessible detailed description.

    • Example: informative visuals on the “All about diamonds” editorial page.

  • 3.1 – Some information is communicated only by color.

    • Example: active states or visual cues that rely solely on a color change for certain interface components.

  • 3.2 – Several text elements lack sufficient contrast with their background.

    • Examples observed in certain elements of the navigation menu, in editorial content, and in certain sections of the footer.

  • 6.1 – Some links are not clear enough when out of context.

    • Example: links to social media in the footer are identified only by an icon.

  • 6.2 – Some links lack accessible text.

    • Example: links containing only an icon and no clear description for assistive technology.

  • 7.1 – Some interactive components lack a correctly defined accessible name or role.

    • Examples: search button in the mobile menu with no accessible name;

    • Language selector implemented with non-semantic elements.

  • 7.3 – Some interactive elements cannot be used with a keyboard.

    • Examples: button for opening cookie settings;

    • Certain interactive elements in the navigation menu.

  • 7.4 – Some scripts cause a change of context without informing the user.

    • Example: opening modals or dynamic content without indication for assistive technology.

  • 7.5 – Some dynamic messages were incorrectly rendered by assistive technology.

    • Example: update or state messages in certain interactive components.

  • 8.5 – Some pages lack a relevant or unique title.

    • Example: pages with titles that do not accurately reflect the content being displayed.

  • 8.7 – Some content uses a different language to that of the page, without this being indicated in the code.

    • Example: aria-label attribute in English on a French webpage.

  • 8.9 – Some HTML tags are used solely for presentation purposes.

    • Example: simulated headings in certain sections of the footer.

  • 8.10 – Changes in reading direction are not always identified in the code when necessary.

  • 9.1 – Some text presented visually as headings is not displayed as such in the accessible structure.

    • Example: simulated headings in certain sections of the footer.

  • 9.2 – The overall structure of the document is not always coherent.

    • Example: sections of content are not always organized according to a logical hierarchy.

  • 9.3 – Some visual lists are not structured with the appropriate tags.

  • 9.4 – Some quotations on editorial or news pages are not correctly indicated in the code.

  • 10.7 – Focus indicators are absent or insufficiently visible on certain interactive elements.

    • Example: certain links and buttons in the menus or footer.

  • 10.8 – Some content designed to be ignored by assistive technology is still accessible.

    • Example: invisible elements in certain dynamic sections.

  • 10.9 – Some information depends solely on formatting or placement.

  • 10.11 – Some content does not adapt correctly when the size of the display is changed.

  • 10.12 – Text spacing cannot always be changed without losing information.

  • 10.13 – Some content on hover or focus cannot be controlled by the user.

  • 11.1 – Some form fields have no accessibility label.

    • Example: fields found in certain steps of the checkout process.

  • 11.5 – Fields of the same nature are not always grouped correctly.

  • 11.9 – Some buttons have an ambiguous description.

    • Example: buttons represented only by an icon or symbol.

  • 11.10 – Some input controls are not being used properly.

  • 11.11 – Help messages for error correction are not always present in forms.

  • 11.13 – The purpose of certain fields cannot be automatically determined to facilitate autocomplete.

  • 12.6 – The main areas of the page (header, navigation, main content, footer) cannot always be easily reached or avoided.

  • 12.7 – Some pages do not have a quick link to the main content.

  • 12.8 – Navigation order on a keyboard is not always coherent.

  • 13.3 – Some downloadable documents do not have an accessible version.

  • 13.8 – Some animated content cannot be controlled by the user.

    • Example: carousels on certain editorial pages.

  • 13.10 – Some functions rely on complex interactions without a simple alternative.

Content not subject to accessibility requirements

  • Files available in office formats published before September 23, 2018;

  • Third-party content which is neither funded nor developed by the organization concerned and which is out of its control:

PREPARATION OF THIS ACCESSIBILITY STATEMENT

This statement was prepared on March 17, 2026.

Technology used to make the website

  • HTML5

  • CSS

  • JavaScript

Test environment

The webpages were tested using combinations of the following browsers and screen readers:

  • NVDA, Firefox (Windows) 

  • VoiceOver, Safari (MacOS) 

The following tools were used for evaluation:

  • CCA (Color Contrast Analyzer)

  • Code Inspector

  • HeadingsMap​

  • Web developer​

  • ARC Toolkit

  • PAC (PDF Accessibility Checker)

Webpages subject to compliance checks

  1. Homepage: https://www.fred.com/en_FR

  2. Legal Disclaimer:  https://www.fred.com/en_FR/mentions-legales/

  3. Contact us: https://www.fred.com/en_FR/contactus/)

  4. Sitemap: https://www.fred.com/en_FR/sitemap/

  5. Accessibility: https://www.fred.com/en_FR/accessibility/

  6. FAQs: https://www.fred.com/en_FR/fred-faq.html

  7. Create an account: https://www.fred.com/en_FR/register/?fromCheckout=true

  8. Sign in: https://www.fred.com/en_FR/checkout/login/

  9. Categories: https://www.fred.com/en_FR/categories/categories/bagues/

  10. Product page (add to shopping bag + shopping bag modal): https://www.fred.com/en_FR/bagues/bague-chance-infinie/4B2007.html

  11. Checkout (different steps): https://www.fred.com/en_FR/checkout/?stage=shipment#shipment

  12. News page: https://www.fred.com/en_FR/actualities/FREDxRoland-Garros.html

  13. Editorial page: https://www.fred.com/en_FR/maison-fred/edito-fred-samuel.html

  14. All about diamonds: https://www.fred.com/en_FR/maison-fred/edito-diamonds.html

FEEDBACK AND CONTACT INFORMATION

If you haven’t been able to access content or a service, you can contact the website manager to be directed to an accessible alternative or receive the content in another form.

REMEDIES

If you notice an accessibility issue that prevents you from accessing content or a feature on the website, and you report it to us but do not receive a response, you have the right to submit your complaint or a request for referral to the Défenseur des droits (Defender of Rights).

There are several options available to you: