Accessibility declaration
IZAC commitments
In order to offer the best possible experience to all its users, IZAC makes the navigation of its site accessible to people with disabilities.
This constant optimisation process is part of the group's general policy in favour of diversity.
To support us in this digital transformation, we have joined forces with Accessiway. Visit the Accessiway website
We firmly believe that the web should be available and accessible to all, and we are committed to providing a website that is accessible to as many people as possible, regardless of their circumstances and abilities.
We want to be part of this long-term approach to citizenship and solidarity. We are committed to ensuring that our site will be able to achieve an accessibility rate in the years to come that will enable us to comply or partially comply with the RGAA 4.1 regulations.
As of 17/11/2022, the site https://izac.fr has a compliance rate of 63.85% with the RGAA 4.1.
This constant optimisation process is part of the group's general policy in favour of diversity.
To support us in this digital transformation, we have joined forces with Accessiway. Visit the Accessiway website
We firmly believe that the web should be available and accessible to all, and we are committed to providing a website that is accessible to as many people as possible, regardless of their circumstances and abilities.
We want to be part of this long-term approach to citizenship and solidarity. We are committed to ensuring that our site will be able to achieve an accessibility rate in the years to come that will enable us to comply or partially comply with the RGAA 4.1 regulations.
As of 17/11/2022, the site https://izac.fr has a compliance rate of 63.85% with the RGAA 4.1.
What is digital accessibility?
Digital accessibility means that people with disabilities can use the web. More specifically, that they can perceive, understand, navigate and interact with the web, and that they can contribute to the web.
Digital accessibility also benefits others, including older people whose abilities change with age. Web accessibility includes all disabilities that affect access, whether visual, cognitive or motor.
An accessible website allows, for example:
● navigate with a voice synthesis and/or a Braille display (notably used by blind and partially sighted people) ;
● customise the display of the site according to their needs (enlarging the characters, changing the colours, etc.);
● navigate without using the mouse (with the keyboard only, via a touch screen, by voice or any other adapted device).
To do this, the site must comply with the standards in force when it is created and updated.
Digital accessibility also benefits others, including older people whose abilities change with age. Web accessibility includes all disabilities that affect access, whether visual, cognitive or motor.
An accessible website allows, for example:
● navigate with a voice synthesis and/or a Braille display (notably used by blind and partially sighted people) ;
● customise the display of the site according to their needs (enlarging the characters, changing the colours, etc.);
● navigate without using the mouse (with the keyboard only, via a touch screen, by voice or any other adapted device).
To do this, the site must comply with the standards in force when it is created and updated.
Accessibility declaration
IZAC undertakes to make its internet, intranet and extranet sites and its software packages accessible in accordance with article 47 of law n°2005-102 of 11 February 2005.
● 63.85 % of the RGAA version 4.1 criteria are respected
● The average compliance rate of the site is 64.27%.
● In detail:
○ Number of compliant criteria: 223
○ Number of criteria not applicable: 819
○ Number of non-compliant criteria: 124
● 1.3 For each information-bearing image with a textual alternative, is this alternative
relevant (excluding special cases)?
● 2.2 For each frame with a frame title, is the frame title relevant?
● 6.1 Is each link explicit (excluding special cases)?
● 6.2 In each web page, does each link have a title?
● 7.2 For each script with an alternative, is that alternative relevant?
● 7.4 For each script that initiates a context switch, is the user warned or does the user have control?
● 7.5 For each web page, are status messages correctly rendered by assistive technologies?
● 8.2 For each web page, is the generated source code valid for the specified document type (excluding special cases)?
● 8.6 For each web page with a page title, is the title relevant?
● 8.9 In each web page, tags should not be used for presentation purposes only. Is this rule respected?
● 9.1 In each web page, is the information structured by the appropriate use of headings?
● 9.2 In each web page, is the structure of the document consistent (excluding special cases)?
● 10.1 In the website, are style sheets used to control the presentation of information?
● 10.2 In each web page, does the visible content carrying information remain present when style sheets are disabled?
● 10.3 In each web page, does the information remain understandable when style sheets are disabled?
● 10.4 In each web page, is the text still readable when the font size is increased to at least 200% (excluding special cases)?
● 10.5 In each web page, are the CSS declarations for element background and font colours used correctly?
● 10.12 In each web page, can the text spacing properties be redefined by the user without loss of content or functionality (excluding special cases)?
● 11.1 Does each form field have a label?
● 11.2 Is each label associated with a form field relevant (excluding special cases)?
● 11.3 In each form, is each label associated with a form field that has the same function and is repeated several times in the same page or set of pages consistent?
● 11.4 In each form, are each field label and its associated field joined together (excluding special cases)?
● 12.6 Can content grouping areas present in several web pages (header, main navigation, main content, footer and search engine areas) be reached or avoided?
Exemptions for disproportionate burden
None
Content not subject to the accessibility requirement
● Files available in desktop formats published before 23 September 2018.
● Video content exempt from text transcripts if the video was published before 23 September 2020.
● Third party content that is not funded or developed by the organisation concerned and is not under its control (cookie banner, youtube player).
Technologies used to produce IZAC, https://izac.fr
● Html5
● CSS
● JavaScript
● Ruby
Test environment
The content rendering checks were performed on the basis of the combination provided by the RGAA 4.1 baseline, with the following versions:
● Firefox 22 and NVDA 2022
● Google chrome and NVDA 2022
Accessibility assessment tools
● WCAG contrast checker
● RGAA assistance
● Accessibility axis
● HeadingsMap
● Web Developer
● Tanaguru webext
● https://izac.fr/pages/mentions-legales
● https://izac.fr/products/pull-col-rond-beige-puh22bertoldo-beige
● https://izac.fr/pages/boutiques-izac
● https://izac.fr/pages/contact
● https://izac.fr/pages/lhistoire-izac
● https://izac.fr/cart
● https://izac.fr/26042531895/checkouts/a745ba692a2ac59c731694fb4e201ed3
● https://izac.fr/26042531895/checkouts/a745ba692a2ac59c731694fb4e201ed3?previous_step
=shipping_method&step=payment_method
● https://izac.fr/pages/alma-le-paiement-en-plusieurs-fois
● https://izac.fr/pages/faq
● Send a message
● Contact IZAC, https://izac.fr/pages/contact
● Write a message to the Human Rights Defender https://formulaire.defenseurdesdroits.fr/
● Contact the delegate of the Human Rights Defender in your region
https://www.defenseurdesdroits.fr/saisir/delegues
● Send a letter by post (free of charge, do not put a stamp)
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07
Compliance status
IZAC, https://izac.fr is partially compliant with the General Accessibility Standard (GAS), version 4.1 due to the non-conformities and deviations listed below.Test results
The compliance audit carried out by AccessiWay on 17/11/2022 reveals that:● 63.85 % of the RGAA version 4.1 criteria are respected
● The average compliance rate of the site is 64.27%.
● In detail:
○ Number of compliant criteria: 223
○ Number of criteria not applicable: 819
○ Number of non-compliant criteria: 124
Non-accessible content
Non-conformity● 1.3 For each information-bearing image with a textual alternative, is this alternative
relevant (excluding special cases)?
● 2.2 For each frame with a frame title, is the frame title relevant?
● 6.1 Is each link explicit (excluding special cases)?
● 6.2 In each web page, does each link have a title?
● 7.2 For each script with an alternative, is that alternative relevant?
● 7.4 For each script that initiates a context switch, is the user warned or does the user have control?
● 7.5 For each web page, are status messages correctly rendered by assistive technologies?
● 8.2 For each web page, is the generated source code valid for the specified document type (excluding special cases)?
● 8.6 For each web page with a page title, is the title relevant?
● 8.9 In each web page, tags should not be used for presentation purposes only. Is this rule respected?
● 9.1 In each web page, is the information structured by the appropriate use of headings?
● 9.2 In each web page, is the structure of the document consistent (excluding special cases)?
● 10.1 In the website, are style sheets used to control the presentation of information?
● 10.2 In each web page, does the visible content carrying information remain present when style sheets are disabled?
● 10.3 In each web page, does the information remain understandable when style sheets are disabled?
● 10.4 In each web page, is the text still readable when the font size is increased to at least 200% (excluding special cases)?
● 10.5 In each web page, are the CSS declarations for element background and font colours used correctly?
● 10.12 In each web page, can the text spacing properties be redefined by the user without loss of content or functionality (excluding special cases)?
● 11.1 Does each form field have a label?
● 11.2 Is each label associated with a form field relevant (excluding special cases)?
● 11.3 In each form, is each label associated with a form field that has the same function and is repeated several times in the same page or set of pages consistent?
● 11.4 In each form, are each field label and its associated field joined together (excluding special cases)?
● 12.6 Can content grouping areas present in several web pages (header, main navigation, main content, footer and search engine areas) be reached or avoided?
Exemptions for disproportionate burden
None
Content not subject to the accessibility requirement
● Files available in desktop formats published before 23 September 2018.
● Video content exempt from text transcripts if the video was published before 23 September 2020.
● Third party content that is not funded or developed by the organisation concerned and is not under its control (cookie banner, youtube player).
Preparation of this accessibility declaration
This declaration was made on 17/11/2022.Technologies used to produce IZAC, https://izac.fr
● Html5
● CSS
● JavaScript
● Ruby
Test environment
The content rendering checks were performed on the basis of the combination provided by the RGAA 4.1 baseline, with the following versions:
● Firefox 22 and NVDA 2022
● Google chrome and NVDA 2022
Accessibility assessment tools
● WCAG contrast checker
● RGAA assistance
● Accessibility axis
● HeadingsMap
● Web Developer
● Tanaguru webext
Pages of the site subject to the compliance check
● https://izac.fr/● https://izac.fr/pages/mentions-legales
● https://izac.fr/products/pull-col-rond-beige-puh22bertoldo-beige
● https://izac.fr/pages/boutiques-izac
● https://izac.fr/pages/contact
● https://izac.fr/pages/lhistoire-izac
● https://izac.fr/cart
● https://izac.fr/26042531895/checkouts/a745ba692a2ac59c731694fb4e201ed3
● https://izac.fr/26042531895/checkouts/a745ba692a2ac59c731694fb4e201ed3?previous_step
=shipping_method&step=payment_method
● https://izac.fr/pages/alma-le-paiement-en-plusieurs-fois
● https://izac.fr/pages/faq
Feedback and contact
If you are unable to access a content or service, you can contact the IZAC manager, https://izac.fr/pages/contact to be directed to an accessible alternative or obtain the content in another form.● Send a message
● Contact IZAC, https://izac.fr/pages/contact
Remedies
This procedure should be used in the following case. You have notified the website operator of a lack of accessibility that prevents you from accessing content or services on the portal and you have not received a satisfactory response.● Write a message to the Human Rights Defender https://formulaire.defenseurdesdroits.fr/
● Contact the delegate of the Human Rights Defender in your region
https://www.defenseurdesdroits.fr/saisir/delegues
● Send a letter by post (free of charge, do not put a stamp)
Défenseur des droits
Libre réponse 71120
75342 Paris CEDEX 07
Multi-annual scheme
In progressAccessiWay navigation aid
AccessiWay improves the accessibility of sites for users with a wide range of disabilities (blind and visually impaired, people with cognitive disorders, motor disorders, epilepsy, etc.), in full compliance with WCAG 2.1, European and French regulations (RGAA 4.1).
To achieve this, Accessiway combines digital accessibility consulting services with an application based on artificial intelligence that runs in the background to constantly optimise its level of accessibility.
Notable improvements include:
● Navigation with screen reader and keyboard:
○ Implementation of the ARIA (Accessible Rich Internet Applications) attribute technique, as well as various behavioural modifications, to ensure that blind users who visit the site with screen readers can read, understand and enjoy the full functionality of the site.
● Optimisation of keyboard navigation:
○ The background process also adjusts the website's HTML code and adds various behaviours using JavaScript code to make the website keyboard friendly. For example, it is possible to navigate the site using the Tab and Shift+Tab keys, use drop-down lists with the arrow keys, close them with Esc, and trigger buttons and links with the enter key.
● Activatable profiles:
○ Safety profile for epilepsy: this profile allows people with epilepsy to use the website safely by eliminating the risk of seizures resulting from flashing animations and risky colour combinations.
Profile for the visually impaired: This profile adapts the website to be accessible to the majority of visual impairments such as impaired vision, tunnel vision, cataracts, glaucoma, etc.
Cognitive disability profile: this profile provides various assistive features to help users with cognitive disabilities such as autism, dyslexia, stroke, and others to focus more easily on the essentials.
○ ADHD Friendly Profile: this profile dramatically reduces distractions and noise to help people with ADHD and neurodevelopmental disabilities navigate, read, and focus on essentials more easily.
○ Blind User Profile (screen readers): this profile adapts the website to be compatible with screen readers such as JAWS, NVDA, VoiceOver and TalkBack.
● Additional user interface, design and readability adjustments:
○ Font adjustments: users can increase and decrease its size, change its family (type), adjust spacing, alignment, line height, etc.
Colour adjustments: users can select different colour contrast profiles such as light, dark, reverse and monochrome. In addition, users can swap colour schemes of titles, texts and backgrounds, with more different colouring options.
Animations: Users with epilepsy can stop all running animations by clicking a button. Interface-controlled animations include videos, GIFs and flashing CSS transitions.
○ Content highlighting: users can choose to highlight important elements such as links and titles. They can also choose to highlight only targeted or hovered elements.
Mute Audio: Users with hearing aids may experience headaches or other problems with automatic audio playback. This option allows users to instantly mute the entire website.
○ Cognitive Impairment: Accessiway uses a search engine linked to Wikipedia and Wiktionary, allowing people with cognitive disabilities to decipher the meaning of phrases, initials, slang, etc.
Additional features: Accessiway offers users the ability to change the colour and size of the cursor, use a print mode, activate a virtual keyboard, and many other features.
To achieve this, Accessiway combines digital accessibility consulting services with an application based on artificial intelligence that runs in the background to constantly optimise its level of accessibility.
Notable improvements include:
● Navigation with screen reader and keyboard:
○ Implementation of the ARIA (Accessible Rich Internet Applications) attribute technique, as well as various behavioural modifications, to ensure that blind users who visit the site with screen readers can read, understand and enjoy the full functionality of the site.
● Optimisation of keyboard navigation:
○ The background process also adjusts the website's HTML code and adds various behaviours using JavaScript code to make the website keyboard friendly. For example, it is possible to navigate the site using the Tab and Shift+Tab keys, use drop-down lists with the arrow keys, close them with Esc, and trigger buttons and links with the enter key.
● Activatable profiles:
○ Safety profile for epilepsy: this profile allows people with epilepsy to use the website safely by eliminating the risk of seizures resulting from flashing animations and risky colour combinations.
Profile for the visually impaired: This profile adapts the website to be accessible to the majority of visual impairments such as impaired vision, tunnel vision, cataracts, glaucoma, etc.
Cognitive disability profile: this profile provides various assistive features to help users with cognitive disabilities such as autism, dyslexia, stroke, and others to focus more easily on the essentials.
○ ADHD Friendly Profile: this profile dramatically reduces distractions and noise to help people with ADHD and neurodevelopmental disabilities navigate, read, and focus on essentials more easily.
○ Blind User Profile (screen readers): this profile adapts the website to be compatible with screen readers such as JAWS, NVDA, VoiceOver and TalkBack.
● Additional user interface, design and readability adjustments:
○ Font adjustments: users can increase and decrease its size, change its family (type), adjust spacing, alignment, line height, etc.
Colour adjustments: users can select different colour contrast profiles such as light, dark, reverse and monochrome. In addition, users can swap colour schemes of titles, texts and backgrounds, with more different colouring options.
Animations: Users with epilepsy can stop all running animations by clicking a button. Interface-controlled animations include videos, GIFs and flashing CSS transitions.
○ Content highlighting: users can choose to highlight important elements such as links and titles. They can also choose to highlight only targeted or hovered elements.
Mute Audio: Users with hearing aids may experience headaches or other problems with automatic audio playback. This option allows users to instantly mute the entire website.
○ Cognitive Impairment: Accessiway uses a search engine linked to Wikipedia and Wiktionary, allowing people with cognitive disabilities to decipher the meaning of phrases, initials, slang, etc.
Additional features: Accessiway offers users the ability to change the colour and size of the cursor, use a print mode, activate a virtual keyboard, and many other features.
Füge eine neue Adresse hinzu
Liquid error (snippets/cu-account_edit line 23): customer_address form must be given an address
Bearbeiten
