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

RE: ALT-attribute usage (fwd)

From: Charles (Chuck) Oppermann <chuckop@MICROSOFT.com>
Date: Mon, 3 Nov 1997 14:32:47 -0800
Message-ID: <8158E266008CCF119B5900805FD4816A01F7362F@red-34-msg.dns.microsoft.com>
To: "'Geoff Freed'" <Geoff_Freed@wgbh.org>, po@trace.wisc.edu, w3c-wai-ig@w3.org
Do you think it's wise that a HTML recommendation be based on the
behavior of a single accessibility aid?

Charles Oppermann
Windows NT User Interface Group, Microsoft Corporation
mailto:chuckop@microsoft.com http://microsoft.com/enable/
"A computer on every desk and in every home, usable by everyone!"

	-----Original Message-----
	From:	Geoff Freed [SMTP:Geoff_Freed@wgbh.org]
	Sent:	Monday, November 03, 1997 1:49 PM
	To:	po@trace.wisc.edu; w3c-wai-ig@w3.org
	Subject:	Re: ALT-attribute usage (fwd)

	        Reply to:   RE>>ALT-attribute usage (fwd)

	I vote for "Item."  Based on my experience with outSPOKEN, I
also vote for the comma since it forces a decent (but not long) pause in
the reading of the text.  To keep things as clear as possible, I think
it's important to have a pause after the text tag.  I just ran several
tests and found that outSPOKEN doesn't seem to care if there are spaces
after the comma.  the pause is the same after no space, one space, two
spaces or more.  But outSPOKEN does not pause at all after a semicolon,
regardless of spaces.

	To confuse the issue a bit further... when it encounters a
period, outSPOKEN drops its pitch slightly.  Therefore, inserting a
period after a text tag might make it clearer that the text tag has
ended.  Maybe a period is a better seperator? 

	CPB/WGBH National Center for Accessible Media

	Date: 11/3/97 4:37 PM
	To: Geoff Freed
	From: po@trace.wisc.edu
	Perfect.  Just the feedback we needed.

	Unless I hear otherwise the guidelines will recommend

	1)  that any graphics used as bullets have the alt text  "Item"
With a 
	character to cause a pause after the word.

	The two candidates are Comma and Semicolon.   Possibly with a
	afterward to keep the word from running into the next word.

	Couple of questions to close this one off

	 - Is there a consensus that there should be "item"?  (I thought
I got one 
	but am not sure)
	- Is comma the proper character for a pause.  It is longer but
longer may 
	not be better.  And Semicolon looks better visually and more
natural so it 
	might get included more.     Should we use Semicolon or comma?
	- Is the space needed?  Can someone confirm?  Is it needed for
comma?   Is 
	it needed for Semicolon?

	Thanks much.

	-- ------------------------------
	Gregg C Vanderheiden Ph.D.
	Guidelines Scribe and Compiler

	------------------ RFC822 Header Follows ------------------
	Received: by wgbh.org with ADMIN;3 Nov 1997 16:35:40 -0500
	Received: by www19.w3.org (8.8.5/8.6.12) id QAA26963; Mon, 3 Nov
1997 16:19:03 -0500 (EST)
	Resent-Date: Mon, 3 Nov 1997 16:19:03 -0500 (EST)
	Resent-Message-Id: <199711032119.QAA26963@www19.w3.org>
	X-Authentication-Warning: www10.w3.org: Host
trace16.waisman.wisc.edu [] claimed to be trace.wisc.edu
	Message-ID: <01BCE86A.BD1B6D80.po@trace.wisc.edu>
	From: Gregg Vanderheiden <po@trace.wisc.edu>
	Reply-To: "po@trace.wisc.edu" <po@trace.wisc.edu>
	To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
	Date: Mon, 3 Nov 1997 15:11:18 -0600
	Organization: Trace Center U of Wisc
	X-Mailer: Microsoft Internet E-mail/MAPI -
	Encoding: 28 TEXT
	Subject: RE: ALT-attribute usage (fwd)
	Resent-From: w3c-wai-ig@w3.org
	X-Mailing-List: <w3c-wai-ig@w3.org> archive/latest/175
	X-Loop: w3c-wai-ig@w3.org
	Sender: w3c-wai-ig-request@w3.org
	Resent-Sender: w3c-wai-ig-request@w3.org
	Precedence: list
Received on Monday, 3 November 1997 19:07:28 UTC

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