Date   

audio ducking

Isaac <bigikemusic@...>
 

Hi, not sure if anyone responded but is there a way to ajust timing for ducking?


Polytonic Greek on Braille Displays

Eleni Vamvakari <elvam2167@...>
 

Hello,

I am considering buying a braille display. Right now, I have three
options, considering my price range. These are a Pacmate, an Orbit
Reader 20 (which I don't really want, as it lacks cursor-routing
buttons), a Braillino, and a Braille Me. The Orbit or Braille Me
would be new. The Pacmate is an Omni that works well, though I don't
know its age. The Braillino is two-years-old and in great condition.
While I may occasionally use the display on its own, I will mostly be
using this with NVDA to read the screen, though not as my primary
means, since I have speech for that.

But before I ask any further questions, I must know this, or there is
no point in continuing. Can NVDA handle polytonic Greek in braille.
I see that there is a Koine and a Greek (Greece) braille table. I am
learning Katharevousa, which, like Koine, uses all three accents and
two breathing marks. I have NVDA 2017.3 for XP and the latest version
for Windows 7. While I have reached an intermediate level with speech
alone, I think that having the letters in front of me would be
extremely helpful. But I must know that they will be displayed
correctly. Finally, can it read Latin, including the macrons? Can
any of these displays read either of these correctly on their own?

As for the displays themselves, which works the best with NVDA? What
are the major differences between these? Note that I don't use
bluetooth or sd cards, so those are not deciding factors for me. For
what it's worth, my only experience with braille displays has been
with a Braille Lite 2000 and a BrailleNote Classic, which I haven't
used since 2006.

Thank you,
Eleni

--
Facebook: elvam2167@...

anyaudio.net: elvam2167

Skype: elvam2167


Re: continues in beta

 

Hi,

To me, based on available evidence 9log file), it appears it is an odd live region that’s speaking when it is supposed to be silent. The log I got also points to UIA not working in that instance.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Tuesday, November 20, 2018 7:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] continues in beta

 

That's interesting.  It sounds as though it thinks it is reading some sort of credit or copyright information as a menu.  I don't know if that makes any sense technically.

 

Gene

----- Original Message -----

From: Don H

Sent: Tuesday, November 20, 2018 12: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: autocorrect in Word 365

Quentin Christensen
 

Excellent, glad to hear you got it working!

Regards

Quentin.

On Wed, Nov 21, 2018 at 10:00 AM Giles Turnbull <giles.turnbull@...> wrote:
thanks Quentin, deleting the existing auto corrects worked a treat :)



--
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: continues in beta

Gene
 

That's interesting.  It sounds as though it thinks it is reading some sort of credit or copyright information as a menu.  I don't know if that makes any sense technically.
 
Gene

----- Original Message -----
From: Don H
Sent: Tuesday, November 20, 2018 12: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: problem with NVDA and libre office

Quentin Christensen
 

While I don't have any better advice than everyone else for the specific issue, I would encourage those using LibreOffice to also report issues against that project as well.  A lot of things like this, where the information isn't being exposed to us, we can't do anything about - it needs to be a change to LibreOffice to expose that, before we can look for it.


On Wed, Nov 21, 2018 at 7:16 AM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
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=btinternet.com@groups.io>
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
>>
>>
>>
>>
>>
>














--
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: Excel reads numeric cells in column E as exponents rather than cell value

Quentin Christensen
 

Hi Matthew,

There's a couple of suggestions there, and although I'm sure I've heard them before, I can't immediately locate them in our issue tracker.  If you have a look and find any related issues, feel free to either subscribe, or comment with more info: https://github.com/nvaccess/nvda/issues

Or, feel free to add new issues for them.  Ideally, if you could make each a different issue, so I think there's three there:
- Add option to pause between information (perhaps a combo box with "comma", "full stop", and "no pause")
- Add a "secondary" information profile.  EG the cell contents would be read in the regular profile for that app, and coordinates, name, etc in the secondary information profile.  The same could then be used in other places - eg text read in normal voice on the web, but the fact that it is a link or a heading would be given in the secondary information voice.
- Add "earcon" options for information such as headings and other elements.  The trick with this one will be not making too complex for the average user to understand, and having default sounds which make a bit of sense (I guess for headings, pick a sound and play it at a different pitch for different heading levels)

Speech refactor was our internal name for updating a heap of code that was done this year, which doesn't have an obvious difference at first, but yes, allows things like these to be implemented a lot easier in future.

Regards

Quentin.

On Wed, Nov 21, 2018 at 12:47 AM Matthew Horspool <mhorspool@...> wrote:

Hi Quentin,

Doing something with how the string is formatted would do wonders for me! I'm a long time JAWS user and technically minded, but I still cannot come to terms with how NVDA "gabbles" out all of its information in one go. Perhaps I've got too used to my creature comforts, but having differentiation between things like this is such a big deal for me that I simply cannot switch to NVDA full-time. If it was improved I would consider a switch much more viable.

Inserting a comma between the cell data and its coordinates would be a good step in the right direction. Could the same be done, please, for table cell coordinates generally, table header information, access keys in menus, the name of a menu and the first control in that menu, etc?

It is only a quick fix though. Longer term, you could do worse than to implement something akin to the JAWS model, e.g. by introducing a message voice which could read coordinates, access keys and suchlike. If this is set differently, a pause will occur naturally as the voice changes. If it's set the same, pauses could be eliminated for those who like the way NVDA does things currently.

Even longer term, something like the Speech and Sounds Manager would be simply fantastic! I have perfect pitch and so, in JAWS, I currently have heading level 1 play a note C, heading level 2 play a D, level 3 an E and so on. Switching to NVDA which must report to heading and its level in speech, because what else is it supposed to do other than not report it at all, feels very sluggish. I also have sounds for buttons, radio buttons, combo and list boxes, tree views and so on and some of this can be replicated in an add-on, but not as neatly. I heard somewhere about something nicknamed "Speech Refactor" which might make some of this stuff possible? Where are we with that?

Thanks,

Matthew

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: 19 November 2018 23:14
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel reads numeric cells in column E as exponents rather than cell value

 

Rick,

 

Well spotted, and interesting pickup.  This is exactly why NVDA itself doesn't try to interpret information, but simply present it as it is displayed.  Many synthesizers do try to interpret data, which is where you end up with St being read as "street" when it is actually used in the context of "saint" or dr for Doctor instead of drive.

 

In this case, it is processing the whole string (value and cell coordinates) as one piece of information: 1.24E4 is read as the scientific formatted number "1.24 times 10 to the power of 4".  If the value was in the cell above it is read as "1.24 times 10 cubed" or in E2 as "1.24 times 10 squared".  It is interesting to note that this affects the OneCore voices, and even then only some of them.  On my system, I have ten OneCore voices.  Of those:

- David, Zira and Mark interpret the coordinates as you encountered

- George, Catherine, Hazel, Susan, Linda, Richard or James, simply read it as it should be read: 1.24 E4

 

I just checked and of the David, Hazel and Zira Microsoft Speech API version 5 voices I have, David reads it as a scientific number, but Hazel and Zira both read 1.24 E4.

 

I will raise this with Microsoft and look to see if we can do anything with how we format the string, maybe we can put a comma in-between the pieces of information.

 

On Mon, Nov 19, 2018 at 9:47 PM Rick <softwarethatworks@...> wrote:

Hello NVDA List:

 

The other day I was reading an Excel  spreadsheet sent to me by a colleague. It had numeric values in column E. When reading these cells with Microsoft One Core voices (I am using Microsoft David) the cell name was read as an exponent to the power of 10. For instance, if the value 1.24 was present in cell E4, the speech produced, “1.24 time 10 to the power of 4” rather than 1.24 E4. This does not happen when using Espeak voices or SAPI 5 voices. Note, if the number in the cell is the result of a formula and not a direct value, the phrase, “has formula” is inserted between the number and the cell name, so it works as expected (i.e. 1.24 has formula E4).

 

Note: This does not happen using Narrator, since Narrator reads the cell name first.

 

I am running the latest released copy of NVDA, Office 365 desktop apps and Windows 10 Professional.

 

Rick

 


 

--

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: Excel reads numeric cells in column E as exponents rather than cell value

Quentin Christensen
 

Hi Rick,

Good question.  There actually isn't currently a way to have cell names read automatically, though it is a good idea.  I created an issue for it: https://github.com/nvaccess/nvda/issues/8963  Feel free to subscribe for updates, or add extra details.

Currently, you could press alt+f3 to jump to the name box, read the name and then press escape, but it would be good to have it read automatically.

Regards

Quentin.


On Tue, Nov 20, 2018 at 12:23 PM Rick <softwarethatworks@...> wrote:

Hello Quentin:

 

Thanks for taking my observation a bit further by trying additional voices.

 

On a somewhat related topic, if I remember correctly from my sighted days, Excel showed the selected cell reference in a small window in the upper left corner, just under the menu. If a cell was named, the name was shown instead of the cell reference. Is there an easy way to have NVDA speak a cell’s name instead of its reference value?

 

Thanks, Rick

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Monday, November 19, 2018 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Excel reads numeric cells in column E as exponents rather than cell value

 

Rick,

 

Well spotted, and interesting pickup.  This is exactly why NVDA itself doesn't try to interpret information, but simply present it as it is displayed.  Many synthesizers do try to interpret data, which is where you end up with St being read as "street" when it is actually used in the context of "saint" or dr for Doctor instead of drive.

 

In this case, it is processing the whole string (value and cell coordinates) as one piece of information: 1.24E4 is read as the scientific formatted number "1.24 times 10 to the power of 4".  If the value was in the cell above it is read as "1.24 times 10 cubed" or in E2 as "1.24 times 10 squared".  It is interesting to note that this affects the OneCore voices, and even then only some of them.  On my system, I have ten OneCore voices.  Of those:

- David, Zira and Mark interpret the coordinates as you encountered

- George, Catherine, Hazel, Susan, Linda, Richard or James, simply read it as it should be read: 1.24 E4

 

I just checked and of the David, Hazel and Zira Microsoft Speech API version 5 voices I have, David reads it as a scientific number, but Hazel and Zira both read 1.24 E4.

 

I will raise this with Microsoft and look to see if we can do anything with how we format the string, maybe we can put a comma in-between the pieces of information.

 

On Mon, Nov 19, 2018 at 9:47 PM Rick <softwarethatworks@...> wrote:

Hello NVDA List:

 

The other day I was reading an Excel  spreadsheet sent to me by a colleague. It had numeric values in column E. When reading these cells with Microsoft One Core voices (I am using Microsoft David) the cell name was read as an exponent to the power of 10. For instance, if the value 1.24 was present in cell E4, the speech produced, “1.24 time 10 to the power of 4” rather than 1.24 E4. This does not happen when using Espeak voices or SAPI 5 voices. Note, if the number in the cell is the result of a formula and not a direct value, the phrase, “has formula” is inserted between the number and the cell name, so it works as expected (i.e. 1.24 has formula E4).

 

Note: This does not happen using Narrator, since Narrator reads the cell name first.

 

I am running the latest released copy of NVDA, Office 365 desktop apps and Windows 10 Professional.

 

Rick

 


 

--

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: Win 10 ver 1809

Ron Canazzi
 

Hi Group,


I installed the 1809 version before it was pulled and besides it screwing up a few default settings, which I was able to reset, I had no issues with it.


Since then, Windows updated again and there are no issues.

On 11/20/2018 6:50 PM, Don H 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.



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


Re: audio ducking

Quentin Christensen
 

In terms of NVDA's options, no there isn't a way to change it presently.

Whether there is a technical way to change that, I'm not sure.  The best option would be to create an issue on GitHub with a rationale for adding the option, and it could then be investigated: https://github.com/nvaccess/nvda/issues/new

Kind regards

Quentin.


On Tue, Nov 20, 2018 at 7:53 PM Isaac <bigikemusic@...> wrote:
Hi, is there a way to change how fast audio ducks and how fast it resumes normal volume, I don't like the two or three second delay in ducking?



--
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 


A NVDA hiccup with microsoft disability support

Robert Doc Wright godfearer
 

when we tried to set up the remote it got to the screen where you decide to accept/don't accept and became stuck. the only thing it could read was the cancel button. I had to turn on narrator to discover what was being asked.


Re: Win 10 ver 1809

Don H
 

On my system running win 10 1809 I get the strange verbage when going to the settings app with both NVDA and Narrator but not with Jaws.

On 11/20/2018 6:58 PM, Joseph Lee wrote:
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: 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.