Übersichten

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

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

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…

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.

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

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.

I like to use invalid HTML and ARIA as a design constraint; a line I can’t step across. Sounds obvious, but in practice it’s not always that simple!

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...

ARIA authoring practices are patterns and examples that are a great starting point, but they shouldn't be used as is - let's discuss why.

In part one of this three-part blog series, Gerard Cohen covers an introduction to the official ARIA standard and reviews the 5 rules of ARIA.

Rolle, Zustand und ein zugänglicher Name — wann ist HTML barrierefrei? Möglichkeiten und Grenzen barrierefreier Techniken, und wie ARIA dabei helfen kann.

How lying to screen readers cures accessibility, when it doesn't rub salt in it!

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.

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

There are certain situations where ARIA is a good (and maybe the only) way to go. But if done wrong, usage of ARIA often leads to even worse accessibility. Especially accessibility novices tend to misuse ARIA to "optimise" smelly code.

This document is a practical guide for developers on how to add accessibility information to HTML elements using the Accessible Rich Internet Applications specification [WAI-ARIA-1.1], which defines a way to make Web content and Web applications more accessible to people with disabilities. This document demonstrates how to use WAI-ARIA in [HTML51], which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.

Do you know when to use and not to use ARIA roles, states, and properties? Follow these 5 rules of ARIA use and you will.