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

Re: Blind and visually impaired developers.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 10 Dec 2009 19:54:21 +0100

On 10.12.2009 00:26, Serge Tumanyan wrote:
> Hello, Stefan.
>
>>> If you are interested in my suggestion please let me know.
>> Sure, if you have any issues or suggestions on what we can do to improve
>> TSVN for blind people just let us know! You maybe can imagine that we
>> just don't see the problems and issues TSVN has for blind people.
>
> Ok, thank you, I really appriciate this. I am in a bit better position
> because I was sighted before I have lost the ability to see and I can
> understand both descriptions sighted and blind. So I can better describe the
> situation to the sighted developers - at least I want to believe in this
> (smile).
>
> Let me introduce the principles we use while working on the computer under
> screen reader - I shall be as short as possible.
> 1. No mouse - everything is done from the keyboard. We can emulate mouse
> from the keyboard - but it is really a hard job and takes a lot of time and
> patience.
> 2. We mostly try to use HotKeys if present for all possible operations - see
> option 1, though menu and tab order is also rather easily usable - simply to
> hit a keystroke is faster then travel through the nmenu or tab order.
> 3. All the dialogues are better to be strictly structured - we then better
> understand the content.
>
> According to the principles I want to suggest you to start from adding the
> hotkeys to the buttons, radio-buttons, combo boxes, checkboxes and so on.
> TSVN lacks the keystrokes and mostly I have to Tab and Tab around to reach a
> button or a radio-button. May be if you have the shortcuts done already the
> screen readers do not get them - this happens sometimes if the shortcut keys
> are assigned in somewhat unstandard way.
> For example I want to start from the starting dialogue (smile) SVN
> checkout - here is the list of controls lacking the hotkeys:
> 1. Combo box to select the repository - ControlID = 1029,

Alt-U should work?

> 2. The next in tab order repository byutton ControlID = 1035,

Since that button doesn't have a text, I don't know how to add an
accelerator key there.

> 3. The next Repository button in the bab order with the ControlID = 1036,

same here.

> 4. Checkout depth combo box with controlID = 1373,

fixed in r17919. Use Alt-e in the next nighly build.

> 5. The revision edit box with the ControlID = 1034,

doesn't have a text either.

> 6. Though the Ok and Cancel buttons do not have hotkeys assigned - it is not
> so important since the Ok button is the default one and reacts on pressing
> Enter and the Cancel button reacts on pressing Escape as supposed to be.

If Enter doesn't work, use Ctrl-Enter - that works in all dialogs where
an edit box is present to enter a log message.

>
> The second thing to do is - to add some internal (non-visible) tags to the
> items in the listviews that you mark with the colour for the sighted
> persons. I noticed one example in the revision log dialogues - you mark
> already merged revisions with the gray colour - and it takes some time for
> the blind developer to distinguish between the merged and non-merged
> revision. There could be several ways here:
> 1. Adding MSAA information, where MSAA stand for Microsoft Active
> Accessability. I do not know exactly if you are familiar with MSAA - if
> not - I surely can help you with descriptions, testing of changes and
> answering questions on it.

Good idea. I'm currently reading the docs for MSAA and will make use of
it where possible and necessary.
I've also got the accessibility checker tool with which I'm now testing
the TSVN dialogs:
http://acccheck.codeplex.com

> The third thing is that some operations can be performed only by Right-mouse
> button drag - it is possible to perform this operation for me, but trust
> me - it is easier to move a mountain then to perform it for me. The
> operation where this is the only way is move operation - may be some others
> that I have not noticed yet because I did not need them till now.
> I suggest to add some kind of TSVN specific Cut and paste operation that can
> be performed from the keyboard if needed - you can use different keystrokes
> from the Windows standard ones - for example Windows+X to cut and Windows+V
> to paste.

The copy/move operations in explorer which TSVN provides via right-drag
can also be done with the explorer "Copy" or "Cut" (the normal copy/cut,
i.e., Ctrl-C or Ctrl-X) and then using "paste" from the TSVN submenu.

> Additionally I shall provide you with exact location of controls that seems
> to lack accessability - if you do not mind of course.

Sure, just send a list of those and I'll add whatever I can.

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=2429282
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-10 19:54:39 CET

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.