Skip to content

Microsoft MakeCode accessibility support

Overview

The Microsoft MakeCode editor for micro:bit is designed and maintained by Microsoft in partnership with the Micro:bit Educational Foundation. It includes features that promote greater accessibility for everyone.

These features include:

  • Keyboard controls (new in 2025)
  • Immersive reader (for example for tutorial content)
  • Zoom, responsive layout options and themes (including dark mode new in 2025)
  • Screen reader support (for Javascript & Python only, screen reader support for block-based coding is in development for summer 2026 release)

You can find details of these accessibility features at:

Microsoft MakeCode Accessibility Statement

We have provided some additional resources, particularly relating to getting started with keyboard controls, and answers to common questions in this page.

Keyboard navigation

In the July 2025 release, keyboard controls were added to the MakeCode block-based editor to allow programs to be created with a keyboard or assistive technologies.

How to turn on keyboard controls

Open a project in the MakeCode editor, and press Tab and then Enter to ‘Enable blocks keyboard controls’. Use Ctrl + / (Windows) or Cmd + / (Mac) to open and close the keyboard controls help in the editor.

More details of the functionality are provided within the Microsoft MakeCode Accessibility Statement. In addition, the resources below may be useful to help you get started.

Keyboard controls guide (PDF)

This guide is designed to be printed or shown on a second screen. It provides a visual guide to the keyboard controls.

Image of start of page 1 of the MakeCode Keyboard Controls pdf for Windows
Keyboard Controls guide (PDF)

Getting started videos

These 3 videos provide step-by-step instructions to guide you through creating projects using only keyboard controls. Each video focuses on different keyboard control functionality:

  1. Getting started with keyboard controls. Turn on keyboard controls, create and edit a program and use the simulator.
  2. Using loops, on shake, show leds, and play melody blocks with keyboard controls.
  3. Using logic, play tone and temperature blocks with keyboard controls.

Note: These videos were created on a Windows computer. In most cases Mac users should use Cmd ⌘ instead of Control. In move mode, Mac users should use Option ⌥ instead of Control.

Visual accessibility

MakeCode offers adaptive layout and scaling to support high levels of zoom, as well as colour theming. These options can be helpful for students with a visual impairment as well as those with dyslexia or another condition that affects reading. Find out more via the links below.

Other resources

These teacher guides outline common barriers and provide concrete suggestions.

FAQs

General

Can I use a screen-reader with micro:bit MakeCode?

Screen readers do not yet work directly with the blocks in MakeCode. This feature is being developed and will be available in summer 2026.

At the moment, the micro:bit Python Editor is the best choice for students who already use a screen reader.

It is also possible to use the Javascript and Python editors in MakeCode when working with groups who are using blocks. These editors work with screen readers, so you can read and edit code as text instead of blocks.

For details visit MakeCode Accessibility.

Is any other help with reading or viewing the screen provided in MakeCode?

  • The Microsoft Immersive Reader is available when certain text is displayed.
  • Zoom and responsive layout options are available
  • Different Themes including High Contrast and Dark more (new in 2025) can be found in the Settings menu

For details visit MakeCode Accessibility.

Please also visit:

MakeCode keyboard controls

Who can benefit from keyboard controls?

Keyboard controls make block-based coding accessible to students with fine motor challenges. Keyboard controls are available to everyone.

Some users find it faster to use keyboard controls or prefer to use them for some actions. Many mouse users already use keyboard shortcuts for copy and paste and will find others useful.

How should I get started using keyboard controls?

To get started, we recommend:

For keyboard navigation, should I use block-based or text-based coding?

For users who are new to coding or the micro:bit, we recommend block-based coding in MakeCode.

For more advanced users, or those wishing to try text-based coding, we recommend the micro:bit Python editor.

Both work well for keyboard or assistive technology users.

Can I navigate the Microsoft MakeCode block editor using the keyboard only?

All areas of the block-based editor are keyboard accessible and programs can be downloaded to a micro:bit using keyboard controls.

Additional features and improvements will be made in future versions based on feedback.

What are the current limitations and workarounds?

There are some limitations in the current release of MakeCode that will be addressed in a future release.

  • Comments: Support for block comments is limited. You can add a block comment from the context menu on a block and open it with Enter or Space and add comment text. Esc closes the comment and block comments cannot be positioned on the workspace. Workspace comments are fully supported.
  • Functions: It is not yet possible to add parameters to functions using keyboard controls or rename the function in the function editor. If you attempt to add a parameter or edit the function in the function editor then you can’t use the keyboard controls to leave the function editor.
  • Editing a field: Clicking outside of the toolbox and workspace while editing a field, i.e. without confirming or cancelling the edit, can temporarily break some keyboard interactions. This only applies when using tab to return to the toolbox or workspace. Normal operation is restored after closing the toolbox with escape, clicking back in the workspace or navigating to the toolbox or workspace with the area menu.
  • Caret browsing: Some users may find that the arrow keys do not work as expected in some situations. This happens if caret browsing is turned on. Press F7 to disable caret browsing. Keyboard controls are not currently compatible with caret browsing in a web browser.

If you encounter a situation where the keyboard controls can’t be used to navigate then use Ctrl + R (Windows) or Cmd + R (Mac) to reload the page and continue.

How do I turn on keyboard controls in MakeCode?

To turn on keyboard controls, open a project in the MakeCode editor, and press Tab and then Enter to ‘Enable blocks keyboard controls’. Use Ctrl + / (Windows) or Cmd + / (Mac) to open and close the keyboard controls help in the editor.

For more details of the keyboard controls, see the Microsoft MakeCode Accessibility statement and the pdf and videos on this page.

Is there a quick way to navigate between areas like the workspace, simulator and toolbox?

Yes, press Ctrl + B (Windows) or Cmd + B (Mac) to open the Areas menu, then the number of the area you want to jump to.

Alternatively, Tab and Shift + Tab can be used to navigate the whole page.

For more details of the keyboard controls, see the Microsoft MakeCode Accessibility statement and the pdf and videos on this page.

Getting involved

How can I provide feedback?

Please send your thoughts, ideas, and comments to us at accessibility@microbit.org. We welcome feedback on improvements that could be made to the keyboard controls or suggestions for additional resources that would help students to learn how to use the keyboard controls.

To get involved with the Foundation's latest user research activities, including work to improve accessibility, join our research community where the current focus is on accessibility.