ARIA

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 […]

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.

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.

“Roles” that specify the purpose of UI elements are crucially important for accessibility compliance and users. Yet many e-commerce sites fail to get this right.

In this article, Kate Kalcevich explains when to use ARIA and how to use it properly so that you can use ARIA in a way that’s helpful to the many disabled people who use [assistive technology](https://makeitfable.com/glossary/?utm_source=Smashing+Magazine&utm_medium=sponsored+content&utm_campaign=Upskill&utm_term=Fable&utm_content=Sept2022) to navigate the Internet. Let’s dive in!

A complete guide to WAI-ARIA 1.1. The only WAI ARIA cheat sheet you would ever need

Now that we had a look at all the possible ARIA properties let's do the same for all of the...

Let’s talk about disabled buttons. Specifically, let’s get into why we use them and how we can do better than the traditional disabled attribute in HTML

If you have an interface where content is dynamically updated, and when the content is updated it does not receive focus, then you likely are going to need a...

Some attributes in ARIA are boolean(-like). These attributes may seem a lot like boolean attributes in HTML, but there are some important differences to be aware of.