Category: Accessibility

There are 158 posts filed in Accessibility (this is page 3 of 27).

Liked A post by Devin PraterDevin Prater (mastodon.host)

This just has to come out. You know, thinking about Microsoft’s Surface Duo or whatever, all I can think of it is that it’s running Android. Why? Because hardware doesn’t matter to me, not that much. Sure, RAM and CPU power matters to me, and disk space of course. But what really matters, …

I’m just curious. Is there anyone other than Fandroids, (die-hard fans of Android) or Google who is seriously suggesting that Android is on par with Apple when it comes to productive accessibility?

On a more serious note, I think Devin’s making a very valid point. Apple may be a company I hate to love, but there’s a reason I switched from Android to Apple a long time ago and it has nothing to do with my love of corporations

The only part of Devin’s post I’d quibble with is the part about whether or not people are pushing for accessibility in the open source arena. If there’s not buy-in from project maintainers and/or project founders, accessibility is going to be an up-hill battle.

And it doesn’t help that the leadership of the open source and free software communities are basically ambivolent at best about this whole accessibility thing.

I was actually looking into getting myself a Surface, but if they’re running Android I think I’ll hold off on that.

Oh and hi devin, glad I found you on the fediverse. That was a nice Monday morning bonus.

Read Meet accessiBe – Israeli Startup for Web Accessibility by Osher Deri

Check out how a startup is using artificial intelligence to help businesses make websites accessible on complete autopilot. With $12 million funding, it
is all set to help businesses and disables globally.

Oh look! The folks behind #AccessiBe are paying for praise again.

Lifnei Iver comes to mind, which in an incredibly ironic twist is extended beyond its literal meaning to be interpreted by the Sages as misleading people, among other things.

And if you have to pay for praise, you know you’re intentionally misleading your users.

Watched Update on Gutenberg accessibility audit by Joe Dolson from WP Campus

In late 2018, WPCampus released a
request for proposals
to conduct an accessibility audit of the WordPress Gutenberg editor. 
The vendor was selected,
and a fundraising goal of $31,200 was met. On April 29, 2019,
Tenon LLC
provided the final audit report to WPCampus. On May 1, 2019, 
WPCampus publicly shared the report documents.
What happened over the next year? Did any accessibility changes come to WordPress and the editor because of the audit?
Join Joe Dolson, a WordPress Accessibility team lead, as he shares outcomes of the WPCampus Gutenberg accessibility audit and the current state of progress
within WordPress accessibility.

This session was incredibly informative, and I’m glad there was a transcript. It made the session easier to consume and it also makes it easier to refer back to, at least for me.
Hey accessibiliBuddies in case you were wondering there really are developers out there who will tell you with a straight face that you can just sprinkle some ARIA on their totally original non-semantic use of html comments and the stuff inside will be displayed in the browser as they intend.
Google: Something something are teh win something something. Also Google:


Dear it’s almost August of 2020 which means we’re a little more than a year out from the “Come-To-Jesus” meeting that was the Gutenberg accessibility audit. So why is basic accessibility for Gutenberg still an up-hill brawl?