Re: [w3ctag/design-reviews] Alternative Text for CSS Generated Content (#351)

The accessibility tree already depends on CSS, and has done for a long while; for example, `display: none` will cause an Element to be excluded from the accessibility tree (because it's not rendered, so assumed to be currently not relevant to the user).

Pseudo-elements with `:content` are also already exposed in the accessibility tree. This feature will allow authors to fine-tune that process, by either marking them as not relevant for accessibility (by providing an empty string as the text alternative), or by providing a more useful string.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/351#issuecomment-478288279