#aria

Originally published at norvik.tech Introduction Explore the implications of Matt...

Australia's ARIA charts have instituted a landmark ban on songs created by AI, declaring the charts a measure of human artistry, not just consumption.

A new CSS-Tricks piece by Durgesh Rajubhai Pawar argues the browser is right to complain when you hide a focused region — and every popular workaround for the warning just moves the bug somewhere quieter. The fix is a reordering, not a new attribute.

Investigate browser behavior when multiple ARIA roles or properties conflict on a single element, how inheritance and overrides work, and debugging techniques to ensure correct semantics for assistive technologies.

Steve Frenzel's Piccalilli piece walks every widget that used to demand aria-expanded and shows how many are now better served by <details>, <dialog>, or the popover API. Keep the attribute for menus, navigation, tree views and combo boxes, and drop it everywhere else.

Adrian Roselli has rebuilt his 2019 disclosure-widget primary nav on the native HTML `popover` attribute. The rebuild is a clean map of what the platform now carries for you, and where you still need ARIA.

When you build an interface, icons are the part you check with your eyes and then stop thinking...

Tabs | Component Deep Dive #37: Tabs — Scroll-Snap, ARIA, and Keyboard Arrows User clicks...

Most component libraries implement accordions and tabs the same way. They shouldn't. Both patterns...

Explore how screen readers process ARIA live regions updates, the timing nuances that affect announcements, how interruptions are handled, and strategies to debug live region issues in SPAs.

Writing 'Primary navigation' on a `<nav>` makes a screen reader announce the word twice. The fix is to trust the landmark and let the label do its actual job.

The 8 ARIA roles you actually need, the ones to avoid, and the common mistakes that break screen readers. Native HTML first, ARIA only when necessary.