Where we develop robust web sites with emphasis on accessibility
Google: Something something #a11y are teh win something something. Also Google:
NEW: @YouTube confirms it is discontinuing its community captions feature, which allowed viewers to contribute subtitles to other channels to make videos accessible to #deaf and hard of hearing people.
The tool will be retired on 28 September 2020.https://t.co/FOPGIcBcVz
— Liam O'Dell (@LiamODellUK) July 30, 2020
Dear #WordPress 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?
In this article, Harris Schneiderman walks you through the process of analyzing a wireframe and making coding decisions to optimize for accessibility.
The most efficient way to build accessible websites and apps is to “shift left” by incorporating accessibility testing into the earliest stages of your development and design process. In this article, Harris will walk you through the process of analyzing a wireframe from an accessibility perspective and making coding decisions to optimize for accessibility in both design and development phases.
Need a complete reference of action hooks and filters found in the Genesis Framework? Here ya go. Note this is intended as a reference, not a tutorial.
Migrating an existing site to Gutenberg, day 4, first note: John and I spent a considerable amount of time fighting with, and swearing at, the Bitnami install script for WordPress.
John’s is working right now but I’m about to go through my fourth reinstall of actual Xampp because when you attempt an uninstall of the WordPress module it doesn’t clean up after itself so you have to nuke the whole thing and start over.
Once I figure this out, (I have an idea what the problem is and it has a lot to do with unlabled fields with placeholders that you can’t easily edit), I’ll start writing down all the dumb stuff you have to do with the keyboard and your screen reader to make this work.
And it’s a lot of dumb stuff.
And we’ll also walk through removing the several plugins that get installed with this thing so you can get back to an actual out of the box WordPress installation.
I absolutely despise install scripts that install a bunch of third-party plugins without asking me first. Extra points taken away if they’re plugins I’ll never use or actively go out of my way to remove wherever I find them.
We’re still going to do the manual install as well but now I’m livid at this script and its stupidity and I keep telling myself we’ll eventually get to actual block development.