Reading out any Python errors for blind kids instead of (or as well as) scrolling them on the LEDs

I’ve been working recently on a tangible system for teaching visually impaired kids to code called [Torino](https://blogs.microsoft.com/ai/2017/03/15/project-torino-microsoft-creates-physical-programming-language-inclusive-visually-impaired-children/). One of the blind kids is ready to progress to a text based language.

His school mates are using Python on the micro:bit and so one of our collaborators has come up with a series of micro:bit Python lessons for him.

But he was stuck on the very first lesson:

from microbit import *
import speech
speech.say("hello")

He could write the program in Notepad++ using his JAWS screen reader. He could flash it to his micro:bit using the keyboard shortcut to uflash that we set up. He has the amp:bit to drive headphones or speakers. But no sound came out. Eventually his mum and I deciphered the scrolling text on the micro:bit, it said “error: unexpected indentation”. Without any of us noticing, his entire program was indented one tab stop. We removed the tabs and the program started working.

He is blind and so there is no way he could access that useful error message (in fact it was a struggle for his mum and I).

That got me thinking. It would be really useful for blind users if the micro:bit had the facility to read out its error messages instead of (or as well as) scrolling them. Is that a plausible patch to write? Any pointers on where I might start?