Accessibility statement

Maketools is committed to making its platform accessible, in line with article 47 of the French law no. 2005-102 of 11 February 2005. Our reference is RGAA 4.1.2, the French standard based on WCAG 2.1 level AA.

This statement covers the whole Maketools platform: the public site (home page, catalogue, game pages, documentation, trust center), sign-in, your account, organisation administration, the studio (forks, editor, releases, access), reports, the LMS connector, and the three games (Prompt Quest, Data Cleaning Rush, Hallucination Hunter), both as demos and as organisation forks.

Compliance status

Maketools is partially compliant with RGAA 4.1.2, because of the non-conformities listed below.

No independent expert has audited the whole platform yet, so the RGAA compliance rate has not been calculated. The audit below is an internal audit, automated and scripted, and it runs again on every code change.

Test results

The September 2026 internal audit covers more than 40 pages and screen states. Each page is tested in light and dark themes, on desktop (1,280 px) and mobile (375 px):

• Automated checks (axe-core, WCAG 2.1 A and AA rules and best practices): no violations of any severity. Contrast is measured on the page as the browser actually renders it, in both themes.
• Keyboard-only journeys: playing each of the three games, forking a game then editing and deploying it, and inviting a member. At every step, the tests check that focus is visible, follows the page order and never gets trapped. They also check the skip link and focus in dialogs: focus moves in, stays inside, then returns to the button that opened the dialog.
• Screen reader output: every page has its own title and the correct document language. Headings start from a single h1 and never skip a level. Game feedback and notifications use live regions. Every chart has a data table with a caption and column headers.
• Adaptation: no horizontal scrolling at 200 % or 400 % zoom (reflow at 320 px). Animations stop when the system asks for reduced motion; the animated scene of the home page then only starts on demand, and a button pauses it at any time. On touch screens, targets are at least 44 px.

These checks are end-to-end tests in the repository (e2e/tests/a11y-*.spec.ts and keyboard.spec.ts), and any regression makes them fail.

Non-accessible content

Non-conformities

• PDF reports (criterion 13.3): the PDF you can download from a dashboard is not tagged, so a screen reader cannot follow its structure (headings, tables). The same figures are available in accessible form in the online report and in the CSV export.
• Tests with assistive technologies: automated tests check how pages are read out (accessible names, roles, live regions), but no one has tested them yet with real screen readers (NVDA, JAWS, VoiceOver, TalkBack). Some differences may remain. These tests are planned as part of the independent audit.
• Emails (invitations, sign-in codes): their templates have not been audited yet.

Exemptions for disproportionate burden

None.

Content not subject to the accessibility obligation

The following content is provided by third parties and is outside Maketools' control:

• Stripe's payment and subscription pages (Checkout, Customer Portal);
• sign-in pages of identity providers: Google, Microsoft, and your organisation's SSO provider;
• your organisation's LMS, which hosts SCORM packages.

About this statement

This statement was written on 24 September 2026.

Technologies used

HTML5, CSS, WAI-ARIA, JavaScript (Angular), SVG, and Canvas for game backgrounds. Canvas backgrounds are hidden from assistive technologies, and every piece of text the game needs is also on the page.

Test environment

• Chromium driven by Playwright, on desktop (1,280 × 800) and on a touch phone (375 px, Pixel 7).
• Light and dark themes, with the "reduce motion" preference on.
• Tools: axe-core 4.13, plus the repository's scripted checks (headings, zoom, touch targets, focus, live regions).

Pages tested

• Public pages: home page (English and French), catalogue, each game's page, documentation, trust center, page not found.
• Each game's demo: Maketools welcome screen (the Skip countdown is announced without moving focus), while playing, paused, and on the end screen.
• Sign-in: sign in, email code, SSO, two-step verification, sign-up, forgotten password and reset, invitation.
• Account: profile, security, two-step verification, sessions, data.
• Administration: organisation creation, members, invitations, groups, security, SSO, API keys, billing, audit log, organisation.
• Studio: forks and the fork dialog, the editor (including in-place editing), the release dialog, releases, access.
• Reports: index, dashboard with data, LMS connector.
• Games: an organisation's game page, a public game (welcome screen, nickname, report), presenter mode and the SCORM game page.

Feedback and contact

If you cannot access some content or a service, contact us. We will point you to an accessible alternative or send you the content in another format.

• Email: charlotte@maketools.ai
• We reply within 5 working days.

Enforcement procedure

If you reported an accessibility issue that prevents you from accessing content or a service and did not get a satisfactory answer, you can refer the matter to the French Défenseur des droits (Defender of Rights):

• through the online form;
• by contacting the Défenseur des droits delegate in your region;
• by post, free of charge and without a stamp: Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07, France.