Accessibility Statement

Accessibility Statement

This statement was created on 26/06/2026

 

Gien’s Commitment

Gien is committed to making its websites, mobile applications, intranet, extranet, and business software accessible to all users.

We value inclusion and diversity, and we are dedicated to ensuring that our website – us.gien.com – is accessible to everyone, especially people with disabilities.

We are firmly dedicated to building a web for all. As part of a long-term and responsible vision, we aim to fully comply with regulatory requirements, including Web Content Accessibility Guidelines version 2.2 level AA standard.

Accessibility statement for Faïencerie de Gien

This accessibility statement applies to us.gien.com.

This website is run by Gien. We want as many people as possible to be able to use this website.

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. Gien is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Feedback and contact information

We’re always looking to improve the accessibility of this website. If you find any problems please contact us:

  • email : wecare@gien.com

  • call :+33 02 38 05 21 02

  • Postal Address : 78 Place de la Victoire, 45500 Gien, France

We’ll consider your request and get back to you in 10 days.

Technical information about this website’s accessibility

We are committed to making our website accessible, in accordance with The Equality Act 2010 and with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. 

Vulnerabilities regarding accessibility

  • 1.1.1 – Non-text Content: Some images, icons, or other non-text content do not have a text description.

  • 1.3.1 – Info and Relationships: In some cases, the structure or meaning of content is shown only visually and is not coded so assistive tools can read it.

  • 1.3.5 – Identify Input Purpose: Some input fields do not tell assistive tools what data they collect, or this is set up wrong.

  • 1.4.1 – Use of Color: In some cases, color alone is used to give meaning or show a difference.

  • 1.4.3 – Contrast (Minimum): Text and images of text do not always have enough contrast, except for items like logos.

  • 1.4.4 – Resize text: Some text cannot be made twice as big without losing content or features (captions and text images excluded).

  • 1.4.10 – Reflow: Content that does not need a 2D layout does not reflow when the screen is resized.

  • 1.4.11 – Non-text Contrast: Some important components do not have a contrast ratio of at least 3:1 with nearby items.

  • 1.4.13 – Content on Hover or Focus: When extra content appears on hover or focus, the user cannot dismiss it, move onto it, or keep it visible long enough (with some exceptions).

  • 2.2.2 – Pause, Stop, Hide: There is no way to pause, stop, or hide moving, blinking, scrolling, or auto-updating content that runs over 5 seconds next to other content.

  • 2.4.3 – Focus Order: When users tab through content, the focus order does not match the meaning or how things work.

  • 2.4.4 – Link Purpose (In Context): The purpose of some links or controls is not clear from their text or context.

  • 2.4.7 – Focus Visible: Some interactive elements have no visible focus indicator when using the keyboard.

  • 3.1.2 – Language of Parts: When text appears in another language, this is not marked in the code.

  • 3.3.2 – Labels or Instructions: There are no labels or instructions when the user must enter data.

  • 3.3.3 – Error Suggestion: When an error is found and a fix is known, the fix is not shown (unless it would break security or purpose).

  • 4.1.2 – Name, Role, Value: Some components do not pass their name, role, state, or value to assistive tools, or do not notify them of changes.

  • 4.1.3 – Status Messages: Some status messages cannot be read by assistive tools without changing focus.

 

You can configure the accessibility widget (overlay) to provide a partially or fully accessible experience with respect to these vulnerabilities.

For the solution to work correctly, the widget must be fully loaded and the adaptations activated. An incorrect configuration of the widget may reduce accessibility.

 

Enforcement Procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations').

If you’re not happy with how we respond to your feedback, you can contact the Equality Advisory and Support Service (EASS).