Accessibility: what d'Origami meets, and where it falls short
Last checked:
The short version
We aim for WCAG 2.2 AA.
That is the usual standard for websites, at its middle level. We aim for it on every page.
Folding needs a mouse, a finger or a pen.
You fold by dragging the paper, and the path you drag decides the fold. The standard allows that.
Turning and zooming the model work with a keyboard.
So do stepping through a model, saving, publishing, your shelf and the menus.
A screen reader can follow a model.
It hears which model is showing, which step it is on, and what kind of fold made that step.
Some things are not right yet.
They are listed below.
Tell us about a barrier.
Email info@dorigami.com.
The details
What we aim for
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. That covers every page and the parts every page shares: the header, the menus, the dialogs, the cookie notice and the footer.
The one thing that needs a pointer
Folding is a drag. Where you press, the path you take and where you let go decide the fold. A key press cannot say that.
WCAG 2.2 asks for everything to work with a keyboard, except where the path of the movement matters (success criterion 2.1.1). Folding is that exception.
Turning and zooming the model are not, so they have keys of their own. Move the focus to the model with the Tab key, then:
- W, A, S and D turn it, a little at a time: A and D to the left and right, W and S up and down
- plus and minus zoom in and out
- 0 brings it back to where it started, as a double-click on the paper does
These keys work only while the model has the focus, so they never get in the way of a screen reader’s own keys or of the page’s. A model’s page also says them in its “How it goes” dialog, under the question mark.
Watching a model with a screen reader
On a model’s page:
- The model is an image, named by its title and the step showing. For example: “Origami Heart, frame 1 of 12”. Before the first step it is “unfolded paper”.
- You can step with the step buttons, or with the keys:
- the left and up arrows go back a step
- the right and down arrows go on a step
- Home goes to the start, End to the last step
- Space plays and pauses, when no button has the focus
- Each new step is read out once, with the kind of fold that made it. For example: “Frame 1 of 12: simple fold”. The kinds are simple fold, reverse fold and shape fold. Back at the start it says “unfolded paper”.
- The same happens while a demo plays, and the words the demo shows beside the model are read out too: the name of the lesson, then each thing it asks you to do, such as “drag face”. So is a notice the model shows, such as “Invalid fold”.
- On the Learn pages, a live model is an image named by its caption and the step showing, and its name follows its own step buttons.
- Turning the model around is not read out, because it does not change the model.
Motion
The moving model on the home page plays once and then stops. If your device asks for less motion, it shows the finished model and does not move.
A model’s own page follows that setting too, and so do the live models on the Learn pages. Each step shows the folded paper at once, without the fold moving into place, and the view jumps to fit the model rather than gliding. Playing a model goes from step to step the same way. A demo’s steps do too, but its pointer still moves across the paper and turns the model, because that movement is what it shows. Turning or zooming the model yourself still moves smoothly, since you asked for that movement.
Where we fall short
- People have not tested it yet. We have checked it with tools and with a keyboard, but we have not yet watched people who use a screen reader or other assistive technology use it.
How we checked
On November 17, 2026:
- We ran an automatic check (axe) on every main page, at a computer’s size and a phone’s size. It found no problems.
- We ran the same check on the pages you see after signing in: your shelf, the save and publish dialogs, the dialog that asks for your public name, the account menu, a new model, and a model page during a demo. It found no problems.
- We went through every dialog with the Tab key. The focus stayed inside each one, and went back to where it was when the dialog closed.
- We signed in by email with the keyboard alone, on the sign-in page and in the dialog that offers it after saving. What happens at each step, such as a code sent or a code that does not work, is written where a screen reader announces it.
An automatic check finds only some problems. That is why we want to hear from you.
Tell us about a barrier
If something on d’Origami is hard or impossible for you to use, email info@dorigami.com. It helps to say:
- which page you were on
- what you were trying to do
- what you use, such as a screen reader, the keyboard or zoom
