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

Re: WAI proposed enhancements

From: Dan Connolly <connolly@w3.org>
Date: Mon, 27 Oct 1997 00:06:46 -0600
Message-ID: <34542F76.C6D@w3.org>
To: Scott Isaacs <scotti@microsoft.com>
CC: "'Dave Raggett'" <dsr@w3.org>, "'w3c-html-wg@w3.org'" <w3c-html-wg@w3.org>, w3c-wai-hc@w3.org
Scott Isaacs wrote:
> 
> I do not consider this workable nor interesting to implement as a long-term
> solution as it does not address any of the real-world issues of hierarchical
> lists.

"workable" is relevant, but "interesting," "long-term,"
and "real-world" are not criteria upon which the HTML WG
is to review the WAI HC report.

Just to be clear, I repeat:

----------------
Date: Fri, 24 Oct 1997 17:22:24 -0500
From: Dan Connolly <connolly@w3.org>

if you don't want the OPTION proposal as
stated to go in HTML4, please supply an alternative to address
the stated accessability requirement:

==========
Some HTML documents include forms with very long selection menus.
The large number of options on these menus makes them hard to browse
when using speech-based browsers or browsers that show a few words
at a time in a very large print.
==========

or argue in the WAI HC WG that this is not a requirement
for HTML4.
----------------

I've prepared full details about the WAI HC WG/HTML WG relationship
in another message.

>  This is essentially defining a new control type (hierarchical list)
> and defining it with a very narrow and fixed definition. I can't offer a
> counter-proposal without taking a few weeks to work through the requirements
> as this is not a trivial problem.  I would like to see the hierarchical list
> postponed and addressed iimmediately post HTML 4.0 at the risk of this
> solution not being interoperable with a hierarchical list that can address a
> wider set of requirements (I listed a few in my earlier mails). This is a
> critical piece of functionality that I do not want to see hastily defined.
> 
> Scott
> 
> > -----Original Message-----
> > From: Dave Raggett [SMTP:dsr@w3.org]
> > Sent: Saturday, October 25, 1997 11:34 AM
> > To:   Scott Isaacs
> > Cc:   'Dan Connolly'; 'w3c-html-wg@w3.org'
> > Subject:      RE: WAI proposed enhancements
> >
> > On Fri, 24 Oct 1997, Scott Isaacs wrote:
> >
> > > Premature send...
> > > <SELECT name="ComOS">
> > >   <OPTGROUP value =washington>
> > >     <OPTION VALUE=vancouver>Vancouver
> > >   <OPTGROUP value="british columbia">
> > >     <option value=vancouver>Vancouver
> > > </SELECT>
> >
> > This is invalid with respect to the Oct 24th Draft of HTML 4.0.
> >
> > You need to add the end tags for OPTGROUP, and to drop the value
> > attribute on OPTGROUP. It would also make sense to tailor the
> > labels for the options and groups for viewing on both old and
> > new browsers, e.g.
> >
> > <SELECT name="ComOS">
> >   <OPTGROUP label="Washington">
> >     <OPTION VALUE="Vancouver WA"
> >         label="Vancouver">Vancouver, Washington
> >   </OPTGROUP>
> >   <OPTGROUP label="British Columbia">
> >     <option value="Vancouver BC"
> >         label="Vancouver">Vancouver, British Columbia
> >   </OPTGROUP>
> > </SELECT>
> >
> >
> > People using old browsers would see the flat list:
> >
> >   Vancouver, Washington
> >   Vancouver, British Columbia
> >
> > People using new browsers would see the hierarchy:
> >
> >   Washtington
> >      Vancouver
> >   British Columbia
> >      Vancouver
> >
> > I hope you will agree that this provides a workable solution
> > that allows the same markup to be viewed effectively on both
> > old and new browsers.
> >
> > 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)

-- 
Dan Connolly, W3C HTML Working Group Chair
http://www.w3.org/People/Connolly/
phone://1/512/310-2971
Received on Monday, 27 October 1997 01:05:18 UTC

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