This is an interesting read. Apparently, the accessibility problems and complexity of Gutenberg was quite a contributing factor to this.
On not choosing WordPress for the W3C redesign project https://w3c.studio24.net/updates/on-not-choosing-wordpress/
RIP. They had some cool ideas with it too, like from what I heard the way it does custom actions was far better than how Talkback does now. We can only hope that Google makes that suck less now that it has multifinger gestures but I'm not holding my breath
Looks like Voice Assistant on Samsung devices will be no more folks...
Official changelog for Android 11-based One UI 3.0 beta update is here! - SamMobile ht…
For anyone considering buying an apple watch now that it works with braille, it's worth noting that not all displays that work with iOS work with it. I was able to pair a Hims display no problem, but pairing a 5th gen Focus results in a device not supported error, though this may have been fixed in the GM release. I also heard orbits work fine. So it may be necessary to crowd source a list of compatible displays or wait for apple to publish a list.
There has to be a happy medium between the corporate "let's maintain everything forever, yay 20 more years of IE" and the open-source "let's release breaking changes every Tuesday just for fun." But I don't think we're there.
Since Mastodon doesn't support citing posts by others yet, here's a manual one. I came to the same realization after my third attempt at switching to Android last year, with the first two having happened in 2013 (4 days) and 2014 (18 days). And I'll just add that Microsoft abandoning Windows 10 mobile is probably the saddest thing that has happened to mobile accessibility in recent years. That OS had so much accessibility promise, but Microsoft blew it.
I've converted a couple of videos from the archived 1996 website of Babylon 5 to a modern format for your enjoyment!
The original file is at the resolution of 156x88 but the content is so 90's internet that I just had to.
Starting with Ivanova welcoming you to the online experience with a bit of a warning.
And sure enough, VoiceOver specifically tells you to use the rotor to enable direct touch for specific apps. So while this might seem a bit annoying at first, ultimately I think this is actually a really good thing for the reasons I mentioned in previous posts.
Before, if you went into any of these apps, you wouldn't even get the chance to turn it on because you'd lose all touch. Well, I noticed my flicktype wasn't kicking into direct touch after a phone restart and I had to turn it on manually. Now I just looked with hints turned on...
Also note I don't put the blame entirely on the developers themselves. No architect or civil engineer has to go out in their spare time to learn how to make accessible buildings or crosswalks. It's part of their core education.
Somehow, my CS education thought it was super important to tell me about linked lists and data structures, but not how blind people use the internet. I think they could have spared at least a week on this.
I think it goes to show how immature our field is, when software engineers can work for decades without learning how to make their apps usable by blind or otherwise disabled people. Imagine if architects designed buildings without wheelchair ramps, or if civil engineers designed crosswalks without grooves or curb cuts.
They used to! And it was super dangerous! But now there are regulations forcing the engineers to figure this stuff out. I imagine accessibility will be the same in the future.
FYI from gorhill (maintainer of uBlock Origin) regarding DuckDuckGo's Privacy Essentials web extension (https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-for-firefox/):
> Regarding 3rd-party exposure, I find that uBO protects you better... For instance, while DDG reports that ad.doubleclick\.net was blocked on CNBC, the network pane reports that not ALL requests to ad.doubleclick\.net were blocked, and as a result, ad.doubleclick\.net still gets to know which page you are visiting. - https://nitter.snopyta.org/gorhill/status/1273263804911140865
I wrote an article explaining the trend with browsers' add-on support and why I think that #Mozilla limiting users' choice on Android massively is part of that trend. The add-on ecosystem is degrading steadily, and I don't expect it to reverse course. https://palant.info/2020/08/31/a-grim-outlook-on-the-future-of-browser-add-ons/
Holy crap, google is apparently taking down all/most fediverse apps from google play on the grounds that that some servers in the fediverse engage in hate speech. At least three apps I know of anyway and I'd imagine the others will follow soon under the exact same reasoning.} Seems to be the case with Husky, Fedilab, and "subway" tooter.
this is a scary precedent if google play is going to ban any apps that can in any way be used to access content with hate speech. So what about a forum client, do they take that down just because there is a forum somewhere on the internet posting hate speech?
This is particularly worrisome because for most people Google Play is the only way they understand to install apps at all.
Picture attached of one of the notices received by fedilab.
"This is the most exquisite example of the Streisand Effect I've ever seen":
Blanked-out areas of Baidu Maps reveal location of Chinese camps, prisons, military facilities, the lot / Boing Boing
Blind geek. Hobbies and interests include tech, sound design, programming, and accessibility particularly of games. Regularly livestream let's plays with @talon on https://pg13lp.com/. News poster and database editor for audiogames.net
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!