#chromevox — Public Fediverse posts

#Accessibility hive mind, I have some questions about #ChromeVox as well as #Chromebook accessibility & #usability in general. I'm working with a #PixelBook that has never been used. ChromeVox is telling me to use commands involving the search key as a modifier, but these seem not to work as any use of the search key invokes #Google #Gemini. What's going on here? Additionally, how are #blind people using #Chromebooks? In what tasks do they excel. In what tasks do they fall short? Any input and/or information would be greatly appreciated.

#Blind #BlindMasto #BlindMastodon #BlindFedi #a11y @mastoblind

#Accessibility hive mind, I have some questions about #ChromeVox as well as #Chromebook accessibility & #usability in general. I'm working with a #PixelBook that has never been used. ChromeVox is telling me to use commands involving the search key as a modifier, but these seem not to work as any use of the search key invokes #Google #Gemini. What's going on here? Additionally, how are #blind people using #Chromebooks? In what tasks do they excel. In what tasks do they fall short? Any input and/or information would be greatly appreciated.

#Blind #BlindMasto #BlindMastodon #BlindFedi #a11y @mastoblind

ChromeOS bekommt Steuerung per Gesichtsbewegung - COMPUTER BILD
https://www.computerbild.de/artikel/cb-News-Notebooks-Netbooks-ChromeOS-bekommt-Steuerung-per-Gesichtsbewegung-36999707.html #ChromeOS #Steuerung #Chromebook #Facetracking #ChromeVox

ChromeOS bekommt Steuerung per Gesichtsbewegung - COMPUTER BILD
https://www.computerbild.de/artikel/cb-News-Notebooks-Netbooks-ChromeOS-bekommt-Steuerung-per-Gesichtsbewegung-36999707.html #ChromeOS #Steuerung #Chromebook #Facetracking #ChromeVox

Hmmm...

Time to see how well I can replicate either the #Chromevox and/or #Talkback keyboard experience with the #jieshuo screen reader's 'Hotkey Scheme' feature. The default has 'waaaaaaaay' too many conflicts in my view (particularly if using web browsers that support keyboard shortcuts).

And since people are able to share said keyboard layouts, anyone thought of creating a #WindowEyes or #SuperNova/#Hal layout?

Hmmm...

Time to see how well I can replicate either the #Chromevox and/or #Talkback keyboard experience with the #jieshuo screen reader's 'Hotkey Scheme' feature. The default has 'waaaaaaaay' too many conflicts in my view (particularly if using web browsers that support keyboard shortcuts).

And since people are able to share said keyboard layouts, anyone thought of creating a #WindowEyes or #SuperNova/#Hal layout?

Alright. #ChromeVox on Windows works out of the box. Using the kbd element actually broke it! A list with 4 sub items was being read as a list with 2 items, because the first letter in the third sub-item was a kbd.

Then, while reading text, there was no announce whatsoever about the `o` key being a keyboard input. It would pause, read o, announce "list item" to say now the list item was being read again in continuation before taking the pause for `o`.

#orca did the trick. The text was (as guessed by @benjaminpaikjones) being read as s, ave.

There was no distinction between kbd and paragraph, though.

Testing #ChromeVox on #Windows might be the next to-do.

Not a good look for Google (to be fair, when is it ever...)

I installed #ChromeVox on #Chromium and there are no voices available out of the box.

To get voices, apparently you need to compile the browser yourself? https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md

Will be installing and configuring #Filezilla tonight, and then I can really jump into this #IndieWeb thing. #Chromebooks and #Chromevox just don’t support plain text editors and #SFTP management very well.

Went from a #Chromebook to a #Windows box overnight, and I’m doing okay, except I keep wanting to push the #Chromevox key, which is the same as the windows key on my keyboard.