Maybe we accessibility folk are a cranky, and at times uncivil bunch. But we wouldn’t be cranky or uncivil if we didn’t have to constantly rehash the basics.
Dear WordPress. I get it. Everybody’s tired of hearing about Gutenberg, and it sucks when you’ve worked so hard on something, only to have a ton of people harshly criticize it. I get it. For Matt and the Gutenberg team, Gutenberg is your baby, and right now it seems like all of us are calling your baby ugly, dismissing all the hard work you’ve put in. Personally, I would love nothing better than to say only positive things about Gutenberg, and to talk about how much better it is than Squarespace’s or Wix’s editor, just to name a few. I would love to not participate in what’s being dismissed as WordPress drama because I, like you, hate drama. Unfortunately I do not have that privilege. I do not have the privilege of simply ignoring Gutenberg’s accessibility problems, because when it becomes the default editor those accessibility problems will directly effect my livelihood. Unless the Classic Editor plugin is per-user and per-post/post type, and unless it seemlessly converts back and forth between Gutenberg blocks and current content, it’s not even close to a workable solution. And that’s not even addressing the fact that, essentially, people with disabilities are being forced to wait on the sidelines again because a break-neck development pace and reliance on volunteers and having a shiny new thing to show off at WordCamp US were more important than whether or not WordPress demonstrated true leadership and did something truly innovative by releasing the first and only block editor that everyone can use no matter their physical ability or technical expertise. OK, so you’ve added some keyboard shortcuts and you do some really awesome things to ensure that what you deliver is an accessibility improvement upon what’s come before in this space. That’s great, but it’s not a first. Wix already does this and has done so for about a year. I mean, I can’t use their editor anymore since they just couldn’t handle attributing WordPress for that awesome update they had for a minute, but hey, they added some keyboard shortcuts and any new site starts with an accessible base and they did it all by themselves so that’s an improvement. I suppose when you go from zero accessibility to partial accessibility you have no choice but to call that an improvement, but that’s not what WordPress is doing. WordPress is improving accessibility on the front end and people with disabilities are picking up the tab. Instead of doing something truly amazing and wonderful and being the first to create a block editor that has complete drag-and-drop capabilities plus the ability for anyone who doesn’t use a mouse or who uses some kind of assistive technology to have complete control over what they create, WordPress is merely copying its competitors when it comes to releasing something that’s inaccessible and then promising to fix it later. Geocities promised to make their page builder accessible. It never happened. Google, same thing. Squarespace, they’re still making us vote on it I think, but I suppose they should maybe get points for at least being honest about the fact they really don’t give a damn. Wix resisted for years and finally started to get around to it, but they made all kinds of promises too and it’s a year later and we’re still waiting for an editor we can use. The list goes on and on and on. Anybody who’s been on the web longer than two seconds knows this song because it’s been played so often. Forgive me if I don’t exactly take promises to fix Gutenberg’s accessibility problems as anything other than promises in the dark. So yeah WordPress, I know WordPress drama sucks. I’d love to return you to your regularly scheduled program. But the WordPress I adopted as my home and as my family is better than Wix or Squarespace or Google or Geocities and I believe that it is still capable of doing great things that will shake the foundations of the web, and passing that up for the sake of speed development and a new shiny is missing an opportunity that you can never take advantage of again.
Last weekend during the Berlin IndieWeb Camp, Aaron Parecki gave a brief overview of where he/we is/are concerning the ‘social reader’. This is of interest to me because since ever I have been reading RSS, I’m doing by hand what he described doing more automatically.
I’ve only dipped my toes into the topic of social readers. I definitely believe they are the best way forward for RSS and the Indieweb in general, but I’m so used to the current way of handling RSS as a consumer that it’s taking me a whhile to make the jump between traditional RSS and social reading without the middle man of a social network.
Current status: About to piss a bunch of people off on the NFB Jobs mailing list by replying to a message which advocates for a weekly salary and annonymity for blind people participating in the drive-by demand letter racket.
The first thing I can tell you that may help you solve part of the problem you’re experiencing is that, unless you have WordPress’s wpautop function overridden, you do not need to add paragraph tags to your code. YOu simply need to separate paragraphs by pressing the enter key twice, as you would in a word processor. If you’re like me and you despise the fact that WordPress picks on the humble paragraph tag, you can disable it using either by filtering wpautop or by using a plugin like Toggle wpautop. To add your syndication sources, (at least for things that aren’t yet supported by the Syndication Links plugin), I would recommend adding some custom buttons to your editor. YOu can do that by using a plugin called Tiny MCE Advanced. YOu can also do it with code but if you’re just trying to get something done quickly and you don’t feel like writing yourself a custom functionality plugin for the buttons, this will do it without all the trouble.
What if users could be sure they wouldn't be annoyed by websites after they grant permission to receive notifications?
I clicked on the link for Jeremy’s presentation, only to be directed to his book on this subject, which I will promptly be buying. I spent a little time looking through the A Book Apart catalog and didn’t realize that had so much cool stuff. And yes, as a user, I would really appreciate not being annoyed on a constant basis by websites I’ve given permission to notify me. I gave Slack permission to do that on the old computer and that was one of the first things I didn’t set up on the new one.
“I'm doing some writing on code + civil rights again; and my conclusion is I need to put my money where my mouth is and move my site away from Wordpress.”