[wittjeff]

From your title my immediate thought was "cool, maybe this will move us a bit closer to making components (or the testing thereof) cover accessibility thoroughly by default".

See, the idea with the semantic web, and the ARIA markup equivalents, is that things should have names, roles, values, and states. Devs frequently mess up role/keyboard interaction agreement (example: role=menu means a list will drop on Enter keypress, and arrow keys will change the active element), and with ensuring that state info (aria-expanded, aria-invalid, etc.) is updated when it should be.

Then I checked the Antithesis website. They don't even have focus state styling on any of the interactive elements. sigh

[terpimost]

Hey, sorry for antithesis.com. Thank you for noticing this!

The bug is subtle: we do have styles for that, but in some change which I probably did we use css variable, which isn't there...

We will fix that soon.

[wittjeff]

I'm a big proponent of use of design systems for efficient remediation and maintenance, so I'm also aware of how a small oops bug can have wide repercussions.

Let me know if you'd like to chat about use of your system to help enforce proper use of semantics and ARIA in web UI. It looks good.