Accessibility

Accessibility statement

Last reviewed October 11, 2026.

We want every student and teacher to be able to use Mokxi. Our target is WCAG 2.1 Level AA for the website and the editor. We are not there everywhere yet, and this page says plainly where we fall short.

This statement covers mokxi.com: the site, the editor at /app, the lessons and the class tools. It is our own assessment. Mokxi has not had a third-party accessibility audit. Our self-assessed Accessibility Conformance Report (VPAT) goes through every WCAG 2.1 Level A and AA criterion, one by one, and says where we support it, where we partly do, and why.

What we have done

  • KeyboardEvery page starts with a Skip to content link. In the editor, the canvas has keys for the common actions (open the part panel, rotate, delete, undo, zoom and more, listed on the keyboard shortcuts page), the part panel is driven with the arrow keys and Enter, and Escape then Tab always leaves the code editor, so the keyboard is never trapped there.
  • Wiring from the keyboardThe circuit canvas is a stop in the Tab order. Tab selects each part, the arrow keys move it, R rotates it and Delete removes it. Enter opens a dialog: pick one of the part’s pins, type to find the pin to connect it to, and press Enter to add the wire, which Undo takes away like any other. While the circuit runs, Space presses a button or flips a switch and the arrow keys turn a knob. Every action is read out to a screen reader.
  • The circuit as textThe Circuit as text view lists every part with its type and settings, and every connection as part.pin to part.pin. While the circuit runs it shows what each part is doing, such as an LED’s brightness, a servo’s angle or a meter’s reading, and announces changes at most once every two seconds. Each part in the list selects it on the canvas.
  • Single-key shortcuts can be turned offThe Keys tile in the canvas menu turns the editor’s single-letter shortcuts off, or makes each one need Alt+Shift, so speech input or a resting hand does not set them off.
  • Focus ringsLinks, buttons and fields show a visible focus ring when you reach them with the keyboard.
  • ContrastText colors are chosen against WCAG AA contrast in both the light and the dark theme, and an automated playtest checks the key text on phones and on a desktop in both themes.
  • Reduced motionWhen your device asks for reduced motion, the site turns off its animations and transitions, and the circuits that run on the site’s pages start paused behind a play button.
  • Screen reader labelsPages use real headings, lists, tables and landmarks. Every circuit drawing on the site has a text name, and icon-only buttons are given labels for screen readers.
  • Phones and touchThe editor works with touch on a phone or tablet. Its controls and the site’s phone header are designed for 44 by 44 pixel touch targets, and an automated playtest taps through the editor on several phone sizes and reports any control that is smaller.
  • Light and dark themesThe site and the editor follow your device’s light or dark setting, and you can switch it yourself.

Known limitations

  • The circuit canvas is visualA circuit is a drawing of parts and wires. The Circuit as text view and the canvas keys cover the parts, the connections and the main controls, but some work still needs a pointer: a mouse, a finger or a pen. Bending a wire by hand, dragging a joystick, drawing on the canvas and reading the oscilloscope do, and the text view does not say where on the canvas or the breadboard a part sits.
  • Plots and instrumentsThe oscilloscope, the serial plotter and the logic analyzer draw graphs, which have no text equivalent yet.
  • The lesson plan PDFsThe printable lesson plans are not tagged PDFs. Each one has the same content as a web page on this site, which is the version to use with a screen reader.
  • Not every control is 44 pixels yetThe playtest still finds some smaller controls in the editor on a phone. We fix them as it reports them.
  • Sign-in screens that are not oursSigning in with Google, Microsoft or GitHub happens on their pages, which we do not control.

Ways in that do not depend on the canvas

What exists today for a student who cannot use the drawing, or a teacher preparing work for one.

  • The code is textThe sketch is written in a standard text editor that works from the keyboard, and the serial monitor shows what the program prints as text you can read and copy.
  • Circuits as filesThe Save menu downloads a project as a JSON file and the Export menu writes a parts list as CSV, both readable without the drawing. A circuit can also be written and run as a SPICE netlist in a text box (SPICE netlists).
  • Words beside every circuitThe lessons, the 12-week course and the part pages describe each circuit in text, and the part pages list every connection in a table, pin by pin.
  • From a terminalThe Mokxi command line tool compiles and runs a sketch with no screen at all and reports what it printed (for developers).

Report a problem

If something on Mokxi does not work with how you browse, tell us. Say which page or part of the editor it was, what you tried to do, and what you use (your browser and device, and any assistive technology). A person reads every message and answers by email.

You can also email support@mokxi.com or call (719) 246-1726.

Mailing address

Mokxi LLC
5142 N Academy Blvd PMB 1021
Colorado Springs, CO 80918
United States