Adrian Roselli

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

May 23 at 8:28pmWeb
Show threadAdrian RoselliMay 24

Here @yatil is arguing the same point I have:
https://bsky.app/profile/yatil.net/post/3lpvdvuvjuk2d

Others seem to feel the same way based on reposts and comments. Eg (only for logged-in bsky users, but screen shot attached):
https://bsky.app/profile/ebthen.bsky.social/post/3lpvrrvtznc2f

The problem is the Google apologists don’t care and the ones who can make changes don’t want to (as evidenced by who they hire and support).

#accessibility #a11y

Show threadChris HayesMay 23
@aardrian @eric
Not at all surprised to hear Elementor has bloat. That thing is an elephant of a page builder.
Show threadAdrian RoselliMay 23

@chris One of my favorite WordPress projects was tearing that out of a client site. Down to the studs.

@eric

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 RoselliMay 23

@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

Show threadNicMay 23

@aardrian @eric

Wow, this whole exchange raised my hackles. And as someone who gave this person free accessibility advice when they asked for it only to have it ignored, this is so painful to see.

Only one of us is paid by one of the biggest companies on the planet to do this work, sir.

Show threadAdrian RoselliMay 24

@NicMakesStuff
I have logged plenty of free advice over the years — including accessible versions of their patterns. They have ignored it consistently. So it’s a better use of my time to warn people. Gets more traction too.

@eric

Show threadBenji MauerMay 24
@aardrian @eric Elementor is one of the worst plugins I have ever had the displeasure of interacting with. Speaking as a former professional web designer with quite a few WordPress sites under my belt, do not use Elementor under any circumstances.
Show threadAdrian RoselliMay 24

@heybenji
Indeed, in the olden days I used to make good coin fixing Elementor sites.

One of my favorite WordPress projects was tearing that out of a client site. Down to the studs.

@eric