Michael Odden
Michael Odden
Just a FYI that I may have identified the step required to reproduce the issue: > It seems to me that a key factor to trigger the error is to...
It seems to me that a key factor to trigger the error is to enable [accessible output](https://p5js.org/tutorials/p5js-with-screen-reader/) (ctrl+shift+1 to enable, ctrl+shit+2 to disable on Windows, replace "ctrl" with "cmd" for...
Another suggestion is for the UI to somehow communicate the fact that the accessibility mode is enabled or not. As it appears now there's no visual clue indicating this.