RE: VS2010 Poses Challenge Against Visually Challenged

  • From: "Homme, James" <james.homme@xxxxxxxxxxxx>
  • To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
  • Date: Fri, 19 Feb 2010 09:48:23 -0500

The new code should call old code if it realizes that it doesn't do what it's 
supposed to do.


Jim Homme,
Usability Services,
Phone: 412-544-1810
Skype: jim.homme
Internal recipients,  Read my accessibility blog

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of RicksPlace
Sent: Friday, February 19, 2010 8:31 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: VS2010 Poses Challenge Against Visually Challenged

Hi: If the screen reader companies use the UIA correctly they should
actually work better with the new accessibility formats. The problem is that
the legace code will likely be rendered useless for anything using UIA only.
Also, MS has been drifting away from putting resources into accessibility
ever since Gates left the company. Jaws uses the on screen model, or use to,
and I am not sure that model will work for the types of painted controls in
the new version of Visual Studio. Windoweyes uses another model and I am not
sure how that will work but it might be better if they ever get all their
code changed. Anyway, the new UI stuff will likely be a real headache for
them until they get up to speed with developing the hooks and modules to
handle the new process. In the mean time it is just use what works. The
screen readers should get better unless they just decide to avoid developing
for MS Products and that is not likely.
Rick USA
----- Original Message -----
From: "Varun Khosla" <varun.lists@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Friday, February 19, 2010 7:49 AM
Subject: Re: VS2010 Poses Challenge Against Visually Challenged

Yes ... you are right. I have also downloaded the portable version of
NVDA and gave it a try on VS and it worked with code editor. In fact,
the first two problems I mentioned previously does not seem to exist
with NVDA — it is speaking the entire line and is very quick to react
with grate predictability.
So the problem now seems to be with Jaws — may be some scripting may
help to solve it.

On 2/19/10, Hrvoje Katić <hrvojekatic@xxxxxxxxx> wrote:
> NVDA supports UI Automation and code editor in VS2010 is simply
> accessible with it. I tried loading a VB project and reading by
> line/word/character works well. Therefore, not sure why it doesn't work
> with JAWS 11 because JAWS11 also supports UI Automation. I didn't try
> RC, the last one I've tried is beta2.
> On 19.2.2010 10:25, Chris Hallsworth wrote:
>> Oh wow! How do you mean you got it to work with NVDA?
>> Chris Hallsworth
>> E-mail and Facebook: christopherh40@xxxxxxxxxxxxxx
>> MSN: ch9675@xxxxxxxxxxx
>> Skype: chrishallsworth7266
>> Twitter:
>> On 19/02/2010 06:56, Hrvoje Katić wrote:
>>> I got code editor in VS2010 working with NVDA, so it's interesting why
>>> it doesn't work with JFW.
>>> On 19.2.2010 6:30, Varun Khosla wrote:
>>>> Hi,
>>>> I've downloaded and installed the update (october 26 release)
>>>> consulting the Windows UI Automation blog:
>>>> Though the menus have started working with Jaws 11, yet the code
>>>> window behaving the same — no improvements.
>>>> I don't know — being my office computer always connected to internet —
>>>> how Windows Update missed this release, although it frequently
>>>> downloads some sort of updates.
>>>> On 2/18/10, Hrvoje Katić<hrvojekatic@xxxxxxxxx> wrote:
>>>>> They added UI Automation support to VS2010, so if you're using XP,
>>>>> it's
>>>>> recommended to install UI Automation update for XP and use JAWS 11
>>>>> which
>>>>> supports UI Automation.
>>>>> On 18.2.2010 15:35, Varun Khosla wrote:
>>>>>> Hi listers,
>>>>>> What was expected has turned out to be true: MS has translated
>>>>>> most of
>>>>>> its VS user interface into WPF user interface in the latest
>>>>>> release of
>>>>>> its popular IDE — VS 2010. I have installed VS 2010 RC today and
>>>>>> found
>>>>>> the most basic things — the code editor — totally inaccessible with
>>>>>> Jaws (10) due to being developed in WPF. Then, I installed jaws 11,
>>>>>> hoping for some resolution, as it is boasted to support UIA (WPF
>>>>>> accessibility API) — but it too turned out to be of little help —
>>>>>> even
>>>>>> menus which were accessible with Jaws10 became inaccessible. Although
>>>>>> some sort of reading abbility is regained with the code editor — but
>>>>>> not at all matching the standard we, as programmers, expect.
>>>>>> Things are getting more and more challenging and difficult as MS
>>>>>> continues to experiment with its UI.
>>>>> __________
>>>>> View the list's information and change your settings at
>>> __________
>>> View the list's information and change your settings at
>> __________
>> View the list's information and change your settings at
> __________
> View the list's information and change your settings at

View the list's information and change your settings at

View the list's information and change your settings at

This e-mail and any attachments to it are confidential and are intended solely 
for use of the individual or entity to whom they are addressed.  If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this e-mail without the author's prior permission. 
 The views expressed in this e-mail message do not necessarily represent the 
views of Highmark Inc., its subsidiaries, or affiliates.
V'�����l�w��f���ڝ�!jxʋ���m�x,j�m�����祊�l��?�+-��肶��)�nX�

Other related posts: