W3C home > Mailing lists > Public > www-style@w3.org > January 2017

Re: How are screen readers supposed to read <hr> which has icons as generated contents?

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 25 Jan 2017 10:35:02 -0500
To: Ian Yang <ian.html@gmail.com>
Cc: CSS public list <www-style@w3.org>
Message-ID: <158b6714-d28f-f0af-23e2-cd7af4b01882@inkedblade.net>
On 01/24/2017 10:17 PM, Ian Yang wrote:
> 2017-01-25 2:25 GMT+08:00 fantasai <fantasai.lists@inkedblade.net <mailto:fantasai.lists@inkedblade.net>>:
>     This is actually already specified.
>       https://www.w3.org/TR/CSS2/generate.html#propdef-content <https://www.w3.org/TR/CSS2/generate.html#propdef-content>
>     specifies Media = all, which includes speech output and
>       https://www.w3.org/TR/css-content-3/#accessibility <https://www.w3.org/TR/css-content-3/#accessibility>
>     makes this more explicit.
>     ~fantasai
> Thank you very much for confirming that the generated content should be accessible to all user agents.
> And the information "Alternative Text for Speech" (https://www.w3.org/TR/css-content-3/#alt), which I haven't heard before, is
> also knowledge-enriching. I just tested the slash syntax on Firefox and Google Chrome, and they doesn't support it yet, though.

The Generated Content draft is in the exploratory stages of development;
it'll take awhile before it really stabilizes, and at that point
implementations are more likely.

Received on Wednesday, 25 January 2017 15:35:46 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:02 UTC