Links, images and the semantics of description
Rian Rietveld's "The perfect link" is a definition rather than a code reference: When you click on them, they take you somewhere else.
The practical payoff is in the details, for instance the alt text of a linked image should signal that the image is a link. A plain image reads "A cherry tree in full bloom."; the same image acting as a link reads "Wikipedia on cherry blossoms."
Image description gets two further treatments. Eric Bailey's "Your Image Is Probably Not Decorative" argues that most images carrying an empty alt attribute (literally alt="", with no space) should instead have had a description. When no description can be written, other routes exist, such as exposing the image inline (spacer.gif) even if it isn't one otherwise, or using <title> in SVG. Jake Archibald, meanwhile, draws on a 2011 Léonie Watson article to argue that emotion belongs in alt text: The relevant parts of an image aren't limited to the cold hard facts.
Rendering changes and motion
George Joeckel documents the news that Google Docs will be rendered in <canvas>, which reads as a major accessibility concern. At one point the thinking was that a separate product would serve screen reader users, a separate but equal arrangement that isn't a good one. The <canvas>-based rendering appears to be on hold for now.
On cursors, Eric Bailey is blunt: I believe that letting CSS load a custom cursor was a mistake.
Motion drew attention from outside the discipline too, with Katie Deighton covering motion sickness and preference toggles in The Wall Street Journal. Bruce Lawson's take on prefers-reduced-motion and browser defaults describes reaching for Intersection Observer to watch for scroll-triggered animation without the browser grinding to a halt, and then cleaning the code with a prefers-reduced-motion media query.
Testing, enforcement and persuasion
- CSS as a gate: Adrian Roselli shows that proper styling can be withheld unless the matching accessibility attributes are in place, for example
[role="region"][aria-labelledby][tabindex]on a scrolling table. - Component-level checks: Varun Vachhar explains running Axe over a component library while coding in Storybook. Contrast problems are bugs, and should get the same tooling as any other bug.
- Making the case: Todd Libby lays out the order of arguments for accessibility at work: ethical, financial, legal, humanization, then simply doing it without asking.
- The hardest component: Kitty Giraudel's "Creating An Accessible Dialog From Scratch," described as taking on the final boss in accessibility.



