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

Re: Spacing

From: David Poehlman <poehlman1@home.com>
Date: Thu, 29 Nov 2001 13:27:38 -0500
Message-ID: <000401c17903$86efa680$2cf60141@mtgmry1.md.home.com>
To: <w3c-wai-ig@w3.org>, "Patrick Burke" <burke@ucla.edu>
maybe we saw it in netscape but I too remember hearing it come in.  It
might have been due to a malformed element?

----- Original Message -----
From: "Patrick Burke" <burke@ucla.edu>
To: <w3c-wai-ig@w3.org>
Sent: Thursday, November 29, 2001 1:22 PM
Subject: Re: Spacing


At 09:36 AM 11/29/01, Patrick Burke wrote:
>At 08:26 AM 11/29/01, David Poehlman wrote:
>>     Perhaps it is a screen reader issue, but: &nbsp; shows up as
being
>>garbage in speech some times.
>
>I haven't studied it scientifical-like, but I think the &nbsp; (&#113;,
>etc.) gets sent direct & unchanged to the voice output when it is part
of
>hyperlinked text or an ALT tag. No idea if it's a browser problem or
MSAA
>problem or Jaws problem (all relating to IE5/5.5, however).

Hmm, I have done the highly complex testing, & I appear to be completely
wrong. To wit: &nbsp; is converted to a simple space (by Jaws 3.7 &
IE5.5)
whether it is part of ahyperlinked text, the ALT of an image, or the ALT
of
a hyperlinked image.

But I *know* I have encountered &nbsp;'s and other &#-type symbols being
sent direct to the voice/braille display. SO we still need to find the
conditions that cause this to happen.

Patrick
Received on Thursday, 29 November 2001 13:27:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:58 GMT