CSS WG level 4 and 5 module changes due to misuse of !important with layer which while not illogical as a solution to external frameworks causing language fragmentation and rushing solutions instead of collaborative, evolving WG specs is reactionary, not innovative. Bothers me.

I do have to admit I'm still struggling with the terminology no code. Could you describe it a little more to me as to what that may have emerged from and why?

So I got to thinking if I were to do something similar for the 100 days of code challenge and would immediately came to mind was history of markup and why it is important to have yes code. There are also binary arguments about what is code, what is language, what is programming.

I'm doing my first irl keynote in a decade May 9th in Austin @knowbility #ACCESSU. I'm also working on a book with the same title as the Keynote. Not sure if I told you about this or if you read anything about it I've also done some recent podcasts.

I'm getting Symantec on its ass that's what I'm doing LOL. Accessibility is availability. We have accessibility tacked onto the tail end. If a site and site content is unavailable for any reason from government control to human conditions to digital divide Etc it's not accessible

If something is in available to us we can't have an experience with it. This places accessibility as the on-ramp to all web content for all interferences. This place is accessibility first and foremost before any other technique or ideology.