Blind Main
The main community at rblind.com, for discussion of all things blindness.
You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.
view the rest of the comments
@dhamlinmusic @main @mastoblind By latest version of NVDA, do you mean 2024.4.2 - or the 2025.1 beta? Also which braille display are you using?
@NVAccess @main @mastoblind Assuming April 2024, whatever one is downloaded from the main download page, and using a Bi40x, the display connects and shows the information o the lock screen, but cannot move focus or do anything itself.
@dhamlinmusic @main @mastoblind I can't readily see an issue similar to that - would you be able to write one up please?
https://github.com/nvaccess/nvda/issues
@NVAccess @main @mastoblind Yeah I will try and get to that, the consistant things are that any screen that is flagged as secure cannot be acted on by the #brailledisplay, even if #nvda is running with elevated permissions, examples are the lock screen and the windows UAC dialogues, such as the one that pops when giving NVDA permission to run on the lock screen. Saving a config to use on secure screens did not make any difference.
@NVAccess @main @mastoblind Ok found this issue being reported back over a decade. https://github.com/nvaccess/nvda/issues/2315
I found a handful of others that were closed for being duplicates of this original issue, or one of a couple other identical ones.
@dhamlinmusic @main @mastoblind is this a new issue for you though? I got the impression this just started happening?
@NVAccess @main @mastoblind Not sure, this is the first time I have had a working PC and time to get the display set up with it and NVDA, but this happened' right away. Best I can tell is it's the same issue. Also where do I go to clear the secure screen profile, cannot figure that out, do not need it if it's not fixing this.
@NVAccess @main @mastoblind Oh additionally if the PC is left idle for a while or restarts the braille display will just read "braille display" until focus is moved with the qwerty.
@NVAccess @main @mastoblind Ok so the braille display not working on secure screens I'm thinking is a microsoft being stupid issue, I realize that this also happened when using a display over USB with narrator itself, bet they are blocking peripherals beyond m&k from interacting with those. The issue where the display is unable to do anything when the PC is first turned on, or has been disconnected for more than like 10min until something is pressed on the qwerty however seems to be #nvda, I checked all the bluetooth and power settings and they are correct.
@NVAccess @main @mastoblind This a applies to screen savers as well, the braille display cannot wake the PC from it.
@dhamlinmusic @main @mastoblind One of the features in NVDA 2025.1 is "Added a general setting to prevent the display turning off during say all or reading with braille." which should at least fix the display dropping out in some cases while reading long pieces of text - it won't help if you leave the PC entirely for long enough that it goes to sleep though
@NVAccess @main @mastoblind Yeah, I found that placing the focus over something like the system clock prevents it from requiring pulling out the qwerty keyboard to get the display working after a few hours, the object updating every minute seems to be enough to get the display out of just showing "braille display" when it reconnects and I enter terminal mode. It just seems to need something to trigger the focus enough to need it to update the display.