101010.pl

Noah T. Carver 👨🏼‍🦯🇺🇦<a href="https://caneandable.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> hive mind, I have some questions about <a href="https://caneandable.social/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> as well as <a href="https://caneandable.social/tags/Chromebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chromebook</a> accessibility & <a href="https://caneandable.social/tags/usability" class="mention hashtag" rel="nofollow noopener" target="_blank">#usability</a> in general. I'm working with a <a href="https://caneandable.social/tags/PixelBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#PixelBook</a> 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 <a href="https://caneandable.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://caneandable.social/tags/Gemini" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gemini</a>. What's going on here? Additionally, how are <a href="https://caneandable.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a> people using <a href="https://caneandable.social/tags/Chromebooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chromebooks</a>? In what tasks do they excel. In what tasks do they fall short? Any input and/or information would be greatly appreciated.<a href="https://caneandable.social/tags/Blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blind</a> <a href="https://caneandable.social/tags/BlindMasto" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindMasto</a> <a href="https://caneandable.social/tags/BlindMastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindMastodon</a> <a href="https://caneandable.social/tags/BlindFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindFedi</a> <a href="https://caneandable.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://a.gup.pe/u/mastoblind" class="u-url mention" rel="nofollow noopener" target="_blank">@mastoblind</a>

Devin Prater :blind: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.<a href="https://issuetracker.google.com/issues/260181154?pli=1" rel="nofollow noopener" translate="no" target="_blank">https://issuetracker.google.com/issues/260181154?pli=1</a> <a href="https://tweesecake.social/tags/ChromeBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeBook</a> <a href="https://tweesecake.social/tags/ChromeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeOS</a> <a href="https://tweesecake.social/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> <a href="https://tweesecake.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://tweesecake.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a>

Devin Prater :blind: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.<a href="https://blog.google/outreach-initiatives/education/global-accessibility-awareness-day-2024/" rel="nofollow noopener" translate="no" target="_blank">https://blog.google/outreach-initiatives/education/global-accessibility-awareness-day-2024/</a><a href="https://tweesecake.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://tweesecake.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a> <a href="https://tweesecake.social/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> <a href="https://tweesecake.social/tags/ChromeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeOS</a> <a href="https://tweesecake.social/tags/Chromebook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chromebook</a> <a href="https://tweesecake.social/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> <a href="https://tweesecake.social/tags/GAAD" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAAD</a>

Trenton MatthewsHmmm... Time to see how well I can replicate either the <a href="https://pone.social/tags/Chromevox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chromevox</a> and/or <a href="https://pone.social/tags/Talkback" class="mention hashtag" rel="nofollow noopener" target="_blank">#Talkback</a> keyboard experience with the <a href="https://pone.social/tags/jieshuo" class="mention hashtag" rel="nofollow noopener" target="_blank">#jieshuo</a> 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 <a href="https://pone.social/tags/WindowEyes" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowEyes</a> or <a href="https://pone.social/tags/SuperNova" class="mention hashtag" rel="nofollow noopener" target="_blank">#SuperNova</a>/#Hal layout?

RuAlright. <a href="https://fosstodon.org/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> 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`.

Ru<a href="https://fosstodon.org/tags/orca" class="mention hashtag" rel="nofollow noopener" target="_blank">#orca</a> did the trick. The text was (as guessed by <a href="https://fosstodon.org/@benjaminpaikjones" class="u-url mention" rel="nofollow noopener" target="_blank">@benjaminpaikjones</a>) being read as s, ave.There was no distinction between kbd and paragraph, though.Testing <a href="https://fosstodon.org/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> on <a href="https://fosstodon.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> might be the next to-do.

RuNot a good look for Google (to be fair, when is it ever...)I installed <a href="https://fosstodon.org/tags/ChromeVox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChromeVox</a> on <a href="https://fosstodon.org/tags/Chromium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chromium</a> and there are no voices available out of the box.To get voices, apparently you need to compile the browser yourself? <a href="https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md" rel="nofollow noopener" target="_blank">https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md</a>

Recent searches

Search options

Administered by:

Server stats:

#chromevox