Controls that can operate other controls in bulk are not new.

The saga of Jakob Nielsen.

A few days ago Benjy Stanton asked about breaking long words in tables.

Just another usability and accessibility pro telling authors not to do the thing they continue to do.

A look at dark patterns that conform to accessibility guidelines while still tricking users.

The relatively new Web Platform Baseline offering does not track browser support for accessibility features built into the web platform.

An overview of the recent accessibility drama on X.

Browsers each provide built-in video players for the element.

This is me trying to get ahead of a potential issue for users when developers mix and match the patterns.

Be certain you have chosen the term that accurately describes the control you want.

Interactive widgets powered with only CSS are relatively common.

Today Microsoft will stop providing tech support and security updates for Internet Explorer 11 in some contexts.

I have spent a few years banging on about ensuring scrolling areas on a page are accessible to keyboard-only users.

Unlike more traditional forms, laid out with simple pairings of labels and fields, these forms are meant to be read in a flow.

I am one of the many people who stumbled across Cistercian numerals and fell down the rabbit hole.

I have written a bunch about responsive tables. Maybe too much.

It is not uncommon that I raise an accessibility or usability issue and am met with "But Google does this".

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.

Stop using the word drop-down. Instead choose a term that accurately describes the control you want.

Regardless of what accessibility conformance level you target, do not arbitrarily open links in a new window or tab.