Accessibility

Last updated 2 November 2026

We, Warehouse SAS, mean Jean to be usable by everyone, whatever their sight, hearing, movement, language or script. This page says how far along it is, what isn’t there yet, and how to tell us when something stops you.

Where it stands

jean.is is partially conformant with RGAA 4.1.2, France’s accessibility framework, because of the problems listed below.

What the audit found

Our audit, last read on 2 November 2026, found that 80.7% of the criteria that apply are met: 71 of 88. Of the other 17, 14 aren’t met, and 3 couldn’t be checked, so they don’t count as met. The other 18 of RGAA’s 106 criteria don’t apply here. Partially conformant means at least half of them are met, but not all.

This is our own audit, made by an AI and not yet checked by any person. Other AI readers, given none of its verdicts and told of no fix, then judged the criteria again in six rounds, and their verdicts are the ones we count. The last round read the 24 that a batch of our fixes claimed to close, and failed 13, nearly all on places the fixes hadn’t touched. Readers have differed on the same code before, so take this share as close, not exact. No person has checked the result or taken Jean through it with a screen reader, and no outside party has audited Jean. You can read the full grid, criterion by criterion and page by page.

What this page covers

Jean at jean.is and the pages of this site, with the documents and collections you create in Jean: their screens and menus, Jean’s changes to accept or reject, and the files they are saved as. We audited them in French, the main pages in English too, and the homepage in Arabic. The desktop app shows the same pages but wasn’t audited on its own, and neither were the other languages. This page doesn’t cover what others make and Jean shows: sites opened in its browser, pages an AI writes in an answer, and the documents you bring. What you write in a document or a collection is yours, its headings and descriptions included.

What isn’t accessible yet

• Hearing what happens: no person has yet checked what a screen reader says as you move through tasks, search, menus, panes, documents, collections, charts and scores. The demonstrations in the help centre and on the Excel page replay a task without saying so, and their button hides itself, so the keyboard falls back to the page.
• Losing your place: in Creations beside a pane, while an offer shows, Tab can reach a card hidden under the offer and the message box.
• Finding your way: the drawer that lists your tasks isn’t marked as navigation. On the families page, a drawn profile card gives each setting and its value side by side without marking them as pairs.
• Keyboard and pointer: pointing Jean at a part of a slide takes a click; the keyboard can’t do it. On a touch screen, a map turns and tilts with two fingers, with nothing to set it straight again. In the Terminal theme, the message box barely shows that it has the keyboard.
• Seeing it: in a document with Jean’s changes, the words changed inside a line are shown by a pale tint alone, unless you set Contrast to More in Settings › Appearance or your system asks for more contrast. Two small lines fall a shade short of AA: “Jean is AI and can make mistakes” drawn on the families page, and a comparison’s “Recommended” tag while its head is stuck under the toolbar.
• Forms: the text size readout in Settings › Appearance has no label, and a design’s layout choices are named only for screen readers, with no name you can see. Search’s results and the box’s menu group their options in a way RGAA’s note doesn’t accept.
• Charts, diagrams, maps and music scores: each can also be read in words just under it, which RGAA accepts, but those words have their limits. A chart with several series tells them apart by colour unless you or your system ask for more contrast, and some colours are too pale to see, so you need its table. A map’s words give its places, not where they lie. A score’s notes are in a notation for reading music.
• Answers and tables: English passages in French pages aren’t always marked as English: an answer’s first line when the rest of it is French, search’s extracts, and the names of English decks, designs and tasks. An answer’s language is guessed once for the whole of it.
• Code: much of the app lets the browser work out each text’s direction (dir="auto"), which RGAA’s wording doesn’t count. It reads correctly all the same.
• Files you save: we read how Word documents and Excel workbooks are built, but haven’t yet run Word’s and Excel’s own accessibility checkers, as RGAA asks. Word documents have real headings, lists, table headers, their language and a title. Workbooks have a named sheet, a frozen first row and a title, not a declared table.

What comes next

We’re working through the list above. Each time readers who didn’t make the fixes judge them again, we publish the new share here. A person’s check with a screen reader is still to come.

What we test on every change

We aim for WCAG 2.2, level AA, which covers what the European standard, EN 301 549, asks of web content.

Beyond this audit, automated tests run on every change, on the first screen, a conversation, Settings and the tasks, and on every page of this site. They cover those pages only and they miss things, so passing them doesn’t make a page accessible:

• Contrast of words: every word on those screens against the pixels behind it, in every look, by night and by day.
• Contrast of controls: buttons that show only an icon, the frames of text boxes and focus rings, at 3:1 against what is beside them.
• Zoom: at 400% those screens lose no words, and text at 200% holds too.
• Targets: on those screens, everything a pointer can press is at least 24 by 24 pixels, or spaced as if it were.
• Motion: at rest nothing moves for more than five seconds, and with your system’s reduced motion nothing moves at all.
• This site: each page is checked in a browser with axe-core for what WCAG 2.2 asks at levels A and AA.

You can read how each check is made.

How we audited

Who: Warehouse SAS itself, on 1 and 2 November 2026, with no person checking the judgments. Claude, Anthropic’s AI, made the tests and the first judgments for us. Separate AI readers, each given a part of the criteria and none of those judgments, then judged them again in six rounds, and the last verdict on each criterion counts. Of the 71 criteria met, 19 rest on the second read, 12 on the third, 18 on the fourth, 8 on the fifth, 3 on the sixth and 11 on the seventh. The last four read copies of Jean with our fixes and were told of none of them.

The sample: 49 pages and screens.

• Asked for by RGAA: the homepage, the terms with their legal notice, this page, the site map, the help centre, and the lock screen, the only sign-in Jean has. There is no separate contact page.
• The main uses: a help article, a task with an answer, search, the tasks, Settings’ General and Capabilities, Creations, a design, a slide deck, charts of one series and of several, a score, a request for approval, and the pages for IT, families, Excel, bringing your history and comparing with ChatGPT.
• What you create: a document new and empty, in use, its menus, and with Jean’s changes to accept or reject; a collection new and empty, with Jean’s changes, its menus, and as a board.
• What ordinary use produces: a flowchart, a map, and an answer with sources, each looked at for what it adds.
• Every step of a process: connecting a first AI, setting a lock, and asking for a key.
• A different look: a task in the Terminal and Mondrian themes, Settings’ Appearance, and the homepage in Arabic.
• Files: an answer and a document saved as Word documents, and a collection saved as an Excel workbook.
• Five chosen at random: the comparison with Open WebUI, the comparisons’ page, the help articles on what Jean costs and on starting free with OpenRouter, and the keyboard shortcuts.

Tools: axe-core 4.14, html-validate 9.7, W3C’s Nu Html Checker, Playwright 1.64, and Jean’s own tests of contrast, zoom, targets and motion, along with the page’s code, read by hand.

Test environment: Chromium 156 on macOS 27, by keyboard and pointer. RGAA’s tests of what assistive technology announces need Firefox with NVDA and Safari with VoiceOver: they weren’t run, so what depends on them isn’t counted as met.

Technologies: HTML, CSS, JavaScript and WAI-ARIA.

Tell us

If something in Jean stops you, if you need something it shows in another form, or if this page is wrong, write to arnaud@jean.is: what you were doing, the browser, and any assistive technology you use. We’ll say what we’ll change, and when.

If you get no answer

In France, you can turn to the Défenseur des droits, which protects people from discrimination, disability included: through its website, through one of its local delegates, or by post, with no stamp, at Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07.

If your organisation serves its own copy

This page speaks for jean.is, not for your copy. An organisation that must publish a statement, as public bodies in the EU do, and in France companies with over 250 million euros of turnover, publishes its own for the address it serves Jean from: what its policy turns off, its own contact, and its country’s procedure for complaints.

In France, that means a declaration on RGAA’s template, from an audit of your own copy, with your multi-year plan, this year’s action plan, and the homepage mention that audit earns. Our grid can help prepare that audit, but it doesn’t replace it.