Just popping my head up to offer some very rare but well-earned praise for GoDaddy.
I just had to log into their DNS manager to update a record for a client. I found that the record editing process was extremely accessible which made my job easier.
There are of course still improvements that need to be made to the interface, but I’m glad to see that some accessibility work has been done.
On a related note, WPEngine is promising a new interface with keyboard accessibility, which is also a welcome improvement.
I’m looking forward to that.
Right about now I’m all for declaring Marco Supreme Ruler of the Universe.
Late in November, I published a personal opinion on the state of Gutenberg accessibility. Today, I’d like to give an introduction to Gutenberg from a screen reader user perspective.
I still have issues with this whole Gutenberg process, and my recent criticisms regarding leadership and project-level accessibility prioritization still hold.
But this quick guide to using Gutenberg with a screen reader gives me a place to start, and at least allows me to work with the thing, and even to think about experimenting with some things on a development version of this site.
So, thank you tons Marco, I probably owe you a keg at this point. 🙂
I’ve tried to come to terms with AMP, but just can’t bring myself to do it.
Google wants to speed up the web, and it has a plan:
For many, reading on the mobile web is a slow, clunky and frustrating experience – but it doesn’t have to be that way. The Accelerated Mobile Pages (AMP) Project is an open source initiative that embodies the vision that publishers can create mobile optimized content once and have it load instantly everywhere. Right off the bat, if you use the AMP project page to get a sense of how capable Google is of doing this right, you may become a little deflated. For starters, it fails on the accessibility front, lacking alt text on images, a lang attribute on the element, controls on its opening video, and sufficient text contrast. It also seems to demonstrate just why we want faster pages by itself weighing in at 44MB over 124 requests, taking nearly 6 seconds to load.
If a client insists on it, I’ll do my best to convince them otherwise, but if they continue to insist I’ll of course implement it because pick your battles (TM).
This has turned out to be a great resource for keeping up with the flaws of AMP though.