This statement was established on January 5, 2026. It was updated on January 5, 2026.
It is valid from the date of publication, must be updated after 3 years, following major changes to the site, or 18 months after a new version of the reference framework.
My Red Socks is committed to making website accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005.
My Red Socks values inclusion and diversity, and ensures that its website https://meschaussettesrouges.com is accessible to everyone, including people with disabilities.
To this end, it implements the following strategy and actions:
https://meschaussettesrouges.com is partially compliant with the general framework for improving accessibility (RGAA).
Test results
The accessibility audit of the site meschaussettesrouges.com was conducted internally. This audit was carried out in accordance with the official RGAA 4.1 methodology, combining automated tools and manual checks (keyboard tests, navigation without a mouse, tests with assistive technologies).
The internal compliance audit reveals that:
54% of RGAA criteria are met.
Result details:
Number of compliant criteria: 40
Number of non-compliant criteria: 10
Number of non-applicable criteria: 32
Content not accessible
The content listed below is not accessible for the following reasons.
Non-compliance
Each informative image lacks alternative text.
Each decorative image is not properly ignored by assistive technologies.
Each frame does not have a frame title.
For each frame with a frame title, that frame title is not relevant.
On each web page, the contrast between the text color and its background color is not high enough.
On each web page, the colors used in interface components or graphic elements conveying information are not sufficiently contrasted.
Each pre-recorded synchronized temporal media does not have synchronized subtitles when needed.
Each pre-recorded time-based media does not have synchronized audio description when needed.
Each temporal medium is not clearly identifiable
Each non-temporal media has no alternative when necessary
Each temporal and non-temporal medium is not compatible with assistive technologies.
For each data table, no appropriate technique is used to associate each cell with its headers.
Each link is not explicit.
On every web page, each link has no label.
On every web page, status messages are not properly conveyed by assistive technologies.
For each web page, the generated source code is not valid according to the specified document type.
In each web page, tags are used solely for presentation purposes.
On each web page, the information is not structured by the appropriate use of headings.
On every web page, the information is no longer understandable when the style sheets are disabled.
On each web page, the CSS declarations for element background colors and fonts are not used correctly.
On every web page, every link whose nature is not obvious is not visible compared to the surrounding text.
On each web page, information is conveyed only through shape, size, or position.
On each web page, the information conveyed by shape, size, or position is not implemented appropriately.
For each web page, the content cannot be displayed without loss of information or functionality and requires scrolling within a restricted window.
On every web page, text spacing properties cannot be redefined without loss of content or functionality.
On each web page, additional content that appears when focusing on or hovering over a component cannot be controlled by the user.
On each web page, additional content styled only with CSS is not accessible via keyboard or pointing device.
Each form field has no label
Each label associated with a form field is not relevant.
In each form, the input validation is not accompanied by suggestions to correct errors.
The "site map" page is not relevant.
In each set of pages, the "site map" page is not accessible in the same way.
On every web page, there is no skip link or quick access to the main content area.
On every web page, features requiring a complex gesture are not available with a simple gesture.
Partially compliantCriterion 1.1Does every informative image have alternative text?
Partially compliantCriterion 1.2Is each decorative image properly ignored by assistive technologies?
Not applicableCriterion 1.3For each informative image with alternative text, is this alternative relevant (except in special cases)?
AgreedCriterion 1.4For each image used as a CAPTCHA or test image, with an alternative text, does this alternative allow identifying the nature and function of the image?
AgreedCriterion 1.5Is there an alternative access solution to the content or function of the CAPTCHA for each image used as a CAPTCHA?
Not applicableCriterion 1.6Does each informative image have a detailed description if necessary?
Not applicableCriterion 1.7For each informative image with a detailed description, is this description relevant?
Not applicableCriterion 1.8Each image containing informative text, in the absence of a replacement mechanism, should be replaced with styled text whenever possible. Is this rule being followed (except in special cases)?
AgreedCriterion 1.9Is each image caption, if necessary, correctly linked to the corresponding image?
Cadres
0 / 2 compliant
, 2 midterms
Partially compliantCriterion 2.1Does each frame have a frame title?
Partially compliantCriterion 2.2For each frame with a frame title, is that frame title relevant?
Couleurs
1 / 3 compliant
, 2 midterms
AgreedCriterion 3.1On each web page, information should not be conveyed by color alone. Is this rule being followed?
Partially compliantCriterion 3.2On each web page, is the contrast between the text color and its background color sufficiently high (except in special cases)?
Partially compliantCriterion 3.3On each web page, are the colors used in interface components or graphic elements conveying information sufficiently contrasted (except in special cases)?
AgreedCriterion 4.1Does each pre-recorded time-based media have, if necessary, a text transcription or an audio description (except in special cases)?
Not applicableCriterion 4.2For each pre-recorded time-based media with a textual transcription or synchronized audio description, are these relevant (except in special cases)?
Partially compliantCriterion 4.3Does each pre-recorded synchronized time-based media have synchronized subtitles if necessary (except in special cases)?
Not applicableCriterion 4.4For each pre-recorded synchronized timed media with synchronized subtitles, are these subtitles relevant?
Partially compliantCriterion 4.5Does each pre-recorded time-based media have synchronized audio description if necessary (except in special cases)?
Not applicableCriterion 4.6For each pre-recorded time-based media with synchronized audio description, is it relevant?
Partially compliantCriterion 4.7Is each temporal medium clearly identifiable (except in special cases)?
Non-compliantCriterion 4.8Does every non-temporal media have an alternative if necessary (except in special cases)?
Not applicableCriterion 4.9For each non-temporal media with an alternative, is this alternative relevant?
AgreedCriterion 4.10Is every automatically triggered sound controllable by the user?
AgreedCriterion 4.11Is the consultation of each temporal media, if necessary, controllable by the keyboard and any pointing device?
AgreedCriterion 4.12Is the consultation of each non-temporal media controllable by the keyboard and any pointing device?
Partially compliantCriterion 4.13Is every temporal and non-temporal media compatible with assistive technologies (except in special cases)?
Not applicableCriterion 7.1Is each script, if necessary, compatible with assistive technologies?
AgreedCriterion 7.2For each script with an alternative, is this alternative relevant?
AgreedCriterion 7.3Is each script controllable by keyboard and by any pointing device (except in special cases)?
AgreedCriterion 7.4For each script that initiates a context change, is the user notified or do they have control over it?
Non-compliantCriterion 7.5On each web page, are status messages properly conveyed by assistive technologies?
Structure du code
5 / 7 compliant
, 2 midterms, 3 not applicable
AgreedCriterion 8.1Is each web page defined by a document type?
Partially compliantCriterion 8.2For each web page, is the language code for each language change valid and relevant?
AgreedCriterion 8.3Is the default language present on every web page?
AgreedCriterion 8.4For each web page with a default language, is the language code relevant?
AgreedCriterion 8.5Does every web page have a page title?
AgreedCriterion 8.6For each web page with a page title, is this title relevant?
Not applicableCriterion 8.7In every web page, is each language change indicated in the source code (except in special cases)?
Not applicableCriterion 8.8On every web page, does every link have a label?
Partially compliantCriterion 8.9On each web page, tags should not be used solely for presentation purposes. Is this rule being followed?
Not applicableCriterion 8.10Are changes in reading direction indicated on every web page?
Structuration de l'information
2 / 3 compliant
, 1 midterms, 1 not applicable
Partially compliantCriterion 9.1On each web page, is the information structured by the appropriate use of headings?
AgreedCriterion 9.2Is the document structure consistent on every web page (excluding special cases)?
Not applicableCriterion 9.3Is each list properly structured on every web page?
AgreedCriterion 9.4On each web page, is every quote properly cited?
Présentation de l'information
4 / 13 compliant
, 6 midterms, 3 non-compliant, 1 not applicable
AgreedCriterion 10.1Are style sheets used on the website to control the presentation of information?
AgreedCriterion 10.2On each web page, does the visible content carrying information remain present when the style sheets are disabled?
Partially compliantCriterion 10.3Is the information on each web page still understandable when the style sheets are disabled?
AgreedCriterion 10.4On each web page, does the text remain readable when the font size is increased up to at least 200%, except in special cases?
Non-compliantCriterion 10.5In each web page, are the CSS declarations for element background colors and fonts used correctly?
Partially compliantCriterion 10.6On every web page, is every link whose nature is not obvious clearly distinguishable from the surrounding text?
AgreedCriterion 10.7On every web page, is the focus indicator visible for each element that receives focus?
Not applicableCriterion 10.8For each web page, are hidden contents intended to be ignored by assistive technologies?
Partially compliantCriterion 10.9On each web page, information should not be conveyed solely by shape, size, or position. Is this rule being followed?
Non-compliantCriterion 10.10On each web page, information should not be conveyed solely by shape, size, or position. Is this rule implemented appropriately?
Partially compliantCriterion 10.11For each web page, can the content be presented without any loss of information or functionality and without requiring vertical scrolling for a window with a height of...
Partially compliantCriterion 10.12On each web page, can the text spacing properties be redefined by the user without loss of content or functionality (except in special cases)?
Non-compliantCriterion 10.13On each web page, are additional contents that appear when focusing on or hovering over an interface component controllable by the user (except in special cases)?
Partially compliantCriterion 10.14On each web page, can additional content appearing only through CSS styles be made visible via keyboard and any pointing device?
Partially compliantCriterion 11.1Does each form field have a label?
Partially compliantCriterion 11.2Is each label associated with a form field relevant (except in special cases)?
AgreedCriterion 11.3In each form, is every label associated with a form field that has the same function and is repeated multiple times on the same page or across a set of pages consistent?
AgreedCriterion 11.4In each form, are each field label and its associated field placed next to each other (except in special cases)?
AgreedCriterion 11.5In each form, are fields of the same type grouped together, if necessary?
Not applicableCriterion 11.6In each form, does each grouping of fields of the same type have a legend?
Not applicableCriterion 11.7In each form, is every legend associated with a grouping of fields of the same nature relevant?
AgreedCriterion 11.8In each form, are items of the same type in a choice list grouped together appropriately?
AgreedCriterion 11.9In each form, is the label of each button appropriate (except in special cases)?
AgreedCriterion 11.10In each form, is input validation used appropriately (excluding special cases)?
Partially compliantCriterion 11.11In each form, is the input validation accompanied, if necessary, by suggestions to help correct input errors?
AgreedCriterion 11.12For each form that modifies or deletes data, or that submits answers to a test or exam, or whose validation has financial or legal consequences, the data entered must be...
Not applicableCriterion 11.13Can the purpose of an input field be inferred to facilitate the automatic filling of fields with user data?
AgreedCriterion 12.1Does each set of pages have at least two different navigation systems (except in special cases)?
AgreedCriterion 12.2In each set of pages, are the menu and navigation bars always in the same place (except in special cases)?
Non-compliantCriterion 12.3Is the "site map" page relevant?
Non-compliantCriterion 12.4In each set of pages, is the "site map" page accessible in the same way?
AgreedCriterion 12.5In each set of pages, is the search engine accessible in the same way?
Not applicableCriterion 12.6Can the content grouping areas present on multiple web pages (header areas, main navigation, main content, footer, and search engine) be...
Partially compliantCriterion 12.7Is a skip link or quick access link to the main content area present on every web page (except in special cases)?
AgreedCriterion 12.8Is the tab order consistent on every web page?
AgreedCriterion 12.9On each web page, navigation must not contain keyboard traps. Is this rule being followed?
Not applicableCriterion 12.10On each web page, are single-key keyboard shortcuts (lowercase or uppercase letters, punctuation, numbers, or symbols) controllable by the user?
Not applicableCriterion 12.11On every web page, are additional contents that appear on hover, focus, or activation of an interface component always accessible by keyboard if necessary?
Not applicableCriterion 13.1For each web page, does the user have control over every time limit that modifies the content (except in special cases)?
AgreedCriterion 13.2On every web page, opening a new window must not be triggered without user action. Is this rule being followed?
AgreedCriterion 13.3On every web page, does every downloadable office document have an accessible version if necessary (except in special cases)?
Not applicableCriterion 13.4For each office document with an accessible version, does this version provide the same information?
AgreedCriterion 13.5On every web page, does every cryptic content (ASCII art, emoticons, cryptic syntax) have an alternative?
AgreedCriterion 13.6On each web page, for every cryptic content (ASCII art, emoticon, cryptic syntax) that has an alternative, is this alternative relevant?
Not applicableCriterion 13.7Are sudden changes in brightness or flashing effects used appropriately on every web page?
Not applicableCriterion 13.8On every web page, is every moving or blinking content controllable by the user?
AgreedCriterion 13.9On each web page, is the content accessible regardless of the screen orientation (portrait or landscape) (except in special cases)?
Non-compliantCriterion 13.10On every web page, can features that are usable or available through a complex gesture also be accessible through a simple gesture (except in special cases)?
Not applicableCriterion 13.11On every web page, can actions triggered by a pointing device on a single point of the screen be undone (except in special cases)?
Not applicableCriterion 13.12On each web page, can features that involve movement of or towards the device be alternatively satisfied (except in special cases)?
Establishment of this accessibility statement
Technologies used for the website development
Shopify Liquid
HTML5
CSS
JavaScript
Test environment
Operating Systems
Apple Mac OS X 13.4
Microsoft Windows 11
Apple iOS 16
Google Android 13
Browsers and Software
In the latest versions available on the different operating systems:
Google Chrome
Windows Edge
Safari
Brave
Adobe Acrobat Reader / Preview on Mac (for PDFs only)
Tools used during the evaluation
Mouse emulations, magnifiers, and on-screen keyboards for different systems.
Voiceover (Apple systems only)
Talkback (Android only)
NVDA 2024 and Freedom Scientific Jaws 2022 (PC systems only)
Tanaguru webext RGAA4
RGAA Assistant
Graphic evaluation tools available on different systems (colors, contrasts, subtitles, etc.)
Feedback and Contact
If you are unable to access content or a service, you can contact the person in charge to be directed to an accessible alternative or to obtain the content in another format.
This procedure is to be used in the following case. You have reported an accessibility issue that prevents you from accessing content or a service, and you have not received a satisfactory response.