Date   

Re: Future of Access

Adriani Botez
 

Nv access should definitely keep an eye on this trend.


Von meinem iPhone gesendet

Am 08.12.2017 um 17:43 schrieb Brian Moore <bmoore@screenreview.org>:

I actually thought this was on hold again! It would be nice because the new rules refer to WCAG 2.0 for web accessibility stuff which is what we in the rest of the world are using.


Many countries have similar regulations but more and more, with a couple of exceptions, WCAG is the standard refered to by most countries.


anyway, this discussion is straying out of NVDA territory so it should likely end here.


sorry, when you work in it for a living, this stuff is actually exciting!


Brian.

Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123

On 12/08/2017 11:26 AM, tonea.ctr.morrow@faa.gov wrote:
I'm sure you already have heard, but just in case you haven't, the U.S. laws regarding software and website access are generally called 508 and were put in place about 2000. As of January 18th, a refresh of 508 goes into effect.

The official name for the refresh is 36 CFR 1194 and it has many parts. Sections 1 to 5 (they use roman numerals) are details on how the refresh was accomplished and the conclusions determined. Any Americans might want to read that so you can get an idea of how you can become involved in future updates of 508. The actual changes to the code are the appendices. Appendix D is the old code (currently in effect) that will be kept for anything "grandfathered". Appendix A contains the Chapters 1 and 2 of the new code 508. Appendix B contains the Chapters 1 and 2 of the new code 255 (hardware). And, Appendix C contains Chapters 3 to 7 of the code and will apply to both 508 and 255.

This link will take you to the U.S. Access Board website where the whole thing is posted for public viewing:
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/i-executive-summary

It defaults to section I of 36 CFR 1194, but you can use any of the links to jump to the portion of the code that you want.

Tonea Morrow




Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Ron Canazzi
 

My friend uses some sort of add on for his phone to game.  He wins a lot--or so he says so!

On 12/8/2017 2:37 AM, Lenron wrote:
I am not worried about desktops are laptops going anywhere. For the
next few years they will for sure have a place. You can only really
hard core game on a desktop or a console or a really good laptop.

On 12/8/17, Adriani Botez <adriani.botez@gmail.com> wrote:
NVDA supports arm 64 as well now.


Von meinem iPhone gesendet

Am 08.12.2017 um 07:38 schrieb Sky Mundell <skyt@shaw.ca>:

Absolutely. However, Serotek, the makers of System Access, Docue Scan,
has a app which I use on my IOS device called Sero, and it runs on Windows
and I am a subscriber to the accessibility anywhere package. However,
apple is going to have to sort out things such as how to do complex
formatting, content creation, on IOS in order for people to really use IOS
at workplaces. This isn't a bias or a slap against the iPhone, it’s the
truth.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron
Canazzi
Sent: Thursday, December 07, 2017 10:21 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required

Hi Group,


I'm wondering if screen readers as we know them will even be around at all
in 5 years. Everyone in the sighted world seems to be going more and more
toward very small tablets or even just smart phones. I know a fellow who
says I'm hopelessly behind and that he hasn't owned a desktop or old style
laptop for over 2 years. If this trend continues, what will become of
desktops and how will screen reader companies adapt. As of now neither
NVDA or VFO are producing screen readers that work with smart phones.



On 12/7/2017 4:48 PM, Arlene wrote:
Oh? It will be a shock. How screen readers will be different in 5 years!

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Adriani Botez
Sent: December-07-17 1:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required

With respect, This is a wrong perception. Updates nowadays are bringing
more security and more functionality. It is more than important to keep
everything uptodate. Support will stop after a while for what you are
using and it will be harder and harder to adapt to new technologies. If
you keep updating regularly, you will be used to learn new functions and
it will be very easy to adapt to new things. In 5 years screen readers
will be much much different than today. For those who keep staying
behind, they will loose the path. Please be aware of that.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von
zahra
Gesendet: Donnerstag, 7. Dezember 2017 16:59
An: nvda@nvda.groups.io
Betreff: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required

i am completely against any update, no different if updates are for
softwares or operating system!
i only use anything that i need!

On 12/7/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
Not necessarily, many of the ones that could have been pirates have
allowed

windows 10 on them, so I think this ias a pink herring. Its more
likely they

just turned them off then forgot. Also some of those machines tend to
be second user hand me downs so they are probably unaware the updates
had been

turned off. You only tend to open the bonnet when things stop working!

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: "Ron Canazzi" <aa2vm@roadrunner.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 2:33 PM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA
2017.4, Windows 7 SP1 or later is absolutely required


I wonder if those who have such systems have pirate copies of
Windows and have turned off auto update.



On 12/7/2017 4:58 AM, Brian's Mail list account via Groups.Io wrote:
Could I ask how people could end up without sp1, as I seem to
recall from

friends that this update some years back now was pushed
automatically to

existing systems and its not just nvda which relies on it either.

Also now, how would a user get it and install it, is it relatively
simple

on the Microsoft site or would you suggest going the whole way and
going

to 10 before 31st Dec while a free update is there. I'm assuming
that the

old version of 7 will still allow the update.
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: "Joseph Lee"
<joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:18 PM
Subject: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


Dear NVDA community,



It was brought to developers' attention that some people were
having issues upgrading to NVDA 2017.4, and turns out some were
using Windows 7 RTM build.
Thus the following community directive:



In order to use NVDA 2017.4 or later, Windows 7 Service Pack 1 or
later

is
ABSOLUTELY required.



To find out which Windows release you've got:



1. Press Windows key to open Start menu.
2. Type "winver" without quotes and press Enter.
3. Check the build shown on About Windows dialog.



If the build number is 7601 or higher, you're all set. If it is
lower than
that:



* If using Windows 7 RTM (build number is 7600), please use NVDA
2017.3, upgrade to Windows 7 SP1 first, then update to NVDA 2017.4.
* If using versions other than 7 (build number is less than 7600),
then NVDA 2017.3 is the last supported version for you.



In the next few weeks, some add-on authors will announce minimum
supported versions of NVDA and Windows. For example, if you are
using StationPlaylist Studio add-on, starting from version 17.12
stable, Windows 7 SP1 or higher is absolutely required.



Thank you.

Cheers,

Joseph

--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"




--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages
www.al-islam.org










--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Ron Canazzi
 

Hi Adriani,


Your reply was unclear.  Which smart phone does NVDA work on?

On 12/8/2017 2:08 AM, Adriani Botez wrote:
NVDA does. That‘s why it supports arm64 now.


Von meinem iPhone gesendet

Am 08.12.2017 um 07:20 schrieb Ron Canazzi <aa2vm@roadrunner.com>:

Hi Group,


I'm wondering if screen readers as we know them will even be around at all in 5 years. Everyone in the sighted world seems to be going more and more toward very small tablets or even just smart phones. I know a fellow who says I'm hopelessly behind and that he hasn't owned a desktop or old style laptop for over 2 years. If this trend continues, what will become of desktops and how will screen reader companies adapt. As of now neither NVDA or VFO are producing screen readers that work with smart phones.



On 12/7/2017 4:48 PM, Arlene wrote:
Oh? It will be a shock. How screen readers will be different in 5 years!

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: December-07-17 1:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

With respect, This is a wrong perception. Updates nowadays are bringing more security and more functionality. It is more than important to keep everything uptodate. Support will stop after a while for what you are using and it will be harder and harder to adapt to new technologies. If you keep updating regularly, you will be used to learn new functions and it will be very easy to adapt to new things. In 5 years screen readers will be much much different than today. For those who keep staying behind, they will loose the path. Please be aware of that.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von zahra
Gesendet: Donnerstag, 7. Dezember 2017 16:59
An: nvda@nvda.groups.io
Betreff: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

i am completely against any update, no different if updates are for softwares or operating system!
i only use anything that i need!

On 12/7/17, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Not necessarily, many of the ones that could have been pirates have
allowed

windows 10 on them, so I think this ias a pink herring. Its more
likely they

just turned them off then forgot. Also some of those machines tend to
be second user hand me downs so they are probably unaware the updates
had been

turned off. You only tend to open the bonnet when things stop working!

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: "Ron Canazzi" <aa2vm@roadrunner.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 2:33 PM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


I wonder if those who have such systems have pirate copies of Windows
and have turned off auto update.



On 12/7/2017 4:58 AM, Brian's Mail list account via Groups.Io wrote:
Could I ask how people could end up without sp1, as I seem to recall
from

friends that this update some years back now was pushed
automatically to

existing systems and its not just nvda which relies on it either.

Also now, how would a user get it and install it, is it relatively
simple

on the Microsoft site or would you suggest going the whole way and
going

to 10 before 31st Dec while a free update is there. I'm assuming
that the

old version of 7 will still allow the update.
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: "Joseph Lee"
<joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:18 PM
Subject: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


Dear NVDA community,



It was brought to developers' attention that some people were
having issues upgrading to NVDA 2017.4, and turns out some were
using Windows 7 RTM build.
Thus the following community directive:



In order to use NVDA 2017.4 or later, Windows 7 Service Pack 1 or
later

is
ABSOLUTELY required.



To find out which Windows release you've got:



1. Press Windows key to open Start menu.
2. Type "winver" without quotes and press Enter.
3. Check the build shown on About Windows dialog.



If the build number is 7601 or higher, you're all set. If it is
lower than
that:



* If using Windows 7 RTM (build number is 7600), please use NVDA
2017.3, upgrade to Windows 7 SP1 first, then update to NVDA 2017.4.
* If using versions other than 7 (build number is less than 7600),
then NVDA 2017.3 is the last supported version for you.



In the next few weeks, some add-on authors will announce minimum
supported versions of NVDA and Windows. For example, if you are
using StationPlaylist Studio add-on, starting from version 17.12
stable, Windows 7 SP1 or higher is absolutely required.



Thank you.

Cheers,

Joseph

--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"




--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages www.al-islam.org









--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"



--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: Future of Access

Brian Moore
 

I actually thought this was on hold again!  It would be nice because the new rules refer to WCAG 2.0 for web accessibility stuff which is what we in the rest of the world are using.


Many countries have similar regulations but more and more, with a couple of exceptions, WCAG is the standard refered to by most countries.


anyway, this discussion is straying out of NVDA territory so it should likely end here.


sorry, when you work in it for a living, this stuff is actually exciting!


Brian.

Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123

On 12/08/2017 11:26 AM, tonea.ctr.morrow@faa.gov wrote:
I'm sure you already have heard, but just in case you haven't, the U.S. laws regarding software and website access are generally called 508 and were put in place about 2000. As of January 18th, a refresh of 508 goes into effect.

The official name for the refresh is 36 CFR 1194 and it has many parts. Sections 1 to 5 (they use roman numerals) are details on how the refresh was accomplished and the conclusions determined. Any Americans might want to read that so you can get an idea of how you can become involved in future updates of 508. The actual changes to the code are the appendices. Appendix D is the old code (currently in effect) that will be kept for anything "grandfathered". Appendix A contains the Chapters 1 and 2 of the new code 508. Appendix B contains the Chapters 1 and 2 of the new code 255 (hardware). And, Appendix C contains Chapters 3 to 7 of the code and will apply to both 508 and 255.

This link will take you to the U.S. Access Board website where the whole thing is posted for public viewing:
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/i-executive-summary

It defaults to section I of 36 CFR 1194, but you can use any of the links to jump to the portion of the code that you want.

Tonea Morrow


Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Adriani Botez
 

I don‘t say one should use mainly the newest things. But one should be open and try to understand how to use new things, maybe in parallel with old things to get used to it. Because there will be a time in the future when you will be forced to change. And one can adapt much easier if the basis is already known. In my view we should not be fully against it. We should stay informed.


Von meinem iPhone gesendet

Am 08.12.2017 um 11:27 schrieb Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io>:

I think as with many things there are many things to bear in mind. If somebody is older and its been hard to get to where they feel comfortable and realising that they do not probably have loads of years of life next, for them repeatable easy to use systems that do not change are higher up the scale of needs than it might be for somebody with their whole lives in front of them.


One cannot really make statements like you have to keep up as unless you like to be fiddling under the hood a lot then it can get very frustrating. I have used Windows 10, and intend to do so again, but unless there is a pressing need, I do not consider using my normal working machine as a windows 10 device.

Windows 7 is fine for some years, but at least \I know apart from the email most other stuff works the same in 10 or can be made to do so. I do have issues with ribbons but then I'm far from alone in this respect even in the sighted use.
To me that particular change was for its own sake and nothing is gained by it, just losses for those who cannot grasp the concept.
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: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 9:06 PM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required


With respect, This is a wrong perception. Updates nowadays are bringing more security and more functionality. It is more than important to keep everything uptodate. Support will stop after a while for what you are using and it will be harder and harder to adapt to new technologies. If you keep updating regularly, you will be used to learn new functions and it will be very easy to adapt to new things. In 5 years screen readers will be much much different than today. For those who keep staying behind, they will loose the path. Please be aware of that.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von zahra
Gesendet: Donnerstag, 7. Dezember 2017 16:59
An: nvda@nvda.groups.io
Betreff: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

i am completely against any update, no different if updates are for softwares or operating system!
i only use anything that i need!

On 12/7/17, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Not necessarily, many of the ones that could have been pirates have
allowed

windows 10 on them, so I think this ias a pink herring. Its more
likely they

just turned them off then forgot. Also some of those machines tend to
be second user hand me downs so they are probably unaware the updates
had been

turned off. You only tend to open the bonnet when things stop working!

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: "Ron Canazzi" <aa2vm@roadrunner.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 2:33 PM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


I wonder if those who have such systems have pirate copies of Windows
and have turned off auto update.



On 12/7/2017 4:58 AM, Brian's Mail list account via Groups.Io wrote:
Could I ask how people could end up without sp1, as I seem to recall
from

friends that this update some years back now was pushed
automatically to

existing systems and its not just nvda which relies on it either.

Also now, how would a user get it and install it, is it relatively
simple

on the Microsoft site or would you suggest going the whole way and
going

to 10 before 31st Dec while a free update is there. I'm assuming
that the

old version of 7 will still allow the update.
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: "Joseph Lee"
<joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:18 PM
Subject: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


Dear NVDA community,



It was brought to developers' attention that some people were
having issues upgrading to NVDA 2017.4, and turns out some were
using Windows 7 RTM build.
Thus the following community directive:



In order to use NVDA 2017.4 or later, Windows 7 Service Pack 1 or
later

is
ABSOLUTELY required.



To find out which Windows release you've got:



1. Press Windows key to open Start menu.
2. Type "winver" without quotes and press Enter.
3. Check the build shown on About Windows dialog.



If the build number is 7601 or higher, you're all set. If it is
lower than
that:



* If using Windows 7 RTM (build number is 7600), please use NVDA
2017.3, upgrade to Windows 7 SP1 first, then update to NVDA 2017.4.
* If using versions other than 7 (build number is less than 7600),
then NVDA 2017.3 is the last supported version for you.



In the next few weeks, some add-on authors will announce minimum
supported versions of NVDA and Windows. For example, if you are
using StationPlaylist Studio add-on, starting from version 17.12
stable, Windows 7 SP1 or higher is absolutely required.



Thank you.

Cheers,

Joseph



--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages www.al-islam.org










Future of Access

tonea.ctr.morrow@...
 

I'm sure you already have heard, but just in case you haven't, the U.S. laws regarding software and website access are generally called 508 and were put in place about 2000. As of January 18th, a refresh of 508 goes into effect.

The official name for the refresh is 36 CFR 1194 and it has many parts. Sections 1 to 5 (they use roman numerals) are details on how the refresh was accomplished and the conclusions determined. Any Americans might want to read that so you can get an idea of how you can become involved in future updates of 508. The actual changes to the code are the appendices. Appendix D is the old code (currently in effect) that will be kept for anything "grandfathered". Appendix A contains the Chapters 1 and 2 of the new code 508. Appendix B contains the Chapters 1 and 2 of the new code 255 (hardware). And, Appendix C contains Chapters 3 to 7 of the code and will apply to both 508 and 255.

This link will take you to the U.S. Access Board website where the whole thing is posted for public viewing:
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/i-executive-summary

It defaults to section I of 36 CFR 1194, but you can use any of the links to jump to the portion of the code that you want.

Tonea Morrow


Re: Context menu differs between right-mouse click and application key

Gene
 

I think the reason you see more options when you use the mouse right click is because, for some reason, using the context menu from the keyboard treats this as a link while using the mouse right click treats it as an image link. 
 
Gene
----- original Message -----

From: Gene
Sent: Friday, December 08, 2017 10:20 AM
Subject: Re: [nvda] Context menu differs between right-mouse click and application key

I just tried using shift context menu key and it doesn't bring up the mouse right click extra options. 
 
I don't see how this could be an NVDA issue since you are dealing with Windows commands and invocations.  You are right clicking from the keyboard, a Windows command and you are right clicking using the NVDA right click mouse command which is the same command as using a physical mouse.
 
Gene
----- Original Message -----
From: Gene
Sent: Friday, December 08, 2017 10:13 AM
Subject: Re: [nvda] Context menu differs between right-mouse click and application key

Try using shift context menu key and see what happens.  I don't know if it applies here, but shift context menu often presents more items than just the context menu key.  I may play with the page you gave, but I haven't yet.  This may be an example of nothing  being wrong but of a little known command being available.
 
Gene
----- Original Message -----
Sent: Friday, December 08, 2017 10:04 AM
Subject: [nvda] Context menu differs between right-mouse click and application key

I am trying to copy a graphic embedded in a link in a web page. The html link code might look something like the following:

 

<a href="www.site.com" target="_blank">Link Text<img src="assets/images/general/new-window.png" alt="opens in a new window" width="16" height="16"></a>

 

Notice that the image tag is embedded in the anchor tag. On the website, I navigate to the graphic (by using the “g” key or by navigating to the link and using cursor keys until NVDA speaks the work graphic). I then right-click on the image by pressing the Application key (or Shift+F10). In Firefox, I get a context menu similar to:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • Search Google for “link text”
  • Send link to device
  • Inspect element

 

However, if I route the mouse to the cursor and press the right mouse button (or press the NumPad / key) I get a different context menu, as follows:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • View image
  • Copy image
  • Copy image location
  • Save image as …
  • Email image
  • Set image as desktop background
  • View image info
  • Send link to device
  • Inspect element

 

Note that the right mouse click presents a context menu that allows working with the image (which is what I want) that is not present in the application key context menu. Similar results appear in other browsers.

 

The question is:

 

Is this an NVDA issue or a Microsoft / browser issue. Once I know, I will forward to the appropriate company.

 

You can try this for yourself: Go to a website like  www.seeingeye.org and press Control+Home to get to the top of the page. This will position you at their logo, which is also a link. Try the two different context menu invocation methods and notice the difference.

 

Thanks, Rick

 


Re: Context menu differs between right-mouse click and application key

Gene
 

I just tried using shift context menu key and it doesn't bring up the mouse right click extra options. 
 
I don't see how this could be an NVDA issue since you are dealing with Windows commands and invocations.  You are right clicking from the keyboard, a Windows command and you are right clicking using the NVDA right click mouse command which is the same command as using a physical mouse.
 
Gene

----- Original Message -----
From: Gene
Sent: Friday, December 08, 2017 10:13 AM
Subject: Re: [nvda] Context menu differs between right-mouse click and application key

Try using shift context menu key and see what happens.  I don't know if it applies here, but shift context menu often presents more items than just the context menu key.  I may play with the page you gave, but I haven't yet.  This may be an example of nothing  being wrong but of a little known command being available.
 
Gene
----- Original Message -----
Sent: Friday, December 08, 2017 10:04 AM
Subject: [nvda] Context menu differs between right-mouse click and application key

I am trying to copy a graphic embedded in a link in a web page. The html link code might look something like the following:

 

<a href="www.site.com" target="_blank">Link Text<img src="assets/images/general/new-window.png" alt="opens in a new window" width="16" height="16"></a>

 

Notice that the image tag is embedded in the anchor tag. On the website, I navigate to the graphic (by using the “g” key or by navigating to the link and using cursor keys until NVDA speaks the work graphic). I then right-click on the image by pressing the Application key (or Shift+F10). In Firefox, I get a context menu similar to:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • Search Google for “link text”
  • Send link to device
  • Inspect element

 

However, if I route the mouse to the cursor and press the right mouse button (or press the NumPad / key) I get a different context menu, as follows:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • View image
  • Copy image
  • Copy image location
  • Save image as …
  • Email image
  • Set image as desktop background
  • View image info
  • Send link to device
  • Inspect element

 

Note that the right mouse click presents a context menu that allows working with the image (which is what I want) that is not present in the application key context menu. Similar results appear in other browsers.

 

The question is:

 

Is this an NVDA issue or a Microsoft / browser issue. Once I know, I will forward to the appropriate company.

 

You can try this for yourself: Go to a website like  www.seeingeye.org and press Control+Home to get to the top of the page. This will position you at their logo, which is also a link. Try the two different context menu invocation methods and notice the difference.

 

Thanks, Rick

 


Re: Context menu differs between right-mouse click and application key

Gene
 

Try using shift context menu key and see what happens.  I don't know if it applies here, but shift context menu often presents more items than just the context menu key.  I may play with the page you gave, but I haven't yet.  This may be an example of nothing  being wrong but of a little known command being available.
 
Gene

----- Original Message -----
Sent: Friday, December 08, 2017 10:04 AM
Subject: [nvda] Context menu differs between right-mouse click and application key

I am trying to copy a graphic embedded in a link in a web page. The html link code might look something like the following:

 

<a href="www.site.com" target="_blank">Link Text<img src="assets/images/general/new-window.png" alt="opens in a new window" width="16" height="16"></a>

 

Notice that the image tag is embedded in the anchor tag. On the website, I navigate to the graphic (by using the “g” key or by navigating to the link and using cursor keys until NVDA speaks the work graphic). I then right-click on the image by pressing the Application key (or Shift+F10). In Firefox, I get a context menu similar to:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • Search Google for “link text”
  • Send link to device
  • Inspect element

 

However, if I route the mouse to the cursor and press the right mouse button (or press the NumPad / key) I get a different context menu, as follows:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • View image
  • Copy image
  • Copy image location
  • Save image as …
  • Email image
  • Set image as desktop background
  • View image info
  • Send link to device
  • Inspect element

 

Note that the right mouse click presents a context menu that allows working with the image (which is what I want) that is not present in the application key context menu. Similar results appear in other browsers.

 

The question is:

 

Is this an NVDA issue or a Microsoft / browser issue. Once I know, I will forward to the appropriate company.

 

You can try this for yourself: Go to a website like  www.seeingeye.org and press Control+Home to get to the top of the page. This will position you at their logo, which is also a link. Try the two different context menu invocation methods and notice the difference.

 

Thanks, Rick

 


Re: nvda's unresponsiveness

Lino Morales
 

Maybe its not an NVDA specific problem sir/mam. What type of processor and speed do you have? Just curious. How about the memory? NVDA 20177.4 is out now. try that and let us know how it runs using mutiple applications.

On 12/5/2017 2:07 PM, Marisane Moruthanyana wrote:
Evening guys

I am Marisane from SA.

I recently posted to you about nvda 2017.3 unresponsiveness, but none
of you came to my rescue.

Nvda goes unresponsive everytime I run more than one applications.

It also goes unresponsive when I am working on he internet.

I use nvda 2017.3 and win10.

My win10 is : Windows 10Ver1703 (64-bit) build 15063.726.

On other occasions, I use jaws16 but it does not go unresponsive when
I run multiple applications or am working on the internet.

What is wrong with nvda? Why so unresponsive in win10?

May I also understand about win10 fall creators? What is that?

Sorry for being without this knowledge about win10.

I am, of course, not technical.

Please help.

Kind regards
Marisane


Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Adriani Botez
 

You can start narator by a simple keystroke. I don‘t see why it should start automatically by default.
Do you really thing NVDA is not pulled? Well, there is no screen reader in this world which gets more feedback than nvda. And I am so glad that nvda is community driven... It would certainly make sense for microsoft to implement nvda‘s functionality instead of creating a new screen reader. But nvda should never never be owned by them. And in no case by vfo and co. who try to gain capital out of a project like this.


Von meinem iPhone gesendet

Am 08.12.2017 um 09:22 schrieb Shaun Everiss <sm.everiss@gmail.com>:

Maybe the comercial readers are doing a good job being this.

But who knows, we have yet to see ai being part of screen reader apps.

Interestingly tts companies are being brought out by others for their use.

Inoetics which I use a lot well aparently on my next reload the voices I have may not work, you can't buy the windows voices anymore, all that is gone.

On the other point, they are now owned by samsung and for a new company that aparently has been round for 10 years with a few offerings thats huge.

It would be like nvda being owned by microsoft, gwmicro, or something like that.

I hesitate to have it owned by vfo as every reader which is not jaws would probably just be pulled but even so.

Imagine if narator and nvda were 1 in windows, turn on your system and you would hear nvda sound on your system by default.




On 8/12/2017 10:51 a.m., Adriani Botez wrote:
There will be new functions, much more productivity, much more user experience and so on. Screen readers will get smarter as well. We have to stay on the path to it, not to battle against it.


Best
Adriani



-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von Arlene
Gesendet: Donnerstag, 7. Dezember 2017 22:48
An: nvda@nvda.groups.io
Betreff: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Oh? It will be a shock. How screen readers will be different in 5 years!

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Adriani Botez
Sent: December-07-17 1:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

With respect, This is a wrong perception. Updates nowadays are bringing more security and more functionality. It is more than important to keep everything uptodate. Support will stop after a while for what you are using and it will be harder and harder to adapt to new technologies. If you keep updating regularly, you will be used to learn new functions and it will be very easy to adapt to new things. In 5 years screen readers will be much much different than today. For those who keep staying behind, they will loose the path. Please be aware of that.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] Im Auftrag von zahra
Gesendet: Donnerstag, 7. Dezember 2017 16:59
An: nvda@nvda.groups.io
Betreff: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

i am completely against any update, no different if updates are for softwares or operating system!
i only use anything that i need!

On 12/7/17, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Not necessarily, many of the ones that could have been pirates have
allowed

windows 10 on them, so I think this ias a pink herring. Its more
likely they

just turned them off then forgot. Also some of those machines tend to
be second user hand me downs so they are probably unaware the updates
had been

turned off. You only tend to open the bonnet when things stop working!

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: "Ron Canazzi" <aa2vm@roadrunner.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 2:33 PM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


I wonder if those who have such systems have pirate copies of Windows
and have turned off auto update.



On 12/7/2017 4:58 AM, Brian's Mail list account via Groups.Io wrote:
Could I ask how people could end up without sp1, as I seem to recall
from

friends that this update some years back now was pushed
automatically to

existing systems and its not just nvda which relies on it either.

Also now, how would a user get it and install it, is it relatively
simple

on the Microsoft site or would you suggest going the whole way and
going

to 10 before 31st Dec while a free update is there. I'm assuming
that the

old version of 7 will still allow the update.
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: "Joseph Lee"
<joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:18 PM
Subject: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required


Dear NVDA community,



It was brought to developers' attention that some people were
having issues upgrading to NVDA 2017.4, and turns out some were
using Windows 7 RTM build.
Thus the following community directive:



In order to use NVDA 2017.4 or later, Windows 7 Service Pack 1 or
later

is
ABSOLUTELY required.



To find out which Windows release you've got:



1. Press Windows key to open Start menu.
2. Type "winver" without quotes and press Enter.
3. Check the build shown on About Windows dialog.



If the build number is 7601 or higher, you're all set. If it is
lower than
that:



* If using Windows 7 RTM (build number is 7600), please use NVDA
2017.3, upgrade to Windows 7 SP1 first, then update to NVDA 2017.4.
* If using versions other than 7 (build number is less than 7600),
then NVDA 2017.3 is the last supported version for you.



In the next few weeks, some add-on authors will announce minimum
supported versions of NVDA and Windows. For example, if you are
using StationPlaylist Studio add-on, starting from version 17.12
stable, Windows 7 SP1 or higher is absolutely required.



Thank you.

Cheers,

Joseph


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"





--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages www.al-islam.org













.



Context menu differs between right-mouse click and application key

Rick
 

I am trying to copy a graphic embedded in a link in a web page. The html link code might look something like the following:

 

<a href="www.site.com" target="_blank">Link Text<img src="assets/images/general/new-window.png" alt="opens in a new window" width="16" height="16"></a>

 

Notice that the image tag is embedded in the anchor tag. On the website, I navigate to the graphic (by using the “g” key or by navigating to the link and using cursor keys until NVDA speaks the work graphic). I then right-click on the image by pressing the Application key (or Shift+F10). In Firefox, I get a context menu similar to:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • Search Google for “link text”
  • Send link to device
  • Inspect element

 

However, if I route the mouse to the cursor and press the right mouse button (or press the NumPad / key) I get a different context menu, as follows:

  • Open link in new tab
  • Open link in new window
  • Open link in new private widow
  • Bookmark this link
  • Save link as …
  • Save link to pocket
  • Copy link location
  • View image
  • Copy image
  • Copy image location
  • Save image as …
  • Email image
  • Set image as desktop background
  • View image info
  • Send link to device
  • Inspect element

 

Note that the right mouse click presents a context menu that allows working with the image (which is what I want) that is not present in the application key context menu. Similar results appear in other browsers.

 

The question is:

 

Is this an NVDA issue or a Microsoft / browser issue. Once I know, I will forward to the appropriate company.

 

You can try this for yourself: Go to a website like  www.seeingeye.org and press Control+Home to get to the top of the page. This will position you at their logo, which is also a link. Try the two different context menu invocation methods and notice the difference.

 

Thanks, Rick

 


Re: Insert F10 not speaking in NVDA 2017.4

Rui Fontes
 

No. Here with last next all is spoken


Rui

Às 15:43 de 08/12/2017, Cearbhall O'Meadhra escreveu:

Hi,

 

I am using NVDA 2017.4 on Windows 10

When I mark the start of a block of text with Insert+F9 NVDA announces the action perfectly. However, when I press insert+F10 to identify the end of the block NVDA does not speak anything. Likewise, when I press Insert + F10 twice it does not report that the text is copied to the clipboard.

 

While the action is not spoken it does actually complete the copying action.

 

Has anyone else found this to be the case?

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 



Insert F10 not speaking in NVDA 2017.4

Cearbhall O'Meadhra
 

Hi,

 

I am using NVDA 2017.4 on Windows 10

When I mark the start of a block of text with Insert+F9 NVDA announces the action perfectly. However, when I press insert+F10 to identify the end of the block NVDA does not speak anything. Likewise, when I press Insert + F10 twice it does not report that the text is copied to the clipboard.

 

While the action is not spoken it does actually complete the copying action.

 

Has anyone else found this to be the case?

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 


The messages going to spam folders from this list

Brian's Mail list account <bglists@...>
 

All of them are in the thread with the subject line Chrome. Maybe I could suggest slightly changing this to something more descriptive to see if the spam filters some seem to have will ignore it. It does seem odd that such a common word should be used to filter spam. its nothing I can alter on the account I have other than by going to spam and sending them all back to inbox for redelivery and sorting by pop3 rules.
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.


Re: How to get old Espeak back for UK English users

Brian's Mail list account <bglists@...>
 

Not my place to say of colourise but half the trouble was and is that many of the programmers of nvda are Australian and Aussies have never spoken queens English like its supposed to be spoke like innit!
Hides behind sofa to avoid tomatoes.
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: "Robert Mendoza" <lowvisiontek@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, December 08, 2017 1:21 PM
Subject: Re: [nvda] How to get old Espeak back for UK English users


I do hope they would incorporate this rather in the next release which is liking specially for reading and writing. Smile.

Robert Mendoza

On 12/8/2017 8:42 PM, Brian's Mail list account via Groups.Io wrote:

Try this.

https://www.dropbox.com/s/vxc7j2ewi9zc9gn/speechPlayerInEspeak-0.4.nvda-addon?dl=1

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: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: <nvda@nvda.groups.io>
Sent: Friday, December 08, 2017 10:56 AM
Subject: [nvda] How to get old Espeak back for UK English users


Go to add ons site. Find speech palayer in Espeak the ready compiled version. install the add on
Switch to it.
go to voice and change the varient to what you like and set up speed etc. then go OK. You should now be able to use it. The dictionaries will either neeneed to be renamed and copied or rewritten, but it seems to work OK here for me.
No crashes either in hindi when used with snaps of the right vintage.
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.





Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

 

thanks so much for your ood prespective and positive attitude for the future.
i realy was worried for the future technology and did not know what
happen and i was realy afraid of losing my favorite one.
God bless you for your help!

On 12/8/17, tonea.ctr.morrow@faa.gov <tonea.ctr.morrow@faa.gov> wrote:
Just as there are people who love to tweak cars, there will always be people
who love to tweak computers. You can't do that with a proprietary system
like an apple cell phone. I do not see desktop computers going away.

Someone may invent a more portable braille system to use with small devices,
like cell phones. Or, the advancements in integrating technology into the
brain may dramatically improve. But, as a sighted person, I can tell you
that size is an aspect of fashion. Glasses were large in the 80's but thin
and narrow in 2000's. They are getting larger again. Cars have seen
"fashionable" sizes.

Desktop computers are still around only because they can crunch numbers much
better than smaller systems and they support much larger screens. 15-30 year
olds love video games and generally have the most disposable income. The
better the graphics, the happier they are. Quite a few games are being
developed with high graphics for desktop systems and then seeing enough
popularity that they get exported to gaming systems like Xbox and
Playstation. Unfortunately, this seems to (in my experience) cause the text
to be much too small. I have to move my chair closer to the TV to play those
games.

My daughter is looking to go to college to study art and animation. If I had
the money, I would buy her one of those really big touch-screen systems, the
ones that are more like an architect's desk than a computer. There was one
on display in the mall and she was great with it. As her mom, I want to
empower her to have her best future. But, reality is that I have to make a
car payment. My point is, there are many reasons that big computers won't go
away for sighted people. Which means your options won't go away either. Not
when the U.S. Access board requires more and more accessibility be built in.
Add in that other countries are doing the same, and I think your future
options look reasonably good.

Tonea Morrow

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron
Canazzi
Sent: Friday, December 08, 2017 12:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4,
Windows 7 SP1 or later is absolutely required

Hi Group,


I'm wondering if screen readers as we know them will even be around at all
in 5 years.  Everyone in the sighted world seems to be going more and more
toward very small tablets or even just smart phones.  I know a fellow who
says I'm hopelessly behind and that he hasn't owned a desktop or old style
laptop for over 2 years.  If this trend continues, what will become of
desktops and how will screen reader companies adapt.  As of now neither NVDA
or VFO are producing screen readers that work with smart phones.





--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages
www.al-islam.org


Re: Anyone with a Text File of All NVDA Desktop Commands?

Gene
 

The information is in a series of tables.  Move from topic to topic with h for move forward by heading or shift h to move back by heading. 
When you get to a topic you want to know about, type the letter t to move to the table which is below the heading.  Then use control alt down arrow to move down the command descriptions.  When you get to one you want to hear the desktop layout command for, use control alt right arrow to move to the desktop layout command.
Move back to the command descriptions with control alt left arrow. 
I said that control alt down arrow will move you down the command descriptions.  Control alt up arrow will move you back.
 
Gene
----- Original Message -----

From: Kenny
Sent: Friday, December 08, 2017 8:42 AM
Subject: Re: [nvda] Anyone with a Text File of All NVDA Desktop Commands?

I did locate that document. Guess I'm lazy and prefer hearing a list
of nothing but the Desktop hotkeys, without having to hear about
laptop and touch mixed in.

At 03:40 PM 12/7/2017, you wrote:
>Hi Kenny:
>
>If you go to the NVDA Menu, select Help and press the Enter key, then
>the second item is called "commands quick reference.  It is a series
>of tables, one below the other,  containing  name of the command, its
>desktop hotkey, its laptop hotkey and its touch gesture.
>
>Kevin Huber
>On 12/7/17, Kenny <kwashingtonbox@...> wrote:
> > It's me again.
> >
> > Well I'm up-and-running with NVDA.
> >
> > It's so hard to get use to the different lingo for the reading cursors
> > though.
> >
> > Still can't figure out what's NVDA's equivalent to JAWS' Virtual
> > cursor. Thinking it's the Review cursor? Can't figure out a way of
> > activating it though. With JAWS I only need tap the [Plus] key on the
> > numpad to activate the Virtual cursor while in a web page.
> >
> > Yes, that's the reading cursor I use the most (Always reading stuff
> > on-line via Google Chrome.
> >
> > Guess if I had a text file listing only the Desktop keys for all the
> > various reading/navigation functions of NVDA, I could pick this stuff
> > up a whole lot quicker.
> >
> > Thanks for any help.
> >
> >
> >
> >
> >
>
>




Re: Anyone with a Text File of All NVDA Desktop Commands?

Kenny <kwashingtonbox@...>
 

I did locate that document. Guess I'm lazy and prefer hearing a list of nothing but the Desktop hotkeys, without having to hear about laptop and touch mixed in.

At 03:40 PM 12/7/2017, you wrote:
Hi Kenny:

If you go to the NVDA Menu, select Help and press the Enter key, then
the second item is called "commands quick reference. It is a series
of tables, one below the other, containing name of the command, its
desktop hotkey, its laptop hotkey and its touch gesture.

Kevin Huber
On 12/7/17, Kenny <kwashingtonbox@gmail.com> wrote:
It's me again.

Well I'm up-and-running with NVDA.

It's so hard to get use to the different lingo for the reading cursors
though.

Still can't figure out what's NVDA's equivalent to JAWS' Virtual
cursor. Thinking it's the Review cursor? Can't figure out a way of
activating it though. With JAWS I only need tap the [Plus] key on the
numpad to activate the Virtual cursor while in a web page.

Yes, that's the reading cursor I use the most (Always reading stuff
on-line via Google Chrome.

Guess if I had a text file listing only the Desktop keys for all the
various reading/navigation functions of NVDA, I could pick this stuff
up a whole lot quicker.

Thanks for any help.





Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

tonea.ctr.morrow@...
 

Just as there are people who love to tweak cars, there will always be people who love to tweak computers. You can't do that with a proprietary system like an apple cell phone. I do not see desktop computers going away.

Someone may invent a more portable braille system to use with small devices, like cell phones. Or, the advancements in integrating technology into the brain may dramatically improve. But, as a sighted person, I can tell you that size is an aspect of fashion. Glasses were large in the 80's but thin and narrow in 2000's. They are getting larger again. Cars have seen "fashionable" sizes.

Desktop computers are still around only because they can crunch numbers much better than smaller systems and they support much larger screens. 15-30 year olds love video games and generally have the most disposable income. The better the graphics, the happier they are. Quite a few games are being developed with high graphics for desktop systems and then seeing enough popularity that they get exported to gaming systems like Xbox and Playstation. Unfortunately, this seems to (in my experience) cause the text to be much too small. I have to move my chair closer to the TV to play those games.

My daughter is looking to go to college to study art and animation. If I had the money, I would buy her one of those really big touch-screen systems, the ones that are more like an architect's desk than a computer. There was one on display in the mall and she was great with it. As her mom, I want to empower her to have her best future. But, reality is that I have to make a car payment. My point is, there are many reasons that big computers won't go away for sighted people. Which means your options won't go away either. Not when the U.S. Access board requires more and more accessibility be built in. Add in that other countries are doing the same, and I think your future options look reasonably good.

Tonea Morrow

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron Canazzi
Sent: Friday, December 08, 2017 12:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Hi Group,


I'm wondering if screen readers as we know them will even be around at all in 5 years.  Everyone in the sighted world seems to be going more and more toward very small tablets or even just smart phones.  I know a fellow who says I'm hopelessly behind and that he hasn't owned a desktop or old style laptop for over 2 years.  If this trend continues, what will become of desktops and how will screen reader companies adapt.  As of now neither NVDA or VFO are producing screen readers that work with smart phones.