I am reminded of when `display: contents` claimed full support even though using it on structural or interactive elements broke them in *every* browser.

Lola’s work needs your support.

It took me longer to understand this image outside the hotel elevator than it took a phone to crack eMudhra’s intermediate certificates.

@nprofile1q... They don’t always (usually). It depends on a lot of factors (language, dictionary, preferences, heuristics, text-to-speech engine, etc).

I tested a few different options here:
https://adrianroselli.com/2022/08/conveying-all-caps-legal-text.html#Options (anchor)

None of those was spelled out. I wrote that post because all-caps text was *not* exposed in legal documents.

So I’m curious where your read all-caps is spelled out?

Related to that last repost of Eric Bailey’s ACD effort from Lola Odelola, I’ve demonstrated that Baseline doesn’t consider accessibility (declared out of scope), which is part of why this effort is so important:
https://adrianroselli.com/2023/12/baseline-does-not-really-cover-baseline-support.html

Google funds Baseline but we have to fund ACD. How appropriate.

I like how El-Sayed handles this.
https://bsky.app/profile/abdulelsayed.bsky.social/post/3my4gocauzs2x

I don’t think he knew this kid was a (GOP-connected Christian nationalist) plant:
https://www.rawstory.com/abdul-el-sayed-2678102480/

For the record, I also disavow the Muslim Brotherhood. Not that anyone asked.

While baking yesterday I managed to burn the fingertips on my dominant hand. But it’s fine because I’m ambidextrous.

Also, I totally meant to put this toothbrush up my nose.

Yeah, this is administration is totally not in Putin’s pocket.

“More Trump Allies Aided Pro-Russian Balkan Government”
https://www.nytimes.com/2026/10/15/us/politics/trump-russia-srpska-elections-wiles.html

“Exclusive: Musk approached Trump to slow down Starlink in Ukraine”
https://archive.is/YreHR#selection-2965.4-2965.69

“Accessibility-first screen reader prediction” is not a solution, folks.

Parsing a DOM and building your _own_ accTree to then *emulate* how desktop screen readers _might_ announce a page as if *maybe* using read-all just ends up putting more burden on human testers.

Never mind missing the bugs, features, heuristics, and more built into a DOM parser and screen reader engine.

Unless your goal is satisfy a dashboard while removing humans from your #accessibility testing.

#a11y #ScreenReader

Aaron Gustafson made a web component for sortable tables:
https://www.aaron-gustafson.com/notebook/sortable-tables-with-progressive-enhancement/

I’m a fan (given many other terrible efforts). Especially the row grouping.

If you use it, I noted 3 things to consider / adapt:
https://adrianroselli.com/2021/04/sortable-table-columns.html#Update01 (anchor)

#HTML #accessibility #a11y

Nic Steenhout on ‘AI’ screen reader testing:
https://nicolas-steenhout.com/ai-screen-reader-testing/

I added it to my post about speech viewer logs (with some bonus nuggets from Weston Thayer):
https://adrianroselli.com/2020/08/speech-viewer-logs-of-lies.html#Update09 (anchor)

#accessibility #a11y

This explains why the product shots looked so weird on the models — plaids with perfect lines, weird folds, and odd artifacting when zoomed. The cardboard cut-out model was just the uncanny bonus.

Ok, tab closed.

(I cropped the photo to show the message buried in the bottom left.)

Trump’s new press secretary, who has repeatedly asserted she is an attorney, seemingly isn’t. Not in California, not in China.

https://www.washingtonpost.com/business/2026/10/13/katie-zacharia-calls-herself-lawyer-legal-experts-arent-sure/

Archive:
https://archive.is/4nVBc

It’s a continued requirement that you have to be unethical to work in this administration.