Eric EggertAug 14, 2024

“WCAG is hard” is a self-fulfilling prophecy. I teach WCAG, the good parts, to people who are not testers all the time and they usually get along fine. Do they understand all the nuance? All the weird language? Not without help.

But it’s not made for that. Principles and Guidelines bring you further than Success Criteria ever can.

But it’s not more complicated than other standards or even documentation. Don’t be afraid. You got this! 🫂

Show threadBenny Powers 🇮🇱🦁
@yatil wai-aria is hard because it has lots of private overloading of related terms

like "focus"

most developers think they know what focus is, until they read the wai-aria combobox pattern

then they open up webkit dev tools and notice that activedescendant is called "shared focus", and chrome dev tools doesn't really tell you about it, and neither does firefox

and while i'm here and salty, also safari doesn't announce it to voiceover, so let's hastily construct a visually-hidden alert role that tries to translate words like "dimmed", "selected" and "3 of 7" into all our supported languages

yeah WCAG is hard sometimes.

edit: let's just take it as a given that "custom widgets aren't allowed" just isn't and will never be a requirement
Aug 14, 2024 at 3:46pmWeb
Show threadEric EggertAug 14, 2024

@bp But that’s aria and browser implementation and tools. That’s not WCAG.

Not using a custom combo box is allowed to meet WCAG, using alternative UI, too. It has nothing to do with WCAG.

Show threadEric EggertAug 14, 2024
@bp I’m on record that the good parts of ARIA should be taken into HTML natively and that everything else is deprecated. Then start from the beginning and do it with components people actually need.
Show threadBenny Powers 🇮🇱🦁Aug 14, 2024
@yatil wouldn't it be more fun if everyone just continued to suffer, though 🤣 ?
Show threadEric EggertAug 14, 2024
@bp That feels like it’s the consensus 🤪