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

RE: Microsoft .NET and Accessibility

From: Harry Woodrow <harrry@email.com>
Date: Tue, 29 Jan 2002 09:24:42 +0800
To: <Demonpenta2@aol.com>, <w3c-wai-ig@w3.org>
Well at a recent Microsoft presentation I went to they said that the idea of
net is that it will work on any client.  Everything that comes down to the
user comes in standard technology such as html xml and such.  The server
side is the bit where Microsoft would have the edge however apparently even
that is available to others.

I noted with interest that Visual Basic Net had some extra properties on all
the controls such as Accessibility Index and several others.

I did ask about accessibility there but the presenters, other than pointing
these items out referred me to a Microsoft Accessibility person and
suggested g.hinkle@microsoft.com as a suitible contact..

These issues were also mentioned in the book Introducing Microsoft.net by
David Platt.

All of the software is completely available for inspection so rather than
saying things like..."Will they" or "I bet they won't'" it may be best to
check the sources first.

Harry Woodrow
-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On Behalf
Of Demonpenta2@aol.com
Sent: Tuesday, 29 January 2002 4:54 AM
To: w3c-wai-ig@w3.org
Subject: Re: Microsoft .NET and Accessibility

In a message dated 1/28/02 3:30:12 PM Eastern Standard Time,
nick@webthing.com writes:

Does this mean they're claiming accessibility, but limiting that
accessibility to Windows users by using proprietary protocols?
Do I detect a whiff of a new "let's lock them in" wheeze?

       You bet.

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.317 / Virus Database: 176 - Release Date: 21/01/2002
Received on Monday, 28 January 2002 20:24:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:07 UTC