Skip to main content


Windows 11 seems to have fixed an accessibility issue where links were aggressively put on a separate line from the screen reader perspective. So, for instance, a hashtag was rendered as # and then a line break and then the link. Seems to happen across multiple browsers/NVDA versions so I suspect it goes deeper than just a browser/screen reader bug.

Has anyone else seen this, and is it fixable under Windows 10? Didn't really appreciate how much it slowed things down for me until it was gone.

If not, thinking I'll hack around my desktop's missing TPM and upgrade as soon as I get it back. Any huge, glaring, a11y-related reason I shouldn't do this? So far so good on the Steam Deck but this isn't and won't be my main productivity machine.
in reply to Nolan Darilek

Are you sure it's a #windows thing? #NVDASR has an option called Use screen layout within its browse mode settings section. Perhaps toggling it will help with the Windows 10 computer as well. It's on by default meaning the virtual document content is displayed the way it's arranged on the screen rather than wrapped at link boundaries.