Pluto is designed to be accessible to all users. We follow web accessibility standards 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. This way:
Ctrl/Cmd + ±
prefers-reduced-motion
Pluto uses semantic HTML and ARIA (Accessible Rich Internet Applications) labels to work with popular screen readers including JAWS, NVDA, VoiceOver, TalkBack, and Narrator. We follow WAI-ARIA best practices to ensure interactive elements are properly announced and navigable. Current screen reader experience:
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.
Pluto is available in multiple languages, making it accessible to non-English speakers. You can:
You can read more on about it in this section.
Found an accessibility issue? Let us know through our feedback tool or community channels!