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: Tue, 24 Jan 2017 13:25:51 -0500
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>, Ian Yang <ian.html@gmail.com>
Cc: CSS public list <www-style@w3.org>
Message-ID: <711cec49-e516-c520-32e1-1ce028ecdbbb@inkedblade.net>
On 01/21/2017 11:59 PM, Amelia Bellamy-Royds wrote:
>     Thank you for the info. Is there a spec defines that CSS generated content should be treated as child content? could you
>     please also provide the data of the support for @media speech? Cheers.
>
>
> There isn't currently a spec that discusses ARIA and CSS generated content. However, browsers are mostly now exposing CSS
> generated content as ordinary text nodes.  Properly specifying this behavior will be part of the CSS-AAM (Accessibility API
> Mappings) spec, and the general work of the new CSS Accessibility task force.

This is actually already specified.
   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
makes this more explicit.

~fantasai
Received on Tuesday, 24 January 2017 18:26:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:06 UTC