W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2003

Re: place-holding characters in edit/text boxes

From: Charles McCathieNevile <charles@sidar.org>
Date: Sun, 7 Sep 2003 02:49:12 +1000
Cc: w3c-wai-ig@w3.org
To: Charles McCathieNevile <charles@sidar.org>
Message-Id: <0B147289-E08A-11D7-8023-000A958826AA@sidar.org>

Aha. We did some testing at Sidar and discovered that Outspoken (the 
only screen reader for the Mac) also has this problem. Which was 
important, because at least one of our people (who was doing the 
testing for a project) uses this as his everyday platform.



On Wednesday, Sep 3, 2003, at 00:09 Australia/Sydney, Charles 
McCathieNevile wrote:

> The best response I have got is "old screen readers and Netscape" - 
> from the times so long ago (6 years) when forms were new, 
> non-standard, and the little boxes were not clear to systems that 
> tried to explain the text on the screen.
> In which case a space would probably not be the thing that triggered a 
> useful response.
> I can't vouch for the accuracy of this already vague information, nor 
> am I equipped to test it, but maybe somebody can do better having this 
> much extra... Reading the archives of the WCAG group through 1998 
> might also be enlightening.
> cheers
> Chaals
> On Thursday, Aug 28, 2003, at 00:20 Australia/Sydney, Lauke PH wrote:
>> Is there any information as to examples of ua/at that exhibit this 
>> flawed
>> behaviour ? Any known cases of problem combinations ? I've asked a 
>> few times
>> before, but the list always seems to go quiet after that...
> --
> Charles McCathieNevile                          Fundación Sidar
> charles@sidar.org                                http://www.sidar.org
Charles McCathieNevile                          Fundación Sidar
charles@sidar.org                                http://www.sidar.org
Received on Saturday, 6 September 2003 12:49:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:25 UTC