MerathonAccessibility
Accessibility statement
About this translation: this page translates the French statement, which remains the reference. The audit below was carried out on the French pages. The English pages use the same templates, but have not been audited separately.
The Merathon presentation website is not subject to the accessibility obligation of article 47 of French law no. 2005-102 of 11 February 2005. J6N is nevertheless committed to making it accessible, by following the French general accessibility improvement framework (RGAA), version 4.1.2.
This statement applies to the Merathon presentation website. It does not cover the Merathon desktop application itself.
Compliance status
The French pages of the Merathon presentation website are fully compliant with RGAA 4.1.2.
- Compliance rate
- 100%
- Compliant criteria
- 59
- Non-compliant criteria
- 0
- Non-applicable criteria
- 47
Test results
The compliance audit carried out on 16 October 2026 shows that 100% of the applicable RGAA 4.1.2 criteria are met: 59 compliant criteria out of 59 applicable, among the 106 in the framework.
The overall rate is the number of compliant criteria divided by the number of applicable criteria. A criterion is compliant for the site if it is compliant on each page where it applies, and not applicable if it applies to no page.
| Page | Compliant | Non-compliant | Not applicable | Rate |
|---|---|---|---|---|
| Home page (French) | 54 | 0 | 52 | 100% |
| Presentation animation (French) | 50 | 0 | 56 | 100% |
| Accessibility statement (French) | 40 | 0 | 66 | 100% |
| Theme | Compliant | Non-compliant | Not applicable | Rate |
|---|---|---|---|---|
| 1. Images | 4 | 0 | 5 | 100% |
| 2. Frames | 2 | 0 | 0 | 100% |
| 3. Colors | 3 | 0 | 0 | 100% |
| 4. Multimedia | 0 | 0 | 13 | — |
| 5. Tables | 4 | 0 | 4 | 100% |
| 6. Links | 2 | 0 | 0 | 100% |
| 7. Scripts | 4 | 0 | 1 | 100% |
| 8. Mandatory elements | 9 | 0 | 1 | 100% |
| 9. Structure of information | 3 | 0 | 1 | 100% |
| 10. Presentation of information | 13 | 0 | 1 | 100% |
| 11. Forms | 4 | 0 | 9 | 100% |
| 12. Navigation | 5 | 0 | 6 | 100% |
| 13. Consultation | 6 | 0 | 6 | 100% |
| Total | 59 | 0 | 47 | 100% |
Inaccessible content
Non-compliance
The audit found no non-compliant criterion.
Exemptions for disproportionate burden
None.
Content not subject to the accessibility obligation
- The GitHub pages linked from the site (downloads, source code, issues, release notes), which belong to a third-party service.
Preparation of this accessibility statement
This statement was prepared on 15 October 2026 and updated on 16 October 2026, following a new internal audit the same day. On 2 November 2026, after two scenes were added to the animation along with a new demo, the automated checks were run again on this content.
Technologies used to build the site
- HTML5
- CSS
- JavaScript
- WAI-ARIA
Test environment
The checks were done with Google Chrome on Linux, driven by Playwright, at widths of 1920, 1280, 640 and 320 pixels, and by keyboard. Rendering through the browser's accessibility tree was checked. No test has yet been carried out with an assistive technology (screen reader, magnification software, voice control).
Tools used to assess accessibility
- axe-core 4.10.3 (WCAG 2.0, 2.1 and 2.2 A and AA rules, and best practices), including while the animation plays and at 200%
- html-validate 9.4.1
- Contrast ratios calculated with the WCAG 2.1 formula, on each displayed text, in the 15 scenes of the animation
- Automatic search for cut-off text, with the spacing of criterion 10.12, at 320 px and at 200%
- Google Chrome developer tools: accessibility tree, tab order
- Manual review of the source code, criterion by criterion
Pages of the site covered
Detailed audit grid
Status of each of the 106 criteria for the whole site, with what was checked. Expand a theme to see its criteria. The criteria are translated from the French framework for information. The interface labels quoted are given in English; the audit checked their French versions.
1. Images4 C, 0 NC, 5 NA
| No. | Criterion | Status |
|---|---|---|
| 1.1 | Does each informative image have a text alternative?GIF: alt; animation: logos, 2 SVGs with role=img, mockup with role=img and aria-label. Statement: no informative image. | Compliant |
| 1.2 | Is each decorative image correctly ignored by assistive technologies?alt="" (header logos, Dock icon), canvas and decorations aria-hidden. | Compliant |
| 1.3 | For each informative image with a text alternative, is this alternative relevant?Alternatives reviewed one by one. | Compliant |
| 1.4 | For each image used as a CAPTCHA or test image, does the alternative identify the nature and function of the image?No CAPTCHA. | Not applicable |
| 1.5 | For each image used as a CAPTCHA, is an alternative means of access present?No CAPTCHA. | Not applicable |
| 1.6 | Does each informative image have a detailed description, if needed?Judged unnecessary: the GIF's alt lists the screens, detailed in the Features section. | Not applicable |
| 1.7 | For each informative image with a detailed description, is this description relevant?No detailed description. | Not applicable |
| 1.8 | Each informative text image must, if possible, be replaced with styled text. Is this rule followed?Only special cases: logo, animated capture of the application. | Not applicable |
| 1.9 | Is each image caption correctly linked to the corresponding image, if needed?figure with role=figure, aria-label identical to the figcaption. | Compliant |
2. Frames2 C, 0 NC, 0 NA
| No. | Criterion | Status |
|---|---|---|
| 2.1 | Does each frame have a frame title?iframe title present. | Compliant |
| 2.2 | For each frame with a frame title, is this title relevant?"Animation de présentation de Merathon, avec musique" (Merathon presentation animation, with music). | Compliant |
3. Colors3 C, 0 NC, 0 NA
| No. | Criterion | Status |
|---|---|---|
| 3.1 | On each web page, information must not be given by color alone. Is this rule followed?Active chip: ✓ check mark; underlined links; diff lines: box + hidden text; diagram wires: dashes + text. | Compliant |
| 3.2 | Is the contrast between the text color and its background color high enough?280 text nodes measured in the 15 scenes, transient text included at its maximum opacity: 4.91:1 minimum. Home page and statement: no defect (axe-core). | Compliant |
| 3.3 | Are the colors used in interface components or informative graphics sufficiently contrasted?Search field 3.67:1, chips 3.35:1, slider rail 4.06:1, focus 9:1. Comparison bars: information also given as text. | Compliant |
4. Multimedia0 C, 0 NC, 13 NA
| No. | Criterion | Status |
|---|---|---|
| 4.1 | Does each pre-recorded time-based medium have a text transcript or audio description, if needed?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.2 | For each pre-recorded time-based medium with a text transcript or synchronized audio description, are these relevant?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.3 | Does each pre-recorded synchronized time-based medium have synchronized captions, if needed?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.4 | For each pre-recorded synchronized time-based medium with synchronized captions, are these captions relevant?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.5 | Does each pre-recorded time-based medium have a synchronized audio description, if needed?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.6 | For each pre-recorded time-based medium with a synchronized audio description, is it relevant?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.7 | Is each time-based medium clearly identifiable?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.8 | Does each non-time-based medium have an alternative, if needed?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.9 | For each non-time-based medium with an alternative, is this alternative relevant?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.10 | Can the user control each automatically triggered sound?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.11 | Can each time-based medium be controlled by keyboard and any pointing device, if needed?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.12 | Can each non-time-based medium be controlled by keyboard and any pointing device?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
| 4.13 | Is each time-based and non-time-based medium compatible with assistive technologies?No audio or video (video, audio, object, embed). The animation is HTML assessed under the other themes; its music never starts by itself. | Not applicable |
5. Tables4 C, 0 NC, 4 NA
| No. | Criterion | Status |
|---|---|---|
| 5.1 | Does each complex data table have a summary?The statement's tables are simple: a single level of headers. | Not applicable |
| 5.2 | For each complex data table with a summary, is it relevant?No complex table. | Not applicable |
| 5.3 | For each layout table, is the linearized content still understandable?No layout table. | Not applicable |
| 5.4 | For each data table with a title, is the title correctly associated with the table?Results tables of the statement: each table has a caption. | Compliant |
| 5.5 | For each data table with a title, is it relevant?Explicit titles: "Results by page", "Results by theme", "Criteria of the Images theme"… | Compliant |
| 5.6 | For each data table, is each column header and row header correctly declared?Column and row headers in th. | Compliant |
| 5.7 | For each data table, is the appropriate technique used to associate each cell with its headers?scope="col" or scope="row" attribute on each th. | Compliant |
| 5.8 | Layout tables must not use elements specific to data tables. Is this rule followed?No layout table. | Not applicable |
6. Links2 C, 0 NC, 0 NA
| No. | Criterion | Status |
|---|---|---|
| 6.1 | Is each link explicit?Labels explicit alone or through their context; the visible label is included in the accessible name. | Compliant |
| 6.2 | On each web page, does each link have a label?No empty link (axe and accessibility tree). | Compliant |
7. Scripts4 C, 0 NC, 1 NA
| No. | Criterion | Status |
|---|---|---|
| 7.1 | Is each script compatible with assistive technologies, if needed?aria-pressed on the cheat sheet chips, native details, complete ARIA slider (valuenow, valuetext), "Size" group in the animation. Checked in Chrome's accessibility tree. | Compliant |
| 7.2 | For each script with an alternative, is this alternative relevant?Animation: "Text version" link to the home page, which repeats all the content. | Compliant |
| 7.3 | Can each script be controlled by keyboard and any pointing device?Tested with a simulated keyboard: start, Space, arrows, Home/End on the slider, pausing the GIF. | Compliant |
| 7.4 | For each script that initiates a change of context, is the user warned or in control of it?No change of context triggered by script. | Not applicable |
| 7.5 | On each web page, are status messages correctly rendered by assistive technologies?Number of entries in role=status; scene, animation size and end announced by an aria-live region. | Compliant |
8. Mandatory elements9 C, 0 NC, 1 NA
| No. | Criterion | Status |
|---|---|---|
| 8.1 | Is each web page defined by a document type?<!doctype html>. | Compliant |
| 8.2 | For each web page, is the generated source code valid for the specified document type?html-validate 9.4.1, standard rule set: no errors on the 3 pages. | Compliant |
| 8.3 | On each web page, is the default language present?lang="fr". | Compliant |
| 8.4 | For each web page with a default language, is the language code relevant? | Compliant |
| 8.5 | Does each web page have a page title? | Compliant |
| 8.6 | For each web page with a page title, is this title relevant?Distinct, descriptive titles. | Compliant |
| 8.7 | On each web page, is each change of language indicated in the source code?"Git Repository Manager", "merge" with lang="en". Common Git terms (commit, rebase, pull request): special case of terms in common use and understood in context. | Compliant |
| 8.8 | On each web page, is the language code of each change of language valid and relevant? | Compliant |
| 8.9 | On each web page, tags must not be used for presentation only. Is this rule followed?Decorative i, b, em, hr replaced; remaining b = product names and keywords. | Compliant |
| 8.10 | On each web page, are changes in reading direction indicated?No right-to-left text. | Not applicable |
9. Structure of information3 C, 0 NC, 1 NA
| No. | Criterion | Status |
|---|---|---|
| 9.1 | On each web page, is information structured through the appropriate use of headings?Hierarchy h1 > h2 > h3 > h4 without gaps, checked in the accessibility tree. | Compliant |
| 9.2 | On each web page, is the document structure coherent?header, nav, main, footer; main on the animation. | Compliant |
| 9.3 | On each web page, is each list correctly structured?Native ul and ol; role=list and listitem in the animation scenes. | Compliant |
| 9.4 | On each web page, is each quotation correctly indicated?The slogan is not a quotation. | Not applicable |
10. Presentation of information13 C, 0 NC, 1 NA
| No. | Criterion | Status |
|---|---|---|
| 10.1 | On the website, are style sheets used to control the presentation of information?No presentation attributes except exceptions (image width and height, SVG attributes). | Compliant |
| 10.2 | On each web page, does visible informative content remain present when style sheets are disabled?States also rendered as text (selected category, checked lines). | Compliant |
| 10.3 | On each web page, does information remain understandable when style sheets are disabled?Coherent DOM order. | Compliant |
| 10.4 | On each web page, does text remain readable when the font size is increased to at least 200%?Home page and statement: browser zoom at 200%, with no loss. Animation: "Enlarge" and "Shrink" buttons below the scene, from 100 to 200%; beyond the window, the scene scrolls, by keyboard and by mouse (WCAG technique G178). | Compliant |
| 10.5 | On each web page, are CSS declarations of element background colors and fonts used correctly?Background color declared on body, inherited everywhere. | Compliant |
| 10.6 | On each web page, is each link whose nature is not obvious visible relative to the surrounding text?Links in text are underlined. | Compliant |
| 10.7 | On each web page, for each element receiving focus, is the focus visible?3 px turquoise outline recorded on each element in the tab order. | Compliant |
| 10.8 | For each web page, are hidden contents meant to be ignored by assistive technologies?.sr text deliberately exposed; inactive scenes in visibility:hidden. | Compliant |
| 10.9 | On each web page, information must not be given by shape, size or position alone. Is this rule followed?Security diagram and diff lines doubled with text. | Compliant |
| 10.10 | On each web page, information must not be given by shape, size or position alone. Is this rule implemented relevantly? | Compliant |
| 10.11 | For each web page, can content be presented without loss of information or functionality, and without horizontal scrolling, at 320 px?Measured at 320 and 640 px: no horizontal scrolling. On the home page, the animation iframe stays 520 px high on small screens so that its controls do not cover the scene. Animation: special case of presentations. | Compliant |
| 10.12 | On each web page, can the user redefine text spacing properties without loss of content or functionality?Spacing from the criterion (line height 1.5, letters 0.12 em, words 0.16 em, paragraphs 2 em) applied to the 3 pages and 15 scenes: no text cut off. In the animation, the scene grows and scrolls instead of cutting off text. | Compliant |
| 10.13 | On each web page, can the user control additional content appearing on focus or hover of an interface component?No tooltip or hover menu. | Not applicable |
| 10.14 | On each web page, can additional content appearing through CSS alone be made visible by keyboard and any pointing device?Skip link visible on focus. | Compliant |
11. Forms4 C, 0 NC, 9 NA
| No. | Criterion | Status |
|---|---|---|
| 11.1 | Does each form field have a label?Search: visible label; slider: aria-label and title. | Compliant |
| 11.2 | Is each label associated with a form field relevant?Visible name included in the accessible name. | Compliant |
| 11.3 | In each form, is each label associated with a field that has the same function and is repeated several times consistent?No repeated field. | Not applicable |
| 11.4 | In each form, are each field label and its associated field adjacent?Search: label just above. Slider: no visible label. | Compliant |
| 11.5 | In each form, are fields of the same nature grouped, if needed?A single field per page. | Not applicable |
| 11.6 | In each form, does each grouping of fields of the same nature have a legend? | Not applicable |
| 11.7 | In each form, is each legend associated with a grouping of fields of the same nature relevant? | Not applicable |
| 11.8 | In each form, are items of the same nature in a list of choices grouped relevantly?No select. | Not applicable |
| 11.9 | In each form, is the label of each button relevant?Action labels: "Pause the animated demo", "Mute", "Enlarge the animation"… The visible text is included in the accessible name. | Compliant |
| 11.10 | In each form, is input validation used relevantly?No validated input. | Not applicable |
| 11.11 | In each form, is input validation accompanied, if needed, by suggestions that help correct errors? | Not applicable |
| 11.12 | For each form that changes or deletes data, submits answers to a test or exam, or has financial or legal consequences, can the data entered be changed, updated or recovered?No data submitted. | Not applicable |
| 11.13 | Can the purpose of an input field be inferred to make it easier to autofill fields with the user's data?No personal data field. | Not applicable |
12. Navigation5 C, 0 NC, 6 NA
| No. | Criterion | Status |
|---|---|---|
| 12.1 | Does each set of pages have at least two different navigation systems?Special case: 3-page site. | Not applicable |
| 12.2 | In each set of pages, are the menu and navigation bars always in the same place?No menu common to the pages. | Not applicable |
| 12.3 | Is the site map page relevant?No site map. | Not applicable |
| 12.4 | In each set of pages, is the site map page accessible from an identical feature? | Not applicable |
| 12.5 | In each set of pages, can the search engine be reached in the same way?The cheat sheet search is not a site search engine. | Not applicable |
| 12.6 | Can content grouping areas present on several web pages be reached or skipped?banner, navigation, main, contentinfo and search landmarks; the statement's grid is divided into titled sections. | Compliant |
| 12.7 | On each web page, is a skip link or quick access link to the main content area present?"Skip to content" as the first element in the tab order. | Compliant |
| 12.8 | On each web page, is the tab order coherent?Recorded key by key on the 3 pages; you enter the animation iframe and leave it in order. | Compliant |
| 12.9 | On each web page, navigation must not contain a keyboard trap. Is this rule followed?You can enter and leave the iframe by keyboard. | Compliant |
| 12.10 | On each web page, can the user control keyboard shortcuts that use a single key?Space and arrows are not character keys within the meaning of the criterion. | Not applicable |
| 12.11 | On each web page, can additional content appearing on hover, focus or activation of an interface component be reached by keyboard?Cheat sheet entries (home page) and detailed grid (statement) in native details, reachable and expandable by keyboard. | Compliant |
13. Consultation6 C, 0 NC, 6 NA
| No. | Criterion | Status |
|---|---|---|
| 13.1 | For each web page, does the user have control over each time limit that changes the content?No refresh, redirect or session. | Not applicable |
| 13.2 | On each web page, opening a new window must not be triggered without a user action. Is this rule followed?No new window. | Not applicable |
| 13.3 | On each web page, does each downloadable office document have an accessible version, if needed?No document for direct download. | Not applicable |
| 13.4 | For each office document with an accessible version, does this version offer the same information? | Not applicable |
| 13.5 | On each web page, does each cryptic content have an alternative?Symbols ⟳ and ⌕ hidden and doubled with text; "·" rendered as a separator. | Compliant |
| 13.6 | On each web page, for each cryptic content with an alternative, is this alternative relevant? | Compliant |
| 13.7 | On each web page, are sudden changes in brightness or flash effects used correctly?GIF: 441 frames, luminance between 16 and 38 out of 255. Animation: a single end circle. | Compliant |
| 13.8 | On each web page, can the user control each moving or blinking content?GIF: pause button, paused with "reduce motion". Animation: never starts by itself, Pause button and Space key. | Compliant |
| 13.9 | On each web page, can the content be viewed whatever the screen orientation?No orientation lock. | Compliant |
| 13.10 | On each web page, can features available through a complex gesture also be used with a simple gesture?No complex gesture. | Not applicable |
| 13.11 | On each web page, can actions triggered with a pointing device on a single point of the screen be canceled?Actions on the click event, so on release. | Compliant |
| 13.12 | On each web page, can features that involve moving the device or a movement toward it be achieved in another way?No motion-based feature. | Not applicable |
Feedback and contact
If you cannot access a piece of content or a service, report it to get an accessible alternative, in another form or by another means.
- Open an issue on GitHub: github.com/J-Dudek/merathon/issues
If possible, state the page concerned, what the problem is, and your browser and assistive technology.
Remedies
If you have reported an accessibility defect that prevents you from accessing a piece of content or a service and have not received a satisfactory answer, you can contact the French Defender of Rights (Défenseur des droits):
- by writing with the online form;
- through the delegate of the Defender of Rights in your region, whose contact details are on the map of delegates;
- by post, free of charge and without a stamp: Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07.