W3C home > Mailing lists > Public > www-style@w3.org > November 1997

Re: RE: User Default Aural Cues

From: James Green <jmkgre@essex.ac.uk>
Date: Mon, 24 Nov 1997 10:11:46 +0000 (GMT)
To: Andrew n marshall <amarshal@usc.edu>
Cc: "'www-style@w3.org'" <www-style@w3.org>
Message-Id: <SIMEON.9711241046.B@sf127.essex.ac.uk>

On Fri, 21 Nov 1997 08:35:35 -0800 Andrew n marshall <amarshal@usc.edu> 
wrote:

> 
> I don't know of an existing implementation, but I assume that audio cues 
> will be more and more important as computers are more capable of working 
> within a pure audio environment.  Some of those cues are probably going to 
> go towards delimiting various types of material from it's more general 
> context, including hyperlinks from their surrounding text.  I make the 
> assumption that users will have settings for these cues, just like we 
> already have settings for question cues, alert cues, and error cues (for 
> example, the Windows Sound control panel).  Authors should have access to 
> these user preferences, in addition to the cues that already exist today.
> 
> I wasn't able to find any BASE tag, so I'm not sure if it would be covered 
> by this.

I think audio cues and such like are a long way off right now. 
Remember, *a lot* of people still use Navigator v3 because it was the 
thing to have and works well. To start thinking about things like 
multimedia is to have everybody keep up with the latest browsing 
technology, and have the equipment to run it properly. Sure you could 
implement it for those people running MS Win95, but that's not creating 
a cross-platform implementation. The only justifyable solution right 
now is having a midi file which *many* people, *not* all, can hear.

I'm sure the browser manufacturers could implement a built-in sound 
alert system, with the page author requesting a specific numerically 
identified sound upon specific action (like the JavaScript on...()), 
but it shouldn't become a standard until the web's original aim for 
information distribution is fully sorted out - bandwidth being a major 
factor (see my other posting).

For your interest, the BASE tag specified a URL to which all other 
HREFs should be related to and/or a specified TARGET, e.g. 
TARGET="_top" to open any new pages in a new window (e.g. out of 
frames).

Comments on this welcome.
 

<snip>

> On Friday, November 21, 1997 5:25 AM, James Green [SMTP:jmkgre@essex.ac.uk] 
> wrote:
> >
> > On Fri, 21 Nov 1997 01:53:19 -0800 Andrew n marshall <amarshal@usc.edu>
> > wrote:
> >
> > > Two that I would really like to see is default values for 'Begin 
> Hyperlink'
> > > and 'End Hyperlink' (corresponding to the default values of cue-before 
> and
> > > cue-after on a hyperlink).  I think this are important defaults for
> > > denoting selectable material in a way familar to the user.
> >
> > I'm not sure I get what you mean... Are you sure the BASE tag is not
> > what you mean?


Term e-mail: jmkgre@essex.ac.uk   |   Home e-mail: jg@cyberstorm.demon.co.uk
Homepage: http://www.cyberstorm.demon.co.uk
Received on Monday, 24 November 1997 05:08:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:52 GMT