Adrian RoselliMay 23

Huh. Turns out @eric was right about conference-driven development cycles:
https://bsky.app/profile/ericwbailey.website/post/3lprn3p6tnc24

Also, Elementor, why the hell did you need 165kb of JS for a carousel?

But hey, at least you’re now guaranteeing WCAG violations for your customers!

#a11y #accessibility

Show threadPatrick H. LaukeMay 23
@aardrian @eric well, gotta keep up the new "EVERYTHING'S COMPUTER!" speed of standards development, you see
Show threadAdrian RoselliMay 23

@patrick_h_lauke
Move fast and break the web!

@eric

Show threadPatrick H. LaukeMay 23
@aardrian @eric ...and i STILL don't get why we (well, they) are doing carousels in bloody CSS of all things... keep thinking that i must be missing something...
Show threadPatrick H. LaukeMay 23
@aardrian @eric it's like those "i drew the mona lisa using coloured cells in Excel" type exercises...
Show threadAdrian Roselli

@patrick_h_lauke
Wasn’t clear to me, either.

I think they were just CSS wonks who don’t truly believe in separation of concerns, never did deep research (panel / panelset anyone?), don’t understand accessibility (nor AAPIs), don’t know how to vet claimed experts, maybe felt WHATWG was too slow, probably wanted to do it in their preferred language, knew they could Google-bully it faster in CSSWG, and maybe (like many designers) failed to comprehend the scope.

Just guesses.

@eric

May 23 at 9:02pmWeb