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

Re: Microsoft .NET and Accessibility

From: Jim Ley <jim@jibbering.com>
Date: Sun, 27 Jan 2002 20:18:10 -0000
Message-ID: <024401c1a76f$bdcb24a0$ca969dc3@emedia.co.uk>
To: <w3c-wai-ig@w3.org>
"David Woolley":
> This means that you construct form layouts using drag and drop and
> one has controls that one places onto those forms, also be drag and
> drop.  In the Visual Basic model, Microsoft provide a core set of
> controls (e.g. file selection dialogues, tree selectors, etc.)

These are inaccessible to me in even my normal browser, let alone if I
try to use any Acess Technologies, the "WebControls" (as they are known)
use browser detection to supposedly tailor the HTML to that browser, now
we know that's unreliable in any case, but they weren't even doing it
successfully.  The controls as they stand are certainly not accessible.

It's already been raised in various newsgroup postings  e.g.
<URL:
http://groups.google.com/groups?selm=xsS_7.634%24X87.83042%40news2-win.se
rver.ntlworld.com >

> Does anyone have some more hands on knowledge of Visual Studio .NET and
> is able to comment on the accessibility of what is generated and the
> ease or difficulty of forcing it to do things well.

If you create your own controls, there's no difference, indeed it may
allow you to take away much of the accessible thinking for forms from the
designer of the end page, but that's not the situation currently.  The
offerings from Microsoft are particularly bad IMO.

Jim.
Received on Sunday, 27 January 2002 15:20:01 GMT

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