Date   

Re: Creating First Line Indent with NVDA

 

I can only answer your second question, and the most simple and concise answer is "consistency."

Using either some set number of spaces or even a tab stop can result in the initial indent being different from paragraph to paragraph.   All it takes is miscounting your spaces or someone having put a section break in where they reset tab stops, and you can get wildly different visual presentations for beginning of paragraph indents.

Using the paragraph controls makes everything consistent without the end user having to do anything other than the initial setup in the document template (which I'd hope would be provided in dotx format if there's a format you're expected to follow).

In the final analysis, for business or anything other than personal purposes, consistent formatting is one of the main reasons to use a word processor or desktop publishing software.   Using the tools that ensure this that are part of those programs is the best, and easiest, way of getting what you want each and every time without the user having to think about it.
--

Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362  

The color of truth is grey.

           ~ André Gide

 

 


Creating First Line Indent with NVDA

David Russell
 

Hello Group,
I am raising the issue of first line indents one more time, but more precise.
This might be for the more technical minded among us. Two questions below.

(1) If setting up paragraph parameters in the ribbon with either
alt+h or alt+o, in MS Word, does the left and right margin need to
exceed a certain parameter in order for NVDA to report each occurrence
first line indent? At 0.5 inch left, and 1 inch right, NVDA reports
first line indent on occasion in my case.

(2) What would be the reason for a sighted MS Word reviewer to
discourage a screen reader user from using the space bar, or tab key
to create first line indents? I have three such friends who encourage
setting this up by the ribbon not doing manually.

Thanks for your help!

--
David Russell
david.sonofhashem@gmail.com


Re: Footnotes in LibreOffice

kelby carlson
 

I am still interested if anybody has suggestions on this issue.

On 12/26/18, Kelby Carlson <kelbycarlson@gmail.com> wrote:
Is there an easy way to navigate to footnotes and endnotes in
LibreOffice using only the keyboard in NVDA? Also, is there a way to
get NVDA to speak the numbers of footnotes when going through the
list? LibreOffice seems much faster and more intuitive than Word and
I'd like to try using it for awhile.

--
Kelby Carlson
--
Kelby Carlson


how to build add-ons for NVDA

Scott Berry <sb356607@...>
 

Hello there,


I would like to learn how to build NVDA add-ons.  I have an idea for one which will download homework assignments and get grades for students in high school and college.  Thanks for all your help.



--
Scott Berry <br>
Certified Medical Office Assistant, Associates in Allied Health, Patient Advocate
Please boogie on over to our site at:
http://www.berrysadvocating.biz


Re: Terminal improvements are coming to NVDA 2019.3!

 

I just now saw this, this is seriously great work. I look forward to testing it out.


Re: Outlook Bug When Scrolling Through Messages

kelby carlson
 

I tried restarting without ad-ons, which also did nothing to improve the situation.


Re: Outlook Bug When Scrolling Through Messages

kelby carlson
 

I did check, and they are the same. How do I send a log?


Re: Outlook Bug When Scrolling Through Messages

Quentin Christensen
 

Maybe double check that the addons are all up to date on the misbehaving computer, just in case (might be same addons but an older version).  If you could send me a log, I can have a look and see if anything pops out.

Quentin.

On Wed, Aug 7, 2019 at 11:31 PM kelby carlson <kelbycarlson@...> wrote:
I don't believe the ad-ons are any different on my laptop than my desktop.

I also have a home laptop with the latest NVDA, WIndows 10, and Outlook, which does not have this problem. This leads me to believe it must have to do with the specific computer, though I can't imagine what the problem is. They are both Lenovo brand.



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


NVDA 2019.2rc2 released

Quentin Christensen
 

Hi everyone,

NVDA 2019.2rc2 has been released. This release fixes a critical bug which made the find dialog unusable for some users.

Read the full release announcement and download NVDA 2019.2rc2 from NV Access: https://www.nvaccess.org/post/nvda-2019-2rc2-released/

As with RC1, we encourage everyone to download and test this version. If nothing critical is found, this will be identical to the final 2019.2 release.

If you do find any errors, please do let us know!

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


Re: Outlook Bug When Scrolling Through Messages

kelby carlson
 

I don't believe the ad-ons are any different on my laptop than my desktop.

I also have a home laptop with the latest NVDA, WIndows 10, and Outlook, which does not have this problem. This leads me to believe it must have to do with the specific computer, though I can't imagine what the problem is. They are both Lenovo brand.


Re: for Qentin or Joseph

Robert Doc Wright godfearer
 

I did that today and still got the same result. When you look into addon manager it shows remote and it states “enabled after restart”. The person I am working with is so backwards where computers are concerned I am not sure what to do next. He is in Clinton Tennessee and I am in Colorado. We have been trying to do this over the telephone.

 

                                                                                                                                If all I have left in this world is God, I have everything!                                                                                                                                                                                                                                                                                                                                                Sent from Mail for Windows 10

 

From: Quentin Christensen
Sent: Monday, August 5, 2019 6:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] for Qentin or Joseph

 

Did you see Jonathan Cohn's reply to your question on this last week?  If so, did that help?

 

His suggestion was: "I have seen this happen when an addon is not completely installed. I ended up going to the
%appdata%\nvda\ directory and finding the semi-installed addon and deleting it"

 

Otherwise, I was going to suggest, a copy of your NVDA log might yield some information.  Based on Jonathan's reply, if that is the issue, uninstalling NVDA won't fix it, as it doesn't remove add-ons.

 

Kind regards

 

Quentin.

 

On Tue, Aug 6, 2019 at 8:47 AM Robert Doc Wright godfearer <godfearer@...> wrote:

I am helping a gentleman who has the latest NVDA and the latest remote. For some reason when he installs the remote addon it sits in addon manager with the statement “enabled after restart”  we have restarted several times and rebooted his win10 c. We even went as far as uninstalling and reinstalling NVDA AND WE STILL GET THE VERY SAME MESSAGE.

 

                                                                                                                                If all I have left in this world is God, I have everything!                                                                                                                                                                                                                                                                                                                                                Sent from Mail for Windows 10

 


 

--

Quentin Christensen
Training and Support Manager

 

NVDA 2019.2 RC 1 now available!

 

 


Re: Bullet levels in Powerpoint

Quentin Christensen
 

It's a tricky one.  If she hasn't changed the font settings, then each indent makes the font smaller.  EG on mine, the leftmost bullet point is 28pt, one indent is 24pt, the 2nd indent is 20pt, then 18pt.

In the paragraph formatting, (alt, h, p, g), it does list the indent.

We do have an issue for this.  I'm not sure whether the problem is PowerPoint not exposing the right information, or NVDA not looking for it.  I'll see if I can find out.  In the meantime, the issue on our tracker is here: https://github.com/nvaccess/nvda/issues/4987 Feel free to comment on that with any additional information.
Kind regards

Quentin.

On Wed, Aug 7, 2019 at 4:07 AM Devin Prater <r.d.t.prater@...> wrote:
Hi all. I have a student working on Powerpoint with NVDA. In a task, the student has to indent bullets on an object. She can input this fine, but how can she quickly check which indentation she’s on on each level? Insert+F doesn’t work, and having NVDA speak indentation doesn’t work either. On NVDA 2019.1.1, Office 2019, Windows 10 1903.




--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


Re: Outlook Bug When Scrolling Through Messages

Quentin Christensen
 

Have you got any add-ons?  If so are they up to date?  If you restart NVDA with add-ons disabled (NVDA+Q, then down arrow to restart with add-ons disabled and enter), does it help?

If you go to your power settings and ensure everything is set to "always on" or "high performance", does that make a difference?

If none of that helps, if you send me a log, I can have a look and see if there's anything obvious inside.

Kind regards

Quentin.

On Wed, Aug 7, 2019 at 3:55 AM kelby carlson <kelbycarlson@...> wrote:
One difference is that the laptop is running Outlook 2016, where the desktop is running Outlook 2013.



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


Re: UI Automated Interface in Word

Quentin Christensen
 

It's basically a different way of getting the information that NVDA needs to tell you what's going on.  Previously NVDA has used iAccessible2 and other APIs to get the information about where the caret is, what is selected, the current font, and so on.

Microsoft is starting to providing more of this information using UI Automation instead of iAccessible2, so this setting is basically a way of starting to transition to use that to get information in Word.  At this time, not every piece of information we currently provide is available through UIA, however, we can't pick and choose and take some from each - we need to get all our information using one method or the other.

So, for now, we are still using the older methods as the default, but if you are doing a particular task for which the information is only available through UIA, or if you would like to try out that option (particularly for add-on developers who might be impacted by such a change), the option is there on the developer options.

Kind regards

Quentin.

On Wed, Aug 7, 2019 at 3:31 AM kelby carlson <kelbycarlson@...> wrote:
Can someone explain what exactly is supposed to happen when this is
turned on? I notice some changes; some are positive, like more ease in
handling lists. Some, however, are very negative, like NVDA saying
"read only" even in documents that can be edited, and not detecting
track changes when the UI setting is turned on. Unfortunately the User
Guide does not explain much about this. Can anyone help?

--
Kelby Carlson





--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


Re: Terminal improvements are coming to NVDA 2019.3!

g melconian <gmelconian619@...>
 

Sure, will do so when I have some free testing time. Have so many projects at the moment which have my attention. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Bill Dengler
Sent: Tuesday, August 6, 2019 12:36 PM
To: nvda@groups.io
Subject: [nvda] Terminal improvements are coming to NVDA 2019.3!

 

Hello,

I’ve been working as a Google Summer of Code student with NV Access over the past couple of months. My project involves improving NVDA performance and stability in the Windows Console used by Command Prompt, PowerShell, and the Windows Subsystem for Linux on Windows 10 version 1803 and later.

The new console support is set to ship as part of NVDA 2019.3, to be released later this year. In the mean time, I’d greatly appreciate your testing of, and feedback from, the latest master (alpha) snapshots, which can be found on this page. A limited version of the new support will also ship in 2019.2 within the next few weeks behind a feature flag.

 

Thanks in advance for testing, and be sure to let me know what you think!

Bill


Re: Terminal improvements are coming to NVDA 2019.3!

 

Hi Bill,

I may need to write a detailed feedback on GitHub, but your code doesn’t work on Windows Terminal Preview app yet- not recognized as  UIA control at this time).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Bill Dengler
Sent: Tuesday, August 6, 2019 12:36 PM
To: nvda@groups.io
Subject: [nvda] Terminal improvements are coming to NVDA 2019.3!

 

Hello,

I’ve been working as a Google Summer of Code student with NV Access over the past couple of months. My project involves improving NVDA performance and stability in the Windows Console used by Command Prompt, PowerShell, and the Windows Subsystem for Linux on Windows 10 version 1803 and later.

The new console support is set to ship as part of NVDA 2019.3, to be released later this year. In the mean time, I’d greatly appreciate your testing of, and feedback from, the latest master (alpha) snapshots, which can be found on this page. A limited version of the new support will also ship in 2019.2 within the next few weeks behind a feature flag.

 

Thanks in advance for testing, and be sure to let me know what you think!

Bill


Request for addition of a Braille section to the Switching From JAWS To NVDA Guide

Kara Goldfinch
 

Hi everyone.

As some of you may be aware,  I did the initial work for the Switching from JAWS To NVDA guide, which anyone is free to edit and add to. Many have done so over the years so thank you for that.

Currently though, the guide doesn't have any info on Braille support for both products as  I have only briefly used a Braille display, and it was long before I started this project.

If anyone feels confident enough to add a section on Braille, then please feel free to do so.

You can find the guide at the following address:

https://github.com/nvaccess/nvda-community/wiki/SwitchingFromJawsToNVDA

You will need a github account and a familiarity with Markdown. It's fairly easy to learn and there is plenty of info available.

All the best,,

Kara Goldfinch

Certified Expert               
View the list of all NVDA Experts


Terminal improvements are coming to NVDA 2019.3!

Bill Dengler
 

Hello,
I’ve been working as a Google Summer of Code student with NV Access over the past couple of months. My project involves improving NVDA performance and stability in the Windows Console used by Command Prompt, PowerShell, and the Windows Subsystem for Linux on Windows 10 version 1803 and later.
The new console support is set to ship as part of NVDA 2019.3, to be released later this year. In the mean time, I’d greatly appreciate your testing of, and feedback from, the latest master (alpha) snapshots, which can be found on this page. A limited version of the new support will also ship in 2019.2 within the next few weeks behind a feature flag.

Thanks in advance for testing, and be sure to let me know what you think!
Bill


StationPlaylist add-on 19.08.1 and 18.09.11-LTS, plans for the long-term suport version #addonrelease

 

Hi all,

 

StationPlaylist add-on 19.08.1 and 18.09.11-LTS are now available. The key difference between these two versions is which SPL suite is the minimum – 19.08.x supports SPL 5.20, and 18.09.11-LTS supports 5.1x. As always, these releases can be found on community add-ons website or through Add-on updater.

 

Today’s releases are bug fix releases. Both include fixes for encoder support, add-on settings, and for 19.08.x, a specific problem related to starting Studio.

 

Also, a note on future 18.09.x releases:

 

  • I expect two more releases in 18.09.x series – one in October and another one shortly after NVDA 2019.3 is released.
  • Support for 18.09.x (and consequently, Studio 5.1x) will cease on December 31, 2019 or at least 30 days after NVDA 2019.3 stable version is released, whichever happens earlier. I’ll announce the exact end of life date then.
  • 18.09.x is Python 2 and 3 compatible.

 

Cheers,

Joseph


Re: Acapela TTS for NVDA

 

Hi,

Although there hasn’t been a deadline set yet, the ideal completion is around 2019.3 beta, or by RC at the latest.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dark Count
Sent: Tuesday, August 6, 2019 10:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Acapela TTS for NVDA

 

I was told by support they are in contact with NVDA dev to transition to python 3.

But no deadlines were given.

 

D C

 

On 8/6/2019 9:31 AM, Luis Carlos Gonzáles Moráles wrote:

Hi group,

It seems that Acapela TTS Voices for NVDA hasn’t been updated for one year or so. Is there some hiyatus or has been the development stopped or something? I’m kinda woried that happens, Since that addon doesn’t support Python 3 at the momento.

Shukrán.  

 

Enviado desde Correo para Windows 10