Pluto is designed with accessibility in mind. We follow web accessibility standards (WCAG 2.2 Level AA) and continuously work to improve the experience for everyone. If you find any accessibility issues, please get in touch!
Here is an overview of the accessibility features of Pluto.
Pluto is fully usable without a mouse. You can navigate and control everything using only your keyboard.
You can execute cells, navigate between cells, and access common functions quickly using shortcuts. You can find a list of all our shortcuts here.
Plutoโs interface is designed to be keyboard accessible similar to a web page. You can move through all interactive elements on the page using the Tab key.
A special note about tab navigation inside cells: when focused inside a cell code editor, the TAB key will indent code instead of navigating. To navigate, you press Esc and then Tab.
This video shows an example:
You can find a fuller overview of the keyboard shortcuts and between-cell navigation here
Pluto also supports touch-only use with your deviceโs on-screen keyboard (OSK): the virtual keyboard that appears on your screen when you tap a text field on tablets, touchscreen laptops, or any device without a physical keyboard.
We design almost everything with enough visual contrast in light and dark mode. Our design goal is that all text meets WCAG 2.2 Level AA contrast standards (minimum ratio of 4.5:1). This improves readability for users with low vision or color blindness.
Pluto automatically follows your operating system or browserโs light/dark mode preference. Dark mode can reduce eye strain.
If you want to use a larger font size, you can use your browserโs zoom function (Ctrl/Cmd + ยฑ) to adjust the size of Plutoโs interface. Pluto is designed to scale well, and it also works in very high zoom levels. The layout will adapt to the available screen size.
Ctrl/Cmd + ยฑ
Pluto respects the prefers-reduced-motion CSS setting. If youโve enabled โReduce motionโ or โPrefers reduced motionโ in your browser or OS accessibility settings, then Pluto will minimize animations. This helps users with motion sensitivity.
prefers-reduced-motion
Pluto uses semantic HTML and ARIA (Accessible Rich Internet Applications) labels to work with screen readers (like JAWS, NVDA, VoiceOver, TalkBack, and Narrator). We follow WAI-ARIA best practices to ensure interactive elements are properly announced and navigable.
Screen reader support is available, but not perfect yet. We need more user feedback to continue improving. The current experience is as follows:
aria-live: polite
We need your feedback! If you use a screen reader with Pluto, please share your experience - what works well and what could be better. Your input is essential for helping us prioritize improvements. See this issue to join the conversation or use our feedback tool to report accessibility barriers.
We try to use simple language in the Pluto interface and in our documentation.
Pluto is available in multiple languages, making it accessible to non-English speakers. Pluto can be used in Left-to-Right and Right-to-Left text layouts (both interface and content). You can read more about language support here. Our documentation is currently only available in English.
HTML export from Pluto are designed to be machine-translation-friendly. This means using lang and translate attributes in the HTML. You can also use machine translation while editing a notebook.
lang
translate
And more? Found an accessibility issue? Let us know through our feedback tool or community channels!
Found an accessibility issue? Let us know through our feedback tool or community channels!