Skip to content
Carré
Features Accessibility
FR EN
Start free
Accessibility

Accessibility
statement.

Drawn up on 29 October 2026

EDUFREM is committed to making Carré accessible to people with disabilities, and to that end applies the technical method of the French Référentiel général d'amélioration de l'accessibilité (RGAA), version 4.1 — the national accessibility standard, which maps onto WCAG 2.1 level AA.

One point of honesty: EDUFREM is not subject to the obligation set out in article 47 of French law no. 2005-102 of 11 February 2005, which applies to companies only above €250 million in revenue. This statement is therefore voluntary. We publish it because Carré is used in classrooms and in training, because our public-sector customers have to factor accessibility into their purchasing, and because a vendor who does not measure its accessibility does not fix it.

This accessibility statement applies to the carre.app-edufrem.com website and to the Carré application (web and desktop), version 0.9.23.

The audit covered version 0.9.23. The fixes made on the day of the audit are live on the website; those that affect the application — text contrast, field labels, the open-notes bar, the microphone waveform, table headers — are included in version 0.9.24, in preparation. The non-compliances listed below are the ones that remain after those fixes.

Compliance status

Carré is partially compliant with RGAA 4.1, because of the non-compliances listed below.

Test results

98.6%

of the applicable RGAA 4.1 criteria are met: 70 compliant criteria out of 71 applicable (35 criteria do not apply to Carré). The audit was carried out in-house, on the sample of pages listed below.

For scale: when the audit opened, twelve criteria were not met. One remains. The two that weighed most: the contrast of secondary text, and the labelling of form fields.

Non-accessible content

Non-compliance

One criterion out of 71 is not met.

  • The outline of fields and cards lacks contrast (RGAA criterion 3.3, WCAG 1.4.11). The line that marks out a text field sits at 1.2 to 1 against its background in the dark theme, where 3 to 1 is required. Text itself is compliant, and the keyboard focus indicator is at 14.4 to 1. A workaround is available today: setting Settings → Accessibility → Contrast to “High” takes every border past 3 to 1.

Two points the audit first raised were settled the same day, and so no longer appear here. The website had only one navigation system: it now has a site map, linked from the footer of every page. And the PDF manuals: no page on the site offers them for download — the guides are in HTML (the user guide and the installation guide), and therefore accessible. One old PDF still sits at the root of the server with nothing linking to it; it will be removed.

One last point, which is not a non-compliance but a limit of this audit: seven screens of the application (notes list, Follow-up, Contacts, Settings, space members, school sign-in, new recording) were not tested in a browser, because the audit tooling could not open an authenticated session. They were checked by code review, which covers labels, accessible names, headings and contrast, but neither the real tab order nor screen-reader behaviour.

Disproportionate-burden exemptions

None.

Content not subject to the accessibility obligation

None. The recordings, transcripts and summaries produced in Carré belong to the people who create them: they are their content, not ours. For every recording, Carré always provides a written transcript and a summary, and it can display live captions during the session.

How this statement was drawn up

This statement was drawn up on 29 October 2026, following an in-house audit carried out the same day on version 0.9.23.

Technologies Carré is built with

  • HTML5, CSS, JavaScript and TypeScript
  • WAI-ARIA
  • React (web application), Electron (desktop application)
  • PHP (interface with the transcription and AI services)

Test environment

  • Chromium 141 on Linux, at 1280×900 and 320×800
  • Four display configurations: dark theme (the default), light theme, high contrast, and a narrow 320 px viewport
  • Two further passes: text enlarged to 200%, and text spacing pushed to 1.5× line height, 0.12 em letter spacing, 0.16 em word spacing and 2 em between paragraphs
  • macOS with VoiceOver for manual checks of how content is announced

Tools used during the evaluation

  • axe-core 4.10.2, driven by Playwright, on every page and in each of the four configurations
  • html-validate 8.24.2 for source-code validity
  • Contrast computed with the WCAG formula, applied to the palette tokens rather than to on-screen samples
  • An automated sweep, across the application's 71 components, for buttons without an accessible name, fields without an associated label, and forced tab orders
  • The browser's accessibility inspector, and keyboard-only navigation

Pages checked for compliance

  1. Home
  2. Features
  3. Pricing
  4. Accessibility
  5. Privacy and offline
  6. Use cases
  7. User guide
  8. Installation guide
  9. Site map
  10. Home, English version
  11. Application: sign-in screen
  12. Application: a note — summary, transcript, my notes and actions, the densest screen in the product

What we are fixing, and when

In the order we are tackling them:

  1. Border contrast in the default theme. Raising every border at once would visually coarsen the whole interface; we are looking to raise only the outlines of fields and buttons, leaving separator rules as they are. First quarter of 2027
  2. An audit of the seven remaining screens under real conditions, with a test account, then a full screen-reader pass. First quarter of 2027
  3. Removing the old PDF still sitting at the root of the server, which nothing links to any more. By the end of 2026
  4. A third-party audit. This one is ours; it is no substitute for an outside pair of eyes. 2027

Feedback and contact

If you cannot reach a piece of content or a feature in Carré, tell us: we need to know, and we commit to replying within one week.

  • By email: contact@edufrem.com
  • From inside the app: the “Feedback?” button at the bottom of the screen
  • By post: EDUFREM, 241 route de Vienne, 69200 Vénissieux, France

Where you can, tell us which page or screen is involved and what you use to navigate: that is often what lets us reproduce the problem first time.

Remedies

Use this procedure in the following case: you have reported an accessibility problem to us that prevents you from reaching a piece of content or a service, and you have not received a satisfactory reply.

Next update of this statement: at the next redesign, or by 29 October 2029 at the latest

🇫🇷 FR