Last week, the Trump administration argued in court that providing ASL interpretation at White House briefings "would severely intrude on the President's prerogative to control the image he presents to the public." The National Association for the Deaf has sued to restore real-time ASL interpretation.
Drupal
Editoria11y
We've spent the past two weeks discussing accessibility standards - what they mean, why they matter, and how to implement them. But there's a gap between knowing what to do and actually doing it consistently. Content editors add images without alt text. Headings get used for styling instead of structure. Links say "click here" instead of describing their destination.
Info and Relationships
You can make text look like a heading with CSS - increase the font size, make it bold, add some spacing. Visually, it looks perfect. But to a screen reader, it's just regular text. The structure and meaning that's obvious to sighted users is completely lost.
This is the essence of WCAG 1.3.1: information, structure, and relationships that are conveyed through visual presentation must also be available programmatically - in the code itself.
Avoid "Accessibility Widgets"
You've probably seen them: that little circular icon in the bottom corner of a website that opens a menu promising to make the site accessible. Install one line of JavaScript, and your site becomes "100% ADA compliant" and "protected from lawsuits." It sounds too good to be true.
That's because it is.
Audio Description (Prerecorded)
I'll be honest: before researching this post, audio description was the accessibility standard I knew the least about. I understood captions for deaf users - that's straightforward. But audio description? I knew it existed, but had never actually implemented it or really understood when it was necessary.
Non-text Content
If you know anything about web accessibility, you probably know about alt text. It's the most widely recognized accessibility technique - that little text description you add to images so screen readers can announce what the image shows. But there's more to non-text content accessibility than just slapping some alt text on every image and calling it done.
Let's dig into what you might not know about making images, icons, charts, and other non-text content accessible.
Use Drupal Flake for PHPUnit testing
Drupal Flake is a new way of doing local Drupal development (running a self-contained Drupal site on your desktop or laptop).
Use Group Purl on your Group site!
One big missing part of the Group module is setting up friendly URLs that contain the group in the path for group content. You can't set this up in Pathauto -- the tokens are too limited to handle this correctly.
Easy unit testing with Drupal Flake and AI - Group PURL, a case study
AI does not replace system engineering. Stories abound about AI running amok, deleting production databases, exposing private data, failing to deliver on promises.
Automating all the things - 24 ideas for things you can automate with your website
Last December I wrote up 24 specific things we've automated on Drupal, and published them as an Advent Calender -- one little nugget each day.
Unleashing the power of ECA: No-code coding for ambitious site builders
Last year I gave a presentation at DrupalCon about automating things using the powerful ECA Module. Here's the recording!
Containerless Dev environments for Drupal development with Nix
The recording of my talk from DrupalCon this year is now available!
This is perhaps my most technical talk, meant for developers and tinkerers who would like an easy way to get started with Drupal.