37 °F Partially cloudy
Blog
-
Read: “My thoughts on Gutenberg accessibility” by @MarcoInEnglish and offered some thoughts of my own
Marco’s being pretty modest in his description of his abilities and what he does for a living, and I’ll save you the time of reading a multi-page biography which would probably border on hagiography (I have a ton of personal and professional respect for Marco) by saying he knows what he’s talking about and should be listened to.
And this is probably as positive as continued critiques are going to get.
There’s so much worth quoting from this post that I had difficulty picking the best excerpt, so I’ll add my thoughts on the other options below, in a slightly different order than they appear in the original post.
… what I see here is a repetitive pattern seen in many other projects, too. Treating accessibility as a bolt-on step at the end of any given cycle never works, will never pay off, and never lead to good inclusive results.
That statement holds true no matter how many slogans or how much positivity you pile on top of it. And I keep bringing up the positivity thing because it’s particularly galling when WordPress leadership preaches inclusion, everyone, and the like, only to have the bits that are inconvenient ignored or dismissed as mere negativity when it comes down to brass tacks.
The fact that a bunch of currently fully able-bodied people have actively decided to not be inclusive from the start means that a lot of decisions requiring a certain amount of both empathy and expertise need to be made at lower levels, and pushed into the product via grass root methods, which are often long and cumbersome and only lead to slow results. These can be very tiring.
This whole situation is crap. The fact that a bunch of us essentially have to stick around because if we don’t the accessibility won’t happen and we have to fight against the laziness of leadership, (and let me be clear here, by leadership I mean the decisionmakers, which doesn’t include most of the people working on Gutenberg, even the designers and developers who carry the title of lead), is demonstration all by itself that accessibility/inclusion isn’t a priority.
I don’t know why other accessibility advocates stick around despite this, I can only speak for myself.
I stick around although with more built-in intermittent breaks out of (1) pure stubbornness and (2) the desire to ensure that people with disabilities are just as able to have an open, independent home on the web just like everyone else and (3) the self-interest I started with.
People with disabilities shouldn’t have to be stuck with Facebook or Twitter, with all their problems, because the benevolent dictator of one of the largest free software projects makes promises, implied or otherwise, about inclusion and “everyone” which he then finds inconvenient to keep.
I once kept a job for two years after the software I needed to do that job became inaccessible because I refused to accept termination and a severence package in lieu of the accessibility issues being resolved. I used that time to hack on WordPress and learn my way around it, and I have benefited greatly from that initial learning and the assistance and friendship or even family of the WordPress community.
If I could manage to keep that job until I could leave on my terms, I will figure out how to stick with WordPress either until things get better or I leave on my terms.
I’m definitely not walking away while that piece paraphrasing my original HeroPress essay is still up on WordPress.org. I still stand by a lot of what’s there, especially the bits about the community, but if I go along to get along, or don’t speak up about this stuff when I think it’s warranted, then essentially I provide an easy way for that piece to be used as promotional material or evidence of a claim that is more like an ideal to be striven for as long as the circumstances are just right.
I don’t have any intention of serving as a token.
I realize all of the above probably sounds like I’m being an arrogant jerk, although I don’t intend arrogance at all, and I hope the people who know me and who have interacted with me also realize that.
I’m thankful for the rest of the accessibility advocates in this community especially, and the rest of the accessibility team who work so hard on a daily basis and never complain when surely they could be doing other things with their free time.
And I’m thankful to the accessibility advocates outside the WordPress community who have spoken up on these issues.
Finally, I’m thankful for Marco joining the discussion.
Yes, I’m tired. But if I can manage to keep a job for two years and leave on my own terms and only on my own terms, I can stick around and help everyone who has spoken up and sacrificed their free time win this. We’ll do it eventually.
-
Aside
Today, (well, I suppose it’s yesterday now), we got a new, bigger crockpot for cooking chili and other good things in, and we got a new coffee pot because the one I brought up here started leaking a while ago.
We also got some mixing bowls and utencils, and a new silverware tray with silverware.
These will go nicely with the other dishes we’ve acquired.
We haven’t made definite plans for Thanksgiving yet, but either way there will be good food and sportsball involved since this Saturday is the Ohio State Michigan game.
I’m looking forward to the four-day weekend and the slowdown of the rest of the secular year.
We’re currently reading the new Atlee Pine book and so far we’re enjoying it. More on that later in the form of a review.
921 S Pugh St, State College, PA 16801(1106ft)41 °F Partly Cloudy
-
Aside
Cannot stop yawning but there’s a light at the end of this project tunnel and it’s not a train.
The hardest parts of this thing will finally be off my plate by the end of today and I can’t wait.
The policies are in place, the mostly user-proof content editing interfaces are in place, and all that’s left to do is train the people who will be entering the content going forward on how to use the interfaces and follow the prompts.
I’m not saying there’s no possible way this could be screwed up, but the content creators at least will have a very difficult time doing this, and I’m proud of that.
921 S Pugh St, State College, PA 16801(1106ft)55 °F Partly Cloudy
-
Aside
Disadvantage to being away from the #GenesisWP framework for a while: You forget things like built-in CPT archive s… https://twitter.com/i/web/status/1199224666436653056
-
This adds an entirely new dimention to the whole ADA trolling thing, and for those in the blind community who advocated for HR 620 that bill would not have addressed this because there are already laws which do, as illustrated by this case.
And for the sake of all of us in the accessibility and disability rights spaces, if the evidence against Finkelstein supports a guilty verdict he definitely needs to be made an example of because attorneys like him are giving all of us a bad name.
-
Aside
There’s a special place in hell, (if hell exists), for developers who create modals that cannot be closed with a keyboard.
I get it, lots of developers aren’t aware of accessibility, bla bla bla, they didn’t mean to be dicks, but when you’re trying to get things done and there’s a modal which has monopolized fucos and you can’t close it so you’re then prevented from moving onto the next task, it’s frustrating.
It’s Monday night, I’m still working, and I just want to get this stuff done.
921 S Pugh St, State College, PA 16801(1106ft)43 °F Clear
-
Aside
What the hell? On Saturday morning, we ordered groceries through Instacart, and we departed from the usual a bit because Saturday was the Penn State V. Ohio State game so we wanted some munchies and sweets and general enjoyable things to eat while we watched the game.
So the Instacart driver gets here and tells us he put things on the stove and the counter but not the microwave.
This means that all of our baked goods are nowhere to be found.
So we fix this by making another Instacart order and we got some other stuff Sunday morning, and don’t get me wrong, we’ve totally enjoyed it.
In the meantime though, we’ve used the microwave several times.
So John goes to make something to eat, and he reaches up to the top of the microwave, and guess what’s there?
The baked goods, or at least some of them.
It’s not that I’m mad at the Instacart driver, it’s just that I would have liked to put those away.
I think they’re OK to eat, but not sure since they’ve sat on the microwave, and the microwave’s been used since Saturday, which means they’ve been warmed up slightly several times.
Total blind moment.
921 S Pugh St, State College, PA 16801(1106ft)45 °F Clear
-
Aside
I just pre-ordered the Indie Microblog book by Manton Reece which is slated to be released on the web on January 2 of next year and I can’t wait to start reading it.
Of course there’s some stuff in there about micro.blog specifically but it also covers using other platforms and setting them up for microblogging a great deal.
I’m specifically interested in the "migration" section and how it handles helping non-technical users migrate away from Twitter and Facebook if they choose to.
It’ll probably be my first read of 2020 and I’m very much looking forward to it.
921 S Pugh St, State College, PA 16801(1106ft)48 °F Clear