ARIA und HTML

It's within the Document Object Model (DOM) that we find one of the keys to building accessible things for the web: the document.

On July 6 2021 the ARIA in HTML specification, that I co-edit along with Steve Faulkner and Patrick H. Lauke, became a W3C Candidate Recommendation Snapshot...

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.

The Web Accessibility Initiative's Accessible Rich Internet Applications Suite (WAI-ARIA, or just ARIA) is a set of tools and guidelines for making web content and applications more accessible. Most notably, it includes a suite of attributes we can add to HTML elements to embed in them more semantic information that

Semantic HTML and Accessible Rich Internet Applications (ARIA) help create interfaces that work for everyone in the most performant, robust, and simple

Semantic HTML and ARIA help create interfaces that work for everyone in the most performant, robust, and simple way possible. And yet, many people still don’t use them. Let's find out why and explain the benefits of these technologies.

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…

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.