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

Re: ALT-attribute usage (fwd)

From: Chris Maden <crism@ora.com>
Date: Mon, 3 Nov 1997 17:32:27 -0500
Message-Id: <199711032232.RAA23473@geode.ora.com>
To: w3c-wai-ig@w3.org
[Geoff Freed]
> 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?

I would prefer a period or colon.  Remember that accessibility should
mean accessibility to the *sighted*, as well as the non-; "Item, Shoes
for sale" looks goofy and ungrammatical.  "Item. Shoes..." and "Item:
Shoes..." are both grammatically acceptable.  If they don't sound good
in a screen reader, I would venture that the screen reader has bugs,
since these are sensical uses of English punctuation.

<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
Received on Monday, 3 November 1997 17:28:34 UTC

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