Re: Updating VO cursor position
Re: Updating VO cursor position
- Subject: Re: Updating VO cursor position
- From: Travis Siegel <email@hidden>
- Date: Fri, 21 Apr 2006 15:02:08 -0400
If your hardware device can put the mouse cursor on it's location,
then just tell vo users to turn on mouse tracking in your app if they
don't already have it on. Most of them do. I don't, but I'm in the
minority in that. That way, when the mouse moved to where your
hardware device is, the vo cursor would too.
That would solve your problem nicely, and no need to fiddle with the
vo cursor directly.
On Apr 21, 2006, at 1:22 PM, Tomas Zahradnicky wrote:
Hi guys,
Don't do it.
Move your control if you like, but leave the vo cursor where it is.
I should have given a more detailed description of what I'm trying
to do.
The control can be moved by a hardware device and I want to keep it
in sync with the device. To describe what it is:
Suppose you have N columns in a window, and there're scrollbars.
The hardware device focuses a group of D columns and can change
this focus by moving the group within the N columns either by 1 or
by D.
User can change the selection from hardware and that causes the
contents of the column window to shift. Once the selection changes,
the hardware device reconfigures itself and VO cursor has to do the
same. Not doing this would lead into a very bad UI in this case.
I'm trying to keep the device focus in sync with the VO focus as
spacebar simulates mouse clicks at nonaccessible controls. If I
don't move the VO cursor, it would point to a wrong location, would
be out of sync with hardware and be practically useless.
We'll figure it out. Honestly. There's nothing more anoying than
to have your cursor jump all over the place with no concept of
where it went and why.
I understand what you're trying to do, but it will make things
easier for vo users if you don't fiddle with the vo cursor
location. Let us move it on our own, it keeps things simple.
Plus, sometimes it's useful to us to know the application did
something with the control we were looking at. If you moved the
vo cursor with the object, we'd never know it changed, and that
could lead to complications in either tech support, or when trying
to explain something to sighted folks, since they will see it
move, and we won't know it moved. It's very important to allow
the vo user (well, any screen reader user) to control the screen
reader. Do what you like with your app, but please don't move the
vo cursor around on us, it only creates confusion.
On Apr 21, 2006, at 11:30 AM, Tomas Zahradnicky wrote:
Tomas
--
# Ing. Tomas Zahradnicky, Jr.
# The Czech Technical University
# Dept of Computer Science, FEE-CTU Prague
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (Accessibility-
email@hidden)
Help/Unsubscribe/Update your Subscription:
40softcon.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden