Month: 27 Nisan 5784 (May 2024)

Get the Classic Editor and Classic widgets plugins, assuming your site is self-hosted. YOu can use the block stuff with a screen reader, but it's still an efficiency nightmare and the accessibility of specific blocks is up for grabs.

@quanin @cachondo The one that comes to mind is the table block, although it may have been fixed. The bigger issue though is that while the default blocks that come with WordPress may be totally accessible, (and "may be" is doing a huge amount of heavy lifting here), third-party block collections are an entirely different story. And the major advantage to the block editor is that third-party blocks can be released/shared/whatever, with the usual no checks on accessibility because decentralized ETC., which is definitely creating way bigger issues than, say, TinyMCE having an issue that then needs to be fixed. And switching to the code editor isn't really a solution since there are blocks for which you need to change settings/set options/configurations.

@quanin @cachondo Oh and also themes are going json so that they can accommodate all the blocks that are out there. So in other words, not many design decisions being made at the theme level in order to accommodate users making the decision and implementing that via blocks. Making WordPress options-not-decisions instead of the traditional decisions-not-options.

John took some baked beans, some of those beef li'l smokies, and some seasonings and put it all together, and it's been sitting in the fridge since he cooked it last night. So yeah it's pretty good.