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

Thanks for the links Fantasai.

Glad to see "Generated content should be searchable, selectable, and
available to assistive technologies," although I think most browsers
currently fail on "searchable" and "selectable".

That requirement also addresses the other discussion in the list about
generated content: it's not part of the DOM, but it should behave as if it
was, when it comes to user interaction.  In this specific case (generated
content for decorative effect) that may not always be ideal, but in section
headings / chapter numbers and so on, it is very frustrating when you can't
search & select.

~ABR



On 24 January 2017 at 11:25, fantasai <fantasai.lists@inkedblade.net> wrote:

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