ARIA

An examination of how aria-label behaves on static elements across browsers, and why real-world support differs from common assumptions.

ARIA provides an attribute which allows to hide elements from screen readers. It works pretty uniformly on non-focusable elements in modern browsers and screen readers, but it still has some very odd peculiarities. So you better try to create solutions that do not need it.

A collection of bad practices in HTML, copied from real websites.

Master ARIA live regions for inclusive web experiences. Discover implementation best practices and practical examples.

A collection of bad practices in HTML, copied from real websites.

As of my 25 July 2025 update at the end of this post, aria-label auto-translation support is less spotty than when I first wrote this post, but still unreliable. It does, actually. Sometimes. One of the big risks of using ARIA to define text content is that it often gets…

Accessible Rich Internet Applications (ARIA) is one of the most powerful tools in a developer’s accessibility toolkit—but it’s also one of the most misunderstood. While ARIA can improve accessibility when used correctly, misuse can actually make things worse for users who rely on assistive technologies (AT), such as screen readers. So, how do you use […]

Same, same but different. Let's find out how to (not) use which attribute!

We're excited to announce the availability, as a developer and origin trial, of ARIA Notify, a new API that's designed to make web content

The output HTML element is an ARIA live region by default.

The [aria-label] attribute is used to provide an accessible name to an element that might not otherwise have one. For example, let’s say you have a button that’s used to download a file. Instead of text, it includes a download icon as an inline SVG, like this… button svg xmlns="http://www.w3.org/2000/svg" height="1em" width="1em" viewBox="0 0 16 16"path fill="currentColor" d="M13.922 5.626A3.72 3.72 0 0010.205 2a3.712 3.712 0 00-2.92 1.418 2.09 2.09 0 00-3.

Back when ARIA live regions were first developed, aria-atomic seemed like a good idea, in case a tool wanted to update a single node, but the only real way to represent the content was reading a co...

I’m Kitty Giraudel, a non-binary trans frontend developer based in Berlin, focused on accessibility and inclusivity.

Rough notes on Sara Soueidan's free chapter "Accessible notifications with ARIA Live Regions".

Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).

Screen reader and browser support tests for the aria-haspopup attribute.

Incorrect ARIA can actually cause more accessibility issues. Learn what else everyone should know about ARIA plus tips for using ARIA.

Three years ago we announced our work on the ARIA-AT program to develop an interoperability testing system for assistive technologies, starting with screen readers. Last year we completed a redesign of the ARIA Practices Giude (APG), which web developers use for guidance on making accessible websites and apps. We’ve been hard at work along the way to build a testing system and collect results on screen reader web rendering interoperability. Today we’re announcing that the first round of test results from ARIA-AT are available and embedded on the APG so web developers can read about screen reader support for various ARIA features.

HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.1 for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

Using ARIA instead of HTML is generally fine for content, layout, structure, and other static bits of a page. A div role=”heading” aria-level=”1″ is the same as h1 as far users and accessibility APIs are concerned. It is unlikely a user will ever notice the difference unless you use both…

Type-Ahead, Autocomplete, Autosuggest — die Combobox hat viele Namen. Wir erläutern die barrierefreie Umsetzung fürs Web nach ARIA 1.2.

ARIA roles and attributes can make your website more accessible, if you know what you're doing.

A collection of bad practices in HTML, copied from real websites.