Image Description
Screen reader and Windows Terminal settings for development
There is no sacred "programmer configuration" for NVDA or JAWS.
There is, however, a point at which hearing every character, every punctuation mark and every line of a compiler simultaneously stops being accessibility and becomes weather.
These are settings worth knowing about. Change the ones that solve an actual problem for you.
NVDA: report dynamic content changes
NVDA can automatically announce new text appearing in terminals. Toggle Report dynamic content changes with NVDA+5 on the number row, or find it in Object Presentation settings.
For a short command, automatic output is excellent. For a build producing hundreds of lines, it may be useless.
Turn it off temporarily, let the command finish, then review or search the result. You are trying to find information, not win an endurance event.
NVDA: typing echo
Character echo gives maximum confirmation but can make long commands painfully slow to listen to. Word echo is a useful middle ground for many people.
If you prefer no typing echo, review the command before pressing Enter when it matters.
Password fields and prompts deserve special care. Do not change security-conscious behaviour merely because silence feels unfamiliar.
NVDA: punctuation
Command lines contain meaningful punctuation: double dashes, slashes, backslashes, quotes, braces and pipes.
If your normal punctuation level hides too much of that, raise it while developing. A configuration profile can keep development settings separate from everyday reading.
NVDA: braille tethering
If you use braille, know whether the display is following focus or review. Moving NVDA's review cursor while braille remains tethered to focus can make speech and braille appear to disagree.
They are not disagreeing. They are reporting two different cursors.
JAWS: Quick Settings versus Settings Center
Insert+V opens Quick Settings for the current application. Insert+6 on the number row opens Settings Center.
Application-specific settings are useful for development. If you want more punctuation in Windows Terminal, you probably do not also want JAWS reading every semicolon in an article about licensing.
JAWS: typing echo and punctuation
The same trade-off applies as with NVDA. Character echo is thorough, word echo is quieter, and punctuation needs to expose enough syntax for you to distinguish the command you typed from the command you meant to type.
JAWS: screen echo
Some terminal programs repaint or update so aggressively that automatic speech becomes repetitive or chaotic. Reducing screen echo can help.
Do not switch things off merely because a guide told you to. If automatic output is useful, keep it. If it has become noise, reduce it and review the result manually.
JAWS: Speech History
If JAWS just announced one useful line and you missed it, Insert+Space, then H opens Speech History.
That is excellent for "what did it just say?" It is not a replacement for reviewing the actual terminal when you need context around the error.
Windows Terminal: keep enough history
The terminal keeps scrollback above the visible window. Its History size controls how much remains available.
If large builds regularly push the useful error out of history, increase it. This is a configuration problem, not a challenge to become faster at pressing review keys.
Windows Terminal: return to input when typing
Scroll to input when typing is useful after you have been examining old output. Starting the next command brings the terminal view back to the live input area.
Windows Terminal: bell behaviour
The terminal bell can be audible, visual, both or neither depending on configuration.
An audible bell may be useful when a command uses it to request attention. If something rings it every four seconds, your opinion may develop.
Windows Terminal: selection and copying
Windows Terminal can automatically copy selected text. That is convenient until selecting something casually replaces the error message you were saving on the clipboard.
Pick predictable behaviour. Predictability is more useful than somebody else's favourite setting.
Windows Terminal: scrollback shortcuts
By default, Control+Shift+Home scrolls to the earliest history and Control+Shift+End to the latest.
These affect the terminal viewport. They do not replace NVDA review or the JAWS Cursor, but they can help when the interesting output is at one end of a long session.
A sensible starting setup
If you want somewhere to begin:
- Keep enough terminal history for your normal builds.
- Leave new-output reporting on until it becomes noisy.
- Use enough punctuation to distinguish command syntax.
- Use application-specific screen-reader settings where practical.
- Learn one reliable way to review old output without moving the live caret.
Then stop configuring and write some software.
Put the settings to work
Using the command line with a screen reader gives you practical exercises for NVDA and JAWS.
Debugging with a screen reader applies the same skills to tracebacks, errors and logs.