Not a good look for Google (to be fair, when is it ever...)
To get voices, apparently you need to compile the browser yourself? https://chromium.googlesource.com/chromium/src/+/lkgr/docs/accessibility/chromevox_on_desktop_linux.md
Alright. #ChromeVox on Windows works out of the box. Using the kbd element actually broke it! A list with 4 sub items was being read as a list with 2 items, because the first letter in the third sub-item was a kbd.
Then, while reading text, there was no announce whatsoever about the `o` key being a keyboard input. It would pause, read o, announce "list item" to say now the list item was being read again in continuation before taking the pause for `o`.
@celia Yes, even <em>, <strong> and <s> are usually not announced by screen readers. You can (and should) use semantic HTML, but you shouldn't rely on it being announced.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.