Accessibility statement

CodeOrbit should be usable by everyone, including people who use a screen reader, navigate by keyboard, zoom in, or are sensitive to motion. We aim to meet WCAG 2.2 at level AA.

CodeOrbit is provided by a microenterprise — Timmie Hemmingsson, trading as Vireo, a sole trader with no employees — and Swedish law exempts services provided by microenterprises from the accessibility requirements (lag (2023:254) om vissa produkters och tjänsters tillgänglighet, 10 §). We follow WCAG 2.2 AA voluntarily, because a tool for learning algorithms is only worth something if everyone who wants to learn can use it.

CodeOrbit is partially compliant with WCAG 2.2 level AA. The limitations below are known. We would rather tell you what does not work yet than claim that everything does.

• No end-to-end test with a screen reader has been done. What is listed under the next heading was checked in the code, with automated tests and by inspecting the pages — not by using the whole product with a screen reader from start to finish. Treat it as reviewed rather than proven.
• Resting elements in the visualisation. Elements that are at rest are drawn in a deliberately quiet colour with less than 3:1 contrast against the background (WCAG 1.4.11), so that the elements being compared or moved stand out. The step table under the visualisation gives every position and its state in words, so nothing depends on seeing that colour.
• No third-party audit. Nobody outside the business has reviewed CodeOrbit’s accessibility.

• Text, focus outlines and the colours of the visualisation are checked against WCAG AA contrast in both the light and the dark theme, and the visualisation’s states are checked to stay distinguishable for the three common kinds of colour blindness. A change that breaks this fails our automated checks.
• The visualisation has a name that says which algorithm is running and which step you are on, and each step’s description is announced to screen readers as you move through the run — on the web and in the Android app.
• Under the visualisation on the web, a table you can open shows every position and its state in words.
• On the website, the playback controls work from the keyboard: the arrow keys step back and forth, and Home and End jump to the start and the end.
• On the website, a run starts paused and moves only when you press play or step through it, and you choose the speed.
• On the website, the prediction questions are real radio groups, so they announce your position in the set and respond to the arrow keys.
• On the website, a form error is tied to its field, announced when it appears, and marked with an icon as well as a colour.
• If your device asks for reduced motion, the website’s entrance animations are switched off and the content is shown at once.
• Every page on the website starts with a link that skips straight to the main content.
• The website is in English and Swedish, and each page declares its language so a screen reader pronounces it correctly.
• Buttons are at least 44 pixels tall, on the website and in the Android app.

If something in CodeOrbit stops you from using it, tell us. Email support@aver-web.se with what you were trying to do and what got in the way. We aim to reply within five working days.

This statement is based on our own review: automated checks of colour contrast and of the pages’ accessibility tree, tests of the components named above, and our own inspection of the pages.

It has not been audited by a third party, and we have not tested the product end to end with a screen reader. We say so rather than imply testing that has not happened.