[css-content] ::marker content available for assistive technology

[wortwart]

According to CSS Generated Content Module Level 3, §1.1, "Generated content should be (...) available to assistive technologies. The content property applies to speech and generated content must be rendered for speech output."

This is already the state of things for the most common usage of content within ::before and ::after pseudo elements. But for other use cases this makes less sense and might lead to unnecessary screenreader noise. For example, a ::marker's content will replace the native list marker which is purely presentational. Screenreaders currently don't read ::marker content which seems the right thing to do.

[JAWS-test]

native list marker which is purely presentational. Screenreaders currently don't read ::marker content which seems the right thing to do.

In my opinion, this is not correct, see

• https://github.com/w3c/accname/issues/203
• https://github.com/w3c/html-aam/issues/256
• https://github.com/FreedomScientific/standards-support/issues/333

[Loirooriol]

Screenreaders currently don't read ::marker content

They don't? But I'm pretty sure the ::marker content is what gets exposed in the accessibility tree, both on Blink and Gecko.