Date   

Re: Using Android Studio with NVDA, Java Access Bridge issue

Jaffar Sidek <jaffar.sidek10@...>
 

Hi.  Since NVDA is a 32 bit application, you must make sure that the WindowsAccessbridge.dll is placed in your Windows/WowSys64 directory.

1. I presume you would have downloadded the Java sdk, both 32 and 64 bit versions.

2. go to your c:\program files (x86)\java\JDK\JRE\bin, copy the WindowsAccessbridge.dll file, navigate to your windows\WowSys64 directory and paste it in there.  if the "continue with administrator rights" prompt comes up, just press the space bar to continue.  IF you are on windows 64 bit, copy the above dll file from your c:\program files\java\JDK\JRE\Bin and copy the WindowsAccessBridge64.dll file into your windows\system32 directory.  This is useful when you use the 64 bit version of Android studio.  Restart your computer.  Now to test if your java accessibility is working,  go to your Java control panel.  If your java control panel is visible to NVDA, then you are ready to use Android Studio with NVDA.  God bless and cheers!

On 29/10/2018 5:04 PM, Shasa wrote:

Hello NVDA family,

I've been doing research on mobile platform for a long time. I preferred the cross platform. I am very interested in web programming. Especially Frantend.
That's why I chose React Native, and I have enough knowledge of JavaScript. I thought I could move on.

The problem is that there is a communication gap between Android Studio and NVDA. Java Access Bridge board. In the locations of the DLL files, JAB is enabled from the Control Panel.
Log Wiever's main output is:
"" "
INFO - __main__ (14:06:41.262):
Starting NVDA
INFO - core.main (14:06:41.667):
Config dir: C:\Users\Destroyer\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (14:06:41.667):
Loading config: C:\Users\Destroyer\AppData\Roaming\nvda\nvda.ini
INFO - core.main (14:06:42.214):
NVDA version 2018.3.2
INFO - core.main (14:06:42.214):
Using Windows version 10.0.17134 workstation
INFO - core.main (14:06:42.214):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (14:06:42.214):
Using comtypes version 1.1.3
DEBUGWARNING - touchHandler.touchSupported (14:06:42.476):
No touch devices found
INFO - external:synthDrivers.espeak_custom.SynthDriver.__init__ (14:06:43.084):
Using eSpeak version 1.48.03  04.Mar.14
INFO - synthDriverHandler.setSynth (14:06:43.453):
Loaded synthDriver espeak_custom
INFO - core.main (14:06:43.453):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (14:06:43.457):
Braille input initialized
INFO - braille.initialize (14:06:43.461):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (14:06:43.473):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:06:43.953):
UIAutomation: IUIAutomation5
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (14:06:44.477):
No locale gesture map for language en
DEBUGWARNING - touchHandler.touchSupported (14:06:44.528):
No touch devices found
"" "

Before configuring JAB, NVDA said, "Java Access Bridge not found."

My system information is as follows:
Windows: 10, 1803;
OS build: 17134.345;
Bit: 64;
About NVDA:
Version: 2018.3.2,
I don't have a setting and plugin to affect JAB.

I made the settings in Oracle's doc:
https://docs.oracle.com/javase/accessbridge/2.0.2/setup.htm,
https://docs.oracle.com/javase/9/access/enable_and_test.htm

This is also Google's document: https: //developer.android.com/studio/intro/accessibility


There is something strange, when I set up the "JDK", it is set up in "JAB". But it says here I have to set up the JAB manually. After the installation of JDK I checked the dll files, all of which are settled in their correct paths. I don't need a dll files copy.
Oracle said that the current versions installed, there is an older version.

Where do you think I'm making a mistake?

If you have friends who are developing with Android Studio, it would be great if they could help me by connecting with NVDA Remote. This problem exceeds my technical knowledge.

And I'm looking forward to the advice of those who have experience writing applications to mobile platforms before. Your contributions will advance me very fast.

Good days, nice uses and nice codings.



Re: In-Process for 26th October

 

i believe javascript is the source of different kind of problems!
i wish that javascript will be removed in the near future from internet.
from vulnerabilities until heavy usage of system resources and heating
my laptop and dynamic web pages and conflict and accessibility
problems for screen readers!
i really hate dynamic web pages and updating web browsers!
i wish static web pages with specific version of browsers without updating.
as you know, i never use firefox quantum and firefox 52 is sufficient
for me forever.

On 10/29/18, Gene <gsasner@gmail.com> wrote:
It appears to me that this needs further discussion and clarification. I
don't know if this is still the case, but in the past, quite some time ago,
I could stop most repetitions of clickable from being spoken by turning JAVA
scripts off. I could also, as I recall, stop most erroneous clickable
announcements by doing so. I'd have to experiment with this to see if my
memory is correct. And, as I said, I don't know if more current versions of
NVDA have this repetition and erroneous clickable announcements. But if
they do, I think that is likely what is generating most of the negative
messages received concerning clickable. I am not assuming anything, I
haven't looked at this for a long time, I have clickable off, and I don't
have a system that can run recent NVDA versions, but I'm raising the
question about whether NVDA is misreading something in JAVA script that is
causing these problems. I don't recall either erroneous clickable
announcements in JAWS nore multiple repetitions of clickable before the text
or control is read. This, I hope, will be further discussed by those using
the current NVDA.

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

From: Gene
Sent: Monday, October 29, 2018 2:11 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


You can turn it off. You can find the setting in documeht formatting. if
you need information about that dialog, we will provide it.

I don't have clickable on. Iff I am on a site and I don't see a way, such
as a link, a button, or another control that is read, to do something, then
I press enter on the text that logically is applicable, if any. While it
may be that rarely, I might want to turn clickable on to be sure about
whether there is or isn't a clickable control to do what I want, it is so
rare, that I don't remember if or when I did so. Logic and inference is
important in using the Internet well.

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

From: Jackie
Sent: Sunday, October 28, 2018 11:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@gmail.com> wrote:
I don't keep up with current versions of NVDA because I don't have
machines
they are compatible with. In the old days, NVDA used to say clickable
much
too often, repeating it many times before it read the text that was
supposed
to be clickable. Often, this text wasn't actually clickable. I don't
know
that because I tried clicking on everything announced as such, but the
context made it obvious. Has this problem been corrected? I would think
that if it has and only clickable items are announced, this wouldn't be a
problem. But perhaps one reason you get so much negative reaction is if
the
problem hasn't been corrected.

But why limit the inquiry to clickable items? Why are block quotes
announced by default and lists. I don't know how others find such
information being announced by default but to me, it's clutter. What
about
landmarks? I never use the landmark announcement but I don't know if
they
are useful. I also wonder whether, even if they are useful, they
discourage
people from learning how to navigate sites without them efficiently. My
concern is that if you become too dependent on special accessibility
accomodations, where a lot of sites don't have them, it may discourage
many
people from using sites that don't. I started using the Internet before
any
of these accomodations but when discussions such as this come up, I
wonder
about such questions.

There may be things I don't know such as that a lot of smaller sites use
landmarks and use them properly but I don't know if that's the case and I
suspect that a lot of sites don't use them at all.

Gene
----- Original Message -----
From: Mary Otten
Sent: Sunday, October 28, 2018 9:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


Remember, your request was only four people to reply with positive. How
is
it used for? I for instance don’t like it and find it worthless. But I
did
not respond, because you were looking for positive responses. So the fact
that you got 50-50 tells me that there are a lot more who don’t like it
then
those who do. Those of us who respected your request are screwed. Get rid
of
it! Or at least make it possible for those of us who have not found it
helpful to shut it off.

Mary



On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@nvaccess.org>
wrote:


Re clickable, the comments from everyone seem divided between "it can
be
really useful so I leave it on" and "it's really annoying and not useful
most of the time, get rid of it". I think it perhaps also depends on the
sites you visit and how readily you turn out of superfluous information
being read. A very good example of that people are much more likely to
complain about what doesn't work than praise what does - I think all the
feedback we had received on clickable previously had been about how
annoying
it was and that it read clickable when it really wasn't helpful.


Re predictive text Adriani, I must admit I hadn't used it myself until
someone asked last week and I tried it out. I think if you are
proficient
with a physical keyboard, it's probably not so useful for an average user
on
PC where you are most likely already typing on a physical keyboard. But
it
could definitely be a lifesaver for some users so it's good that it's
there.




On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:

Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to
supposedly
do
something. I often wonder at the logic of page design when nobody
knows

quite what they will get when they use a control.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I
have
to
do it or not. In fact, most times “clickable” does not perform an
action
at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS
Outlook
and Firefox. At work I am using profiles for SAP web based services
because
they have thousants of tables which in fact are only layout tables
but
NVDA
recognize them as normal tables. So I have to use profiles to disable
tables
because otherwise I get crazy when navigating through the complex
pages.



Windows 10 predictible text is a new function to me, but I find it
more

useful for tablests and smartfones. I don’t use it on normal
keyboards.
But
I guess it is a very good feature for people with motoric
disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about
the

recently released NVDA 2018.3.2, a shout out to GlitchedVision for
his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now
available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



<http://www.nvaccess.org/> www.nvaccess.org

Facebook: <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess















--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess





--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com





--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


windows 10 mail

Robert Doc Wright godfearer
 

has an addon been created for the mail app in windows 10? Is there any consideration of developing such an addon?


Re: OCR problem.

John Moore <johnm1642@...>
 

No. The one from the NVDA site called Windows Speech Recognition. And no I was not the one who messaged you. I was recommended to this list to ask about this.

On Oct 28, 2018, at 22:27, Quentin Christensen <quentin@...> wrote:

I don't have an answer, but someone asked about this recently, so now it looks like you've worked out what caused it so I'll be able to go back to them with that (unless it was you who emailed me?)  Which speech recognition add-on do you mean?  Dictation bridge?

Regards

Quentin.

On Mon, Oct 29, 2018 at 1:18 PM John Moore <johnm1642@...> wrote:
Hello everyone. I am new to the group although I have used NVDA off and on
for a number of years now. Is anyone else having issues with the Wondows
Speech Recognition ad-on conflicting with the Windows 10 OCR? If I have the
Speech Recognition ad-on enabled and I hit NVDA+r I hear "Recognizer not
found." However, if I disable it, it works. If anyone else is having this
issue, what is the best way to resolve it without having to uninstall the
ad-on? Thanks in advance for the help.





--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Fw: [espeak-ng] MBROLA now is open source software

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

----- Original Message -----
From: "Valdis Vitolins" <valdis.vitolins@odo.lv>
To: <espeak-ng@groups.io>
Sent: Sunday, October 28, 2018 8:45 PM
Subject: [espeak-ng] MBROLA now is open source software


https://github.com/numediart/MBROLA

Can somebody send this message to NVDA mailing list also?

Thanks!
Valdis


Using Android Studio with NVDA, Java Access Bridge issue

Shasa
 

Hello NVDA family,

I've been doing research on mobile platform for a long time. I preferred the cross platform. I am very interested in web programming. Especially Frantend.
That's why I chose React Native, and I have enough knowledge of JavaScript. I thought I could move on.

The problem is that there is a communication gap between Android Studio and NVDA. Java Access Bridge board. In the locations of the DLL files, JAB is enabled from the Control Panel.
Log Wiever's main output is:
"" "
INFO - __main__ (14:06:41.262):
Starting NVDA
INFO - core.main (14:06:41.667):
Config dir: C:\Users\Destroyer\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (14:06:41.667):
Loading config: C:\Users\Destroyer\AppData\Roaming\nvda\nvda.ini
INFO - core.main (14:06:42.214):
NVDA version 2018.3.2
INFO - core.main (14:06:42.214):
Using Windows version 10.0.17134 workstation
INFO - core.main (14:06:42.214):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (14:06:42.214):
Using comtypes version 1.1.3
DEBUGWARNING - touchHandler.touchSupported (14:06:42.476):
No touch devices found
INFO - external:synthDrivers.espeak_custom.SynthDriver.__init__ (14:06:43.084):
Using eSpeak version 1.48.03  04.Mar.14
INFO - synthDriverHandler.setSynth (14:06:43.453):
Loaded synthDriver espeak_custom
INFO - core.main (14:06:43.453):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (14:06:43.457):
Braille input initialized
INFO - braille.initialize (14:06:43.461):
Using liblouis version 3.6.0
INFO - braille.BrailleHandler.setDisplayByName (14:06:43.473):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (14:06:43.953):
UIAutomation: IUIAutomation5
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (14:06:44.477):
No locale gesture map for language en
DEBUGWARNING - touchHandler.touchSupported (14:06:44.528):
No touch devices found
"" "

Before configuring JAB, NVDA said, "Java Access Bridge not found."

My system information is as follows:
Windows: 10, 1803;
OS build: 17134.345;
Bit: 64;
About NVDA:
Version: 2018.3.2,
I don't have a setting and plugin to affect JAB.

I made the settings in Oracle's doc:
https://docs.oracle.com/javase/accessbridge/2.0.2/setup.htm,
https://docs.oracle.com/javase/9/access/enable_and_test.htm

This is also Google's document: https: //developer.android.com/studio/intro/accessibility


There is something strange, when I set up the "JDK", it is set up in "JAB". But it says here I have to set up the JAB manually. After the installation of JDK I checked the dll files, all of which are settled in their correct paths. I don't need a dll files copy.
Oracle said that the current versions installed, there is an older version.

Where do you think I'm making a mistake?

If you have friends who are developing with Android Studio, it would be great if they could help me by connecting with NVDA Remote. This problem exceeds my technical knowledge.

And I'm looking forward to the advice of those who have experience writing applications to mobile platforms before. Your contributions will advance me very fast.

Good days, nice uses and nice codings.


Re: In-Process for 26th October

Gene
 

It appears to me that this needs further discussion and clarification.  I don't know if this is still the case, but in the past, quite some time ago, I could stop most repetitions of clickable from being spoken by turning JAVA scripts off.  I could also, as I recall, stop most erroneous clickable announcements by doing so.  I'd have to experiment with this to see if my memory is correct.  And, as I said, I don't know if more current versions of NVDA have this repetition and erroneous clickable announcements.  But if they do, I think that is likely what is generating most of the negative messages received concerning clickable.  I am not assuming anything, I haven't looked at this for a long time, I have clickable off, and I don't have a system that can run recent NVDA versions, but I'm raising the question about whether NVDA is misreading something in JAVA script that is causing these problems.  I don't recall either erroneous clickable announcements in JAWS nore multiple repetitions of clickable before the text or control is read.  This, I hope, will be further discussed by those using the current NVDA.
 

Gene
----- Original Message -----
From: Gene
Sent: Monday, October 29, 2018 2:11 AM
Subject: Re: [nvda] In-Process for 26th October

You can turn it off.  You can find the setting in documeht formatting.  if you need information about that dialog, we will provide it. 
 
I don't have clickable on.  Iff I am on a site and I don't see a way, such as a link, a button, or another control that is read, to do something, then I press enter on the text that logically is applicable, if any.  While it may be that rarely, I might want to turn clickable on to be sure about whether there is or isn't a clickable control to do what I want, it is so rare, that I don't remember if or when I did so.  Logic and inference is important in using the Internet well.
 
Gene
----- Original Message -----
From: Jackie
Sent: Sunday, October 28, 2018 11:54 PM
Subject: Re: [nvda] In-Process for 26th October

Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@...> wrote:
> I don't keep up with current versions of NVDA because I don't have machines
> they are compatible with. In the old days, NVDA used to say clickable much
> too often, repeating it many times before it read the text that was supposed
> to be clickable.  Often, this text wasn't actually clickable.  I don't know
> that because I tried clicking on everything announced as such, but the
> context made it obvious.  Has this problem been corrected?  I would think
> that if it has and only clickable items are announced, this wouldn't be a
> problem.  But perhaps one reason you get so much negative reaction is if the
> problem hasn't been corrected.
>
> But why limit the inquiry to clickable items?  Why are block quotes
> announced by default and lists.  I don't know how others find such
> information being announced by default but to me, it's clutter.  What about
> landmarks?  I never use the landmark announcement but I don't know if they
> are useful.  I also wonder whether, even if they are useful, they discourage
> people from learning how to navigate sites without them efficiently.  My
> concern is that if you become too dependent on special accessibility
> accomodations, where a lot of sites don't have them, it may discourage many
> people from using sites that don't.  I started using the Internet before any
> of these accomodations but when discussions such as this come up, I wonder
> about such questions.
>
> There may be things I don't know such as that a lot of smaller sites use
> landmarks and use them properly but I don't know if that's the case and I
> suspect that a lot of sites don't use them at all.
>
> Gene
> ----- Original Message -----
> From: Mary Otten
> Sent: Sunday, October 28, 2018 9:31 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] In-Process for 26th October
>
>
> Remember, your request was only four people to reply with positive. How is
> it used for? I for instance don’t like it and find it worthless. But I did
> not respond, because you were looking for positive responses. So the fact
> that you got 50-50 tells me that there are a lot more who don’t like it then
> those who do. Those of us who respected your request are screwed. Get rid of
> it! Or at least make it possible for those of us who have not found it
> helpful to shut it off.
>
> Mary
>
>
>
> On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...>
> wrote:
>
>
>   Re clickable, the comments from everyone seem divided between "it can be
> really useful so I leave it on" and "it's really annoying and not useful
> most of the time, get rid of it".  I think it perhaps also depends on the
> sites you visit and how readily you turn out of superfluous information
> being read.  A very good example of that people are much more likely to
> complain about what doesn't work than praise what does - I think all the
> feedback we had received on clickable previously had been about how annoying
> it was and that it read clickable when it really wasn't helpful.
>
>
>   Re predictive text Adriani, I must admit I hadn't used it myself until
> someone asked last week and I tried it out.  I think if you are proficient
> with a physical keyboard, it's probably not so useful for an average user on
> PC where you are most likely already typing on a physical keyboard.  But it
> could definitely be a lifesaver for some users so it's good that it's
> there.
>
>
>
>
>   On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
> <bglists@...> wrote:
>
>     Its better than saying nothing. Sometimes in the shark these are also
>     ambiguous, one suspects because the info exposed on what they do is
>     incomplete and so one has to just indicate they are there to supposedly
> do
>     something. I often wonder at the logic of page design when nobody knows
>
>     quite what they will get when they use a control.
>      Brian
>
>     bglists@...
>     Sent via blueyonder.
>     Please address personal E-mail to:-
>     briang1@..., putting 'Brian Gaff'
>     in the display name field.
>     ----- Original Message -----
>     From: "Adriani Botez" <adriani.botez@...>
>     To: <nvda@nvda.groups.io>
>     Sent: Friday, October 26, 2018 10:57 PM
>     Subject: Re: [nvda] In-Process for 26th October
>
>
>     Hey Quentin,
>
>
>
>     I am replying to this e-mail after reading the last in-process.
>
>
>
>     For me at least, saying “clickable” does not help in deducting if I have
> to
>     do it or not. In fact, most times “clickable” does not perform an action
> at
>     all when pressing enter on it.
>
>
>
>     Regarding profiles, i am using profiles for MS Excel, MS Word, MS
> Outlook
>     and Firefox. At work I am using profiles for SAP web based services
> because
>     they have thousants of tables which in fact are only layout tables but
> NVDA
>     recognize them as normal tables. So I have to use profiles to disable
> tables
>     because otherwise I get crazy when navigating through the complex
> pages.
>
>
>
>     Windows 10 predictible text is a new function to me, but I find it more
>
>     useful for tablests and smartfones. I don’t use it on normal keyboards.
> But
>     I guess it is a very good feature for people with motoric disabilities.
>
>
>
>
>
>     Best
>
>     Adriani
>
>
>
>
>
>     Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
>     Christensen
>     Gesendet: Freitag, 26. Oktober 2018 08:20
>     An: nvda@nvda.groups.io
>     Betreff: [nvda] In-Process for 26th October
>
>
>
>     Hi everyone,
>
>
>
>     This week's In-Process is out. Today, we have more information about the
>
>     recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
>     innovative fundraiser, and not one but two quick tutorials - on
>     Configuration Profiles, & Predictive Text in Windows 10. Enjoy!
>
>
>
>     https://www.nvaccess.org/post/in-process-26th-october-2018/
>
>
>
>     Regards
>
>
>
>     Quentin.
>
>     --
>
>     Quentin Christensen
>     Training and Support Manager
>
>
>
>     Official NVDA Training modules and expert certification now available:
>     <http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/
>
>
>
>      <http://www.nvaccess.org/> www.nvaccess.org
>
>     Facebook:  <http://www.facebook.com/NVAccess>
>     http://www.facebook.com/NVAccess
>     Twitter: @NVAccess
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   --
>
>   Quentin Christensen
>   Training and Support Manager
>
>
>   Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
>
>   www.nvaccess.org
>
>   Facebook: http://www.facebook.com/NVAccess
>   Twitter: @NVAccess
>
>
>
>
>


--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com



Re: In-Process for 26th October

 

hi gene and quentin.
announcing clickable multiple times is the issue that i faced many
times on websites.
also, i am not comfortable with announcing any elements and many
months ago, i unchecked all the elements except reporting page number!
i believe it made for me using the web very easy, because i can read
anything that i want easily without hearing elements which makes
reading pages difficult and time consuming!
i really appreciate you all developers of nvda because of providing
changing reporting elements very easy for us.

On 10/29/18, Gene <gsasner@gmail.com> wrote:
You can turn it off. You can find the setting in documeht formatting. if
you need information about that dialog, we will provide it.

I don't have clickable on. Iff I am on a site and I don't see a way, such
as a link, a button, or another control that is read, to do something, then
I press enter on the text that logically is applicable, if any. While it
may be that rarely, I might want to turn clickable on to be sure about
whether there is or isn't a clickable control to do what I want, it is so
rare, that I don't remember if or when I did so. Logic and inference is
important in using the Internet well.

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

From: Jackie
Sent: Sunday, October 28, 2018 11:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@gmail.com> wrote:
I don't keep up with current versions of NVDA because I don't have
machines
they are compatible with. In the old days, NVDA used to say clickable
much
too often, repeating it many times before it read the text that was
supposed
to be clickable. Often, this text wasn't actually clickable. I don't
know
that because I tried clicking on everything announced as such, but the
context made it obvious. Has this problem been corrected? I would think
that if it has and only clickable items are announced, this wouldn't be a
problem. But perhaps one reason you get so much negative reaction is if
the
problem hasn't been corrected.

But why limit the inquiry to clickable items? Why are block quotes
announced by default and lists. I don't know how others find such
information being announced by default but to me, it's clutter. What
about
landmarks? I never use the landmark announcement but I don't know if
they
are useful. I also wonder whether, even if they are useful, they
discourage
people from learning how to navigate sites without them efficiently. My
concern is that if you become too dependent on special accessibility
accomodations, where a lot of sites don't have them, it may discourage
many
people from using sites that don't. I started using the Internet before
any
of these accomodations but when discussions such as this come up, I
wonder
about such questions.

There may be things I don't know such as that a lot of smaller sites use
landmarks and use them properly but I don't know if that's the case and I
suspect that a lot of sites don't use them at all.

Gene
----- Original Message -----
From: Mary Otten
Sent: Sunday, October 28, 2018 9:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


Remember, your request was only four people to reply with positive. How
is
it used for? I for instance don’t like it and find it worthless. But I
did
not respond, because you were looking for positive responses. So the fact
that you got 50-50 tells me that there are a lot more who don’t like it
then
those who do. Those of us who respected your request are screwed. Get rid
of
it! Or at least make it possible for those of us who have not found it
helpful to shut it off.

Mary



On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@nvaccess.org>
wrote:


Re clickable, the comments from everyone seem divided between "it can
be
really useful so I leave it on" and "it's really annoying and not useful
most of the time, get rid of it". I think it perhaps also depends on the
sites you visit and how readily you turn out of superfluous information
being read. A very good example of that people are much more likely to
complain about what doesn't work than praise what does - I think all the
feedback we had received on clickable previously had been about how
annoying
it was and that it read clickable when it really wasn't helpful.


Re predictive text Adriani, I must admit I hadn't used it myself until
someone asked last week and I tried it out. I think if you are
proficient
with a physical keyboard, it's probably not so useful for an average user
on
PC where you are most likely already typing on a physical keyboard. But
it
could definitely be a lifesaver for some users so it's good that it's
there.




On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:

Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to
supposedly
do
something. I often wonder at the logic of page design when nobody
knows

quite what they will get when they use a control.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I
have
to
do it or not. In fact, most times “clickable” does not perform an
action
at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS
Outlook
and Firefox. At work I am using profiles for SAP web based services
because
they have thousants of tables which in fact are only layout tables
but
NVDA
recognize them as normal tables. So I have to use profiles to disable
tables
because otherwise I get crazy when navigating through the complex
pages.



Windows 10 predictible text is a new function to me, but I find it
more

useful for tablests and smartfones. I don’t use it on normal
keyboards.
But
I guess it is a very good feature for people with motoric
disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about
the

recently released NVDA 2018.3.2, a shout out to GlitchedVision for
his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now
available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



<http://www.nvaccess.org/> www.nvaccess.org

Facebook: <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess















--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess





--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com





--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali


Re: In-Process for 26th October

Gene
 

You can turn it off.  You can find the setting in documeht formatting.  if you need information about that dialog, we will provide it. 
 
I don't have clickable on.  Iff I am on a site and I don't see a way, such as a link, a button, or another control that is read, to do something, then I press enter on the text that logically is applicable, if any.  While it may be that rarely, I might want to turn clickable on to be sure about whether there is or isn't a clickable control to do what I want, it is so rare, that I don't remember if or when I did so.  Logic and inference is important in using the Internet well.
 
Gene

----- Original Message -----
From: Jackie
Sent: Sunday, October 28, 2018 11:54 PM
Subject: Re: [nvda] In-Process for 26th October

Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@...> wrote:
> I don't keep up with current versions of NVDA because I don't have machines
> they are compatible with. In the old days, NVDA used to say clickable much
> too often, repeating it many times before it read the text that was supposed
> to be clickable.  Often, this text wasn't actually clickable.  I don't know
> that because I tried clicking on everything announced as such, but the
> context made it obvious.  Has this problem been corrected?  I would think
> that if it has and only clickable items are announced, this wouldn't be a
> problem.  But perhaps one reason you get so much negative reaction is if the
> problem hasn't been corrected.
>
> But why limit the inquiry to clickable items?  Why are block quotes
> announced by default and lists.  I don't know how others find such
> information being announced by default but to me, it's clutter.  What about
> landmarks?  I never use the landmark announcement but I don't know if they
> are useful.  I also wonder whether, even if they are useful, they discourage
> people from learning how to navigate sites without them efficiently.  My
> concern is that if you become too dependent on special accessibility
> accomodations, where a lot of sites don't have them, it may discourage many
> people from using sites that don't.  I started using the Internet before any
> of these accomodations but when discussions such as this come up, I wonder
> about such questions.
>
> There may be things I don't know such as that a lot of smaller sites use
> landmarks and use them properly but I don't know if that's the case and I
> suspect that a lot of sites don't use them at all.
>
> Gene
> ----- Original Message -----
> From: Mary Otten
> Sent: Sunday, October 28, 2018 9:31 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] In-Process for 26th October
>
>
> Remember, your request was only four people to reply with positive. How is
> it used for? I for instance don’t like it and find it worthless. But I did
> not respond, because you were looking for positive responses. So the fact
> that you got 50-50 tells me that there are a lot more who don’t like it then
> those who do. Those of us who respected your request are screwed. Get rid of
> it! Or at least make it possible for those of us who have not found it
> helpful to shut it off.
>
> Mary
>
>
>
> On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...>
> wrote:
>
>
>   Re clickable, the comments from everyone seem divided between "it can be
> really useful so I leave it on" and "it's really annoying and not useful
> most of the time, get rid of it".  I think it perhaps also depends on the
> sites you visit and how readily you turn out of superfluous information
> being read.  A very good example of that people are much more likely to
> complain about what doesn't work than praise what does - I think all the
> feedback we had received on clickable previously had been about how annoying
> it was and that it read clickable when it really wasn't helpful.
>
>
>   Re predictive text Adriani, I must admit I hadn't used it myself until
> someone asked last week and I tried it out.  I think if you are proficient
> with a physical keyboard, it's probably not so useful for an average user on
> PC where you are most likely already typing on a physical keyboard.  But it
> could definitely be a lifesaver for some users so it's good that it's
> there.
>
>
>
>
>   On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
> <bglists@...> wrote:
>
>     Its better than saying nothing. Sometimes in the shark these are also
>     ambiguous, one suspects because the info exposed on what they do is
>     incomplete and so one has to just indicate they are there to supposedly
> do
>     something. I often wonder at the logic of page design when nobody knows
>
>     quite what they will get when they use a control.
>      Brian
>
>     bglists@...
>     Sent via blueyonder.
>     Please address personal E-mail to:-
>     briang1@..., putting 'Brian Gaff'
>     in the display name field.
>     ----- Original Message -----
>     From: "Adriani Botez" <adriani.botez@...>
>     To: <nvda@nvda.groups.io>
>     Sent: Friday, October 26, 2018 10:57 PM
>     Subject: Re: [nvda] In-Process for 26th October
>
>
>     Hey Quentin,
>
>
>
>     I am replying to this e-mail after reading the last in-process.
>
>
>
>     For me at least, saying “clickable” does not help in deducting if I have
> to
>     do it or not. In fact, most times “clickable” does not perform an action
> at
>     all when pressing enter on it.
>
>
>
>     Regarding profiles, i am using profiles for MS Excel, MS Word, MS
> Outlook
>     and Firefox. At work I am using profiles for SAP web based services
> because
>     they have thousants of tables which in fact are only layout tables but
> NVDA
>     recognize them as normal tables. So I have to use profiles to disable
> tables
>     because otherwise I get crazy when navigating through the complex
> pages.
>
>
>
>     Windows 10 predictible text is a new function to me, but I find it more
>
>     useful for tablests and smartfones. I don’t use it on normal keyboards.
> But
>     I guess it is a very good feature for people with motoric disabilities.
>
>
>
>
>
>     Best
>
>     Adriani
>
>
>
>
>
>     Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
>     Christensen
>     Gesendet: Freitag, 26. Oktober 2018 08:20
>     An: nvda@nvda.groups.io
>     Betreff: [nvda] In-Process for 26th October
>
>
>
>     Hi everyone,
>
>
>
>     This week's In-Process is out. Today, we have more information about the
>
>     recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
>     innovative fundraiser, and not one but two quick tutorials - on
>     Configuration Profiles, & Predictive Text in Windows 10. Enjoy!
>
>
>
>     https://www.nvaccess.org/post/in-process-26th-october-2018/
>
>
>
>     Regards
>
>
>
>     Quentin.
>
>     --
>
>     Quentin Christensen
>     Training and Support Manager
>
>
>
>     Official NVDA Training modules and expert certification now available:
>     <http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/
>
>
>
>      <http://www.nvaccess.org/> www.nvaccess.org
>
>     Facebook:  <http://www.facebook.com/NVAccess>
>     http://www.facebook.com/NVAccess
>     Twitter: @NVAccess
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   --
>
>   Quentin Christensen
>   Training and Support Manager
>
>
>   Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
>
>   www.nvaccess.org
>
>   Facebook: http://www.facebook.com/NVAccess
>   Twitter: @NVAccess
>
>
>
>
>


--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com



SPL add-on 18.11.1/18.09.5-LTS #addonrelease

 

Hi all,

 

StationPlaylist Studio add-on 18.11.1 and 18.09.5-LTS are now available (the LTS is meant for Studio 5.1x users). These releases fixes issues with metadata streaming status announcement at startup and introduces support for Studio 5.31. As always, the new releases are just an update check away (standalone or via Add-on Updater).

 

Cheers,

Joseph


Re: bug with new Windows 10 App Essentials

Jacob Kruger
 

John, are you initiating a search from the address bar, or from the text box in the google landing page?


Instead of hitting alt + tab, what does it announce if you hit F6 once or twice, depending on which toolbars you have enabled?


I have just installed updates to win 10 app essentials, just fired up google chrome 69.0, typed a search in the address bar, hit enter, and, it had already focused on document contents, but, at times, when I enter other specific webpage addresses, I do use the F6 key to jump past bookmarks toolbar, and, landin the document itself.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"...resistance is futile...but, acceptance is versatile..."

On 2018-10-27 10:45 PM, Don H wrote:
Running latest NVDA on Win 10 1809.  Installed update to Windows 10 App Essentials and restarted NVDA as requested.  After seeing this bug I did a reboot of my computer that did not change the problem.
Using Google Chrome in the past I could start Google Chrome type in a search and hit enter.  I then could use the h key to move through the results.  Now the only way to get to the results is to hit alt tab to get to it.  I disabled the new Windows 10 App Essentials and it went back to what I had before.




Re: In-Process for 26th October

Quentin Christensen
 

Gene re your query about whether things which can't be clicked on being announced as clickable has been "corrected", you'll need to check with the web developers.  Technically, it's not an error on our part, as we are only sharing with the user the information the web developer has given us - we have no way of testing whether anything will actually happen or not if you try and activate any given element.  The problem, as you allude to, is that too often things are announced as clickable when they are not and when that announcement isn't useful.  So for now, the best we can do is work out whether users do use it or not as if people don't find it useful, we could uncheck that option by default.  Without opening a Pandora's box, yes we could ask about other document formatting options, or indeed, any options' default state, but clickable is probably the one we get the most negative responses about.





On Mon, Oct 29, 2018 at 3:54 PM Jackie <abletec@...> wrote:
Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@...> wrote:
> I don't keep up with current versions of NVDA because I don't have machines
> they are compatible with. In the old days, NVDA used to say clickable much
> too often, repeating it many times before it read the text that was supposed
> to be clickable.  Often, this text wasn't actually clickable.  I don't know
> that because I tried clicking on everything announced as such, but the
> context made it obvious.  Has this problem been corrected?  I would think
> that if it has and only clickable items are announced, this wouldn't be a
> problem.  But perhaps one reason you get so much negative reaction is if the
> problem hasn't been corrected.
>
> But why limit the inquiry to clickable items?  Why are block quotes
> announced by default and lists.  I don't know how others find such
> information being announced by default but to me, it's clutter.  What about
> landmarks?  I never use the landmark announcement but I don't know if they
> are useful.  I also wonder whether, even if they are useful, they discourage
> people from learning how to navigate sites without them efficiently.  My
> concern is that if you become too dependent on special accessibility
> accomodations, where a lot of sites don't have them, it may discourage many
> people from using sites that don't.  I started using the Internet before any
> of these accomodations but when discussions such as this come up, I wonder
> about such questions.
>
> There may be things I don't know such as that a lot of smaller sites use
> landmarks and use them properly but I don't know if that's the case and I
> suspect that a lot of sites don't use them at all.
>
> Gene
> ----- Original Message -----
> From: Mary Otten
> Sent: Sunday, October 28, 2018 9:31 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] In-Process for 26th October
>
>
> Remember, your request was only four people to reply with positive. How is
> it used for? I for instance don’t like it and find it worthless. But I did
> not respond, because you were looking for positive responses. So the fact
> that you got 50-50 tells me that there are a lot more who don’t like it then
> those who do. Those of us who respected your request are screwed. Get rid of
> it! Or at least make it possible for those of us who have not found it
> helpful to shut it off.
>
> Mary
>
>
>
> On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...>
> wrote:
>
>
>   Re clickable, the comments from everyone seem divided between "it can be
> really useful so I leave it on" and "it's really annoying and not useful
> most of the time, get rid of it".  I think it perhaps also depends on the
> sites you visit and how readily you turn out of superfluous information
> being read.  A very good example of that people are much more likely to
> complain about what doesn't work than praise what does - I think all the
> feedback we had received on clickable previously had been about how annoying
> it was and that it read clickable when it really wasn't helpful.
>
>
>   Re predictive text Adriani, I must admit I hadn't used it myself until
> someone asked last week and I tried it out.  I think if you are proficient
> with a physical keyboard, it's probably not so useful for an average user on
> PC where you are most likely already typing on a physical keyboard.  But it
> could definitely be a lifesaver for some users so it's good that it's
> there.
>
>
>
>
>   On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
> <bglists=blueyonder.co.uk@groups.io> wrote:
>
>     Its better than saying nothing. Sometimes in the shark these are also
>     ambiguous, one suspects because the info exposed on what they do is
>     incomplete and so one has to just indicate they are there to supposedly
> do
>     something. I often wonder at the logic of page design when nobody knows
>
>     quite what they will get when they use a control.
>      Brian
>
>     bglists@...
>     Sent via blueyonder.
>     Please address personal E-mail to:-
>     briang1@..., putting 'Brian Gaff'
>     in the display name field.
>     ----- Original Message -----
>     From: "Adriani Botez" <adriani.botez@...>
>     To: <nvda@nvda.groups.io>
>     Sent: Friday, October 26, 2018 10:57 PM
>     Subject: Re: [nvda] In-Process for 26th October
>
>
>     Hey Quentin,
>
>
>
>     I am replying to this e-mail after reading the last in-process.
>
>
>
>     For me at least, saying “clickable” does not help in deducting if I have
> to
>     do it or not. In fact, most times “clickable” does not perform an action
> at
>     all when pressing enter on it.
>
>
>
>     Regarding profiles, i am using profiles for MS Excel, MS Word, MS
> Outlook
>     and Firefox. At work I am using profiles for SAP web based services
> because
>     they have thousants of tables which in fact are only layout tables but
> NVDA
>     recognize them as normal tables. So I have to use profiles to disable
> tables
>     because otherwise I get crazy when navigating through the complex
> pages.
>
>
>
>     Windows 10 predictible text is a new function to me, but I find it more
>
>     useful for tablests and smartfones. I don’t use it on normal keyboards.
> But
>     I guess it is a very good feature for people with motoric disabilities.
>
>
>
>
>
>     Best
>
>     Adriani
>
>
>
>
>
>     Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
>     Christensen
>     Gesendet: Freitag, 26. Oktober 2018 08:20
>     An: nvda@nvda.groups.io
>     Betreff: [nvda] In-Process for 26th October
>
>
>
>     Hi everyone,
>
>
>
>     This week's In-Process is out. Today, we have more information about the
>
>     recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
>     innovative fundraiser, and not one but two quick tutorials - on
>     Configuration Profiles, & Predictive Text in Windows 10. Enjoy!
>
>
>
>     https://www.nvaccess.org/post/in-process-26th-october-2018/
>
>
>
>     Regards
>
>
>
>     Quentin.
>
>     --
>
>     Quentin Christensen
>     Training and Support Manager
>
>
>
>     Official NVDA Training modules and expert certification now available:
>     <http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/
>
>
>
>      <http://www.nvaccess.org/> www.nvaccess.org
>
>     Facebook:  <http://www.facebook.com/NVAccess>
>     http://www.facebook.com/NVAccess
>     Twitter: @NVAccess
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   --
>
>   Quentin Christensen
>   Training and Support Manager
>
>
>   Official NVDA Training modules and expert certification now available:
> http://www.nvaccess.org/shop/
>
>
>   www.nvaccess.org
>
>   Facebook: http://www.facebook.com/NVAccess
>   Twitter: @NVAccess
>
>
>
>
>


--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com





--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: In-Process for 26th October

Jackie
 

Well, I actually responded to the email that was provided for a
response in the request. I indicated that for me, there have been
countless times when an object was clickable, but because the web
developer in question didn't make it a link or a button, it would be
impossible to know that unless NVDA said "clickable". I did also
indicate that saying it multiple times was beyond annoying.
Additionally, I also suggested that there be a way to toggle the
feature on or off, per user preference. It's incorrect to assume that
because folks didn't respond positively on list that no one likes the
feature. I rather suspect instead that many of us simply used the
private email w/which we were provided.

If web authors would develop according to WCAG, there would be no need
for the feature. They don't; thus, there is. If you're fortunate
enough to visit only those websites that adhere to those standards,
then great. If on the other hand, you find yourself visiting a
multiplicity of sites, many of which do not conform to accessibility
guidelines, then it helps to know that an element can be interacted
with, because all indications are that it cannot.

They were looking for positive responses because they simply wanted to
see if anyone found it useful, & perhaps get an estimate of how many
that might be. They didn't want to just axe a feature because some
folks commented negatively on it. Those who find things useful usually
don't comment, so all they're bound to hear is the negative ones.

On 10/28/18, Gene <gsasner@gmail.com> wrote:
I don't keep up with current versions of NVDA because I don't have machines
they are compatible with. In the old days, NVDA used to say clickable much
too often, repeating it many times before it read the text that was supposed
to be clickable. Often, this text wasn't actually clickable. I don't know
that because I tried clicking on everything announced as such, but the
context made it obvious. Has this problem been corrected? I would think
that if it has and only clickable items are announced, this wouldn't be a
problem. But perhaps one reason you get so much negative reaction is if the
problem hasn't been corrected.

But why limit the inquiry to clickable items? Why are block quotes
announced by default and lists. I don't know how others find such
information being announced by default but to me, it's clutter. What about
landmarks? I never use the landmark announcement but I don't know if they
are useful. I also wonder whether, even if they are useful, they discourage
people from learning how to navigate sites without them efficiently. My
concern is that if you become too dependent on special accessibility
accomodations, where a lot of sites don't have them, it may discourage many
people from using sites that don't. I started using the Internet before any
of these accomodations but when discussions such as this come up, I wonder
about such questions.

There may be things I don't know such as that a lot of smaller sites use
landmarks and use them properly but I don't know if that's the case and I
suspect that a lot of sites don't use them at all.

Gene
----- Original Message -----
From: Mary Otten
Sent: Sunday, October 28, 2018 9:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] In-Process for 26th October


Remember, your request was only four people to reply with positive. How is
it used for? I for instance don’t like it and find it worthless. But I did
not respond, because you were looking for positive responses. So the fact
that you got 50-50 tells me that there are a lot more who don’t like it then
those who do. Those of us who respected your request are screwed. Get rid of
it! Or at least make it possible for those of us who have not found it
helpful to shut it off.

Mary



On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@nvaccess.org>
wrote:


Re clickable, the comments from everyone seem divided between "it can be
really useful so I leave it on" and "it's really annoying and not useful
most of the time, get rid of it". I think it perhaps also depends on the
sites you visit and how readily you turn out of superfluous information
being read. A very good example of that people are much more likely to
complain about what doesn't work than praise what does - I think all the
feedback we had received on clickable previously had been about how annoying
it was and that it read clickable when it really wasn't helpful.


Re predictive text Adriani, I must admit I hadn't used it myself until
someone asked last week and I tried it out. I think if you are proficient
with a physical keyboard, it's probably not so useful for an average user on
PC where you are most likely already typing on a physical keyboard. But it
could definitely be a lifesaver for some users so it's good that it's
there.




On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:

Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to supposedly
do
something. I often wonder at the logic of page design when nobody knows

quite what they will get when they use a control.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I have
to
do it or not. In fact, most times “clickable” does not perform an action
at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS
Outlook
and Firefox. At work I am using profiles for SAP web based services
because
they have thousants of tables which in fact are only layout tables but
NVDA
recognize them as normal tables. So I have to use profiles to disable
tables
because otherwise I get crazy when navigating through the complex
pages.



Windows 10 predictible text is a new function to me, but I find it more

useful for tablests and smartfones. I don’t use it on normal keyboards.
But
I guess it is a very good feature for people with motoric disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about the

recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



<http://www.nvaccess.org/> www.nvaccess.org

Facebook: <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess















--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess




--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com


Re: In-Process for 26th October

Gene
 

I don't keep up with current versions of NVDA because I don't have machines they are compatible with. In the old days, NVDA used to say clickable much too often, repeating it many times before it read the text that was supposed to be clickable.  Often, this text wasn't actually clickable.  I don't know that because I tried clicking on everything announced as such, but the context made it obvious.  Has this problem been corrected?  I would think that if it has and only clickable items are announced, this wouldn't be a problem.  But perhaps one reason you get so much negative reaction is if the problem hasn't been corrected. 
 
But why limit the inquiry to clickable items?  Why are block quotes announced by default and lists.  I don't know how others find such information being announced by default but to me, it's clutter.  What about landmarks?  I never use the landmark announcement but I don't know if they are useful.  I also wonder whether, even if they are useful, they discourage people from learning how to navigate sites without them efficiently.  My concern is that if you become too dependent on special accessibility accomodations, where a lot of sites don't have them, it may discourage many people from using sites that don't.  I started using the Internet before any of these accomodations but when discussions such as this come up, I wonder about such questions. 
 
There may be things I don't know such as that a lot of smaller sites use landmarks and use them properly but I don't know if that's the case and I suspect that a lot of sites don't use them at all.
 
Gene

----- Original Message -----
From: Mary Otten
Sent: Sunday, October 28, 2018 9:31 PM
Subject: Re: [nvda] In-Process for 26th October

Remember, your request was only four people to reply with positive. How is it used for? I for instance don’t like it and find it worthless. But I did not respond, because you were looking for positive responses. So the fact that you got 50-50 tells me that there are a lot more who don’t like it then those who do. Those of us who respected your request are screwed. Get rid of it! Or at least make it possible for those of us who have not found it helpful to shut it off.

Mary


On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...> wrote:

Re clickable, the comments from everyone seem divided between "it can be really useful so I leave it on" and "it's really annoying and not useful most of the time, get rid of it".  I think it perhaps also depends on the sites you visit and how readily you turn out of superfluous information being read.  A very good example of that people are much more likely to complain about what doesn't work than praise what does - I think all the feedback we had received on clickable previously had been about how annoying it was and that it read clickable when it really wasn't helpful.

Re predictive text Adriani, I must admit I hadn't used it myself until someone asked last week and I tried it out.  I think if you are proficient with a physical keyboard, it's probably not so useful for an average user on PC where you are most likely already typing on a physical keyboard.  But it could definitely be a lifesaver for some users so it's good that it's there.


On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to supposedly do
something. I often wonder at the logic of page design when nobody knows
quite what they will get when they use a control.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Adriani Botez" <adriani.botez@...>
To: <nvda@nvda.groups.io>
Sent: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I have to
do it or not. In fact, most times “clickable” does not perform an action at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS Outlook
and Firefox. At work I am using profiles for SAP web based services because
they have thousants of tables which in fact are only layout tables but NVDA
recognize them as normal tables. So I have to use profiles to disable tables
because otherwise I get crazy when navigating through the complex pages.



Windows 10 predictible text is a new function to me, but I find it more
useful for tablests and smartfones. I don’t use it on normal keyboards. But
I guess it is a very good feature for people with motoric disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about the
recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



 <http://www.nvaccess.org/> www.nvaccess.org

Facebook:  <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess












--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: In-Process for 26th October

Quentin Christensen
 

Very true Mary!

Ok, based on the feedback it does seem that there are some users who prefer it is perhaps what I should have said, although as you said, a lot of people like yourself who don't like it didn't respond (and indeed, that is the feedback we had received plenty of beforehand).

On Mon, Oct 29, 2018 at 1:31 PM Mary Otten <maryotten@...> wrote:
Remember, your request was only four people to reply with positive. How is it used for? I for instance don’t like it and find it worthless. But I did not respond, because you were looking for positive responses. So the fact that you got 50-50 tells me that there are a lot more who don’t like it then those who do. Those of us who respected your request are screwed. Get rid of it! Or at least make it possible for those of us who have not found it helpful to shut it off.

Mary


On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...> wrote:

Re clickable, the comments from everyone seem divided between "it can be really useful so I leave it on" and "it's really annoying and not useful most of the time, get rid of it".  I think it perhaps also depends on the sites you visit and how readily you turn out of superfluous information being read.  A very good example of that people are much more likely to complain about what doesn't work than praise what does - I think all the feedback we had received on clickable previously had been about how annoying it was and that it read clickable when it really wasn't helpful.

Re predictive text Adriani, I must admit I hadn't used it myself until someone asked last week and I tried it out.  I think if you are proficient with a physical keyboard, it's probably not so useful for an average user on PC where you are most likely already typing on a physical keyboard.  But it could definitely be a lifesaver for some users so it's good that it's there.


On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to supposedly do
something. I often wonder at the logic of page design when nobody knows
quite what they will get when they use a control.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Adriani Botez" <adriani.botez@...>
To: <nvda@nvda.groups.io>
Sent: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I have to
do it or not. In fact, most times “clickable” does not perform an action at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS Outlook
and Firefox. At work I am using profiles for SAP web based services because
they have thousants of tables which in fact are only layout tables but NVDA
recognize them as normal tables. So I have to use profiles to disable tables
because otherwise I get crazy when navigating through the complex pages.



Windows 10 predictible text is a new function to me, but I find it more
useful for tablests and smartfones. I don’t use it on normal keyboards. But
I guess it is a very good feature for people with motoric disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about the
recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



 <http://www.nvaccess.org/> www.nvaccess.org

Facebook:  <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess












--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: In-Process for 26th October

Mary Otten
 

Remember, your request was only four people to reply with positive. How is it used for? I for instance don’t like it and find it worthless. But I did not respond, because you were looking for positive responses. So the fact that you got 50-50 tells me that there are a lot more who don’t like it then those who do. Those of us who respected your request are screwed. Get rid of it! Or at least make it possible for those of us who have not found it helpful to shut it off.

Mary


On Oct 28, 2018, at 6:54 PM, Quentin Christensen <quentin@...> wrote:

Re clickable, the comments from everyone seem divided between "it can be really useful so I leave it on" and "it's really annoying and not useful most of the time, get rid of it".  I think it perhaps also depends on the sites you visit and how readily you turn out of superfluous information being read.  A very good example of that people are much more likely to complain about what doesn't work than praise what does - I think all the feedback we had received on clickable previously had been about how annoying it was and that it read clickable when it really wasn't helpful.

Re predictive text Adriani, I must admit I hadn't used it myself until someone asked last week and I tried it out.  I think if you are proficient with a physical keyboard, it's probably not so useful for an average user on PC where you are most likely already typing on a physical keyboard.  But it could definitely be a lifesaver for some users so it's good that it's there.


On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to supposedly do
something. I often wonder at the logic of page design when nobody knows
quite what they will get when they use a control.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Adriani Botez" <adriani.botez@...>
To: <nvda@nvda.groups.io>
Sent: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I have to
do it or not. In fact, most times “clickable” does not perform an action at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS Outlook
and Firefox. At work I am using profiles for SAP web based services because
they have thousants of tables which in fact are only layout tables but NVDA
recognize them as normal tables. So I have to use profiles to disable tables
because otherwise I get crazy when navigating through the complex pages.



Windows 10 predictible text is a new function to me, but I find it more
useful for tablests and smartfones. I don’t use it on normal keyboards. But
I guess it is a very good feature for people with motoric disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about the
recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



 <http://www.nvaccess.org/> www.nvaccess.org

Facebook:  <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess












--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: OCR problem.

Quentin Christensen
 

I don't have an answer, but someone asked about this recently, so now it looks like you've worked out what caused it so I'll be able to go back to them with that (unless it was you who emailed me?)  Which speech recognition add-on do you mean?  Dictation bridge?

Regards

Quentin.

On Mon, Oct 29, 2018 at 1:18 PM John Moore <johnm1642@...> wrote:
Hello everyone. I am new to the group although I have used NVDA off and on
for a number of years now. Is anyone else having issues with the Wondows
Speech Recognition ad-on conflicting with the Windows 10 OCR? If I have the
Speech Recognition ad-on enabled and I hit NVDA+r I hear "Recognizer not
found." However, if I disable it, it works. If anyone else is having this
issue, what is the best way to resolve it without having to uninstall the
ad-on? Thanks in advance for the help.





--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


OCR problem.

John Moore <johnm1642@...>
 

Hello everyone. I am new to the group although I have used NVDA off and on
for a number of years now. Is anyone else having issues with the Wondows
Speech Recognition ad-on conflicting with the Windows 10 OCR? If I have the
Speech Recognition ad-on enabled and I hit NVDA+r I hear "Recognizer not
found." However, if I disable it, it works. If anyone else is having this
issue, what is the best way to resolve it without having to uninstall the
ad-on? Thanks in advance for the help.


Re: In-Process for 26th October

Quentin Christensen
 

Re clickable, the comments from everyone seem divided between "it can be really useful so I leave it on" and "it's really annoying and not useful most of the time, get rid of it".  I think it perhaps also depends on the sites you visit and how readily you turn out of superfluous information being read.  A very good example of that people are much more likely to complain about what doesn't work than praise what does - I think all the feedback we had received on clickable previously had been about how annoying it was and that it read clickable when it really wasn't helpful.

Re predictive text Adriani, I must admit I hadn't used it myself until someone asked last week and I tried it out.  I think if you are proficient with a physical keyboard, it's probably not so useful for an average user on PC where you are most likely already typing on a physical keyboard.  But it could definitely be a lifesaver for some users so it's good that it's there.


On Sat, Oct 27, 2018 at 5:50 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
Its better than saying nothing. Sometimes in the shark these are also
ambiguous, one suspects because the info exposed on what they do is
incomplete and so one has to just indicate they are there to supposedly do
something. I often wonder at the logic of page design when nobody knows
quite what they will get when they use a control.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Adriani Botez" <adriani.botez@...>
To: <nvda@nvda.groups.io>
Sent: Friday, October 26, 2018 10:57 PM
Subject: Re: [nvda] In-Process for 26th October


Hey Quentin,



I am replying to this e-mail after reading the last in-process.



For me at least, saying “clickable” does not help in deducting if I have to
do it or not. In fact, most times “clickable” does not perform an action at
all when pressing enter on it.



Regarding profiles, i am using profiles for MS Excel, MS Word, MS Outlook
and Firefox. At work I am using profiles for SAP web based services because
they have thousants of tables which in fact are only layout tables but NVDA
recognize them as normal tables. So I have to use profiles to disable tables
because otherwise I get crazy when navigating through the complex pages.



Windows 10 predictible text is a new function to me, but I find it more
useful for tablests and smartfones. I don’t use it on normal keyboards. But
I guess it is a very good feature for people with motoric disabilities.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Quentin
Christensen
Gesendet: Freitag, 26. Oktober 2018 08:20
An: nvda@nvda.groups.io
Betreff: [nvda] In-Process for 26th October



Hi everyone,



This week's In-Process is out. Today, we have more information about the
recently released NVDA 2018.3.2, a shout out to GlitchedVision for his
innovative fundraiser, and not one but two quick tutorials - on
Configuration Profiles, & Predictive Text in Windows 10. Enjoy!



https://www.nvaccess.org/post/in-process-26th-october-2018/



Regards



Quentin.

--

Quentin Christensen
Training and Support Manager



Official NVDA Training modules and expert certification now available:
<http://www.nvaccess.org/shop/> http://www.nvaccess.org/shop/



 <http://www.nvaccess.org/> www.nvaccess.org

Facebook:  <http://www.facebook.com/NVAccess>
http://www.facebook.com/NVAccess
Twitter: @NVAccess












--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Thinking of buying a computer

Kerryn Gunness <k_gunness@...>
 


if you ask me, i would say get a lenovo, i use one
its good
aser is also good
i would not recommend asus, because i no someone had one, it crashed after about 2 years
 
kerryn

----- Original Message -----
Sent: Sunday, October 28, 2018 7:48 PM
Subject: Re: [nvda] Thinking of buying a computer

Hi.


Asus might be good, I haven't ever had a mid to high end Asus to compare by.


I have a Lenovo Yoga 2 pro and a Lenovo Thinkpad T480s and both are decent keyboard wise. Newer Lenovo don't have context key, but you can remap another key to it. I don't like dell very much because their sound card drivers use lots of processor and it's just generally grossly inefficient. I don't like HP because I've broken two of them and I've owned two of them. I don't like Tosheba because their batteries are pretty lousy longterm life-wise, I've had a couple of different acers both of which had different issues, butr at least their keyboards were nice, well the one the space bar kept getting stuck and it was brand new. So, they all suc if you ask me, you just have to get lucky and get a good one what ever you go for.


Cheers:
Aaron Spears, A.K.A. valiant8086. General Partner - Valiant Galaxy Associates "We make Very Good Audiogames for the blind community - http://valiantGalaxy.com"

<Sent with Thunderbird 52.1.0 portable>
On 10/28/2018 5:44 PM, Arnþór Helgason wrote:

I am considering to update my Eiser labtop.

Some people recommend the Lenovo computers, but others have pointed out some incompatibility with the keyboard.

I usually use an USB-keyboard and very seldom the built-in board on the computer.


Any comments reganding Lenovo and NVDA?


Best regards,

Arnthor

---



Arnþór Helgason,

Vináttusendiherra/Friendship Ambassador

Tjarnarbóli 14,

170 Seltjarnarnesi.

Farsími | Mobile: +354 8973766

arnthor.helgason@...

arnthor.helgason@...

http://arnthorhelgason.blog.is

http://hljod.blog.is