W3C home > Mailing lists > Public > w3c-wai-hc@w3.org > October to December 1997

RE: SELECT/ OPTION GROUPS with the SIZE attribute (fwd)

From: Scott Isaacs <scotti@microsoft.com>
Date: Wed, 29 Oct 1997 11:55:18 -0800
Message-ID: <5F68209F7E4BD111A5F500805FFE35B920FC15@red-msg-54.dns.microsoft.com>
To: "'Dave Raggett'" <dsr@w3.org>
Cc: "'MegaZone'" <megazone@livingston.com>, w3c-html-wg@w3.org, w3c-wai-hc@w3.org
Offhand, I am concerned it potentially won't scale and it doesn't handle
the following:

1) nested value lists (my example from much earlier)
2) multi-columns
3) rich HTML items
4) mult-select for hierarchy
5) Individually checked items similar to a menu
6) Disabling of items or nested groups

Scott


> -----Original Message-----
> From:	Dave Raggett [SMTP:dsr@w3.org]
> Sent:	Wednesday, October 29, 1997 8:23 AM
> To:	Scott Isaacs
> Cc:	'MegaZone'; w3c-html-wg@w3.org; w3c-wai-hc@w3.org
> Subject:	RE: SELECT/ OPTION GROUPS with the SIZE attribute (fwd)
> 
> On Tue, 28 Oct 1997, Scott Isaacs wrote:
> 
> > I guess I am trying to avoid hierarchy and therefore sub-groups.
> > I want hierarchy, but the current proposal fails to address many
> > of the issues with hierarchy.
> 
> I believe you are referring to rendering issues only. Can you
> confirm this?  I would very much appreciate any evidence as to
> how the proposal is inadequate on grounds unrelated to rendering.
> 
> > I also disagree with the suggested rendering as it only addresses
> > single select lists (unless I missed something).  I still do not
> > know how to handle multi-select hierarchical lists, or lists with
> > an undefined size. 
> 
> I don't feel its appropriate for the HTML spec to make detailed
> proposals for rendering. The example in the latest draft was only
> intended to show the hierarchy and not intended as a suggested
> rendering. In any case the HTML working group resolved not to add
> new rendering attributes. There are many ways to present multiple
> selection hierarchies, for instance with a hierarchical menu where
> the currently selected choices are indicated by check marks, or by
> a tree-view control that allows levels of detail to be expanded and
> collapsed. If we want to give authors control over this I suggest
> we start discussing extensions to CSS.
> 
> > Instead of recommending syntax changes to listboxes, why not add
> > text to HTML 4.0 with guidelines on how to properly use lists to
> > make them more accessible. This recommendation can also apply to
> > radio button groups and check box groups (they are no different
> > than a list box in providing a list of options to the user). 
> 
> I will do my best to make the spec clearer on the accessibility
> issues arising from long lists.
> 
> Regards,
> 
> -- Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
> phone: +44 122 578 2984 (or 2521) +44 385 320 444 (gsm mobile)
> World Wide Web Consortium (on assignment from HP Labs)
Received on Wednesday, 29 October 1997 15:45:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:56:11 UTC