1. nvda@nvda.groups.io
   Date   
Re: Focus Highlight and NVDA 2020.1

Quentin Christensen
 

Brian,

I had a look through our issues and while there are several there for, or involving, focus highlight, none seemed to match the problems you've encountered.  If it does happen again, please do send me a log if you can (and if you can, ideally at debug level and with add-ons disabled, just in case).

One thing I did just try, is setting Windows 10 to High Contrast Mode and using Focus Highlight, and that works for me with Windows 10 1903 and 1909 using NVDA 2020.2beta2 at least.

Regards

Quentin.

On Wed, Jul 15, 2020 at 9:10 AM Brian Vogel <britechguy@...> wrote:
I did not create a ticket, at least not yet.

And since using High Contrast under Windows can obscure many things that would otherwise appear, I'd definitely try turning that off to see if something appears.  There are times where you can't have everything you want at once.  I had the same sort of issues when using ZoomText with color tweaking.  It took precedence over certain things and, as a result, obscured their very existence.

If it turns out that High Contrast and Focus Highlight are not playing well together, a feature request to make Focus Highlight sense whether High Contrast is turned on, and modify what gets used as the framing color based on whether it's in a regular theme or a high contrast one.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 



--
Quentin Christensen
Training and Support Manager
Re: Possible bug with NVDA and Notepad++

Gene
 

If I understand your message, which I may not have when I first answered it, you are saying that if you haven't read the material before, you can set the start place, then set the end place as you read. That's true. I don't know how many people select in that way. I don't recall ever selecting material unless I know already what I want to select.

Does the problem you are describing only occur on specific programs or in general?

Gene

-----Original Message-----
From: Gene
Sent: Tuesday, July 14, 2020 7:57 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

You can move to the start point, then hold shift and move down by line while
holding the shift key, not releasing it at all. You will hear each line you
are selecting as you move. In your message, you said you first mark the
start point, then move to the end of the message. So in your example, you
want to select from the start point to the end of the message. Move to the
start point, then use the command control shift end to move to the end of
the file and select from the start point to the end.

When you select, you use the movement commands with the shift added. You
can hold the shift and move and hear what you are moving through such as
holding the shift, not releasing it, and repeatedly pressing down arrow.
You can use more than one movement command. You can use shift down arrow,
then use shift plus right arrow.

Gene
-----Original Message-----
From: William Wong
Sent: Tuesday, July 14, 2020 6:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

Hi thanks for the reply.

I know the normal way of Window selection by shift key, but using shift
key I have to keep pressing the shift key till I find the correct end
point of selection.

I found nvda f9/10 useful is because I can first mark the start point
with nvda f9, then I can move on to read the rest of the content and
decide on where to end selection.



Luke Davis 於 15/7/2020 0:23 寫道:
On Tue, 14 Jul 2020, William Wong wrote:

I came across a bug:
This is not a bug. You have conflated (confused) two different kinds of selection.

1. open any txt file with Notepad ++
2. select a start position by nvda f9
That is selecting with review mode. You should then use review commands (number pad in desktop keyboard mode), and then NVDA+F10 when you're finished (possibly twice).

This should only be used when the windows selection commands don't work.

> 3. press ctrl end to move to end of document

You are now moving cursors and such, which changes the screen. That will make review mode commands unpredictable. You can not use cursor movement commands while using review commands, and expect the review commands to keep working.

4. press nvda f10 to mark as end position
The review mode is only intended to work on a static screen. When you start changing the screen out from under it, you can't expect the review mode copy method to work any more. It's not a bug, that's how it's supposed to work. In fact it can't be any other way.

In an environment like NotepadPlusPlus, you can just use normal Windows selection and copy commands. Control+A to select all; Shift and arrow keys to select by character or line; shift and control+arrow keys to select words; Shift and home/end to select to start/end of line; and shift+control+home/end to select to the beginning/end of the document.

You should leave NVDA+F9/F10 out of it in applications like this.

Luke
Re: Possible bug with NVDA and Notepad++

Gene
 

You can move to the start point, then hold shift and move down by line while holding the shift key, not releasing it at all. You will hear each line you are selecting as you move. In your message, you said you first mark the start point, then move to the end of the message. So in your example, you want to select from the start point to the end of the message. Move to the start point, then use the command control shift end to move to the end of the file and select from the start point to the end.

When you select, you use the movement commands with the shift added. You can hold the shift and move and hear what you are moving through such as holding the shift, not releasing it, and repeatedly pressing down arrow. You can use more than one movement command. You can use shift down arrow, then use shift plus right arrow.

Gene

-----Original Message-----
From: William Wong
Sent: Tuesday, July 14, 2020 6:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

Hi thanks for the reply.

I know the normal way of Window selection by shift key, but using shift
key I have to keep pressing the shift key till I find the correct end
point of selection.

I found nvda f9/10 useful is because I can first mark the start point
with nvda f9, then I can move on to read the rest of the content and
decide on where to end selection.



Luke Davis 於 15/7/2020 0:23 寫道:
On Tue, 14 Jul 2020, William Wong wrote:

I came across a bug:
This is not a bug. You have conflated (confused) two different kinds of selection.

1. open any txt file with Notepad ++
2. select a start position by nvda f9
That is selecting with review mode. You should then use review commands (number pad in desktop keyboard mode), and then NVDA+F10 when you're finished (possibly twice).

This should only be used when the windows selection commands don't work.

> 3. press ctrl end to move to end of document

You are now moving cursors and such, which changes the screen. That will make review mode commands unpredictable. You can not use cursor movement commands while using review commands, and expect the review commands to keep working.

4. press nvda f10 to mark as end position
The review mode is only intended to work on a static screen. When you start changing the screen out from under it, you can't expect the review mode copy method to work any more. It's not a bug, that's how it's supposed to work. In fact it can't be any other way.

In an environment like NotepadPlusPlus, you can just use normal Windows selection and copy commands. Control+A to select all; Shift and arrow keys to select by character or line; shift and control+arrow keys to select words; Shift and home/end to select to start/end of line; and shift+control+home/end to select to the beginning/end of the document.

You should leave NVDA+F9/F10 out of it in applications like this.

Luke
Re: Possible bug with NVDA and Notepad++

William
 

Hi thanks for the reply.

I know the normal way of Window selection by shift key, but using shift key I have to keep pressing the shift key till I find the correct end point of selection.

I found nvda f9/10 useful is because I can first mark the start point with nvda f9, then I can move on to read the rest of the content and decide on where to end selection.



Luke Davis 於 15/7/2020 0:23 寫道:

On Tue, 14 Jul 2020, William Wong wrote:

I came across a bug:
This is not a bug. You have conflated (confused) two different kinds of selection.

1. open any txt file with Notepad ++
2. select a start position by nvda f9
That is selecting with review mode. You should then use review commands (number pad in desktop keyboard mode), and then NVDA+F10 when you're finished (possibly twice).

This should only be used when the windows selection commands don't work.

 > 3. press ctrl end to move to end of document

You are now moving cursors and such, which changes the screen. That will make review mode commands unpredictable. You can not use cursor movement commands while using review commands, and expect the review commands to keep working.

4. press nvda f10 to mark as end position
The review mode is only intended to work on a static screen. When you start changing the screen out from under it, you can't expect the review mode copy method to work any more. It's not a bug, that's how it's supposed to work. In fact it can't be any other way.

In an environment like NotepadPlusPlus, you can just use normal Windows selection and copy commands. Control+A to select all; Shift and arrow keys to select by character or line; shift and control+arrow keys to select words; Shift and home/end to select to start/end of line; and shift+control+home/end to select to the beginning/end of the document.

You should leave NVDA+F9/F10 out of it in applications like this.

Luke
Re: Focus Highlight and NVDA 2020.1

Brian Vogel
 

I did not create a ticket, at least not yet.

And since using High Contrast under Windows can obscure many things that would otherwise appear, I'd definitely try turning that off to see if something appears.  There are times where you can't have everything you want at once.  I had the same sort of issues when using ZoomText with color tweaking.  It took precedence over certain things and, as a result, obscured their very existence.

If it turns out that High Contrast and Focus Highlight are not playing well together, a feature request to make Focus Highlight sense whether High Contrast is turned on, and modify what gets used as the framing color based on whether it's in a regular theme or a high contrast one.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 
Re: Focus Highlight and NVDA 2020.1

Robert Kingett
 

It doesn't work for me at all, from what sighted people tell me, but maybe because I'm using high contrast on Windows 10? What's the link to the ticket on github?
Re: Focus Highlight and NVDA 2020.1

Brian Vogel
 

An Update.

Tyler, thanks for the bit on punctuation, as going back to most is what fixed it.

I have done an uninstall/reinstall on NVDA 2020.1 and, so far, the Focus Highlight functionality is working.  But this was the case before, too, so I have the feeling that the same issue is going to crop up again.  We shall see.

--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 
Re: Focus Highlight and NVDA 2020.1

Tyler Spivey
 

In addition to my previous message, if it says it can't load the
provider, that usually means there's something in the log. Check the end
of it for a traceback.

On 7/14/2020 12:36 PM, Brian Vogel wrote:
The functionality formerly handled by the Focus Highlight Add-On has
been integrated into the core functionality of NVDA under the Vision
preferences.  However, I have had no success in getting Focus Highlight
to either work in the first place, or have its functionality stick.  I
have uninstalled and reinstalled NVDA, and that didn't fix the issue,
either.

Right now, if I attempt to enable Focus Highlight in the Vision
settings, I am consistently getting the error message, "Could not load
the Focus Highlight vision enhancement provider."

I thought I'd ask here if anyone knew if there was something I have done
to cause this or could do to fix it before I file a trouble ticket on
GitHub.

(As an aside, and I know that this is my doing, where is it that I can
tweak how much punctuation NVDA pronounces?  In playing around I now
have NVDA saying, "Loading NVDA dot dot dot," when loading, as well as
reading way more punctuation than it does by default.  I can't seem to
find the settings I tweaked when experimenting that caused this.)
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

*/Science has become just another voice in the room; it has lost its
platform.  Now, you simply declare your own truth./*

      ~ Dr. Paul A. Offit, in /New York Times/ article, /How
Anti-Vaccine Sentiment Took Hold in the United States/
<https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html>;/,/September
23, 2019

 

 
Re: Focus Highlight and NVDA 2020.1

Tyler Spivey
 

Answering your second question, either press NVDA+p or go to NVDA,
Preferences, Settings, Speech and find Punctuation/symbol level.
Setting it to some should work.

However, the Punctuation/symbol pronunciation dialog can modify what's
said at what level. If you want to reset that, delete
%appdata%\nvda\symbols-en.dic.

On 7/14/2020 12:36 PM, Brian Vogel wrote:
The functionality formerly handled by the Focus Highlight Add-On has
been integrated into the core functionality of NVDA under the Vision
preferences.  However, I have had no success in getting Focus Highlight
to either work in the first place, or have its functionality stick.  I
have uninstalled and reinstalled NVDA, and that didn't fix the issue,
either.

Right now, if I attempt to enable Focus Highlight in the Vision
settings, I am consistently getting the error message, "Could not load
the Focus Highlight vision enhancement provider."

I thought I'd ask here if anyone knew if there was something I have done
to cause this or could do to fix it before I file a trouble ticket on
GitHub.

(As an aside, and I know that this is my doing, where is it that I can
tweak how much punctuation NVDA pronounces?  In playing around I now
have NVDA saying, "Loading NVDA dot dot dot," when loading, as well as
reading way more punctuation than it does by default.  I can't seem to
find the settings I tweaked when experimenting that caused this.)
--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

*/Science has become just another voice in the room; it has lost its
platform.  Now, you simply declare your own truth./*

      ~ Dr. Paul A. Offit, in /New York Times/ article, /How
Anti-Vaccine Sentiment Took Hold in the United States/
<https://www.nytimes.com/2019/09/23/health/anti-vaccination-movement-us.html>;/,/September
23, 2019

 

 
Focus Highlight and NVDA 2020.1

Brian Vogel
 

The functionality formerly handled by the Focus Highlight Add-On has been integrated into the core functionality of NVDA under the Vision preferences.  However, I have had no success in getting Focus Highlight to either work in the first place, or have its functionality stick.  I have uninstalled and reinstalled NVDA, and that didn't fix the issue, either.

Right now, if I attempt to enable Focus Highlight in the Vision settings, I am consistently getting the error message, "Could not load the Focus Highlight vision enhancement provider."

I thought I'd ask here if anyone knew if there was something I have done to cause this or could do to fix it before I file a trouble ticket on GitHub.

(As an aside, and I know that this is my doing, where is it that I can tweak how much punctuation NVDA pronounces?  In playing around I now have NVDA saying, "Loading NVDA dot dot dot," when loading, as well as reading way more punctuation than it does by default.  I can't seem to find the settings I tweaked when experimenting that caused this.)
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 
Re: Possible bug with NVDA and Notepad++

Luke Davis
 

On Tue, 14 Jul 2020, William Wong wrote:

I came across a bug:
This is not a bug. You have conflated (confused) two different kinds of selection.

1. open any txt file with Notepad ++
2. select a start position by nvda f9
That is selecting with review mode. You should then use review commands (number pad in desktop keyboard mode), and then NVDA+F10 when you're finished (possibly twice).

This should only be used when the windows selection commands don't work.

> 3. press ctrl end to move to end of document

You are now moving cursors and such, which changes the screen. That will make review mode commands unpredictable. You can not use cursor movement commands while using review commands, and expect the review commands to keep working.

4. press nvda f10 to mark as end position
The review mode is only intended to work on a static screen. When you start changing the screen out from under it, you can't expect the review mode copy method to work any more. It's not a bug, that's how it's supposed to work. In fact it can't be any other way.

In an environment like NotepadPlusPlus, you can just use normal Windows selection and copy commands. Control+A to select all; Shift and arrow keys to select by character or line; shift and control+arrow keys to select words; Shift and home/end to select to start/end of line; and shift+control+home/end to select to the beginning/end of the document.

You should leave NVDA+F9/F10 out of it in applications like this.

Luke
Re: Possible bug with NVDA and Notepad++

Gene
 

Holding shift and using any movement commands will select text. It isn't just the arrow keys. Control shift home will select the text from where you are to the top of the document. Control shift end will select text to the end of the document.
Shift home will select text from wherever you are on a line to the start of the line. Control end will select text to the end of the line.

Gene

-----Original Message-----
From: William Wong
Sent: Tuesday, July 14, 2020 4:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

Do you know the window way of selecting text?


Do you mean by ctrl shift up or down, left or right to select text?


Gene 於 14/7/2020 17:30 寫道:
The procedure you are using is intended for selecting and copying text when there is no cursor, such as in an error message. Do you know the Windows way of selecting text?

If this bug is a general one, it needs to be corrected but it appears many people use this method for selecting and copying text when the Windows method is available. The Windows method requires less key strokes and should be known because it is a part of Windows and is independent of any screen-reader.

Gene
-----Original Message----- From: zahra
Sent: Tuesday, July 14, 2020 4:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

hello.
i reproduce cant selected text in firefox too.
its not specific for notepad plus plus.

On 7/14/20, William Wong <sine.kazurin@gmail.com> wrote:
Hi,

For the sake of posting replicated issue on Github, I would like to
raise the issue here.


I came across a bug:

1. open any txt file with Notepad ++

2. select a start position by nvda f9

3. press ctrl end to move to end of document

4. press nvda f10 to mark as end position

5. sometimes nvda can perform selection, but will not automatically
speak the selected text, whereas sometimes nvda may say unable to select
text.

I am not sure if this is a bug, or any one can give me any feedback?
thanks.
Re: Automatic Column and Row Header Reading

Cearbhall O'Meadhra
 

Tyler,

 

I normally keep “Tables” unchecked in the document formatting settings in NVDA because NVDA becomes extremely sluggish when it is set and frequently lapses into “Unknown”. When I leave “Tables” unchecked, I can still set the row and column headings and the NVDA response is much sharper.

 

Does this make sense?

 

All the best,

 

Cearbhall

 

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

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sam Taylor via groups.io
Sent: Tuesday, July 14, 2020 12:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Automatic Column and Row Header Reading

 

Thank you, Tyler. No, it wasn't, and this is precisely what I needed to do. I have this off for usual activity, and clearly I'm going to have to set up a trigger. If this isn't mentioned in the documentation along with the need for enabling row/column headers which I did know about, it may be worth including.

Thanks again.

Sam

 

On 14/07/2020 9:31 am, Tyler Spivey wrote:

Is Tables checked in NVDA, Preferences, Settings, Document Formatting?
If not, check it.
 
On 7/13/2020 3:46 PM, Sam Taylor via groups.io wrote:
Thanks Cearbhall,
 
I have constructed a test workbook without any blank lines. Still I
cannot get NVDA to read the coordinates as it should. I have tested with
NVDA 2019 and 2017 with the same result, so I am beginning to wonder
whether there is some type of setting in Excel itself which is causing
this to happen.
 
Thanks
 
Sam
 
 
On 13/07/2020 11:00 pm, Cearbhall O'Meadhra wrote:
 
Sam,
 
 
 
Have you any blank columns separating blocks of columns. If so, you
would need to set the column headings on the first cell in the heading
row of each block to make NVDA call out the column headings for that
block.
 
 
 
All the best,
 
 
 
Cearbhall
 
 
 
m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...
 
 
 
 
 
*From:*nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Sam
Taylor via groups.io
*Sent:* Monday, July 13, 2020 11:08 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Automatic Column and Row Header Reading
 
 
 
Yep, I did that also, but still nothing appears to change. I followed
the example in the Excel with NVDA study material.
 
 
 
 
 
On 13/07/2020 6:00 pm, Quentin Christensen wrote:
 
    You need to tell NVDA where the headers are for it to read them. 
    Press NVDA+shift+c to set column headers and NVDA+shift+r to set
    row headers.  Note that you need to be in the first cell you want
    headers read.
 
     
 
    Quentin
 
     
 
    On Mon, Jul 13, 2020 at 5:30 PM Sam Taylor via groups.io
    <http://groups.io> <samtaylor9@...
    <mailto:me.com@groups.io>> wrote:
 
        Hi all,
 
        11.2.1 of the NVDA user guide mentions that NVDA is able to
        automatically announce appropriate row and column headers when
        navigating around Excel worksheets.
 
        I used to be able to achieve this but it doesn't appear to
        work for me any more, and indeed as of NVDA 2019.3.
 
        The cell coordinates just appear to read as usual, rather than
        reading any additional cell references.
 
        I have enabled the Report Table row / column headers option in
        NVDA's Document Formatting settings.
 
        y duCan anybodyplicate or suggest anything? This is highly
        likely to be user error.
 
        Cheers
 
        Sam
 
         
 
 
     
 
    -- 
 
    Quentin Christensen
    Training and Support Manager
 
     
 
    Web: www.nvaccess.org <http://www.nvaccess.org/> 
 
    Training: https://www.nvaccess.org/shop/
 
    Certification: https://certification.nvaccess.org/
 
    User group: https://nvda.groups.io/g/nvda
 
    Facebook: http://www.facebook.com/NVAccess 
    Twitter: @NVAccess <https://twitter.com/NVAccess>
 
 
 
 
 
Re: Possible bug with NVDA and Notepad++

William
 

Do you know the window way of selecting text?


Do you mean by ctrl shift up or down, left or right to select text?


Gene 於 14/7/2020 17:30 寫道:

The procedure you are using is intended for selecting and copying text when there is no cursor, such as in an error message.  Do you know the Windows way of selecting text?

If this bug is a general one, it needs to be corrected but it appears many people use this method for selecting and copying text when the Windows method is available.  The Windows method requires less key strokes and should be known because it is a part of Windows and is independent of any screen-reader.

Gene
-----Original Message----- From: zahra
Sent: Tuesday, July 14, 2020 4:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

hello.
i reproduce cant selected text in firefox too.
its not specific for notepad plus plus.

On 7/14/20, William Wong <sine.kazurin@gmail.com> wrote:
Hi,

For the sake of posting replicated issue on Github, I would like to
raise the issue here.


I came across a bug:

1. open any txt file with Notepad ++

2. select a start position by nvda f9

3. press ctrl end to move to end of document

4. press nvda f10 to mark as end position

5. sometimes nvda can perform selection, but will not automatically
speak the selected text, whereas sometimes nvda may say unable to select
text.

I am not sure if this is a bug, or any one can give me any feedback?
thanks.
Re: Possible bug with NVDA and Notepad++

Gene
 

The procedure you are using is intended for selecting and copying text when there is no cursor, such as in an error message. Do you know the Windows way of selecting text?

If this bug is a general one, it needs to be corrected but it appears many people use this method for selecting and copying text when the Windows method is available. The Windows method requires less key strokes and should be known because it is a part of Windows and is independent of any screen-reader.

Gene

-----Original Message-----
From: zahra
Sent: Tuesday, July 14, 2020 4:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Possible bug with NVDA and Notepad++

hello.
i reproduce cant selected text in firefox too.
its not specific for notepad plus plus.

On 7/14/20, William Wong <sine.kazurin@gmail.com> wrote:
Hi,

For the sake of posting replicated issue on Github, I would like to
raise the issue here.


I came across a bug:

1. open any txt file with Notepad ++

2. select a start position by nvda f9

3. press ctrl end to move to end of document

4. press nvda f10 to mark as end position

5. sometimes nvda can perform selection, but will not automatically
speak the selected text, whereas sometimes nvda may say unable to select
text.

I am not sure if this is a bug, or any one can give me any feedback?
thanks.







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

Cearbhall O'Meadhra
 

Sam,

 

Are you able to edit text in each individual cell? If not, that might be a pointer to an Excel option that need to be set

 

We used to have to make sure that “Allow editing in cells” under the advanced tab in Excel > Options in order to make NVDA work while editing, for example.

 

All the best,

 

Cearbhall

 

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

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sam Taylor via groups.io
Sent: Monday, July 13, 2020 11:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Automatic Column and Row Header Reading

 

Thanks Cearbhall,

I have constructed a test workbook without any blank lines. Still I cannot get NVDA to read the coordinates as it should. I have tested with NVDA 2019 and 2017 with the same result, so I am beginning to wonder whether there is some type of setting in Excel itself which is causing this to happen.

Thanks

Sam

 

On 13/07/2020 11:00 pm, Cearbhall O'Meadhra wrote:

Sam,

 

Have you any blank columns separating blocks of columns. If so, you would need to set the column headings on the first cell in the heading row of each block to make NVDA call out the column headings for that block.

 

All the best,

 

Cearbhall

 

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

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sam Taylor via groups.io
Sent: Monday, July 13, 2020 11:08 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Automatic Column and Row Header Reading

 

Yep, I did that also, but still nothing appears to change. I followed the example in the Excel with NVDA study material.

 

 

On 13/07/2020 6:00 pm, Quentin Christensen wrote:

You need to tell NVDA where the headers are for it to read them.  Press NVDA+shift+c to set column headers and NVDA+shift+r to set row headers.  Note that you need to be in the first cell you want headers read.

 

Quentin

 

On Mon, Jul 13, 2020 at 5:30 PM Sam Taylor via groups.io <samtaylor9=me.com@groups.io> wrote:

Hi all,

11.2.1 of the NVDA user guide mentions that NVDA is able to automatically announce appropriate row and column headers when navigating around Excel worksheets.

I used to be able to achieve this but it doesn't appear to work for me any more, and indeed as of NVDA 2019.3.

The cell coordinates just appear to read as usual, rather than reading any additional cell references.

I have enabled the Report Table row / column headers option in NVDA's Document Formatting settings.

y duCan anybodyplicate or suggest anything? This is highly likely to be user error.

Cheers

Sam

 


 

--

Quentin Christensen
Training and Support Manager

 
Re: Possible bug with NVDA and Notepad++

zahra
 

hello.
i reproduce cant selected text in firefox too.
its not specific for notepad plus plus.

On 7/14/20, William Wong <sine.kazurin@gmail.com> wrote:
Hi,

For the sake of posting replicated issue on Github, I would like to
raise the issue here.


I came across a bug:

1. open any txt file with Notepad ++

2. select a start position by nvda f9

3. press ctrl end to move to end of document

4. press nvda f10 to mark as end position

5. sometimes nvda can perform selection, but will not automatically
speak the selected text, whereas sometimes nvda may say unable to select
text.

I am not sure if this is a bug, or any one can give me any feedback?
thanks.






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

William
 

Hi,

For the sake of posting replicated issue on Github, I would like to raise the issue here.


I came across a bug:

1. open any txt file with Notepad ++

2. select a start position by nvda f9

3. press ctrl end to move to end of document

4. press nvda f10 to mark as end position

5. sometimes nvda can perform selection, but will not automatically speak the selected text, whereas sometimes nvda may say unable to select text.

I am not sure if this is a bug, or any one can give me any feedback? thanks.
Re: Current status of Tiflotecnia voices?

Socheat Muth
 

Hi all,

Sorry for reviving this topic. But will the new voices be added in the future? I'm asking this because it seems that some new voices are missing. Like, Nathan, and some more new voices that I couldn't remember off the top of my head. They are all in vocalizer expressive V2.2. Again, will the Tiflotecnia's vocalizer gets these voices in the future? If these more voices added, will the customer require to pay for the upgrade?

Many thanks.
Re: Automatic Column and Row Header Reading

Sam Taylor
 

Many thanks Quentin. Works perfectly.


On 14/07/2020 10:11 am, Quentin Christensen wrote:
Good pickup, yes you need to have NVDA set to report "tables", as well as column and row headers in NVDA's document formatting for this to work.  It's not well documented so I will ensure this is updated and noted in the User Guiide and Excel module.

If you otherwise prefer to have reporting of tables off, you can setup a configuration profile for Excel which has this setting enabled:

1) Open Excel
2) Press NVDA+control+p to open the configuration profiles dialog
3) press alt+n to create a new profile
4) Leave the name and press tab once to "use this profile for".
5) press the right arrow to move to "Current application (Excel)
6) Press Enter.

That creates the profile and now any change you make to NVDA's settings while in Excel will be saved in this profile rather than the "normal" profile.

Regards

Quentin.

On Tue, Jul 14, 2020 at 9:48 AM Sam Taylor via groups.io <samtaylor9=me.com@groups.io> wrote:

Thank you, Tyler. No, it wasn't, and this is precisely what I needed to do. I have this off for usual activity, and clearly I'm going to have to set up a trigger. If this isn't mentioned in the documentation along with the need for enabling row/column headers which I did know about, it may be worth including.

Thanks again.

Sam


On 14/07/2020 9:31 am, Tyler Spivey wrote:
Is Tables checked in NVDA, Preferences, Settings, Document Formatting?
If not, check it.

On 7/13/2020 3:46 PM, Sam Taylor via groups.io wrote:

Thanks Cearbhall,

I have constructed a test workbook without any blank lines. Still I
cannot get NVDA to read the coordinates as it should. I have tested with
NVDA 2019 and 2017 with the same result, so I am beginning to wonder
whether there is some type of setting in Excel itself which is causing
this to happen.

Thanks

Sam


On 13/07/2020 11:00 pm, Cearbhall O'Meadhra wrote:

Sam,

 

Have you any blank columns separating blocks of columns. If so, you
would need to set the column headings on the first cell in the heading
row of each block to make NVDA call out the column headings for that
block.

 

All the best,

 

Cearbhall

 

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

 

 

*From:*nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Sam
Taylor via groups.io
*Sent:* Monday, July 13, 2020 11:08 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Automatic Column and Row Header Reading

 

Yep, I did that also, but still nothing appears to change. I followed
the example in the Excel with NVDA study material.

 

 

On 13/07/2020 6:00 pm, Quentin Christensen wrote:

    You need to tell NVDA where the headers are for it to read them. 
    Press NVDA+shift+c to set column headers and NVDA+shift+r to set
    row headers.  Note that you need to be in the first cell you want
    headers read.

     

    Quentin

     

    On Mon, Jul 13, 2020 at 5:30 PM Sam Taylor via groups.io
    <http://groups.io> <samtaylor9@...
    <mailto:me.com@groups.io>> wrote:

        Hi all,

        11.2.1 of the NVDA user guide mentions that NVDA is able to
        automatically announce appropriate row and column headers when
        navigating around Excel worksheets.

        I used to be able to achieve this but it doesn't appear to
        work for me any more, and indeed as of NVDA 2019.3.

        The cell coordinates just appear to read as usual, rather than
        reading any additional cell references.

        I have enabled the Report Table row / column headers option in
        NVDA's Document Formatting settings.

        y duCan anybodyplicate or suggest anything? This is highly
        likely to be user error.

        Cheers

        Sam

         


     

    -- 

    Quentin Christensen
    Training and Support Manager

     

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

    Training: https://www.nvaccess.org/shop/

    Certification: https://certification.nvaccess.org/

    User group: https://nvda.groups.io/g/nvda

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


--
Quentin Christensen
Training and Support Manager
5421 - 5440 of 80826  
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter