Assistive technology testing on any site is important. I know that.

But effectively being demoted from someone who contributes content to a site to someone who simply tests the final product with assistive tech because Gutenberg required when Gutenberg is part of the project I’ve invested years in and accessibility is an afterthought for the top dog of said project is a thing I am never going to get used to.

I’ll get over this particular instance and steal myself for the next one but if I ever get the opportunity it’s no-mouse plus no-monitor plus screen reader plus Gutenberg challenge for said top dog.

For the entire next possible WordCamp US.

This is crap and while yeah we should all be professional bla bla bla this is personal and I’m not apologizing for it or even here for putting a positive spin on this.

Read A note by John Carson on , , Gutenberg and the TwentyTwenty theme by John CarsonJohn Carson

Being a screen reader user, I find it very disturbing that more attention has not been given to accessibility . Just a thought; it would have been much easier and simpler to design and develop for accessibility before starting to code this project. It will be much more difficult to implement accessibility after the fact. Who made the decision to move forward with a project this large without accessibility from the ground up? In my opinion this is the most ridiculously moronic decision I’ve ever encountered!

I met John when I started working for Freedom Scientific.

He had already been with the company a long time, (ever since the days when it was Henter-Joyce and when Jaws 3.0 was new).

He taught me everything I know about screen reader internals, has likely forgotten more about screen readers and assistive technology in general than I’ve ever learned, and did a ton of the scripting work that still makes Jaws for Windows work with websites.

He retired in 2017, and started working with WordPress in 2019. So he can’t be targeted with the “just afraid of change” argument.

I’ve watched him test the TwentyTwenty theme with three different browser/screen reader combos, read through every line of the CSS, and I’ll watch him read through every line of the functions file and other associated templates.

And he was developing with Javascript before there were frameworks.

I’m not saying any of this because we’re friends or otherwise, I’m saying this because he’s earned the right to be listened to.

And yes, his post is pretty damning because this stuff should not still be happening on a project whose leardership continues to claim that WordPress is for everyone despite specifically refusing to put policies in place (accessibility) which are part and parcel of every successful accessibility effort.

Matt, I get it. Gutenberg has been a goal of yours since at least the final WordCamp San Francisco. I get that you and the rest of the Gutenberg team have worked very hard on it, and that you really are trying to move the web forward.

I also get that you’re probably tired of every accessibility advocate, in and outside this community, giving you crap about this stuff. Hearing that you’re not doing a good job, however politely, is not pleasant. It’s not even pleasant when it’s polite, especially in the Gutenberg case, because everybody’s essentially calling your baby ugly.

I can’t speak for anyone else who’s advocated for accessibility in this space, because I’m not them.

Speaking for myself though, I’d genuinely like to quit criticizing you over this, and I’m saying that as someone who has been and will continue to be one of your harshest critics for as long as it takes. No, I’m not forking WordPress and I’m not walking away.

Seriously, quit being so bullish about this. I have no idea why you are as opposed as you are to even the prospect of an enforcible, project-wide accessibility policy, and enforcing same, but setting policy goals regarding accessibility for a project this size, (or really any project), is required for any accessibility changes to be lasting and successful.

An accessibility policy is how you ensure that you don’t keep repeating the same mistakes.

Technical accessibility is the beginning, not the end of accessibility efforts. And if you really want to move the web forward while safeguarding its openness and independence, please do not carry on one of the worst aspects of the free software movement, the one that leaves whether or not people with disabilities are included as part of the “everyone” you champion up to developer and designer and founder choice.

We’re still fighting discrimination in the workplace, and we’re still fighting for equal access when it comes to the technology we use to do our jobs. But the beauty of WordPress and its community is that we can create opportunities for ourselves.“People of WordPress: Amanda Rush” published at

In order for everyone, including people with disabilities, to be able to create opportunities for ourselves, WordPress the project has to make accessibility a priority. The way that happens is through leadership making accessibility a project-wide goal instead of just something individuals work for and fight for.

Last time this became an issue, Web Accessibility Deathmatch happened. If we’re going to keep it positive, and prevent that from happening again, then things have to change and that change has to be led from the top down, since this is a project with a benevolent dictator.

Matt, please rethink your public stance regarding a project-wide accessibility policy.

Current status: Banging on the Twentytwenty theme with all the screen readers and helping @whiskeydragon1 set up his .org account because he’s also testing. #ScreenReaderTagTeam #AllTheProps #5FTF and we haz some patches coming.

It’s very nice to have someone in real time and not remote or chat-based to bounce ideas off of.

Liked This Feature Should Be Easy by Brent Simmons (

A feature is pretty much never as easy as it seems. The main function of a feature — whether that’s making a https call to a read-it-later service or adding some fairly simple new view — is often the easiest part.

Co-signed: Every single developer on the planet.
Amanda wearing a blue knit cap
Amanda wearing a blue knit cap

I’m spending Contributor day working on some accessibility fixes to the Indieweb Publisher theme, which I will submit as a pull request when done because I need some easy wins if the WordPress accessibility fight is going to continue.

I’m also celebrating Blue Beanie Day early because every day is a good day for web standards.

Read Indieweb Thoughts Post State of the Word by David ShanskeDavid Shanske

It has been a while since I wrote out some thoughts on where the Indieweb is on WordPress. Sitting here, after hearing Matt Mullenweg gave the State of the Word at WordCamp US, and after I assisting Tantek Çelik in his talk on Taking Back the Web, which was one of the contributing factors to my being at WordCamp US.