The myth of perfect ARIA support | Eric Bailey

A look at why ARIA should be treated like any other web technology:

All web technology has compatibility issues... [and] ARIA is a web technology.

In other words: use semantic HTML wherever possible so that you keep ARIA use to a minimum; break complicated interactions down as much as possible to prevent ARIA overlapping and getting muddled; always check for support (like you would with any other web language); use automated accessibility tools like WAVE and Axe; test your code. Just like JavaScript, CSS, or anything else, it's best to keep things simple so, as Eric puts it:

ARIA should be the last tool you pull out of your toolbox, not your first.

Explore Other Notes


How to tame line-height in CSS

An interesting read that covers some of the basic terminologies of typesetting, as well as the technicalities of how browsers actually interpret the line-height value. Hint: it's not what you'd […]

Made By Me, But Made Possible By:


Build: Gatsby

Deployment: GitHub

Hosting: Netlify

Connect With Me:

Twitter Twitter

Instagram Instragram

500px 500px

GitHub GitHub

Keep Up To Date:

All Posts RSS feed.

Articles RSS feed.

Journal RSS feed.

Notes RSS feed.