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.
> First letters navigation? Come on. Any blind person can tell that this wasn't written by anyone who uses these technologies.
Here I think you're reading way too much into a minor grammatical slip, possibly by a non-native English speaker. Sure, this post was written on behalf of a megacorp, but it was still written by a fallible human, and we should be reasonable about minor mistakes like that.
Seriously, Google needs to port Talkback onto Chrome OS and just kill Chromevox already! I tried Chromevox recently just to see if the thing still runs and just, no! Put Talkback onto Chromevox. @pixelate
Linux distro's heading to where macOS today: where the root filesystem is mostly immutable, but not entirely. #ChromeOS arrived there a decade ago, but everyone seems to be moving in the same direction.
Here's another #macOS rant (gosh I fucking hate this junk don't I): it loves creating problems out of non-issues (literally never had this problem on #Windows 10/11 or the many #Linux distros I've used and still are actively using) and append a number to it.
One being... external disk mounts. For whatever reason, what started out to be an external device that's formatted appropriately, as vanilla as can be using Disk Utility and mounts to, say, "SSD1TB", will randomly at times just started consistently mounting to a directory it creates by itself, "SSD1TB 1" - which fucks up all my symlinks to that drive until I manually fix the issue so it mounts to the right mount point again.
Another being, which is more confusing honestly how it's able to fuck it up, which is its own local hostname. I set the hostname as "aerith", which macOS compulsorily add a suffix to it, ".local". It's been on that hostname perfectly fine for a week ~2 weeks or so - then out of nowhere one day while being out, it says that that hostname's already used in the network and they then changed it to "aerith-2.local". Weird, I thought, but I thought maybe it's a one-time thing at that Mamak (eatery) I was at. Since then though, even at my home or anywhere else, changing it back to "aerith" is impossible and it'd always change it back to "aerith-2" - which TRIGGERS me.
#Apple, please just dump macOS already and use any of the Linux distros or Windows (jk hell no) or #ChromeOS (HELL NO). Y'all clearly have no idea what you're doing.
Another thing #macOS somehow butchers that I've not encountered on any other OS-es:
Setting up a static IP. Doing this itself is easy, not easier than #Linux but a lot easier than on #Windows. But for too many times now when I bring my #MacBook out and about to get work done, I'd just thought oh all of these (public) WiFi and even my personal hotspot from my #iPhone just straight up don't work. Then I remember, it was because of my static IP setting cos macOS somehow sets up network configurations such as having a static IP globally instead of per internet connection or WiFi SSID.
Why... would you enforce the static IP (I thought) I've configured for ONE connection, for ALL networks, obviously that wouldn't/shouldn't work? If private IP addresses in my home network follow a convention such as 123.321.0.X and I set a static IP of 123.321.0.11 for my Mac on a specific connection within my home network - when I use a different connection on a different network, OBVIOUSLY it wouldn't/shouldn't work since those other connections/networks highly likely uses a different IP address convention. Why can't macOS just default to DHCP, which it does, and apply these network configurations per connection rather than globally (bcos again, it just doesn't make sense)? Especially on the UI/UX side of things, it does seem like you're applying the configuration only to a particular connection you've selected - except it doesn't.
It's shit like this that makes me wonder who the fuck works at #Apple for this junk to be the case since forever and nobody's fixing it.
I'll add in a bonus though: macOS is also the only OS I've used that doesn't implement spell check (not correction) by default. For whatever reason, even as I'm typing this now, macOS straight up doesn't check or notify of any wrong spellings.
Googling how to enable it returns an official documentation by Apple with step by step instructions on how to have it enabled and yet the specific setting they mentioned should be in the System Settings' Keyboard menu just isn't there. Funny how that's a really common thing I encounter too - "it should be there, but it just isn't".
Late night thought. Why would anyone spend $300, $350, $450 or more on a Chromebook (even a "Chromebook Plus" when you can spend $200 on a A-condition Early 2015 Macbook Air 11"? Or $250 on an excellent condition 2017 era Macbook Air 13"?
Both can also be converted 100% to being Chromebooks if that's your vibe.
PS - I know the answer: most don't know about the cheap availability of intel-powered, 2014-2018 Macbook Airs. Even if the battery is torched, replacing the batteries is easy and a $50 added cost. You can also put a TB of SSD inside for under $100.
What I also didn't know: Macbook Airs are 100% able to set up with ChromeOS Flex if that's your jive or requirement. IMO they may be the best Chromebooks available today :)
Today I managed to flash #libreboot to my (new-to-me, abandoned by #ChromeOS ) ASUS Chromebook Flip C101P. It's now able to boot postmarketOS from the internal eMMC (with fde!)
> Techniquement, #ChromeOS étant aussi un système Linux, la part de marché représenterait même en fait 6,32 %. « En termes de pourcentage global, c'est encore relativement peu, mais quand on pense au nombre de personnes que cela représente, c'est beaucoup », souligne #GamingOnLinux.
Hey all! Do you love #Android and #ChromeOS? Our team is #hiring! We’re looking for a developer advocate (we call them Developer Relations Engineers) to join our team in Silicon Valley or NYC. You'll help developers optimize their Android apps for ChromeOS, teach them about large screen Android, work with us to build a happy and thriving ChromeOS developer ecosystem, and more!
Des millions d'appareils #Android , #Linux et #ChromeOS sont vulnérables aux nouvelles attaques #WiFi ! Les #pirates peuvent voler des données ou vous espionner.
Aucun correctif pour l'instant, il est conseillé deconfigurer manuellement les certificats CA pour la protection.
@piouzi Thanks for elaborating. At this time, we don't have plans for the development of a standalone ChromeOS app separate from the Android one, but we'll pass on your feedback to the team for future consideration.