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

OPTION -- Making SELECT structures with lots of...

From: jaap van lelieveld <Jaap.van.Lelieveld@inter.NL.net>
Date: Mon, 20 Oct 1997 21:31:12 +0100
To: w3c-wai-ig@w3.org
Message-ID: <Q+7S08h/nblV092yn@inter.nl.net>
As an add-on to the discussion I would like to say waht we need
is the "tree-structure" with the "closed" and "expanded" behaviour
we know from windows.
This is (hidden) in the text (SCOPE-attribute), but if we want this 
why don't we say this more clearly to the HTML group?
This will be equivalent to what windows users are accustomed to.

The question was raised:
> Would one or another of the above versions be better for
> accessibility reasons?  Under what conditions?
> How much is this sort of hierarchy going to help speech, braille,
> etc. users as compared to search-for-string, go-to-number and
> other functions that the browser can provide to get around in
> a flat list?

The first requirement is that the structure used by the designer is
clear. If so a standardized structure - like the tree- or tabsheet one -
helps especially the speech user to navigate faster.

Make sure the "jump on letter typed" option is always working !
Best regards,

Message from: Jaap van Lelieveld      The Netherlands
              Chairman of EBU commission on Technical Devices and Services
E-mail:       Jaap.van.Lelieveld@inter.nl.net

USING: YARN V0.92 as an offline reader, and
       UQWK / OLMENU under UNIX for mail and news transfer
Received on Monday, 20 October 1997 16:37:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:46 UTC