W3C home > Mailing lists > Public > www-style@w3.org > June 2011

Re: [css3-speech] reading list-style markers

From: Daniel Weck <daniel.weck@gmail.com>
Date: Tue, 14 Jun 2011 11:17:42 +0100
Cc: www-style@w3.org
Message-Id: <A27A1FF7-A623-4D88-8D94-F3F720086FCB@gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>, Charles Belov <Charles.Belov@sfmta.com>
Thanks Fantasai!

How does that sound?

<p class="note">Note that it is common for user-agents such as screen  
readers to announce the nesting depth of list items, or more  
generally, to indicate additional structural information pertaining to  
complex hierarchical content. The verbosity of these additional audio  
cues and/or speech output can usually be controlled by users, and  
contribute to increasing usability. These navigation aids are  
implementation-dependent, but it is recommended that user-agents  
supporting the CSS Speech module ensure that these additional audio  
cues and speech output don't generate redundancies or create  
inconsistencies (for example: duplicated or different list item  
numbering scheme). </p>

http://dev.w3.org/csswg/css3-speech/#lists

Cheers, Daniel

On 14 Jun 2011, at 10:35, fantasai wrote:

> On 06/13/2011 09:20 PM, Daniel Weck wrote:
>> Fantasai, would you like to follow-up on Charles' updated proposal  
>> "user-agent should announce the nesting depth of list items
>> in some implementation-specific manner"?
>> Or do you mean by "have the option of formatting them differently"  
>> that you recommend completely removing the "nesting depth"
>> requisite, and not requiring any additional speech output than the  
>> list item marker itself?
>> Obviously we could consider an additional CSS-Speech property to  
>> allow authors to toggle on/off structural announcements (i.e.
>> speech output not directly inferred by document text), but I'm not  
>> sure this is a good idea given the wide array of possible
>> cue combinations that can be generated when navigating list / table  
>> structures.
>
> It should be a UA decision of whether and how to indicate nesting  
> structure,
> and the user should be able to control that. We can suggest  
> indicating the
> nesting level as something to consider, but making it a testable  
> requirement
> is imo overreaching what CSS Speech should be doing. This is not a  
> usability
> spec. It's a technology spec.
>
> ~fantasai
>
>

Daniel Weck
daniel.weck@gmail.com
Received on Tuesday, 14 June 2011 10:18:13 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT