aaron

1 month ago

aaron
1 month ago

Has anyone thought about making a #virtual #Braille #display for #Windows that would hijack the touch screen for use with #NVDASR or #JAWS as a Braille input device, and allow using things like a mode for navigation with dot taps like command mode with #BrailleScreenInput on #iOS with #VoiceOver? I'd pay for this. #Accessibility.

#Accessibility #Windows #ios #nvdasr #braille #jaws #voiceover #BrailleScreenInput #virtual #display

reshared this

in reply to aaron

Jamie Teh

in reply to aaron 1 month ago

I've thought about it, yes. Do I have time to do it? No. :)

in reply to Jamie Teh

Jamie Teh

in reply to Jamie Teh 1 month ago

More seriously, it would probably need to be integrated into core to work well. NVDA's touch support has all the fundamentals to make this possible, but I think it would be difficult to do it well in an add-on without overriding all of NVDA's other touch commands or without many many hacks.

in reply to aaron

Matt Campbell

in reply to aaron 1 month ago

To clarify, do you mean a virtual Braille display or a virtual Braille keyboard? It sounds like the latter. Maybe something that emulates a device that's solely a Braille keyboard, like an Orbit Writer?

in reply to Matt Campbell

aaron

in reply to Matt Campbell 1 month ago

@matt I mean a Braille keyboard, I said display because that's how devices like the Orbit Writer connect, as a display rather than as a keyboard. Now I see how that could be confusing wording!

@Matt Campbell

in reply to aaron

Matt Campbell

in reply to aaron 1 month ago

So this begs the question, why spend money on touchscreen-based Braille input rather than a Braille keyboard? I understand why Braille screen input makes sense on a phone, because of portability. Are you wanting to use that on a Windows tablet?

Not saying you shouldn't want this, just trying to clarify the rationale and see what kind of business case there might be.

in reply to Matt Campbell

aaron

in reply to Matt Campbell 1 month ago

@matt I already have my surface pro, and without the keyboard it is basically pointless. Braille screen input on Windows would make windows on touch actually tollorable. The way NVDA currently handles it makes it harder to use than it needs to be.

@Matt Campbell

in reply to aaron

Matt Campbell

in reply to aaron 1 month ago

So it sounds like the cleanest way to do this wouldn't be actually emulating a Braille device, but doing an NVDA add-on that does Braille screen input.

in reply to Matt Campbell

aaron

in reply to Matt Campbell 1 month ago

@matt That would work, if you only intend to use NVDA. I also use JAWS from time to time, haha.

@Matt Campbell

⇧

aaron 1 month ago • •

aaron
1 month ago