W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2000

Re: Tentative meeting on the DOM with AT vendors for the User Agent Guidelines

From: mark novak <menovak@facstaff.wisc.edu>
Date: Wed, 2 Feb 2000 11:05:00 -0600
Message-Id: <v01540b0cb4be102a62e6@[]>
To: pjenkins@us.ibm.com, w3c-wai-ua@w3.org, w3c-wai-pf@w3.org
hi Phil

At 2:56 PM 2/1/00, pjenkins@us.ibm.com wrote:

>> i'd advocate that DOM is just another tool/method, and if company A
>> chooses to use DOM, or an  OSM, or some other idea, that is company A's
>> decision.  i don't support the concept that *all* companies have to
>> use DOM .  I understand the advantages and dis-advantages, just concerned
>> about any "tone" we present to the AT community.
>We need to distinguish between "browser company" and "AT company".

when you say "we", I'm not sure who you are referring to.  I think
you mean the UA group, and if correct, I agree that the UA guidelines/group
to keep in mind the differing requirements of a UA  versus a AT developer.

>I feel
>the "browser company" meets its part of the accessibility contract when it
>provides information to the AT via the DOM.

I would also agree with this, but I wouldn't say that is the "only" way
a UA might be able to meet this requirement.  The UA should expose
all of its content, and using DOM would seem a "logical" method to do

>If the AT doesn't utilize the
>DOM, and that is the only [or best] method that "browser" provides, it is
>still the AT's responsibility to provide the work around or implement the

Again, I would agree, the AT (if they want to stay in business) will have
to provide access to the information in the UA.  "If" using DOM is found
to be the best method to do so, and the AT doesn't use DOM, then they may
or may not meet their responsibility. The UA group should provide examples,
source code, etc., to encourage DOM use.   But that is a decision best left to
the AT developer, not the UA group.

>We can't go forward with accessible technology by always shackling
>ourselves with legacy solutions.  The solution needs to be technically
>accessible.  We can't continue to burden developers and authors with
>redundant solutions either.  Redundant solutions cost TWICE as much.  Side
>issues, such as whether some or when all AT's support it and whether the
>user has the time/money/space/patience to upgrade both the browser and the
>AT, should also be separated.

I'm not suggesting any of this...  I'm simply cautioning the UA group that
"how" we present using DOM or any other technology to the AT community
is just as important as the technology itself.

Received on Wednesday, 2 February 2000 12:02:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:25 UTC