I have a true call device and its files are stored on an sd card. A lot
of the ways to operate this software do not seem to have keyboard
shortcuts, and drag and drop is used here to do what in explorer we
would simply use copy for. Quite why software companies feel the need
toreinvent the wheel has always eluded me.


Another program from the past that had touse drag and drop was a version
of Nero, but I stopped using it when I found some much more intuitive
burners.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 16, 2016 10:35 PM
Subject: Re: [nvda] Sighted instructins, was Fly Outsn?


Technically, I'm not sure why, but drag and drop are difficult for blind
people to work with. I have had to use drag and drop very rarely but
fortunately, there are usually other ways to accomplish tasks and, I
have seldom seen programs that require its use. I have seen some web
sites where something you want to do can't be done without drag and
drop. It appears to me that you can't do drag and drop while in browse
mode or the equivalent for JAWS, the Virtual PC cursor. You might be
able to do it when browse mode is off but that would depend on various
factors and I wouldn't count on it on a lot of pages.

Gene
----- Original Message -----

From: Arianna Sepulveda
Sent: Monday, May 16, 2016 4:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Sighted instructins, was Fly Outsn?


Brian, now you have me curious. When are drag-and-drop operations
typically used? I'm planning on learning those commands for NVDA, but
would like to know when sited people typically use them. Well, not the
NVDA commands, ohbviously, but doing it with the mouse, so that I can
perform their keyboard equivalents. I also have JAWS, and plan to learn
the drag-and-drop keyboard equivalents for that screen reader, as well.




Thanks,
Ari

On May 16, 2016, at 9:22 AM, Brian Vogel <britechguy@gmail.com> wrote:


We can all find instances of instructions that are completely unsuited
to a blind or visually-impaired computer user and I understand the
concerns there. The fact is, though, for at least 90% plus of the kinds
of questions I'm routinely seeing on these forums I can find the answer
with a quick web search and the instructions presented are step-by-step
of the open this dialog, click on this option, check the checkbox, hit
OK type. That's what I'm talking about.

I hope that people have noticed that I try my darndest to give "screen
reader terminology focused" instructions when writing for this
audience. At the same time I will continue to make the point that for
instructions that don't use an untranslatable visual component like,
"Click on the purple icon," but instead say something like, "Click on
the Adobe Reader icon," you really should be able to directly translate
this to, "Find, select, and activate the Adobe Reader Icon." Like so
many things, what may be involved in "Find, select, and activate" can
vary wildly depending on how a given user has his or her environment
configured.

Also, just to semi-defend the sighted tech support person who asks,
even after having been told you can't see, "Can you see the blue screen
to your right?," it's very easy to literally forget what you've been
told when you've been working with someone over the phone for a while
and the entire "script" you're used to using has been working, and
generally it will. It's not any sort of malice and, very often, it comes
about as a direct result of the proficiency of the individual asking for
support such that the tech literally forgets during the course of the
interaction that they're dealing with someone who can't see.

It makes perfect sense to remind someone, gently at first but with more
force as they persist in giving instructions that you can't use after
they've been told, that you can't see and that they need to adjust the
instructions accordingly. It's a real challenge at times, particularly
for actions such as "drag and drop" that can be emulated via the
keyboard but that most people, including screen reader users, have no
idea how to do with the keyboard. This happens to be one of those
things that I constantly forget because it can most frequently be worked
around but, on very rare occasions, it can't and I have to figure out
how it's done with the screen reader commands again.

It should come as no surprise, though, that some materials written for
the Graphical User Interface environment will presume that the audience
is actually using the graphical user interface. It's the same kind of
"writing for your intended audience" that I think we all try to do as
much as possible.

Brian
--

Never underestimate the difficulty of changing false beliefs by facts.
~ Henry Rosovsky