w3c
clarify css generated content alternative text
Today I stumbled upon https://www.maxdesign.com.au/articles/test-cases-css-content.html which includes this quote from https://www.w3.org/TR/css-content-3/#alt
The content property thus accepts alternative text to be specified after a slash (/) after the last
. If such alternative text is provided, it must be used for speech output instead.
This makes it sound as if css content alternatives are only meant for speech - which would surprise me.
But it is a somewhat unfair quote since the spec references CSS Speech just before this. However, since this quote was reproduced in said article, I think it's worthwhile to point it out.
Also, accname's step 2.6.2 does not seem to take css content alternatives into account.
I didn't try to confirm test results from the maxdesign article. Also, @aardrian's evergreen article covers more testing.
Since css-content-3's issue 4 is "Start work on an AAM for CSS.", I thought we should have an issue on the ARIA end. (I didn't find an issue on the CSS end.)
