< img src="" class=" ff-og-image-inserted "> Sara tweeted something just recently that resonated with me:

Likewise, Pro Idea: Utilizing ARIA associates as CSS hooks guarantees your element will just look (and/or function) correctly if stated qualities are utilized in the HTML, which, in turn, makes sure that they will constantly be included (otherwise, the element will obv. be broken)

Yes! I didn’t discuss it when I blogged about available interactions This is my favored method of hooking up CSS and JavaScript interactions. Here’s old Codepen where you can see it in action:

 [aria-hidden=' real'] screen: none;

In order for the performance to work for everybody— screen reader users or not– I need to ensure that I’m toggling the worth of aria-hidden in my JavaScript.

There’s another benefit to this strategy. Usually, ARIA characteristics– like aria-hidden— are included by JavaScript at runtime (instead of being hard-coded in the HTML). If something fails with the JavaScript, the aria-hidden worth isn’t set to “real”, which implies that the CSS never ever starts. The default state is for material to be shown. There’s no presumption that the JavaScript needs to operate in order for the CSS to make good sense.

It’s practically as though ease of access and progressive improvement are linked in some way …

Leave a Reply

Your email address will not be published. Required fields are marked *