Since October, I have been removing from the screens of Verikora, Folioviv and Sovkora what does not serve the person looking at them. I write each removal down in a decision record next to the code, with the principle behind it and what it costs.
I show five of them here. The screens are drawn in pen, not captured: each number on a drawing points to one line of its legend. Éric Tremblay, the person in the examples, comes from our demo cast, not from our customers or our administrators.
| Choice | Kept, rather than | Rule | Figure |
|---|---|---|---|
| Arrival | one filled button, rather than a drop zone in the middle | recognition rather than recall | 1 filled button on the home, measured on 15 November |
| Phone | one row per document and a menu, rather than a table and five tabs | WCAG 2.2, criterion 1.4.10 | 0 px of overflow at 390 px, measured |
| Empty screen | one sentence and one action, rather than a blank page | one action, two at most | 1 tap to the first file |
| Error | the message in place of the result, rather than a notice that fades | WCAG 2.2, criterion 3.3.3 | the skeleton waits 300 ms |
| Themes and motion | light, dark or system, and nothing moves under reduced motion | WCAG 2.2, criterion 2.3.3 | 0 animation under reduced motion, measured |
One primary action on arrival
Éric opens Verikora with a lease as a PDF. The point is to learn what is questionable in it, not to look for where to drop it.
The first version of the home had a drop zone and two checkboxes, repeated on three screens; what there was to do came fourth. On 4 November, I removed from the home the dotted zone, its second primary button and the « Ou essayez » (or try) suggestions.
Before
- 1The dotted zone: in the middle of the page, it took the place of the answer.
- 2Its filled button: a second primary button, on top of the header's.
- 3« Ou essayez » (or try): suggestions for someone who already has their document.
After
- 4« Vérifier un document » (check a document): the only filled button on the screen; behind it, a real file field for the keyboard and for phones.
- 5The whole window: a PDF dropped anywhere starts the check.
I wrote the rule in one line: the answer first, at most one drop zone per screen, and everywhere else the whole window takes the file. It is recognition rather than recall: nobody should have to look for the one thing the page exists for. In our library, that is the drop overlay. Only the very first day's screen keeps the suggestions, because someone who has nothing yet needs an example.
I refused a « Load the demo » button: no service did it. When Verikora does not know which document it has, it asks one question, « Which document? », rather than start an analysis that would cost anyway. In exchange, a file dropped on the page takes the owner's default options, since they only make sense once the file is known.
In Sovkora, the Studios screen is a list, and the same rule gives one action per row. Before, it was a grid of cards in two columns, three per screen, where nobody could tell an installed Studio from one that needs a pack.
Before
- 1The cards: three per screen, with no readable state.
After
- 2The filter « All 45 · Ready 29 · To get 16 »: it lives in the address, so the filtered list can be sent as a link.
- 3The state: written in words on every row.
- 4The action: one per row, « Run » if the Studio is ready, « Get the pack » if not.
I set aside two tabs, « Ready » and « To get »: the same Studio would have lived in two places depending on what you own. The description now fits on a single line, cut short.
On a phone, nothing spills over
Éric rereads a check standing in a stairwell, phone in one hand.
Verikora's settings had five tabs in a row. On a 390 px screen, they pushed the page 167 px too far, and 197 px at 360 px. That breaks WCAG 2.2's reflow rule (criterion 1.4.10, level AA): content must fit the width without scrolling in two directions. On a phone, those sections are now one menu.
Before
- 1Five tabs in a row: the last ones leave the screen.
- 2The overflow: the whole page slides sideways.
After
- 3One menu: the open section is written out, the others are one tap away.
The lists followed. A row printed four « label: value » pairs per document: you had to read a form to find a title and a result. On a wide screen, the table stays.
Before
- 1Four label: value pairs: for every document, before the result even shows.
After
- 2The title: what the person looks for first.
- 3One line of facts: the type and the date, « Bail · 1 nov. 2026 » (lease, 1 Nov 2026).
- 4The result: at the end of the row; the rest waits in the detail, one tap away.
What it costs: on a phone, you see two lines per document, not the whole file. Measured on 15 November, none of the nine screens scrolls sideways at 390 px, in light or dark.
Sovkora's phone app followed the same reasoning for its navigation. For it I only have its decision record, no measure.
- 1Four tabs at the bottom: within reach of the thumb.
- 2An icon and a word: the word is never cut.
- 3Nothing at the top: no hidden menu in the place hardest to reach with one hand.
Most people hold their phone in one hand and reach the lower half of the screen. A visible bar is found more easily than a hidden menu, and an icon with its word is understood better than an icon alone. The plan, the packs and the credits are not on the phone: whoever wants them goes to the web.
An empty screen says what to do
Éric creates a collection « À classer » (to sort) and opens it before putting anything in.
- 1The owl: it goes with the sentence, it never replaces it.
- 2The sentence: « Rien ici pour l'instant. Déposez un document ou créez un dossier. » (nothing here yet; drop a document or create a folder)
- 3The only drop zone on the screen: with what it accepts: PDF, Word, OpenDocument, text or photo, up to 10 MB.
An empty screen is the product's chance to explain what the place is for and what to do first. I put the rule in the library, so that every product follows it: the empty state has a title that says what is empty, a description that says what will fill it, one action, two at most, and the mascot state always surrounds words. It takes one tap to go from the empty screen to the first file, none if you drop the document on the page. On the first day, the whole empty library offers two examples to try, a tenant's lease and a landlord's file.
A page that is not meant for you says so instead of looking broken: « Les dossiers de candidats sont pour les gestionnaires » (applicant files are for managers), then a single button, « Changer de rôle » (change role). Folioviv follows the same rule with its beaver: « Aucune réservation pour l'instant » (no bookings yet), then what will come here, your bookings, your invoices and your files.
An error stays in its place
Éric drops a maintenance contract. The PDF is made in a way Verikora cannot read.
- 1The message: where the report would have been: « Ce PDF n'est pas sous une forme que nous pouvons vérifier. Choisissez une autre copie du document, ou réessayez. » (this PDF is not in a form we can check; choose another copy of the document, or try again)
- 2« Réessayer » (try again): the next move, on the same screen.
- 3« Choisir un autre fichier » (choose another file): one tap leads to the upload page.
- 4The menu and the top bar: they stay usable.
- 5« Lancer la vérification » (run the check): the filled button of the « Au regard de la loi » (under the law) card, a second one on the screen, not fixed yet.
The message says what happened in our words, with no engine name; the technical message stays in our logs. When a PDF has no text, it also says what goes on: « L'examen du fichier, lui, a lieu. » (the file itself is still examined). WCAG 2.2 (criterion 3.3.3, level AA) asks that the fix be suggested when it is known. I go a little further: the error and its next move take the place of the result that did not come. In the library, that is the alert.
I set aside the notice that fades after a few seconds: for a failure that needs action, the person may not even be looking. I also set aside one loading screen shared by every page, which is only a centred spinner under another name. Each page has its own skeleton, in its own shape, shown only after 300 ms so a fast page never flickers. The only spinner in Verikora belongs to a button that is working, and a test refuses every other one. That makes thirty-eight small files, two per page, and a new page has to bring its own or its test fails. If people retry a page that keeps failing because the cause is not theirs, the error will need a link to the service status.
Two themes, and nothing moves if you asked
- 1« Système » (system): follows the device, through prefers-color-scheme.
- 2« Clair » (light): the same screen, the same tokens.
- 3« Sombre » (dark): the default theme; the choice is kept in the browser.
Every screen exists in light and dark. The colours come from one set of tokens that both themes read, and the theming page says how a product wears its own colour. prefers-color-scheme is what lets « Système » follow the device.
Motion follows the same logic. prefers-reduced-motion exists because motion can make some people sick, and WCAG 2.2 (criterion 2.3.3, level AAA) asks that motion triggered by an interaction can be turned off. I kept one motion system only: an animation is there to show something, never to decorate, and it stops under reduced motion. On the nine screens measured, no animation runs with reduced motion; with motion allowed, we count up to 11 on the settings and 6 on the Studios list. Every step of a check is also written in words, so reduced motion loses nothing.
What we have not fixed yet
On the failed check screen, the « Au regard de la loi » card keeps its filled button under « Réessayer » (number 5 on the drawing above). Two filled buttons on one screen is what I refuse everywhere else.
I set myself targets of at least 44 px on a phone. That is stricter than WCAG 2.2's minimum of 24 px (criterion 2.5.8, level AA), and I do not keep to it everywhere. Measured at 390 px, « Réessayer » is 40 px tall and « Choisir des fichiers » (choose files) 36 px. The buttons that expand a row of the checks list are 28 × 28 px, and their name for screen readers was left in English.
In Folioviv, the empty bookings screen says to open a shop's page, but its only button opens your own shop.
I have noted them. If a screen of our products makes you hesitate, write to me: that is where most of these choices come from.
What we measured, and what we did not
The screens were measured on 15 November on our development builds, with Playwright, at 1440 and 390 px, in light and dark, with reduced motion and then with motion allowed. We counted horizontal overflow, controls under 44 px, running animations and filled buttons. The « before » figures (167 px, three screens, four pairs per row) are the ones written in our records on the day of each decision; we did not measure them again. The drawings are made from those screens and those records, and they are not to scale. Nothing was timed and nobody was interviewed: what a choice saves is counted in moves and in gaps to the rule, never in minutes.
