Improve fcc system with a screen reader

Contributors
1

hi, i use several screen readers, jaws for windows, nvda for windows and windows narrator windows 11. making some accessibility suggestions:

  1. make the system more flexable and not so strict.
  2. maybe have the error messages in more plain english, some times they are hard to understand and multiple guessing.
  3. have a tool to then be able to clear cache from left over code when trying sayin on a work shop or a step.
  4. have a tool which will show up hidden characters, stray characters, hidden spacing and screen readers cannot see that.
  5. have a way or a tool and then maybe the line of code and tell the screen reader user what line number the error is.
  6. have a keyboard shortcut in the editor or a search function to jump to that, i cannot do that with the control f for jaws find, and then have to either scroll up or down, and could make it more efficient.
  7. and use google chrome, firefox and using microsoft edge as my default browser at the moment.
  8. marvin…
2

Several of those suggestions sound reasonable. However,

It helps if you list specific error messages you think can be improved. Note though that part of learning programming is learning how to understand technical language.

There is a button to reset the code for a step. That doesn’t help if you paste over the reset code with code you saved elsewhere though.

3

The editor does have some features that might be useful for you.

For example F8 is “go to next problem” which will place the cursor at the next syntax error and provide a description of the problem.

If you press F1 while in the editor it will open the command palette and list all of the commands like this.

Trim Trailing Whitespace CTRL + K might be useful