[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Several things to discuss in terms of accessability.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 03 May 2010 18:31:35 +0200

On 03.05.2010 09:08, Serge Tumanyan wrote:
> Hello, All.
>
> First of all I would like to thank everyone and say that I love the latest
> changes in TSVN - they make me even more productive then before. Especially
> I like that the accHelp for the revision list now has the labels for already
> merged and for the working copy is at this revision - this is a miracle and
> enhances my productivity a lot.
>
> Now the things I want to discuss:
> 1. The dialogue Branch/Tags has changed a lot from the previous versions and
> is more usable now but the second field in the tab order with the ControlID
> = 1029 that has a label 'To Path' has a visible static test control label
> located before this exact control but I can not catch it on the screen -

I don't see such a test control label there.
The control which comes before the "To Path" in tab order is an edit
control showing the "From WC at URL:".

But I've just adjusted the controls a little bit since the edit control
overlapped with the combo box right after the "To Path:" label. Maybe
that's what is confusing your screen reader?

> does this mean that it is now a graphic label with the correct window name
> that is not drawn? The reason I am asking about it is that I can not catch
> the hotkey with any of the methods I have now in JAWS scripting language in
> opposite to the prior situation when all the labels were observed by screen
> intercepting methods. Something has changed here and I can not understand
> what has changed exactly.
>
> There are two ways to behave here:
> 1. To try to understand what is wrong here and to try to rework it to get
> the information necessary for me without any visual changes.
> 2. Simply to assign the accKeyboardShortcut property to this particular
> control (I have understood from experimenting the it is Alt+T) and then my
> scripts will catch it easily.

Alt+T is the acc key for the "To Path:" label, which then sets the focus
to the combo box right after it. That combo box is there to enter url
paths relative to the repository root.

> I believe that now my scripts and your changes are quite good for starting
> point to include them in the installer and notice in documentation that the
> support for JAWS versions starting from 9 started in TSVN with providing
> this list address for those who want to ask for some fixes - people have
> different traditions of work in SVN and some other people can notice
> something that was not noticed by me because our traditions are different.
>
> If you believe that this is reasonable - we can discuss how to catch the
> fact screen reader is installed and where is it installed and what should be
> done to install the scripts.

Just tell us how we can find out whether JAWS is installed and where so
we can extend our installer.
I think it would be best to add another "Feature" which is shown in the
installer page, where the user can now choose to install additional icon
sets and spell checker modules.
And if you're ok with it, I'd like to have the JAWS script feature
disabled by default, so that only users who really need it get it installed.

Is there a restart needed for JAWS to find those installed scripts? If
yes, we might also show a dialog after TSVN finished installing to
inform users about that fact.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2601962
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-03 18:31:38 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.