Date   

Re: Some issues coming between Google Chrome and NVDA

Dejan Ristic
 

I also use Chrome. The only thing is that I have been experiencing the mentioned problems only in these two instances. Note that I mentioned that the Opera browser behaved in the same way. I also tested Avast! Safe Zone Browser, and it also did behave in the same way. Mozilla firefox and Internet explorer are good to use in these cases, but they slow down. That's why I like Chrome and Opera so much, and that's why I use them as much as the accessibility features allow me to do so.


On 8/11/2016 2:13 PM, Gene wrote:
I'd have to update my Chrome and find out.  I almost never use Chrome.  Since I have seen not one complaint other than yours, and since many list members use Chrome, at this time, I suspect that you are having problems that others, at least in general, aren't having.  I may experiment with Chrome later today, depending on what others say. 
 
Gene
----- Original Message -----
Sent: Thursday, August 11, 2016 4:11 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA

Il 11/08/2016 10:43, Gene ha scritto:
> Failure of Chrome to remain accessible with two Google apps does not
> render it unsupported by NVDA.

Gene, if you read my ticket, you will discover that Chrome is not able
to read headings, some links, and there are xml parsing error and really
ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?









Re: Some issues coming between Google Chrome and NVDA

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

One of the main reasons I'm not using anything else but firefox at the moment is all this now it workds now it won't stuff. They obviously do not test their new versions very well from what i can tell. At least firefox do fix things like they fixed the navigation sounds not working in 47, and its fine in the later versions, aand lists work properly in web pages as well.

Btrian

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

----- Original Message -----
From: "Jacob Kruger" <jacob@blindza.co.za>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 11, 2016 1:44 PM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA


Not sure if this message is going to make it through to list, since seem
to have mail server issues, but, also, just make sure you try using
different review modes - document review mode should be default when
browsing web contents, but, also try object review and screen review
mode - or at least, just make sure you have tried the navigation keys
while in document review mode, and while you are focused on some element
which is specifically in the document contents - my one, ongoing issue
with chrome is just getting NVDA to focus on webpage contents, at times,
but, it works fine after figure out a work-around for that each time.


Stay well


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

On 2016-08-11 2:13 PM, Gene wrote:
I'd have to update my Chrome and find out. I almost never use
Chrome. Since I have seen not one complaint other than yours, and
since many list members use Chrome, at this time, I suspect that you
are having problems that others, at least in general, aren't having.
I may experiment with Chrome later today, depending on what others say.
Gene
----- Original Message -----
*From:* Simone Dal Maso <mailto:simone.dalmaso@gmail.com>
*Sent:* Thursday, August 11, 2016 4:11 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] Some issues coming between Google Chrome and NVDA

Il 11/08/2016 10:43, Gene ha scritto:
Failure of Chrome to remain accessible with two Google apps does not
render it unsupported by NVDA.
Gene, if you read my ticket, you will discover that Chrome is not able
to read headings, some links, and there are xml parsing error and really
ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it <http://www.yahoo.it> with chrome, can you
surf it?






Re: Some issues coming between Google Chrome and NVDA

Jacob Kruger
 

Not sure if this message is going to make it through to list, since seem to have mail server issues, but, also, just make sure you try using different review modes - document review mode should be default when browsing web contents, but, also try object review and screen review mode - or at least, just make sure you have tried the navigation keys while in document review mode, and while you are focused on some element which is specifically in the document contents - my one, ongoing issue with chrome is just getting NVDA to focus on webpage contents, at times, but, it works fine after figure out a work-around for that each time.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."
On 2016-08-11 2:13 PM, Gene wrote:

I'd have to update my Chrome and find out.  I almost never use Chrome.  Since I have seen not one complaint other than yours, and since many list members use Chrome, at this time, I suspect that you are having problems that others, at least in general, aren't having.  I may experiment with Chrome later today, depending on what others say. 
 
Gene
----- Original Message -----
Sent: Thursday, August 11, 2016 4:11 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA

Il 11/08/2016 10:43, Gene ha scritto:
> Failure of Chrome to remain accessible with two Google apps does not
> render it unsupported by NVDA.

Gene, if you read my ticket, you will discover that Chrome is not able
to read headings, some links, and there are xml parsing error and really
ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?







Re: Some issues coming between Google Chrome and NVDA

mk360
 

I've many problems too, but I use next for NVDA. the thing is Chrome sometimes works fine, sometimes it doesn't. So, I think one thing is supported, other thing is partially supported or supported when Chromium team doesn't change things.

Note that the evaluations of how accessible is the product depends of the user... I use chrome because my chromecast need it and well, because I know many programs that are less usable than chrome, but I can't say it works correctly, only that it is usable.

Is something similar to the accessibility of windows 10 aniversary... the insiders are happy with the accessibility provided, I think it works fine, but many end users think that some things don't work.


Regards,

mk.


El 11-08-2016 a las 8:13, Gene escribió:
I'd have to update my Chrome and find out.  I almost never use Chrome.  Since I have seen not one complaint other than yours, and since many list members use Chrome, at this time, I suspect that you are having problems that others, at least in general, aren't having.  I may experiment with Chrome later today, depending on what others say. 
 
Gene
----- Original Message -----
Sent: Thursday, August 11, 2016 4:11 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA

Il 11/08/2016 10:43, Gene ha scritto:
> Failure of Chrome to remain accessible with two Google apps does not
> render it unsupported by NVDA.

Gene, if you read my ticket, you will discover that Chrome is not able
to read headings, some links, and there are xml parsing error and really
ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?







Re: Some issues coming between Google Chrome and NVDA

Gene
 

I'd have to update my Chrome and find out.  I almost never use Chrome.  Since I have seen not one complaint other than yours, and since many list members use Chrome, at this time, I suspect that you are having problems that others, at least in general, aren't having.  I may experiment with Chrome later today, depending on what others say. 
 
Gene

----- Original Message -----
Sent: Thursday, August 11, 2016 4:11 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA

Il 11/08/2016 10:43, Gene ha scritto:
> Failure of Chrome to remain accessible with two Google apps does not
> render it unsupported by NVDA.

Gene, if you read my ticket, you will discover that Chrome is not able
to read headings, some links, and there are xml parsing error and really
ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?






Re: Some issues coming between Google Chrome and NVDA

Dejan Ristic
 

Thank you for doing so.


But, let's consider that these issues did not exist before. Do you agree with the fact that some major changes in Chrome can be done, so that the relation between NVDA and Chrome may be improved as far as the instance of accessibility is concerned?

On 8/11/2016 10:25 AM, Simone Dal Maso wrote:
Google Chrome on my opinion should be removed from supported NVDA browser.
It is absolutely not usable, at least on my three pc.
I opened a ticket about this:

https://github.com/nvaccess/nvda/issues/6249

Il 10/08/2016 21:02, Dejan Ristic ha scritto:
Both the previous and the current version of Chrome have decreased some
accessibility features as far as Facebook and Google Translate are
concerned.


When I type in the search field what I wish to find on Facebook, I am no
longer able to hear the list of the items found when I use the up and
down arrows to go through them after I have typed my search term. NVDA
only pronounces my search term when I up and down, but does not show the
list of the items found as it did before. Compare Mozilla Firefox with
Chrome, and all will be clear. The same goes for the Opera browser.


As for Google Translate, it is impossible for me to choose between the
list of the source and target languages. The only NVDA-output
pronounciation is: "list submenu expanded" and "list submenu collapsed".
The same goes for the Opera browser.

When I handle it by Mozilla Firefox, I succeed in choosing between the
desired source and target languages. It means that both lists are spoken
correctly.


I use the latest version of NVDA, and the latest version of both Chrome
and Opera.


My operating system is: Windows 7 Ultimate, 64bit.


Allow me to ask you whether you shake hands with the same issues?


Thankful in advance,

Dejan







Re: Some issues coming between Google Chrome and NVDA

Simone Dal Maso
 

Il 11/08/2016 11:27, Jacob Kruger ha scritto:
Quick test, and it worked fine here with chrome 52 and latest NVDA
master snapshot?
Oh... thank you! So this is only a problem of mine. Thank you very much, I will try to reinstall chrome.


Re: Some issues coming between Google Chrome and NVDA

Jacob Kruger
 

Quick test, and it worked fine here with chrome 52 and latest NVDA master snapshot?

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

On 2016-08-11 11:11 AM, Simone Dal Maso wrote:
Il 11/08/2016 10:43, Gene ha scritto:
Failure of Chrome to remain accessible with two Google apps does not
render it unsupported by NVDA.
Gene, if you read my ticket, you will discover that Chrome is not able to read headings, some links, and there are xml parsing error and really ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?







Re: Some issues coming between Google Chrome and NVDA

Simone Dal Maso
 

Il 11/08/2016 10:43, Gene ha scritto:
Failure of Chrome to remain accessible with two Google apps does not
render it unsupported by NVDA.
Gene, if you read my ticket, you will discover that Chrome is not able to read headings, some links, and there are xml parsing error and really ttones of errors.
What I'd like to know is if I am the only one that can't use Chrome.
If you open www.yahoo.it with chrome, can you surf it?


Re: Some issues coming between Google Chrome and NVDA

Gene
 

Failure of Chrome to remain accessible with two Google apps does not render it unsupported by NVDA.  This may be more of Googles routine breaking of things.  They seem to break something about every six months in production versions.  Here we are, somewhere between four and six months since the last thing that was broken. 
 
This routine breaking of things and not correcting the problem or problems until after they reach production versions is hardly a demonstration of a proper commitment.  That's one reason I don't use Chrome as my main browser.  I've seen too many completely unnecessary problems in production versions over time.  That the problems are usually corrected doesn't mitigate the fact that they reach production versions. 
 
Gene

----- Original Message -----
Sent: Thursday, August 11, 2016 3:25 AM
Subject: Re: [nvda] Some issues coming between Google Chrome and NVDA

Google Chrome on my opinion should be removed from supported NVDA browser.
It is absolutely not usable, at least on my three pc.
I opened a ticket about this:

https://github.com/nvaccess/nvda/issues/6249

Il 10/08/2016 21:02, Dejan Ristic ha scritto:
> Both the previous and the current version of Chrome have decreased some
> accessibility features as far as Facebook and Google Translate are
> concerned.
>
>
> When I type in the search field what I wish to find on Facebook, I am no
> longer able to hear the list of the items found when I use the up and
> down arrows to go through them after I have typed my search term. NVDA
> only pronounces my search term when I up and down, but does not show the
> list of the items found as it did before. Compare Mozilla Firefox with
> Chrome, and all will be clear. The same goes for the Opera browser.
>
>
> As for Google Translate, it is impossible for me to choose between the
> list of the source and target languages. The only NVDA-output
> pronounciation is: "list submenu expanded" and "list submenu collapsed".
> The same goes for the Opera browser.
>
> When I handle it by Mozilla Firefox, I succeed in choosing between the
> desired source and target languages. It means that both lists are spoken
> correctly.
>
>
> I use the latest version of NVDA, and the latest version of both Chrome
> and Opera.
>
>
> My operating system is: Windows 7 Ultimate, 64bit.
>
>
> Allow me to ask you whether you shake hands with the same issues?
>
>
> Thankful in advance,
>
> Dejan
>
>
>
>
>




Re: Some issues coming between Google Chrome and NVDA

Simone Dal Maso
 

Google Chrome on my opinion should be removed from supported NVDA browser.
It is absolutely not usable, at least on my three pc.
I opened a ticket about this:

https://github.com/nvaccess/nvda/issues/6249

Il 10/08/2016 21:02, Dejan Ristic ha scritto:
Both the previous and the current version of Chrome have decreased some
accessibility features as far as Facebook and Google Translate are
concerned.


When I type in the search field what I wish to find on Facebook, I am no
longer able to hear the list of the items found when I use the up and
down arrows to go through them after I have typed my search term. NVDA
only pronounces my search term when I up and down, but does not show the
list of the items found as it did before. Compare Mozilla Firefox with
Chrome, and all will be clear. The same goes for the Opera browser.


As for Google Translate, it is impossible for me to choose between the
list of the source and target languages. The only NVDA-output
pronounciation is: "list submenu expanded" and "list submenu collapsed".
The same goes for the Opera browser.

When I handle it by Mozilla Firefox, I succeed in choosing between the
desired source and target languages. It means that both lists are spoken
correctly.


I use the latest version of NVDA, and the latest version of both Chrome
and Opera.


My operating system is: Windows 7 Ultimate, 64bit.


Allow me to ask you whether you shake hands with the same issues?


Thankful in advance,

Dejan




Re: Twitter any help or addons?

Simone Dal Maso
 

Use software like TwBlue.
Best regards.

Il 11/08/2016 09:57, John from Woodside Apps ha scritto:
Hello
I use twitter very rarely and had to use it yesterday
and found it almost impossible.
Any tips,add-ons?

Latest Stable NVDA
Win 7 pro 64bit
Firefox latest version.


Twitter any help or addons?

 

Hello
I use twitter very rarely and had to use it yesterday
and found it almost impossible.
Any tips,add-ons?

Latest Stable NVDA
Win 7 pro 64bit
Firefox latest version.

--
John from Woodside Apps.
Accessible Apps and games for mobile devices.
Super Tile Smash is now available
Free version is at
https://play.google.com/store/apps/details?id=wa.supertilesmash.free
The PRO no adverts version is called Super Tile Smash PRO.
Talking Stones
An addictive,sound rich game playable by anyone with any level of eyesight.
Free trial version can be found at
https://play.google.com/store/apps/details?id=woodsideapps.stones.free
Talking Stones Pro with unlimited levels is at
https://play.google.com/store/apps/details?id=woodsideapps.stones
Our other Android Apps
https://play.google.com/store/apps/dev?id=6590954580289174510
Our IOS Apps
https://itunes.apple.com/us/developer/john-sturt/id1089097833
Also for the great accessible game RapITap go to
Free Version is at https://play.google.com/store/apps/details?id=au.com.twentytwopoint.rapitapfree


Re: tahanks, and a please

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

I think if you really do have issues then a ticket on github is probably best of all as they get reviewed regualarly and if more info is needed then they ask for it.
Just saying this happens when it may not happen to everyone is a bit hard, as to find anything weird you first need to duplicate the effects.
There is an ongoing issue in 10 with those dialogues that ask things, liike there are x suspended operations, click here to run them with elevated priveliges or something similar. these do not always show up so you keep wondering why for examplesomthing won't copy. No system sound is made and its only by fiddling about with alt tab and some navigation modes that you discover the issues.
This, according to my friends is not just an nvda issuee. it seems that Microsoft are not always making the window a front one from the screenreaders viewpoint. The sighted would see it however.
Brian

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

----- Original Message -----
From: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 10, 2016 8:39 PM
Subject: Re: [nvda] tahanks, and a please


You might want to post directly to James Teh and Michael Curren. I don't
think they are on this list only the NVDA add-on and DEV list. COrrect
me if I'm wrong.


On 8/10/2016 3:32 PM, lali wrote:

Dear NVDA Developers!

A much, much thanks for you to dveloped nvda to get started with win
10 anniversary update.

Can I have 2 questions?

1.In Mail, If I type, I noticed, that the letters does not speak.

2.If I am in edge, the b key for button is not working. Can you fix?

God bless!

Laller

Küldte a Windows 10 Posta <https://go.microsoft.com/fwlink/?LinkId=550986>


Re: Mail app in WIN 10 broken again

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

I have given up on it as it made it default when I did the anniversary update. I have however had to reinstall the Outlook Express again, losing all the email again. The daft thing is that yes, Outlook Express is old, and yes officially its not supported, but the way it is made to work is by using some specially written files to allow it to use the resources of newer windows versions instead. A kind of translation between the program and the operating system.
There are still the same issues of it suddenly not seeing message bodies and complaining of not enough memory as was in the xp version when used with nvda at times, but its minor compared to the long tree structures in Tbird live mail etc, and the ever changing confusion of the new mail app.

I never do quite understand why companies feel the need to reinvent whells when the old one only needed some new tyres, and a punctures and perhaps a rebalance!

Brian

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

----- Original Message -----
From: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, August 10, 2016 8:12 PM
Subject: [nvda] Mail app in WIN 10 broken again


Just downloaded Mail app update and its saying read only with the newest update. I'm using master branch of NVDA.



Re: mark voice

 

Hi,
Any screen reader that can read data related to newer voices can use it. Jamie from NV Access has just commented on this, telling folks to wait until it gets merged into next branch.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of David Moore
Sent: Wednesday, August 10, 2016 8:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] mark voice

Hi Bobby,
I think that those voices only work for Narrator, but I am not sure if they are choices in NVDA or not. I am not sure about that, I will check later and let you know!
David Moore (list moderator)


-----Original Message-----
From: Bobby
Sent: Wednesday, August 10, 2016 4:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] mark voice

Hay I was wondering ware I can get Microsoft mark and eva. I did the windows 10 update last week and those voices didn't come with this update at all. I want those voices so I can start using them on nvda.


Re: mark voice

David Moore
 

Hi Bobby,
I think that those voices only work for Narrator, but I am not sure if they are choices in NVDA or not. I am not sure about that, I will check later and let you know!
David Moore (list moderator)

-----Original Message-----
From: Bobby
Sent: Wednesday, August 10, 2016 4:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] mark voice

Hay I was wondering ware I can get Microsoft mark and eva. I did the
windows 10 update last week and those voices didn't come with this
update at all. I want those voices so I can start using them on nvda.


Re: Your First NVDA App Module: fix focus problem

 

Hi,

I have forwarded this to developers list.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of ??? Victor Cai
Sent: Wednesday, August 10, 2016 8:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] Your First NVDA App Module: fix focus problem

 

Hi Joseph and all,
Could we write app modules to fix “caret focus” problem?

case one: LibreOffice Calc

In some cases, when pressing arrows to move across cells, NVDA just braille “cell (skip content)” and speech nothing.

Developer info for navigator object:

name: None
role: ROLE_TABLECELL
states:
isFocusable: False
hasFocus: False
Python object:
Python class mro: (, , , , , , , , , , )
description: None
location: None
value: None
appModule: <’soffice’ (appName u’soffice’, process ID 307208) at address 565d330>
appModule.productName: u’LibreOffice’
appModule.productVersion: u’5.1.3.2’
TextInfo:
windowHandle: 1836756L
windowClassName: u’SALFRAME’
windowControlID: 0
windowStyle: 349110272
windowThreadID: 307212
windowText: u’\u4e09\u91cd\u5340.ods - LibreOffice Calc’
displayText: exception: ‘NoneType’ object is not iterable
IAccessibleObject:
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1836756, objectID=-4, childID=-792
IAccessible accName: None
IAccessible accRole: None
IAccessible accState: exception: unsupported operand type(s) for &: ‘NoneType’ and ‘int’
IAccessible accDescription: None
IAccessible accValue: None
IAccessible2 windowHandle: 0
IAccessible2 uniqueID: 0
IAccessible2 role: ROLE_SYSTEM_CELL
IAccessible2 states: (0)
IAccessible2 attributes: None

case two: Chrome app line

Steps to reproduce:

1.      Open Google Chrome.

2.      Download and install line

3.      Login account.

4.      Choose a friend to chat.

5.      Press NVDA+space to switch to focus mode and type text string.

6.      Press enter to send message.

7.      Switch to browse mode and press up arrow to leave section editable.

8.      Press down arrow to come back and switch to focus mode.
expected: User could type text string and send message.
actual: The focus is not in the same place.
User need to press NVDA+numpadDivide to Move mouse to current navigator object, and press numpadDivide (Left mouse button click) to come back to section.

Developer info: section has focus true

Developer info for navigator object:
name: None
role: ROLE_SECTION
states: STATE_FOCUSABLE, STATE_EDITABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object:
Python class mro: (, , , , , , , , , , , )
description: None
location: None
value: u’\u8acb\u8f38\u5165\u8a0a\u606f\u3002’
appModule: <’appModuleHandler’ (appName u’chrome’, process ID 251112) at address 575f650>
appModule.productName: u’Google Chrome’
appModule.productVersion: u’52.0.2743.116’
TextInfo:
windowHandle: 1181606L
windowClassName: u’Chrome_RenderWidgetHostHWND’
windowControlID: 186829216
windowStyle: 1445986304
windowThreadID: 246556
windowText: u’Chrome Legacy Window’
displayText: exception: ‘NoneType’ object is not iterable
IAccessibleObject:
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1181606, objectID=-4, childID=-30983
IAccessible accName: None
IAccessible accRole: u’div’
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: u’\u8acb\u8f38\u5165\u8a0a\u606f\u3002’
IAccessible2 windowHandle: 1181606
IAccessible2 uniqueID: -30983
IAccessible2 role: IA2_ROLE_SECTION
IAccessible2 states: IA2_STATE_OPAQUE, IA2_STATE_EDITABLE (1032)
IAccessible2 attributes: u’display:block;tag:div;class:mdRGT06Input;id:_chat_room_input;’



Re: recent change

Sam Bushman
 

Hi All,

I am the one who had the problem and yes the fix works.

Add this to your default dictionary.

Comment: outlook 2016 work around

Pattern: “Associated Draft No Associated Drafts,”

Then put a dash “-“ for the  replacement.

Yes check case sensitive and anywhere.

 

Hope this helps.

 

Thanks,

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Wednesday, August 10, 2016 4:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] recent change

 

I've seen this discussed two or three times on this and, perhaps another list.  As I recall, there is no solution in terms of making adjustments in either program.  I believe you can solve it by using the speech dictionary.  Use the speech dictionary to cause nothing to be spoken when the phrase no associated drafts and the phrase associated drafts has been spoken.  My recollection is that I suggested this and that it worked.  If you need to know how to do this, let us know.

 

Gene

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

From: slery

Sent: Wednesday, August 10, 2016 3:57 PM

Subject: [nvda] recent change

 

In the last few days, I have noticed a change in how nvda reads in Outlook 2016. It used to say unread, read the subject, then it read the author.

 

It has now started saying “no associated drafts” before reading anything else about the message. What can I do to change this?

 

Latest nvda

Outlook 2016 (office 365)

Windows 10

 

Cindy


Your First NVDA App Module: fix focus problem

蔡宗豪 Victor Cai
 

Hi Joseph and all,
Could we write app modules to fix “caret focus” problem?

case one: LibreOffice Calc

In some cases, when pressing arrows to move across cells, NVDA just braille “cell (skip content)” and speech nothing.

Developer info for navigator object:

name: None
role: ROLE_TABLECELL
states:
isFocusable: False
hasFocus: False
Python object:
Python class mro: (, , , , , , , , , , )
description: None
location: None
value: None
appModule: <’soffice’ (appName u’soffice’, process ID 307208) at address 565d330>
appModule.productName: u’LibreOffice’
appModule.productVersion: u’5.1.3.2’
TextInfo:
windowHandle: 1836756L
windowClassName: u’SALFRAME’
windowControlID: 0
windowStyle: 349110272
windowThreadID: 307212
windowText: u’\u4e09\u91cd\u5340.ods - LibreOffice Calc’
displayText: exception: ‘NoneType’ object is not iterable
IAccessibleObject:
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1836756, objectID=-4, childID=-792
IAccessible accName: None
IAccessible accRole: None
IAccessible accState: exception: unsupported operand type(s) for &: ‘NoneType’ and ‘int’
IAccessible accDescription: None
IAccessible accValue: None
IAccessible2 windowHandle: 0
IAccessible2 uniqueID: 0
IAccessible2 role: ROLE_SYSTEM_CELL
IAccessible2 states: (0)
IAccessible2 attributes: None

case two: Chrome app line

Steps to reproduce:

  1. Open Google Chrome.
  2. Download and install line
  3. Login account.
  4. Choose a friend to chat.
  5. Press NVDA+space to switch to focus mode and type text string.
  6. Press enter to send message.
  7. Switch to browse mode and press up arrow to leave section editable.
  8. Press down arrow to come back and switch to focus mode.
    expected: User could type text string and send message.
    actual: The focus is not in the same place.
    User need to press NVDA+numpadDivide to Move mouse to current navigator object, and press numpadDivide (Left mouse button click) to come back to section.
Developer info: section has focus true

Developer info for navigator object:
name: None
role: ROLE_SECTION
states: STATE_FOCUSABLE, STATE_EDITABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object:
Python class mro: (, , , , , , , , , , , )
description: None
location: None
value: u’\u8acb\u8f38\u5165\u8a0a\u606f\u3002’
appModule: <’appModuleHandler’ (appName u’chrome’, process ID 251112) at address 575f650>
appModule.productName: u’Google Chrome’
appModule.productVersion: u’52.0.2743.116’
TextInfo:
windowHandle: 1181606L
windowClassName: u’Chrome_RenderWidgetHostHWND’
windowControlID: 186829216
windowStyle: 1445986304
windowThreadID: 246556
windowText: u’Chrome Legacy Window’
displayText: exception: ‘NoneType’ object is not iterable
IAccessibleObject:
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1181606, objectID=-4, childID=-30983
IAccessible accName: None
IAccessible accRole: u’div’
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: u’\u8acb\u8f38\u5165\u8a0a\u606f\u3002’
IAccessible2 windowHandle: 1181606
IAccessible2 uniqueID: -30983
IAccessible2 role: IA2_ROLE_SECTION
IAccessible2 states: IA2_STATE_OPAQUE, IA2_STATE_EDITABLE (1032)
IAccessible2 attributes: u’display:block;tag:div;class:mdRGT06Input;id:_chat_room_input;’