note
· · to read

It's taken us a while, but we're finally able to continue work on documenting how to use the #WordPress block editor with a screen reader. Everything has been updated to include both Windows and Mac keystrokes, and has been tested with the latest versions of WordPress, Jaws for Windows, NVDA, and VoiceOver for the Mac, along with Firefox and Chrome.

Part 1: https://www.customerservant.com/block-editor-part-one/

Part 2: https://www.customerservant.com/block-editor-part-two/

John and I hope this material is useful!

note
· · to read

It's about to be beer:30. I've gotten the site at least unborked for today, and negotiated a reversion to the Classic Editor until I can get some of these other bits and pieces to work correctly. Plus, I got Slack to run without puking on this little notebook.

note
· · to read

Today in "Why Backups Are Good For You":

Who knew that trying to unf*ck a custom taxonomy to try to make the select work properly in the block editor would result in:

Surprise! Total borking of the site!

Man this is going to be a long process. And my hate for the block editor incraments by one for the second time today. There will be alcohol later.

note
· · to read

Have I mentioned how absolutely hostile the WordPress block editor is? Because I feel like that needs to be mentioned again after I had to change a custom taxonomy for a post only to have to go through a bunch of crap just to get this thing back to being able to be edited in the block editor and then have to redo a bunch of blocks that just disappeared. Reasons why I hate the block editor incrament by 1.

note
· · to read

Have I mentioned how absolutely hostile the WordPress block editor is? Because I feel like that needs to be mentioned again after I had to change a custom taxonomy for a post only to have to go through a bunch of crap just to get this thing back to being able to be edited in the block editor and then have to redo a bunch of blocks that just disappeared. Reasons why I hate the block editor incrament by 1.