so this appears a bug in Chrome<->VoiceOver communication (possibly)

it seems that the screen reader is somehow getting the text of our SCREAMER buttons after the text-transform: uppercase; is applied.

dmazzoni@: are you a good assignee?  this will affect a bunch of MD stuff.

This is an issue going back years:
1) text-transform: uppercase is exposed to ATs as ACTUAL UPPERCASE
2) speech engines interpret ACTUAL UPPERCASE as acronyms in certain cases (like this one)

This is usually the exact case ("A D D??") that causes people to discover this issue, and every time it comes up we have this discussion.

We may want to revisit it, but last time I polled Google SR users they were fairly unanimous that exposing text-transform: uppercase as ACTUAL UPPERCASE was the way they wanted it, and we have no control over what the speech engine does with the input it gets (modulo our own speech engines), so this typically ends up being a WONTFIX.

Agreed, this is WAI.

Authors who wish to override this logic could just add a redundant aria-label on the button with lowercase text. It could even be done automatically.

The problem is that the browser can't know for sure if the uppercase was done for style or if there's a semantic reason behind it.

Also because braille.

who am I to deny SR users what they want