Robert Knight

Some improvement was made in this [PR](https://github.com/microbit-foundation/python-editor-v3/pull/1161) which can be tested using the [beta](https://python.microbit.org/v/beta).

The Chakra-UI component is fully accessible - https://chakra-ui.com/docs/components/form/number-input. NVDA, in my experience on chromium based browsers seems to be ignoring `aria-valuenow`, `aria-valuemin` and `aria-valuemax`. The current value is read in...

Investigate whether this happens with the Chakra-UI example.

This issue is also observed in the Chakra-UI example.

Unfortunate case where we are filtering out `__new__` (with other special methods), but they are the only methods documented in the class: 

> > all available languages are precached > > Does that mean everyone pays the cost of every language now? Before interactivity or after/in the background? ~~For this version, yes....

Toast shown when changing language while offline and language assets are not already cached. Text is a working placeholder and needs discussion. 

The following workaround can be applied to the code referenced in this issue. Add this line to the top of the file to ignore errors present: `# pyright: reportGeneralTypeIssues=false, reportUndefinedVariable=false`...

I think the search highlighting is now too dark: 

This is still currently an issue for me. The longer you let the while loop run, the worse the effect is as everything waits to catch up. The same thing...