W3C home > Mailing lists > Public > www-style@w3.org > November 2015

Re: [css-content] Request for note regarding selection, search, and accessibility of generated content

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Wed, 11 Nov 2015 11:51:27 -0500
To: Michiel Bijl <michiel@agosto.nl>
Cc: www-style list <www-style@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Message-ID: <5643720F.6010106@igalia.com>
On 11/11/2015 11:28 AM, Michiel Bijl wrote:
> 
>> On 11 Nov 2015, at 15:29, Joanmarie Diggs <jdiggs@igalia.com
>> <mailto:jdiggs@igalia.com>> wrote:
>>
>> Does VoiceOver have commands to read rendered text by unit (character,
>> word, line)? If so, what happens when you use those commands to read
>> text with generated content?
> 
> Yes it does. It announces a h1 with a before and after as “heading level
> 1, 3 items”. So it sees all nodes (which pseudo elements are I guess)
> separate. If I use the arrow keys to navigate by character, VoiceOver
> ignores the generated content. Trying to navigate by word has the same
> result.

If VoiceOver is skipping over text that you (and VoiceOver users) would
expect to have presented when navigating, could you please open a bug
against WebKit [1]?

>> In the case of line, is the line spoken the
>> same as the line rendered? Or does VoiceOver, like at least some Windows
>> screen readers, have its own definition of "line" (e.g.
>> 125-characters-long slices of the text within the element)?
> 
> Not sure about its definition, but it doesn’t speak the whole line/sentence.

Do you mean because of how its navigation works? (i.e. if you navigate
enough, you get the entire line/sentence but in pieces) Or do you mean
you cannot get at the generated content at all when navigating by
line/sentence?

>> Some background: From what I have seen, generated content IS exposed to
>> ATs when you ask for the entire text of this element. BUT it fails to be
>> exposed on some platforms if you ask for a specific unit (line, word,
>> character) for a given offset.

> [...] but I can’t think of anything where you would put
> handy information in generated content instead of in your HTML.

If by "handy information" you mean content with meaning such as the
phrase "Example 6" or "Issue 1", then isn't this document an example
where handy information is put in generated content instead of in your
HTML: https://drafts.csswg.org/css-pseudo-4/ ?

Phrases such as "Example 6" and "Issue 1" are the sorts of things I'd
like to be able to jump to quickly via my browsers' find in page
feature, and be able to select, copy, and paste. But it's generated
content, so.... (BTW, does VoiceOver skip over those phrases when
arrowing by character, word, and line?)

Thanks for looking into this!
--joanie

[1]
https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=Accessibility&op_sys=All&rep_platform=Macintosh&short_desc=AX%3A%20
Received on Wednesday, 11 November 2015 16:53:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:58 UTC