Date   

Re: Win 10 ver 1809

 

Hi,
Based on the log I got, it appears UIA events are not seen by NVDA on some systems. I can't reproduce this problem on any of my machines running Version 1809 and Insider Preview builds.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rui Fontes
Sent: Tuesday, November 20, 2018 4:18 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Win 10 ver 1809

Yes, it is only occurring in Windows 10 ver 1809.
Narrator does not read this information...

Rui Fontes


Às 23:50 de 20/11/2018, Don H escreveu:
Wonder how many on the list installed Win 10 version 1809 when it
first came out and before it was pulled back. It seems that the
strange verbage I get when openning up the settings app relates to
version 1809 and does not happen with version 1803.





Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

 

Hi,
For now, the new setting is mostly used to handle emojis.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Tuesday, November 20, 2018 1:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

Ah ha! Hang on, let me check that, because I am using OneCore but I do have symbol level set to none. Let's give it a shot here. Yep! That worked just fine, thanks! Now another question, it says it can do Unicode characters more generally, how do I get to all of those?


On 11/20/2018 12:39, Joseph Lee wrote:
Hi,
Eh? That's weird. Have you tried with OneCore synthesizer too? If the new CLDR setting is checked from voice settings yet NVDA isn't reading emojis, chances are that you may have symbol level set to none or some.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John
Isige
Sent: Tuesday, November 20, 2018 10:23 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, just restarted with all addons disabled. Here we go with trying to enter an emoji. I could enter one, but it read the same way, 1 of 50, so I have no idea what it was. So I deleted it.


On 11/20/2018 0:26, Joseph Lee wrote:
Hi,
What you're describing is the behavior of emoji panel in Version 1803. Can you try with all add-ons turned off (from exit dialog, select restart with add-ons disabled)?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John
Isige
Sent: Monday, November 19, 2018 10:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.


On 11/19/2018 22:47, hurrikennyandopo ... wrote:
Hi


I just noticed now when you are on the recent one if you shift/tab
now it gives you the categories where now you right or left arrow to
them then press the enter key on the one you want then shift tab or
tab to get to the list of them. it seems to be speaking mine out correctly.


it seems like a slight modification to the tutorial.


Gene nz


On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me,
with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on.
This happens even with the one-core voices, which used to read more
emojis than any other synthesizer. This happens whether the copy is
installed or portable. Windows 10 64-bit, latest upates, not 1809
though. Here's the log from when I try to get to an emoji to put
into this message in Thunderbird.


INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main
(21:37:01.523):
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
(21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO -
synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO -
brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class
'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class
'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule:
<'windowsinternal_composableshell_experiences_textinput_inputapp'
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at
79f59e0> UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent
link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA
className: GridViewItem UIA patterns available:
LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern,
ScrollItemPattern, SelectionItemPattern



--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net Regardless of where
you are in New Zealand if you are near one of the APNK sites you can
use a copy of the NVDA screen reader on one of their computers. To
find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified
expert near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains
the official list of NVDA certified individuals from around the
world, who have sat and successfully passed the NVDA expert exam.







Re: Win 10 ver 1809

Rui Fontes
 

Yes, it is only occurring in Windows 10 ver 1809.
Narrator does not read this information...

Rui Fontes


Às 23:50 de 20/11/2018, Don H escreveu:

Wonder how many on the list installed Win 10 version 1809 when it first came out and before it was pulled back.  It seems that the strange verbage I get when openning up the settings app relates to version 1809 and does not happen with version 1803.


Re: Win 10 ver 1809

Ian Blackburn
 

I did and it worked well
Window is narrator way better
Regards Ian

On 21 Nov 2018, at 7:50 am, Don H <lmddh50@...> wrote:

Wonder how many on the list installed Win 10 version 1809 when it first came out and before it was pulled back. It seems that the strange verbage I get when openning up the settings app relates to version 1809 and does not happen with version 1803.


Win 10 ver 1809

Don H
 

Wonder how many on the list installed Win 10 version 1809 when it first came out and before it was pulled back. It seems that the strange verbage I get when openning up the settings app relates to version 1809 and does not happen with version 1803.


Re: autocorrect in Word 365

Giles Turnbull
 

thanks Quentin, deleting the existing auto corrects worked a treat :)


Re: Why do some links not do what they say while others do?

Jonathan COHN
 

Travis is probably correct, but in all cases this is a matter of the developer not verifying focus control is working in your browser. Of course since you are using not one of the big four browsers, you will probably find that the developers of the site will not have tested with water fox. In cases where additional data is added to the HTML code the web developer needs to either  focus on the new data or use a live region both of which NVDA will support. 

One final note, I know your browser is essentially an older version of Firefox, but as likely as not, web developers will not have heard of this browser. 


Re: NVDA 2018.4-Beta 1 doesn't read emojis for me.

John Isige
 

Ah ha! Hang on, let me check that, because I am using OneCore but I do have symbol level set to none. Let's give it a shot here. Yep! That worked just fine, thanks! Now another question, it says it can do Unicode characters more generally, how do I get to all of those?

On 11/20/2018 12:39, Joseph Lee wrote:
Hi,
Eh? That's weird. Have you tried with OneCore synthesizer too? If the new CLDR setting is checked from voice settings yet NVDA isn't reading emojis, chances are that you may have symbol level set to none or some.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John Isige
Sent: Tuesday, November 20, 2018 10:23 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, just restarted with all addons disabled. Here we go with trying to enter an emoji. I could enter one, but it read the same way, 1 of 50, so I have no idea what it was. So I deleted it.


On 11/20/2018 0:26, Joseph Lee wrote:
Hi,
What you're describing is the behavior of emoji panel in Version 1803. Can you try with all add-ons turned off (from exit dialog, select restart with add-ons disabled)?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of John
Isige
Sent: Monday, November 19, 2018 10:10 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4-Beta 1 doesn't read emojis for me.

OK, let's see if this works. No, if I shift tab from most recent I get "search emoji", then continuing to shift tab I get the categories like "transportation", but if I use the arrows, it just does "1 of 250" and so on.


On 11/19/2018 22:47, hurrikennyandopo ... wrote:
Hi


I just noticed now when you are on the recent one if you shift/tab
now it gives you the categories where now you right or left arrow to
them then press the enter key on the one you want then shift tab or
tab to get to the list of them. it seems to be speaking mine out correctly.


it seems like a slight modification to the tutorial.


Gene nz


On 20/11/2018 4:46 PM, John Isige wrote:
Just tested the beta, and it doesn't read emojis, at least for me,
with any synthesizer. I get X of Y, e.g. 1 of 50, 2 of 50, and so on.
This happens even with the one-core voices, which used to read more
emojis than any other synthesizer. This happens whether the copy is
installed or portable. Windows 10 64-bit, latest upates, not 1809
though. Here's the log from when I try to get to an emoji to put
into this message in Thunderbird.


INFO - __main__ (21:37:00.319):
Starting NVDA
INFO - core.main (21:37:01.154):
Config dir: C:\Users\khomus\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (21:37:01.154):
Loading config: C:\Users\khomus\AppData\Roaming\nvda\nvda.ini
INFO - core.main (21:37:01.523):
NVDA version 2018.4beta1
INFO - core.main (21:37:01.523):
Using Windows version 10.0.17134 workstation INFO - core.main
(21:37:01.523):
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
(21:37:01.523):
Using comtypes version 1.1.3
INFO - core.main (21:37:01.523):
Using configobj version 5.1.0 with validate version 1.0.1 INFO -
synthDriverHandler.setSynth (21:37:03.980):
Loaded synthDriver oneCore
INFO - core.main (21:37:04.438):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO -
brailleInput.initialize (21:37:04.441):
Braille input initialized
INFO - braille.initialize (21:37:04.444):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (21:37:04.457):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (21:37:04.520):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (21:37:04.536):
UIAutomation: IUIAutomation5
INFO - core.main (21:37:05.927):
NVDA initialized
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(21:43:23.134):
Developer info for navigator object:
name: u'\U0001f6c0'
role: ROLE_LISTITEM
states: STATE_SELECTABLE, STATE_SELECTED
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.UIA.ListItem object at 0x07C36F10>
Python class mro: (<class 'NVDAObjects.UIA.ListItem'>, <class
'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class
'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>, <type 'object'>)
description: ''
location: RectLTWH(left=727, top=479, width=40, height=40)
value: None
appModule:
<'windowsinternal_composableshell_experiences_textinput_inputapp'
(appName
u'windowsinternal_composableshell_experiences_textinput_inputapp',
process ID 8388) at address 7ab9710>
appModule.productName: u'Microsoft\xae Windows\xae Operating System'
appModule.productVersion: u'10.0.17134.191'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 199668
windowClassName: u'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
windowThreadID: 11456
windowText: u'Microsoft Text Input Application'
displayText: u''
UIAElement: <POINTER(IUIAutomationElement) ptr=0xa73a930 at 79f59e0>
UIA automationID:
UIA frameworkID: XAML
UIA runtimeID: (42, 199668, 4, 34)
UIA providerDescription: [pid:8388,providerId:0x0 Main(parent
link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)] UIA
className: GridViewItem UIA patterns available:
LegacyIAccessiblePattern, VirtualizedItemPattern, InvokePattern,
ScrollItemPattern, SelectionItemPattern



--
Image NVDA certified expert
Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net Regardless of where
you are in New Zealand if you are near one of the APNK sites you can
use a copy of the NVDA screen reader on one of their computers. To
find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert
near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains
the official list of NVDA certified individuals from around the
world, who have sat and successfully passed the NVDA expert exam.






Re: Why do some links not do what they say while others do?

Travis Siegel <tsiegel@...>
 

Generally, the links that say click here for ore information that do't seem to do anything are the javascript links that simply pop up a window over top of the existing page with the information in question.  Often times, these windows have timers, so they go away after a certain amount of time.  I've not found a reliable way for NVDA to find these windows.  Sometimes, if it's a permanent window, it's opened at the bottom of the page (as NVDA sees it), so scrolling to the bottom of the page, you will see the extra content that link added to the page.  Otherwise, I've found no way at all to see the window content.

On 11/20/2018 3:34 PM, Brian's Mail list account via Groups.Io wrote:
Many sites now helpfully say, click here for main content, or a variation on the theme. But some do as they say, while others seem to cause no discernable change. I have always wondered about this, and its been around for many years. Is there a page authoring or other reason why these links seem not to work?

I'm talking about all browsers really though at the moment I only have waterfox firefox and IE on windows 7.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.



Why do some links not do what they say while others do?

Brian's Mail list account
 

Many sites now helpfully say, click here for main content, or a variation on the theme. But some do as they say, while others seem to cause no discernable change. I have always wondered about this, and its been around for many years. Is there a page authoring or other reason why these links seem not to work?

I'm talking about all browsers really though at the moment I only have waterfox firefox and IE on windows 7.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


Re: continues in beta

 

Hi,
Based on the log I got from this person, it appears UIA events are not seen by NVDA in some cases (even with log level set to debug, relevant info isn't showing up).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail list account via Groups.Io
Sent: Tuesday, November 20, 2018 12:28 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] continues in beta

What do you mean? Is this a windows 10 thing, as I hear no junk on windows 7.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Don H" <lmddh50@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 6:32 PM
Subject: [nvda] continues in beta


With the last release of NVDA when you open up the settings menu NVDA
reads what I call trash. This issue still remains with the 2018-4 beta 1.
It is saying something like
C equals microsoft windows
O equals Microsoft corporation
L equals readman
F equals Washington
c equals us windows




Re: continues in beta

Brian's Mail list account
 

What do you mean? Is this a windows 10 thing, as I hear no junk on windows 7.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Don H" <lmddh50@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 6:32 PM
Subject: [nvda] continues in beta


With the last release of NVDA when you open up the settings menu NVDA reads what I call trash. This issue still remains with the 2018-4 beta 1.
It is saying something like
C equals microsoft windows
O equals Microsoft corporation
L equals readman
F equals Washington
c equals us windows



Re: NVDA 2018.4 beta 1

Sarah k Alawami
 

No I'm using the slower ring if you will. I can't remember but yeah I am usi gsnaps but they are updated I thin weekly.

Take care

On 20 Nov 2018, at 11:15, Joseph Lee wrote:

Hi,

If you are using alpha snapshots, you don’t have to grab a beta, as the code is identical at this point (although in the next few days, it may diverge somewhat).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Tuesday, November 20, 2018 11:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4 beta 1

 

I should know the answer to this, but do I as I'm already using a beta need to grab this one? Or am I good to go go go?

Take care

On 19 Nov 2018, at 18:56, hurrikennyandopo ... wrote:

Hi guys

 

it looks as though there is a beta release of nvda 2018.4 beta 1.

 

You can take it for a test drive just grab your snap shot first from https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.

 

Gene nz

 

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

<


Re: NVDA 2018.4 beta 1

Brian's Mail list account
 

Yes I have the alpha as a portable, and like to use the beta as a working version, which is why to some extent I do not like it updating to the stable every time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 7:15 PM
Subject: Re: [nvda] NVDA 2018.4 beta 1


Hi,

If you are using alpha snapshots, you don't have to grab a beta, as the code
is identical at this point (although in the next few days, it may diverge
somewhat).

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Tuesday, November 20, 2018 11:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4 beta 1



I should know the answer to this, but do I as I'm already using a beta need
to grab this one? Or am I good to go go go?

Take care

On 19 Nov 2018, at 18:56, hurrikennyandopo ... wrote:

Hi guys



it looks as though there is a beta release of nvda 2018.4 beta 1.



You can take it for a test drive just grab your snap shot first from
https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.



Gene nz



--


Check out my website for NVDA tutorials and other blindness related material
at http://www.accessibilitycentral.net Regardless of where you are in New
Zealand if you are near one of the APNK sites you can use a copy of the NVDA
screen reader on one of their computers. To find out which locations (or
location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa
People's Network Kaharoa). To find an NVDA certified expert near you, please
visit the following link https://certification.nvaccess.org/. The
certification page contains the official list of NVDA certified individuals
from around the world, who have sat and successfully passed the NVDA expert
exam.






Re: NVDA 2018.4 beta 1

Brian's Mail list account
 

Basically the beta of the last version ran through the rc to the stable, so if that is what you did then yes, you need to restart using the beta again by downloading it. I know it seems cock eyed, but its not my fault!

Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sarah k Alawami" <marrie12@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 7:06 PM
Subject: Re: [nvda] NVDA 2018.4 beta 1


I should know the answer to this, but do I as I'm already using a beta
need to grab this one? Or am I good to go go go?

Take care

On 19 Nov 2018, at 18:56, hurrikennyandopo ... wrote:

Hi guys


it looks as though there is a beta release of nvda 2018.4 beta 1.


You can take it for a test drive just grab your snap shot first from
https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.


Gene nz


--
[Image NVDA certified expert]
Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net Regardless of where
you are in New Zealand if you are near one of the APNK sites you can
use a copy of the NVDA screen reader on one of their computers. To
find out which locations (or location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries
(Aotearoa People's Network Kaharoa). To find an NVDA certified expert
near you, please visit the following link
https://certification.nvaccess.org/. The certification page contains
the official list of NVDA certified individuals from around the world,
who have sat and successfully passed the NVDA expert exam.





Re: NVDA 2018.4 beta 1

Brian's Mail list account
 

Yes saw that it made a nasty error noise when it loaded but it seems OK on a reboot.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "hurrikennyandopo ..." <hurrikennyandopo@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 2:56 AM
Subject: [nvda] NVDA 2018.4 beta 1


Hi guys


it looks as though there is a beta release of nvda 2018.4 beta 1.


You can take it for a test drive just grab your snap shot first from https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.


Gene nz


--
[Image NVDA certified expert]
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.



Re: problem with NVDA and libre office

Brian's Mail list account
 

Bit clunky though. I imagine thatches program is not exposing the correct data for nvda to read.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "The Gamages via Groups.Io" <james.gamage@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, November 20, 2018 10:26 AM
Subject: Re: [nvda] problem with NVDA and libre office


Hello,

To read the alignment in Libre office Writer,
Press alt then right arrow to the format menu,
Arrow down to “ alignment” and right arrow to the sub menu.
Now up and down arrow, some will say “selected” but the one that says “checked” will be the current alignment.

Best Regards, Jim.

From: Ashley Wayne
Sent: 20 November 2018 03:02
To: nvda@nvda.groups.io
Subject: Re: [nvda] problem with NVDA and libre office

Hi thank you, I did not realize that. Well, at least I wasn't missing
something obvious.


On 11/19/2018 7:16 PM, zahra wrote:
hi.
both openoffice and libreoffice dont support reporting alignment for
nvda screen reader.
i am not sure about jaws and libreoffice compatibility with jaws, but
i am sure that you cant read alignment information when using
libreoffice or openoffice.

On 11/20/18, Ashley Wayne <a.r.wayne2008@...> wrote:
Hi all,


I cannot seem to get NVDA to announce the alignment of text in libre
office writer, such as left or centered. I will have alignment checked
under the document formatting section of preferences but still nothing.
NVDA key plus F will read other attributes like font type or size but
still not alignment. When I go to other applications with text, like
websites for example, NVDA will then read alignment information. What
am I missing here? Thank you so much for any help.

Ashley



---
This email has been checked for viruses by AVG.
https://www.avg.com





Re: NVDA 2018.4 beta 1

 

Hi,

If you are using alpha snapshots, you don’t have to grab a beta, as the code is identical at this point (although in the next few days, it may diverge somewhat).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Tuesday, November 20, 2018 11:06 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.4 beta 1

 

I should know the answer to this, but do I as I'm already using a beta need to grab this one? Or am I good to go go go?

Take care

On 19 Nov 2018, at 18:56, hurrikennyandopo ... wrote:

Hi guys

 

it looks as though there is a beta release of nvda 2018.4 beta 1.

 

You can take it for a test drive just grab your snap shot first from https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.

 

Gene nz

 

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: NVDA 2018.4 beta 1

Sarah k Alawami
 

I should know the answer to this, but do I as I'm already using a beta need to grab this one? Or am I good to go go go?

Take care

On 19 Nov 2018, at 18:56, hurrikennyandopo ... wrote:

Hi guys


it looks as though there is a beta release of nvda 2018.4 beta 1.


You can take it for a test drive just grab your snap shot first from https://www.nvaccess.org/files/nvda/snapshots/

Time for any bug finding if any.

Hopefully they were picked up in the alfas first.


Gene nz


--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: wonder vs. wander

Sarah k Alawami
 

Actually , my mac read everything with out exaggeration or what not. It all sounded normal to me. Now if I would have taken the time to "spell" everything , I would probably notice the mistakes, but yeah.

On 19 Nov 2018, at 11:28, Brian Vogel wrote:

On Mon, Nov 19, 2018 at 01:21 PM, Kwork wrote:
NVDA is saying awl words correctly, if exaggeratedly at times.
Any time you hear a speech synthesizer saying something "exaggeratedly" that should be a big, honkin' warning that something's off.

Kudos, though, on this post.  It was extremely clever.  I do, however, believe that one should be able to hear the difference, even in synthesized speech in the middle of a sentence, between pro deuce and produce (as but one example).  There's also the question of whether we're talking produce as a verb or noun, as the stress is on the second syllable in the first instance and the first syllable in the second.  That being said, the speed at which many blind individuals can understand voice output from screen readers just astounds me.  I could no sooner wrap my head around speech that fast than fly to the moon using my own arms as propulsion.  If you have speech produced at ear blistering (for me) speeds then the elisions between two short words and a single word with the same phonemes becomes much harder to suss out.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

50241 - 50260 of 100970