Re: [XBoard-devel] Button-bar focus

[Tim Mann]

I guess the tab chain could go through all the windows, even the ones
where there is nothing you can do other than screen-read text and
perhaps select it and copy it with Ctrl+C.

Windows probably has an accessibility standard document that says how
apps with multiple windows are supposed to work, in order to play well
with screen readers and such.  Maybe googling or searching on
microsoft.com would find it....

On Sat, 04 Jul 2009 23:12:40 +0200, "h.g. muller" <address@hidden> wrote:
> OK, thanks for the explanation. Now I see the logic.
> 
> Indeed the JAWS version allowed you to move an 'active square'  over
> the board with the arrow keys, and the board was not in the chain.
> 
> In the light of what yo tell me there might be a logical problem with
> the JAWS version of 4.4.0. This has a few extra windows (engine output,
> evaluation graph) that are just for display, where there is nothing to do,
> either with the mouse or the keyboard, and so it is logical that they
> should not be part of the chain.
> 
> Except that with JAWS, you sometimes want pure output elements to
> have focus, because that is when the screen reader starts reading them.
> Perhaps something other than tab should be provided for this.
> 
> I guess that the fact that these windows do get focus after you pop them
> up should be considered a bug then in the normal version of 4.4.0. Especially
> since there is no way there to pass focus back to anything else by means of
> the keyboard, other than closing them. At the very least tab should be 
> recognized
> as a command to re-enter the proper chain in these windows.
> 
> 


-- 
Tim Mann  address@hidden  http://tim-mann.org/