I adore desktop mode. It's what I started out with so I just stick
toggle quoted message
Show quoted text
with it. Even when I am using a laptop I tend to prefer laptops with
the full keyboard. These days i hate that a fiar bit of keyboards have
decided that we don't need the aplications key anymore.
On 10/23/18, Sarah k Alawami <marrie12@...> wrote:
Tha'ts true I don't often have time to see the bigger picture. I learn
what I can, and tht's pretty much it. I remember when I used to be
someoen who coudl read a manual in about 3 hours and memorise everything
about what ever it was when I was reading. Now not so much. Lol! Which
is why I'm on this list. Hehahahaha.
On 23 Oct 2018, at 13:10, Brian's Mail list account via Groups.Io wrote:
It is definitely hard to put yourself in somebody elses shoes and if
you like, see the wood for the trees without spending a fair amount of
time with that person and that is sadly not always possible in these
busy days. Its hard also to teach organised thinking. Many people are
pretty random and do not look at what they need to do with an
overview so they can work to a logical method that shows progress in
the learning enough to not lose confidence that they can do it.
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Joseph Lee"
Sent: Tuesday, October 23, 2018 4:17 PM
Subject: Re: [nvda] Switching from Desktop to Laptop Keyboard
Most commands that uses Numpad are shifted to main keyboard area on
layout. In a way, the laptop layo8ut commands makes slightly more
(especially object navigation commands, but that's a bit ahead of the
at the moment).
Speaking of commands, tasks and what not: if I'm not mistaken, based
conversations we had so far, I think you're having a conflict between
important task or two at hand and suddenly being thrusted into a new
reader world. Am I correct? If yes, I advise focusing more on the
hand and how to accomplish it using concepts and commands more than
To others: some of you might say that it is important to teach people
use screen readers and commands. I'd argue that, sometimes it is
let people focus on their work more than the technology that gives
access to information on screen. For this reason, a screen reader
a prospective one) must not only become a teacher, but also a
willing to listen, diagnose, and offer pragmatic solutions that fits
context at hand. Many expert certification programs (including the
offered by NV Access) tells you how things work and what to do for
situations (or simulations), but they won't teach you how to become a
listener and diagnosing issues beyond the technology they're
becoming a good listener and able to recognize, diagnose, and offer
solutions and advice for issues beyond NVDA takes time to master (and
if we try to teach uniformity, people have different worldviews
minds and souls).
I may need to devote an entire thread regarding what it truly means
to be an
NVDA expert and influential add-on developer.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Rechell
Schwartz via Groups.Io
Sent: Tuesday, October 23, 2018 8:01 AM
Subject: [nvda] Switching from Desktop to Laptop Keyboard
I have been using NVDA on a laptop that is connected to an external
I need to temporarily travel, and will need to use the native laptop
Am I need to go through a complete learning curve again ( I see from
user's guide that many of the commands are different) or is there nay
workaround or tips on this?
Guardian Life Insurance Companyn
IT - BTS Group UI/UX
----------------------------------------- This message, and any
to it, may contain information that is privileged, confidential, and
from disclosure under applicable law. If the reader of this message
the intended recipient, you are notified that any use, dissemination,
distribution, copying, or communication of this message is strictly
prohibited. If you have received this message in error, please notify
sender immediately by return e-mail and delete the message and any
attachments. Thank you.