Re: Is WPF Accessable?
- From: "Richard Thomas" <rthomas@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 20:24:02 -0500
Hi Sean:
I am really raw with UI Automation. I just read some about it, looked at some
code, think it was what is called client rather than provider, written in C#
and Vb.net which walked the control tree.
I am tstarting to learn to write for UI Automation and would prefer Vb.net but
could learn to work in C#.
Rick USA
----- Original Message -----
From: Sean Farrow
To: programmingblind@xxxxxxxxxxxxx
Sent: Thursday, February 21, 2008 6:33 PM
Subject: RE: Is WPF Accessable?
Hi:
I am not a beta test of window-eyes, but knowing a bit about automation and
about UI automation, I woul be happy to write such a setup. I would write the
setup in a mixture of Delphi, and one of the .net languages--this could include
chrome from remobjects software.
Any volentiers and what .net language would people prefer?
Sean.
------------------------------------------------------------------------------
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: 21 February 2008 23:08
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Is WPF Accessable?
Any detailed docs on the process and can it be written in Vb.net? Or, is
there something about c++ which makes it a better choice for automation coding.
WindowEyes is getting a Scripting Language using a Com Host I think they
called it and so I'm thinking of getting started messing with accessibility
coding. Perhaps automation can pick up anything the WindowEyes scripting
process misses.
Rick USA
----- Original Message -----
From: Chris Meredith
To: programmingblind@xxxxxxxxxxxxx
Sent: Thursday, February 21, 2008 5:44 PM
Subject: RE: Is WPF Accessable?
There's no really short answer to that question, sadly. As it stands now,
WPF is accessible using UI Automation. Sadly, however, screen reader vendors
haven't added access to UI Automation, for reasons of which I'm not entirely
certain, though I expect it has something to do with their reluctance to write
part of their product in managed code (I'm not entirely certain what
performance hits they would encounter there). There is an unmanaged UI
Automation API, but documentation is minimal at best, and Microsoft strongly
advises using the managed API. What I want to know, and perhaps someone more
wise in the ways of screen reader development than I can provide an answer
here, is why the vendors don't write potential UI Automation handlers in
managed C++, which is a recommended way of mixing managed and unmanaged code in
the same application (and I expect they're using C++ for at least part of their
development as it stands).
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Thomas
Sent: Thursday, February 21, 2008 2:34 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Is WPF Accessable?
Hi Punit:
Don't know, still trying to find a set of instalation instructions for VS
2008 Pro to set up an installation plan.
Rick USA
----- Original Message -----
From: Punit Diwan
To: programmingblind@xxxxxxxxxxxxx
Sent: Thursday, February 21, 2008 10:33 AM
Subject: Is WPF Accessable?
Dear Members,
We all are aware that Microsoft .NET 3.0 and later comes loaded
with WPF application development functionality. Now VS 2008, every can easily
develop WPF enabled applications.
I want to ask is it possible to develop WPF applications for we
people? I tried Linq and it seems accessable to me. Did any one tried WPF
application development using designer.
I assume once we develop WPF enabled app, we will have to use UI
Automation to make it acessable as recommended by Microsoft. Waiting for your
comments.
Thanks
Punit Diwan
Other related posts:
