Accessibility
Last updated: November 13, 2026
We want marimo to be usable by everyone, including people who use assistive technology. This page explains where marimo stands today, what works, what we know does not, and how to reach us.
This statement covers the open-source marimo notebook editor, molab, and marimo.io.
#Current status
marimo has not been formally audited against the Web Content Accessibility Guidelines (WCAG). We do not claim conformance with WCAG 2.1 Level AA or any other level. We have not systematically tested the notebook editor with screen readers, and you may run into barriers.
#Settings you can change
- Choose a light, dark, or system theme.
- Change the code editor font size.
- Show dataframes as plain output instead of interactive tables.
- Turn off reactive reference highlighting.
- Turn off AI features.
- Apply your own CSS to change fonts and colors.
#Keyboard use
- Use hotkeys to move between, run, create, and delete cells.
- Remap any hotkey in the hotkeys menu (Ctrl/Cmd-Shift-H) or in your
marimo.tomlfile. - Open the command palette to find actions by name.
- Switch to a vim keymap if you prefer.
#If the editor doesn’t work for you
marimo notebooks are stored as plain Python files, so you don’t need marimo’s browser editor to read or write them.
- Edit notebooks in your own editor or IDE. Run
marimo edit --watch notebook.pyto keep marimo in sync with your changes. - Run a notebook as a regular script with
python notebook.py. - Export a notebook to static HTML, Markdown, a Jupyter notebook, PDF, or a Python script.
If you need a notebook or page from us in another format, contact us and we will help.
#Known limitations
- Screen reader support in the live editor is untested and likely incomplete.
- Plots from third-party libraries are often rendered as images or canvas elements without text alternatives. Their accessibility depends on the plotting library.
- Notebooks written by other people may not include headings, descriptions, or text alternatives for charts. We cannot review every notebook.
- Third-party widgets and custom UI plugins may not be accessible.
#What we’re working on
We recently added accessible names to buttons, sliders, form inputs, and table controls, and we added automated accessibility checks to our frontend code. We will update this page as that work continues.
#Tips for notebook authors
Use markdown headings to structure your notebook. Describe what each chart shows in nearby text. Choose color schemes that don’t rely on color alone to carry meaning.
#Feedback
If you hit an accessibility barrier, tell us:
- Email contact@marimo.io if you’d rather not report publicly.
- Open an issue on GitHub and include “accessibility” in the title.
Please describe what you were trying to do, the browser and assistive technology you used, and what happened. We are a small team and can’t promise a response time, but we read every report.