W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2001

RE: INPUT TYPE="file", speech output,

From: Jim Thatcher <thatch@attglobal.net>
Date: Sun, 22 Apr 2001 20:38:18 -0500
To: w3c-wai-ua@w3.org, w3c-wai-gl@w3.org
Cc: www-validator@w3.org
Message-id: <NDBBKJDAKKEJDCICIODLOEIBDAAA.thatch@attglobal.net>
You have heard from Cathy Laws that the Browse Button is recognized with HPR
and so you can conclude it is in the DOM since that is where HPR gets the
data to speak. But HPR is missing something. As a sighted user, I can type
in a file designation in the edit field. I think that is an HPR
implementation fault (design defect), not seeing that they should also
provide a text entry field along with the browse button. It isn't an
accessibility fault, however, since the browse button is adequate.

I tried Window-Eyes which relies on MSAA, as I understand it. Neither the
Browse button nor the text entry field are known to them - but please note I
am not a Window-Eyes expert. That, in my opinion (and interpretation), is a
bug for MSAA.

As I understand it, JFW parses HTML and, like HPR, JFW has a flaw in their
interpretation of the validate page, only finding the edit field, not the
browse button.

In all three cases, it seems to me it is not an issue for the content
provider, but for the assistive technology instead.

Jim
jim@jimthatcher.com
Accessibility Consulting
http://jimthatcher.com
512-306-0931

-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]On
Behalf Of gregory j. rosmaita
Sent: Friday, April 20, 2001 6:34 PM
To: w3c-wai-gl@w3.org; w3c-wai-ua@w3.org
Cc: www-validator@w3.org
Subject: Re: INPUT TYPE="file", speech output,


mark wrote:
> someone correct me if I'm wrong, but I don't believe Amaya (on Windows)
uses
> MSAA either, yet if you view the validator page on Amaya in alternate
view,
> the word "Browse..." or that text appears, which could then easily be read
> aloud.

to which i replied:
> right and right, although the second "right" is true only if your browser
> is screen-scraping to build its off-screen model, but if the "Browse"
> button is going to be included in the serial stream/navigation order based
> on the DOM tree, then the AT needs to know where to look for it...

when what i meant to type was quote although the second "right" is true only
if your screen-reader is screen-scraping to build its off-screen model
unquote

gregory
Received on Sunday, 22 April 2001 21:40:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:50 GMT