Joy of Code has just pushed a tutorial for making a Svelte component library. Interestingly, he used the W3 APG Accordion pattern as the demo. Great to see.

https://youtu.be/teXFHcugXaI

He’s right to question their use of form inputs in that example, though; who thought that was a good idea!? 🫠

#A11y #Accessibility #APG #SvelteKit #JoyOfCode

Make Your Own Svelte Component Library

YouTube

@philsherry I find it more frustrating that the APG example is three disclosure widgets that *don’t even have a group label* nor does one close when another opens.

It is such a non-pattern that it hurts.

@aardrian Yeah, a lot of strange choices in those patterns, but just seeing accessible patterns referenced by a heavyweight JS framework tutorial channel was like [Leo pointing meme]
@aardrian Do we know who builds those and whether they take PRs?

@philsherry Yes and yes.

Last time I tried a PR to fix a demonstrable WCAG violation was 2019 and still sits open:
https://github.com/w3c/aria-practices/pull/1194

On issues, one person in particular throws up chaff:
https://github.com/w3c/aria-practices/issues/1233
https://github.com/w3c/aria-practices/issues/353

So issues and PRs stay open and I just threw my hands up and started helping clients avoid/remove the patterns instead.

Moves feed delay menu to prior to feed. by aardrian · Pull Request #1194 · w3c/aria-practices

Addresses #877.

GitHub
@aardrian One of “those”, eh. Reminds me of a certain government department which chooses to ignore things and then miraculously invents something fairly similar, months later, but badly and with much less flexibility or research. And then they quietly close any outstanding PRs that might be on their screen during that time.
@philsherry I could rattle off a few OSS projects and at least one closed source JS table library, calendar library, Google Chrome developer site, etc.