Bookmarked https://adactio.com/links/19494. Exactly. This is also why I …

Bookmarked https://adactio.com/links/19494.

Exactly. This is also why I don’t (entirely) understand “_not_ using microformats for styling.”

I’ve done this quite a bit: using ARIA attributes as “hooks” for styling and behaviour. It’s a way of thinking of accessibility as the baseline to build upon rather than something that can sprinkled on top later.

I mean, guessing ARIA is considered more “native” than HTML classes? Because it’s semantics and behavior, in a way? Also, it’s not like it hasn’t been already done.

One response to “Bookmarked https://adactio.com/links/19494. Exactly. This is also why I …”

  1. Jan Boddez Avatar

    Of course the markup could change. Then my styles would change with it. I don’t rely on classes too much anyway, not because doing so would be bad, but because I’ve been around since the web standards and CSS Zen Garden days. I would write HTML and only then style it (and try to avoid “non-semantic” wrapper divs like the plague). You know, like how modern developers use Tailwind and the like? Well, the complete opposite of that.