Skip to content.
Adrian Roselli Crypto Neural Network Framework MVP

All Posts Tagged: ARIA

Sortable Table Column Mad Libs

Visually and functionally sortable column headers on tables are straightforward (I have a post coming on that soon). However, making them accessible can be a bit frustrating. To clarify, making them accessible to screen readers is frustrating. There are two critical areas where screen readers fall down here: lack of…

Posted:

Tags: accessibility, ARIA, html, pattern, standards, tables, usability, UX

Be Wary of doc-subtitle

In early March, Steve Faulkner shared this nugget for making sub-headings: 👉If you want to semantically identify a heading subtitle, look no further than role="doc-subtitle" w3.org/TR/dpub-aria-1.0/#doc-subtitle #HTML #ARIA #WebDev pic.twitter.com/uaHcVRp6oz Steve Faulkner (@stevefaulkner) March 7, 2020 On its surface it looks pretty handy. Handy enough that Chris Ferdinandi wrote about…

Posted:

Tags: accessibility, ARIA, browser, html, pattern, rant, standards

ARIA Grid As an Anti-Pattern

First I will cover what an ARIA grid is per the ARIA specification, and then I will discuss two patterns proposed by the ARIA Authoring Practices. ARIA 1.1 Data Grids Layout Grids As Defined The Provided Examples 1. Simple List of Links 2. Pill List For a List of Message…

Posted:

Tags: accessibility, ARIA, ARIAbuse, rant, standards, UX

Disclosure Widgets

A disclosure widget is a simple control whose sole purpose is to hide or show stuff. Native HTML has one built in via the <details> and <summary> elements. Until recently, if you wanted to use it in modern browsers you needed to use a polyfill. In most cases it was…

Posted:

Tags: accessibility, ARIA, html, standards

Avoid aria-roledescription

HTML has all sorts of built-in features that, when used correctly, are accessible, will localize, and which just work. For example, if I want a button, I use <button>, and a screen reader will announce it as button. For users in other languages, they will hear whatever is their word…

Posted:

Tags: accessibility, ARIA, ARIAbuse, browser, rant, standards, UX

CSUN 2020: CSS Display Properties versus HTML Semantics

While originally I was scheduled to attend CSUN to present two talks one talk, I ended up not attending (my father won A Major Award so I joined him instead). I gave my talk remotely in my scheduled slot (during my father’s award dinner). While I would have loved to…

Posted:

Tags: accessibility, ARIA, css, html, slides, standards

Role-up

transitive verb [ ‘rōl əp ] roled-up, roleing-up, roles-up Definition of role-up To use an ARIA role on an HTML element to change its semantics and/or force it to accept an accessible name (via aria-label, aria-labelledby, or even aria-describedby). To add ARIA roles everywhere without understanding, often via framework or…

Posted:

Tags: accessibility, ARIA, ARIAbuse

Defining ‘Toast’ Messages

In current user interface terms a toast is a message that appears on the screen; it is often short, often appears only briefly, and often animates up from the bottom (like a piece of ghostly yet precisely-crafted toast), though other directions and a fade-in/-out is common. The Name When Google…

Posted:

Tags: accessibility, ARIA, pattern, usability, UX

My Priority of Methods for Labeling a Control

Here is the priority I follow when assigning an accessible name to a control: Native HTML techniques, aria-labelledby pointing at existing visible text, Visibly-hidden content that is still in the page, aria-label. Too often folks will grab ARIA first to provide an accessible name for a thing. Or they may…

Posted:

Tags: accessibility, ARIA, ARIAbuse, css, pattern, usability, UX

aria-label Does Not Translate

It does, actually. Sometimes. One of the big risks of using ARIA to define text content is that it often gets overlooked in translation. Automated translation services often do not capture it. Those who pay for localization services all too often miss content in ARIA attributes when sending text strings…

Posted:

Tags: accessibility, ARIA, ARIAbuse, Chrome, Edge, i18n, L10n

Accessible Drop Caps

Since the early days of the web, when images could be floated and text would wrap around them, designers have wanted to bring drop caps onto the web. Then we learned how terrible a pattern like <img alt=”M” align=”left”>atthew is for users, and CSS introduced :first-letter, letting us believe all…

Posted:

Tags: accessibility, ARIA, css, design, html, pattern, usability, UX, WCAG

Stop Giving Control Hints to Screen Readers

TL;DR: for standard HTML controls and standard ARIA patterns (widgets), you do not need to add instructions for screen readers on how to use them nor what they are. When a screen reader encounters an element on the page that invites interaction beyond reading, it typically provides users with instructions…

Posted:

Tags: accessibility, ARIA, ARIAbuse, browser, html, standards, WCAG