Kind: Replies

Yay!

Callisto is the bestest good girl and she deserves all the treats and toys.

I don't have any of that set up on this box yet, and I promise you didn't want me doing that while I was in the process of hitting the wall earlier.

@yatil There are opposing ideas, and then there are mutually exclusive ideas, and respectfully I think he's mixed up these two concepts. And just to throw the other often cited tech argument in here, you cannot ship-of-theseus your way out of overlays not fixing accessibility and maybe if I an accessibility bigwig come in here they'll start working.

It's going OK. Just super busy around here.

@alastc @SteveFaulkner The best thing in this scenario is that there's no such thing as a working overlay, and the worst is that overlay vendors like AudioEye now have the capital to claim that "See? Even an accessibility veteran approves of our product", whether he actually does or not. It's already been extensively documented and demonstrated that, from where things stand now, there is not an overlay solution that can fix web accessibility, because overlays are at the wrong end of the stack just for starters. Bringing on an accessibility veteran will not fix this.

What have they done now?

@alastc @SteveFaulkner The problem I see is that, even reading this in the most charitable way possible, an accessibility veteran going in to fix something t hat is fundamentally broken is something like deploying hope as a strategy. Which it's not.

Wow this is incredibly disappointing.

Lol "marketing weenies" I'm stealing that.

Why? Why do they have to ruin everything! Why can't we just have a simple cane that someone hasn't tried to screw up because they think it will help us (TM)?

Yay!

@ViciousBabushka Yes please Fox News keep threatening someone who is infinitely richer than you. By all means. I'm going to go pop some popcorn.

@technolass Also, Disable Gutenberg/Classic Editor essentially use the same function to do the disabling. The classic editor is still in WordPress for various reasons, it's just that these plugins provide an easy way for users to do the disabling without needing to write code.

@technolass So they all work, that's not the issue. The issue is that the community as a whole is going toward an options not decisions model instead of the traditional decisions not options model, which has implications for themes and plugins. Specifically for themes, it means that designers are assuming that users now have the capability to enact whatever design decisions they choose, so designers aren't making decisions about topography ETC. So you can use Classic Editor/Disable Gutenberg with these themes, but you end up in a situation where you need to hire someone to do all theme customizations for you with regard to topography and such. Alternatively, you can tell your clients that they have to use a 6/7 year old theme and they're stuck with whatever design decisions and all the other problems Gutenberg is attempting to solve from the Classic Editor era. The latter is not an option for this organization.

Yes I'm talking about the techno group.

@technolass I can't do it this week, but yeah we can totally get together with some drinks and I'll walk you through some stuff.

@technolass Na I got it. Thanks though.

Yeah I'm going to try.

@KaraLG84 Yeah I think the markdown block is reasonably useful, although I prefer original markdown and not WordPress's flavor of markdown which accommodates the wp_autop function, which I loathe.