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

I think so about cat is out of the bag really.
but this spec justifies the means of `contents` is really a contents not only for style.

for example, if TA cares Content in HTML, ignores Style (its not wired for me), contents author can recognize it's bad for adding Content in CSS `content` and we also enlighte them to sparate Style and Content.
but once this spec will standardized, put Contents in Style is justified by annotating with alt.
it's end up with TA author MUST parse all css if they wanna assist accessing user to Content.
and User can't disable CSS (like Reader Mode in these days) because of CSS has not only Style but also Content too. (I don't talk about Reader Mode implementation detail).

but If you says "That is Current Web and support that by Standard Spec", I can say nothing :(

-- 
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-478235928