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

Re: [css3-lists] [css3-speech] Interaction between list-style-type and speak properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 7 Feb 2011 13:04:04 -0800
Message-ID: <AANLkTimXBBKh4UODhPjUiSkixBD__d3yNpd19EbXAjHH@mail.gmail.com>
To: "Belov, Charles" <Charles.Belov@sfmta.com>
Cc: www-style@w3.org
On Mon, Feb 7, 2011 at 12:48 PM, Belov, Charles <Charles.Belov@sfmta.com> wrote:
> There doesn't seem to be anything explicit in either the CSS3 lists
> draft (1) or the CSS3 Speech draft (2) as to whether setting
> list-style-type to other than normal affects the spoken rendering of the
> list item marker.  I am requesting that this be made explicit in one
> document or the other, probably in CSS3 Speech.

Is this a generic issue surrounding generated content, or is it
specific just to list markers?

If it's specific just to list markers, I recommend Speech specifying
that the list-style-type is ignored and list markers read in some
standard way.  The new Lists spec I'm drafting will allow, for
example, images to be used for list counters, which can't be spoken

> But in the case of a public meeting, where we have a legally published
> agenda, and items are called by the chair by letter, it would be
> important to me that the rendered speech be:
> A. First item
> B. Second item
> C. Third item
> and I would definitely *not* want to leave this decision
> to the user agent.

This is an important case for more than just Speech.  In general,
sometimes the list marker is important content and shouldn't be

To solve this, I'm going to propose an 'inline' value for
list-style-type and a 'marker' value for display, which lets you write
the marker directly in the content, mark it as a marker, then display
it like a list item marker.  In this case, Speech should indeed read
the actual content of the marker.

This proposal will show up in the draft sometime this week as I finish
out my first draft.

Received on Monday, 7 February 2011 21:15:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:56 UTC