#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

Oh hey, forgot about this open issue lol. ChromeVox on ChromeOS is so dead. I made an issue for a feature to jump to the next/previous spelling error detected in a text edit area, and well, it's as dead as the ChromeVox What's new document. Oh wait they've not been sending out what's new emails to the ChromeVox email list since like version 94 or so.

More seriously though, a ton of schools, and jobs, are switching to ChromeBooks. I'm not saying one cannot be productive on a ChromeBook, because I was able to. But *only* with the help of Chrostini (Linux support) and Android apps. So like, you seriously have to use every single feature to get work done that's more than just Email and Google Docs.

https://issuetracker.google.com/issues/260181154?pli=1
#ChromeBook #ChromeOS #ChromeVox #accessibility #blind

Google Issue Tracker

Chromebooks already have great screen reading capabilities built in...

Awww Google, how cute of you. Great? Nope. Next time, remember. Nothing about us, **without us**. ChromeVox has barely been updated in *years*, just like VoiceOver for Mac, and Narrator. ChromeVox barely has any options for fine-tuning verbosity, keyboard commands, pronunciation, and some keyboard commands, like Search + Control + A for accessibility actions, aren't even well-documented. I should know. I had to use an Acer Spin 713 for a good 3 months as my primary laptop. So kindly stop talking, then ask, then act before you speak further.

"Updated keyboard shortcuts and first-letters navigation in Google Drive"...

First letters navigation? Come on. Any blind person can *tell* that this wasn't written by anyone who uses these technologies.

And nowhere in this article is anything new for ChromeVox. See? This is the kind of, frankly, bullshit that I hate on GAAD. Just shut your mouth and listen for once.

https://blog.google/outreach-initiatives/education/global-accessibility-awareness-day-2024/

#Accessibility #blind #google #ChromeOS #Chromebook #ChromeVox #GAAD

How we’re building accessibility into our Chromebooks around the world

Google
How is it that we're in 2024 and #Chromevox still refuses to speak anything if you choose to browse as a guest? #ChromeOS #accessibility #a11y #fail

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?

I think people are really missing out on a great experience with #Chromebooks apart from the quick booting of the computer, and the fast loading of screens, I really enjoy the Google workspace experience on the machines. Sure, it is not as easy to switch from. #JAWS or #NVDA to #ChromeVox but I don’t see it as a negative. These are very affordable and capable alternatives to both. #Mac and #PC
Here is a video I did a few months back on the #ChromeVox #ScreenReader on #Chromebook I do not have my set up finished at the new place, but will continue posting once I do, probably within the next week. Feedback is always welcome. https://youtu.be/h9CB_fgGN4w
Customizing the Chromebook Shelf with ChromeVox (Part 1)

YouTube
Been poking about with #webcomponents and tried how things work with #chromevox. Funny thing is that it makes MutationObservers not working at all as the elements passed to .observe method are no longer elements, but some 'Pe'-object... 😬 #a11y
new #pinafore problem: on #ChromeOS with #ChromeVox when arrowing through the home tl it's suddenly now started just saying "Unlisted post from ,username>" or "public post from <username>" instead of the actual post text