Accessibility: Non-compliant

Accessibility statement

Elwing Tech SAS is committed to making www.ritmic.co accessible in accordance with Article 47 of Law No. 2005-102 of February 11, 2005, on equal rights and opportunities, participation and citizenship of disabled persons, as well as provisions transposing the European Accessibility Act (EU Directive 2019/882).

This accessibility statement applies to Ritmic (ritmic.co).

Compliance status

Ritmic.co is not compliant with RGAA (General Accessibility Improvement Framework) 4.1. 

Accessibility technical review

Date: July 7, 2026 Method: Automated review + inspection of rendered DOM (browser). This is not an official RGAA audit as per DINUM method (106 criteria on a representative sample of pages with full manual screen reader/keyboard tests) — it is a working base to prioritize fixes before a certified audit.

Summary

Status Number of findings
✅ Compliant points 7
⚠️ Points to fix 5
❓ Not automatically verifiable 3


✅ Compliant points

  1. Page language declared (lang="fr")
  2. Consistent heading structure (only one H1, logical H2 hierarchy)
  3. 97/97 images have an attribute alt (no image without alt)
  4. 154/154 form fields have an associated label (via <label>, aria-label or wrapping)
  5. 73/73 buttons have accessible text or label
  6. Skip link ("Skip to content") present
  7. Structural landmarks present: main, nav, footer


⚠️ Points to fix


1. Keyboard focus indicator (RGAA criterion 10.7 / WCAG 2.4.7) — High priority

On the tested sample (footer links, social networks), the outline style is disabled (outline-style: none) without a visible replacement indicator (no box-shadow or border on focus detected). Concrete consequence: a keyboard user cannot see where they are on the page. → Action: add a clear :focus-visible style (outline, highlight) on all interactive elements.

2. Insufficient contrast (RGAA criterion 3.3 / WCAG 1.4.3) — Medium to high priority

29 text elements detected with contrast ratio below the required threshold (4.5:1 normal text, 3:1 large/bold text), including:

  • Currency selector "EUR €" (ratio ≈ 1.1:1)
  • Link "Sign up" in small size (ratio ≈ 1:1)
  • Title "New: The Yuvy 3 is here!" (ratio ≈ 1.09:1 — to be visually checked, probably on image background, see limitations below)

→ Action: visually check each case, adjust text colors or background opacity.

3. Untitled iframes (RGAA criterion 7.3) — Medium priority

4 iframes out of 4 do not have a title attribute, which prevents screen reader users from understanding their content before entering it. → Action: add a descriptive title to each iframe (e.g., title="YouTube video player").

4. Images with alt empty

22 images have an alt="". This is correct if and only if these images are purely decorative. To be confirmed one by one.

5. Embedded video content (subtitles)

No tag <video> native detected — videos appear to be embedded via the iframes mentioned in point 3. The subtitles of these videos are not verifiable from the site itself (depends on the hosting platform, e.g., YouTube).

❓ Not automatically verifiable — requires manual review

  • Text contrast on image backgrounds (hero banners): contrast scripts do not read the visual content of background images.
  • Complete keyboard navigation: tab order, keyboard traps, behavior of dropdown menus and carousels.
  • Screen reader compatibility (NVDA, JAWS, VoiceOver): voice announcements, focus management in dynamic components (popups, product filters).
  • Text zoom at 200% and responsive at 320px wide (RGAA 10.x): to be tested manually in the browser.

Recommendation

This report can directly feed the annual action plan and the multi-year plan required by the EAA. For the final accessibility statement, a full RGAA 4.1 audit is still recommended, especially on the "not automatically verifiable" points above, before publishing an official compliance rate.

Establishment of this accessibility statement

This statement was made on July 7, 2026.

  • Technologies used to build the site: Liquid

Improvement and contact

If you cannot access content or a service, you can contact the person responsible at Elwing Tech SAS to be directed to an accessible alternative or to obtain the content in another form.

We try to respond within 2 business days.

Appeal procedures

If you notice an accessibility issue preventing you from accessing content or a feature of the site, report it to us, and you do not receive a response, you have the right to send your complaints or a referral request to the Defender of Rights.

Several options are available to you: