i did not understand.
i wish to turn off announcing graphic in nvda.
how should i do it?
i even disabled reporting headings, links, tables, etc in document formatting,
and as i said, only let comment and page number to be remained check!
On 6/11/18, Brian's Mail list account via Groups.Io
<bglists@...> wrote:

actually, none of the three format announcing property sheets seems to
have a way of selectable just stopping the announcement of the object type
if its a graphics. Sure you can turn off object type announcements but this

one supposes then leaves you a little in the dark about everything else. I
think, personally, I've come to live with this, making sure that when I hear

the word start to be spoken I go away or hit control to shut it up.
It is giving valuable info of course and its a sad fact of our lives that
telling us what is on the screen to help us understand layout is one of the

problems. While its telling us about buttons and their state ie pressed or
not it also tells us if the bit we are on is a graphic and even a graphic
button indeed.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Rui Fontes" <rui.fontes@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 10, 2018 3:10 PM
Subject: Re: [nvda] how can i set nvda that never announce graphic graphic
out of graphic?

Sorry! It is on Document formating...

Rui


Às 15:02 de 10/06/2018, zahra escreveu:

which item in brows mode should i change that not hear graphic anymore?
i did not find in brows mode or in other preferences one option
related to graphic, so i decided to ask here.

On 6/10/18, Rui Fontes <rui.fontes@...> wrote:

NVDA menu, Preferences, Browse mode...

Rui


Às 14:44 de 10/06/2018, zahra escreveu:

hello every one.
like gene, recently i changed my mind and decided to give chrome a
try.
it is very greater than firefox in stability, speed, and handling big
and dynamic web pages like quora which i subscribed and answered
hundreds of questions.
however, when nvda sees a title or the name of one person, first says
graphic, graphic and when i navigate by word nvda says graphic and out
of graphic!
i dont want to hear graphic at all!
what should i do in nvda to achieve this?
it even says
graphic sometimes both before and after the names!
for example: graphic zahra, zahra graphic.
i realy hate hearing anything except the content that i read or want
to interact with.
thanks so much for any help, God bless all!

Try using the speech dictionary to stop graphic from being spoken. I
suspect it will work.

Gene
----- Origiinal Message -----

From: Brian's Mail list account via Groups.Io
Sent: Monday, June 11, 2018 2:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] how can i set nvda that never announce graphic graphic
out of graphic?


actually, none of the three format announcing property sheets seems to
have a way of selectable just stopping the announcement of the object type
if its a graphics. Sure you can turn off object type announcements but this

one supposes then leaves you a little in the dark about everything else. I
think, personally, I've come to live with this, making sure that when I hear

the word start to be spoken I go away or hit control to shut it up.
It is giving valuable info of course and its a sad fact of our lives that
telling us what is on the screen to help us understand layout is one of the

problems. While its telling us about buttons and their state ie pressed or
not it also tells us if the bit we are on is a graphic and even a graphic
button indeed.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Rui Fontes" <rui.fontes@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 10, 2018 3:10 PM
Subject: Re: [nvda] how can i set nvda that never announce graphic graphic
out of graphic?

Sorry! It is on Document formating...

Rui


Às 15:02 de 10/06/2018, zahra escreveu:

which item in brows mode should i change that not hear graphic anymore?
i did not find in brows mode or in other preferences one option
related to graphic, so i decided to ask here.

On 6/10/18, Rui Fontes <rui.fontes@...> wrote:

NVDA menu, Preferences, Browse mode...

Rui


Às 14:44 de 10/06/2018, zahra escreveu:

hello every one.
like gene, recently i changed my mind and decided to give chrome a
try.
it is very greater than firefox in stability, speed, and handling big
and dynamic web pages like quora which i subscribed and answered
hundreds of questions.
however, when nvda sees a title or the name of one person, first says
graphic, graphic and when i navigate by word nvda says graphic and out
of graphic!
i dont want to hear graphic at all!
what should i do in nvda to achieve this?
it even says
graphic sometimes both before and after the names!
for example: graphic zahra, zahra graphic.
i realy hate hearing anything except the content that i read or want
to interact with.
thanks so much for any help, God bless all!

Information on the rather handy new issue URL should also be included. If you want to create an issue directly, you can also go to https://github.com/nvaccess/nvda/issues/new

On 6/10/2018 8:44 PM, Gene New Zealand wrote:

Hi guys

I am putting together a tutorial on making a ticket for nvda in git hub. I know there are users here who do not know how to create one or even where to go or what to do.

I know when i do it I put in as much info as i can so hopefully it can be fixed. I just do not want to over do it and make it confusing if they do not have to do it when doing a ticket.

This is in draft so for give any mistakes.

Is there stuff i should put into it that i might of left out remember it is for a new user.

I will paste in what i have done so far so it can be moved around and is in draft or parts added or deleted.

Reporting an issue/bug report to NVACCESS

 

Where to go to issue a bug to be fixed

 

 

If you are a user of the NVDA screen reader wheather you use the next snap shot alfa code, the Master snap shot beata code or the stable version of NVDA that is released to the public, if you come across a bug it can be reported at the following web page at https://github.com/nvaccess/nvda/issues

 

Getting a Git hub account or simply signing in

 

To report any issues to be fixed you must have a Git Hub account.  .

If you do not have a Git Hub account you will need to go to the sign up link then press the enter key. It will ask you for a user name, email address, password and once done locate the create a account button then press the space bar or enter key for it to be created.

If you already have a account it is just a matter of locating the sign in link and entering your details to log into git hub.

 

 

After you have signed into git hub

 

 

After you have signed into git hub to report a issue on your page you will have some links and buttons and headings. The first button is a search button, the second a create new button, the third a view profile and more button, and a sign out button.

Searching for a issue on git hub

 

 

Before you report a issue/bug report to NVACCESS you will need to do a search to see if any one else has reported the bug. If one can not be found then you will need to open a new new issue. This is a button.

 

 

There are some other buttons there but the one you want is new issue button. Press the enter key on it and a new section will come up and ask you the following.

 

You can arrow through the page to see all the sections.

 

Press the enter key on this button and a new section will appear. You can arrow up and down this page to get all the information there or jump around with B for buttons

 

As you go down the page you will hear the following.

This may depend if you arrow down the page or jump down by buttons. If you jump down by buttons you will hear the following. For example add header text button, add bold text button, add atalic text button, insert a quote button, insert code button, add a link button, add a bulleted list button, add a numbered list button, add a task list button, insert a reply button, Directly mention a user or team, Reference an issue or pull request, browse button, submit new issue button.

You may find it easier to arrow through rather than use single letter navigation keys to get all of the information.

 

They will need to know the following In the header text edit area what the issue is. For example

 

Under the ### Steps to reproduce:

> A list of the steps you take to demonstrate the problem.

> 

> Example:

> 

> 1. Open Chrome

> 2. Browse to www.google.com

> 3. Type "Hello"

> 4. Notice an error sound when enter is pressed.

 

> Please also remember to attach a zip of any files required to reproduce the issue.

 

### Expected behavior:

> Tell us what should happen.

 

### Actual behavior:

> Tell us what happens instead.

 

They will also need to know the NVDA version wheather it is a next-14027,c80e529f

 Snap shot, or a master snap shot with its version number. Also wheather it is a portable or installed version of NVDA.

 

They may need other information such as if it was > Example: Running in a VM

 

Windows version:

> Example: Windows 10 Version 1607 Build 14393.1066

 

### Other questions:

 

Does the issue still occur after restarting your PC?

 

Have you tried any other versions of NVDA?

> Please list them and the result

 

Browse…

No files selected.

Attach files by dragging & dropping, selecting them, or pasting from the clipboard. 

 

Under this section would be where you would post your NVDA log.

 

Make sure under the general settings in NVDA it is set to Logging level: debug

 

 

After you have filled in the information that that they require locate the submit new issue button and your ticket will be created.

Please note

 

 

For NVACCESS to try and track down any bugs to be fixed you need to have the steps to recreate the problem you are having. Make sure your Logging level: is set to debug is set under the General settings in NVDA. You can also obtain the log which it produces from the Tool.. view log section in NVDA. A log will be produced after you press the enter key on the view log menu. Press the ALT key until a menu drops down then arrow down to you hear NVDA say save log as then press the ENTER key. NVDA will default to the file name then it is a matter of tabbing until you hear a location to save to you are happy with such as the Desk top then shift/tabbing back to the save button then pressing the enter key on the save button.

 

   

For more information on using Git Hub with a screen reader which goes beyond making a ticket please go to the following link at http://bats.fyi/2016/08/19/mastering-github-with-a-screen-reader-part-1/

 

 

 

 

 

 

Gene nz

Hi guys


I am putting together a tutorial on making a ticket for nvda in git hub. I know there are users here who do not know how to create one or even where to go or what to do.


I know when i do it I put in as much info as i can so hopefully it can be fixed. I just do not want to over do it and make it confusing if they do not have to do it when doing a ticket.

This is in draft so for give any mistakes.


Is there stuff i should put into it that i might of left out remember it is for a new user.


I will paste in what i have done so far so it can be moved around and is in draft or parts added or deleted.

Reporting an issue/bug report to NVACCESS

Where to go to issue a bug to be fixed


If you are a user of the NVDA screen reader wheather you use the next snap shot alfa code, the Master snap shot beata code or the stable version of NVDA that is released to the public, if you come across a bug it can be reported at the following web page at https://github.com/nvaccess/nvda/issues

Getting a Git hub account or simply signing in

To report any issues to be fixed you must have a Git Hub account. .
If you do not have a Git Hub account you will need to go to the sign up link then press the enter key. It will ask you for a user name, email address, password and once done locate the create a account button then press the space bar or enter key for it to be created.
If you already have a account it is just a matter of locating the sign in link and entering your details to log into git hub.


After you have signed into git hub


After you have signed into git hub to report a issue on your page you will have some links and buttons and headings. The first button is a search button, the second a create new button, the third a view profile and more button, and a sign out button.
Searching for a issue on git hub


Before you report a issue/bug report to NVACCESS you will need to do a search to see if any one else has reported the bug. If one can not be found then you will need to open a new new issue. This is a button.


There are some other buttons there but the one you want is new issue button. Press the enter key on it and a new section will come up and ask you the following.

You can arrow through the page to see all the sections.

Press the enter key on this button and a new section will appear. You can arrow up and down this page to get all the information there or jump around with B for buttons

As you go down the page you will hear the following.
This may depend if you arrow down the page or jump down by buttons. If you jump down by buttons you will hear the following. For example add header text button, add bold text button, add atalic text button, insert a quote button, insert code button, add a link button, add a bulleted list button, add a numbered list button, add a task list button, insert a reply button, Directly mention a user or team, Reference an issue or pull request, browse button, submit new issue button.
You may find it easier to arrow through rather than use single letter navigation keys to get all of the information.

They will need to know the following In the header text edit area what the issue is. For example

Under the ### Steps to reproduce:

A list of the steps you take to demonstrate the problem.

Example:

1. Open Chrome
2. Browse to www.google.com<http://www.google.com>
3. Type "Hello"
4. Notice an error sound when enter is pressed.

Please also remember to attach a zip of any files required to reproduce the issue.

### Expected behavior:

Tell us what should happen.

### Actual behavior:

Tell us what happens instead.

They will also need to know the NVDA version wheather it is a next-14027,c80e529f
Snap shot, or a master snap shot with its version number. Also wheather it is a portable or installed version of NVDA.

They may need other information such as if it was > Example: Running in a VM

Windows version:

Example: Windows 10 Version 1607 Build 14393.1066

### Other questions:

Does the issue still occur after restarting your PC?

Have you tried any other versions of NVDA?

Please list them and the result

Browse…
No files selected.
Attach files by dragging & dropping, selecting them, or pasting from the clipboard.

Under this section would be where you would post your NVDA log.

Make sure under the general settings in NVDA it is set to Logging level: debug


After you have filled in the information that that they require locate the submit new issue button and your ticket will be created.
Please note


For NVACCESS to try and track down any bugs to be fixed you need to have the steps to recreate the problem you are having. Make sure your Logging level: is set to debug is set under the General settings in NVDA. You can also obtain the log which it produces from the Tool.. view log section in NVDA. A log will be produced after you press the enter key on the view log menu. Press the ALT key until a menu drops down then arrow down to you hear NVDA say save log as then press the ENTER key. NVDA will default to the file name then it is a matter of tabbing until you hear a location to save to you are happy with such as the Desk top then shift/tabbing back to the save button then pressing the enter key on the save button.


For more information on using Git Hub with a screen reader which goes beyond making a ticket please go to the following link at http://bats.fyi/2016/08/19/mastering-github-with-a-screen-reader-part-1/








Gene nz

Hi, John,


Gene NZ has a great tutorial on his web site which is
www.accessibilitycentral.net. It's under audio tutorials.


Hope this helps.


Rosemarie




On 6/10/2018 7:06 PM, John J. Boyer wrote:

Thanks,
John

i did not understand.
i wish to turn off announcing graphic in nvda.
how should i do it?
i even disabled reporting headings, links, tables, etc in document
formatting,
and as i said, only let comment and page number to be remained check!

On 6/11/18, Brian's Mail list account via Groups.Io
<bglists@...> wrote:

actually, none of the three format announcing property sheets seems to
have a way of selectable just stopping the announcement of the object
type
if its a graphics. Sure you can turn off object type announcements but
this

one supposes then leaves you a little in the dark about everything else.
I
think, personally, I've come to live with this, making sure that when I
hear

the word start to be spoken I go away or hit control to shut it up.
It is giving valuable info of course and its a sad fact of our lives that
telling us what is on the screen to help us understand layout is one of
the

problems. While its telling us about buttons and their state ie pressed
or
not it also tells us if the bit we are on is a graphic and even a graphic
button indeed.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Rui Fontes" <rui.fontes@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, June 10, 2018 3:10 PM
Subject: Re: [nvda] how can i set nvda that never announce graphic
graphic
out of graphic?

Sorry! It is on Document formating...

Rui


Às 15:02 de 10/06/2018, zahra escreveu:

which item in brows mode should i change that not hear graphic anymore?
i did not find in brows mode or in other preferences one option
related to graphic, so i decided to ask here.

On 6/10/18, Rui Fontes <rui.fontes@...> wrote:

NVDA menu, Preferences, Browse mode...

Rui


Às 14:44 de 10/06/2018, zahra escreveu:

hello every one.
like gene, recently i changed my mind and decided to give chrome a
try.
it is very greater than firefox in stability, speed, and handling big
and dynamic web pages like quora which i subscribed and answered
hundreds of questions.
however, when nvda sees a title or the name of one person, first says
graphic, graphic and when i navigate by word nvda says graphic and
out
of graphic!
i dont want to hear graphic at all!
what should i do in nvda to achieve this?
it even says
graphic sometimes both before and after the names!
for example: graphic zahra, zahra graphic.
i realy hate hearing anything except the content that i read or want
to interact with.
thanks so much for any help, God bless all!

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

Sorry! It is on Document formating...

Rui


Às 15:02 de 10/06/2018, zahra escreveu:

which item in brows mode should i change that not hear graphic anymore?
i did not find in brows mode or in other preferences one option
related to graphic, so i decided to ask here.

On 6/10/18, Rui Fontes <rui.fontes@...> wrote:

NVDA menu, Preferences, Browse mode...

Rui


Às 14:44 de 10/06/2018, zahra escreveu:

hello every one.
like gene, recently i changed my mind and decided to give chrome a try.
it is very greater than firefox in stability, speed, and handling big
and dynamic web pages like quora which i subscribed and answered
hundreds of questions.
however, when nvda sees a title or the name of one person, first says
graphic, graphic and when i navigate by word nvda says graphic and out
of graphic!
i dont want to hear graphic at all!
what should i do in nvda to achieve this?
it even says
graphic sometimes both before and after the names!
for example: graphic zahra, zahra graphic.
i realy hate hearing anything except the content that i read or want
to interact with.
thanks so much for any help, God bless all!

Hi guys

I am putting together a tutorial on making a ticket for nvda in git hub. I know there are users here who do not know how to create one or even where to go or what to do.

I know when i do it I put in as much info as i can so hopefully it can be fixed. I just do not want to over do it and make it confusing if they do not have to do it when doing a ticket.

This is in draft so for give any mistakes.

Is there stuff i should put into it that i might of left out remember it is for a new user.

I will paste in what i have done so far so it can be moved around and is in draft or parts added or deleted.

Reporting an issue/bug report to NVACCESS

 

Where to go to issue a bug to be fixed

 

 

If you are a user of the NVDA screen reader wheather you use the next snap shot alfa code, the Master snap shot beata code or the stable version of NVDA that is released to the public, if you come across a bug it can be reported at the following web page at https://github.com/nvaccess/nvda/issues

 

Getting a Git hub account or simply signing in

 

To report any issues to be fixed you must have a Git Hub account.  .

If you do not have a Git Hub account you will need to go to the sign up link then press the enter key. It will ask you for a user name, email address, password and once done locate the create a account button then press the space bar or enter key for it to be created.

If you already have a account it is just a matter of locating the sign in link and entering your details to log into git hub.

 

 

After you have signed into git hub

 

 

After you have signed into git hub to report a issue on your page you will have some links and buttons and headings. The first button is a search button, the second a create new button, the third a view profile and more button, and a sign out button.

Searching for a issue on git hub

 

 

Before you report a issue/bug report to NVACCESS you will need to do a search to see if any one else has reported the bug. If one can not be found then you will need to open a new new issue. This is a button.

 

 

There are some other buttons there but the one you want is new issue button. Press the enter key on it and a new section will come up and ask you the following.

 

You can arrow through the page to see all the sections.

 

Press the enter key on this button and a new section will appear. You can arrow up and down this page to get all the information there or jump around with B for buttons

 

As you go down the page you will hear the following.

This may depend if you arrow down the page or jump down by buttons. If you jump down by buttons you will hear the following. For example add header text button, add bold text button, add atalic text button, insert a quote button, insert code button, add a link button, add a bulleted list button, add a numbered list button, add a task list button, insert a reply button, Directly mention a user or team, Reference an issue or pull request, browse button, submit new issue button.

You may find it easier to arrow through rather than use single letter navigation keys to get all of the information.

 

They will need to know the following In the header text edit area what the issue is. For example

 

Under the ### Steps to reproduce:

> A list of the steps you take to demonstrate the problem.

> 

> Example:

> 

> 1. Open Chrome

> 2. Browse to www.google.com

> 3. Type "Hello"

> 4. Notice an error sound when enter is pressed.

 

> Please also remember to attach a zip of any files required to reproduce the issue.

 

### Expected behavior:

> Tell us what should happen.

 

### Actual behavior:

> Tell us what happens instead.

 

They will also need to know the NVDA version wheather it is a next-14027,c80e529f

 Snap shot, or a master snap shot with its version number. Also wheather it is a portable or installed version of NVDA.

 

They may need other information such as if it was > Example: Running in a VM

 

Windows version:

> Example: Windows 10 Version 1607 Build 14393.1066

 

### Other questions:

 

Does the issue still occur after restarting your PC?

 

Have you tried any other versions of NVDA?

> Please list them and the result

 

Browse…

No files selected.

Attach files by dragging & dropping, selecting them, or pasting from the clipboard. 

 

Under this section would be where you would post your NVDA log.

 

Make sure under the general settings in NVDA it is set to Logging level: debug

 

 

After you have filled in the information that that they require locate the submit new issue button and your ticket will be created.

Please note

 

 

For NVACCESS to try and track down any bugs to be fixed you need to have the steps to recreate the problem you are having. Make sure your Logging level: is set to debug is set under the General settings in NVDA. You can also obtain the log which it produces from the Tool.. view log section in NVDA. A log will be produced after you press the enter key on the view log menu. Press the ALT key until a menu drops down then arrow down to you hear NVDA say save log as then press the ENTER key. NVDA will default to the file name then it is a matter of tabbing until you hear a location to save to you are happy with such as the Desk top then shift/tabbing back to the save button then pressing the enter key on the save button.

 

   

For more information on using Git Hub with a screen reader which goes beyond making a ticket please go to the following link at http://bats.fyi/2016/08/19/mastering-github-with-a-screen-reader-part-1/

 

 

 

 

 

 

Gene nz

I use Internet Explorer for mobile Facebook, and NVDA works fine.

Which browser are you using?

David Moore

Sent from Mail for Windows 10

 

From: marcio via Groups.Io
Sent: Sunday, June 10, 2018 3:12 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Here again, this time asking really about NVDA

 

I ended up concluding that it's a problem from Mobile Facebook page.
I've tested it on other websites and surprisingly this doesn't happen.
Out of the mentioned page, it's alright.
Em 10/06/2018 13:29, Sarah k Alawami escreveu:

So are you saying that only in brose mode you can hear the �radio buttons. I think this was also the case on a job application I was reading as well. I had to go into browse mode to check but that was maybe a month ago. I just never �thought about it as I am always in browse mode when trying to fill out forms and stuff.

On Jun 10, 2018, at 1:24 AM, marcio via Groups.Io <marcinhorj21@...> wrote:

 

Strange. Maybe it's happening only with me?...

Em 10/06/2018 05:17, Joseph Lee escreveu:

Hi,
Yes, the mobile interface (m.facebook.com).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of marcio via Groups.Io
Sent: Sunday, June 10, 2018 1:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Here again, this time asking really about NVDA

Actually, I only can check/uncheck one of those buttons if �I'm with the browse mode. With the focus mode I can do nothing about it.
You're using m.facebook as I said?
Em 10/06/2018 04:56, Joseph Lee escreveu:

Hi,
So when I try to delete a post with Firefox, when I press Enter on the radio button, NVDA switches me to focus mode and I can then use up and down arrow keys to select a different radio button. NVDA announces selection status as it should. This was also observed with Internet Explorer.
I get a feeling that, perhaps with browse mode, radio button selection status isn't announced right. Is this correct? If so, and if other folks can reproduce this with 2018.1.x:
* If this happens with 2018.1.x as well, then this is either differences in rendering engines, or Facebook made a server-side change.
* If this problem does not happen with 2018.1.x, then it might be 2018.2 issue.
Note that I'm testing these scenarios with latest NVDA next snapshots running on Windows 10.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph
Lee
Sent: Sunday, June 10, 2018 12:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Here again, this time asking really about NVDA

Hi,
Okay, we're getting somewhere. Can someone try to reproduce this, and if possible, with other web browsers such as IE, Chrome, and Edge please? Once we get folks to try and reproduce this, we'll know if this is an NVDA regression, browser rendering differences, or something else.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of marcio
via Groups.Io
Sent: Sunday, June 10, 2018 12:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Here again, this time asking really about NVDA

I'm using Firefox, latest version, on the mobile Facebook page.
I was trying to delete a post, so I had to check the button to do it.
Then I noticed this.
Em 10/06/2018 04:39, Joseph Lee escreveu:

Hi there,
Hmmm, I see. Can you go into specifics such as which Facebook page to visit (preferably a public page), whether it is for regular or mobile interface, and web browser you're using?

P.S. For those attending a certain seminar in a few weeks, I'll mention this email thread as a possible case study regarding user interactions and questions to ask them.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of marcio
via Groups.Io
Sent: Sunday, June 10, 2018 12:33 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Here again, this time asking really about NVDA

Any Facebook page with this buttons is having that behavior.
Em 10/06/2018 04:24, Joseph Lee escreveu:

Hello,
Can you tell us how we can reproduce this problem please? Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of marcio
via Groups.Io
Sent: Sunday, June 10, 2018 12:21 AM
To: nvda@nvda.groups.io
Subject: [nvda] Here again, this time asking really about NVDA

So, guys, I'm here again :)
This time, I have a question abo ���ut the latest version of NVDA.
In earlier versions, when I had a radio button I could know if it was checked or unchecked.
Now I can't. I don't know if it's something changed on NVDA itself or if it's happening only with me.
If it's something new from this version, I would like to know how I can do my NVDA back to speak the button's status.

Thanks in advance

Marcio

 

 

 

 

Thanks,
John

Thanks,
John

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

From: Howard Traxler

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 8:38 PM

Subject: Re: [nvda] password remover

Sorry folks, I know this does not relate to NVDA, but it's my response to Kerryn.

 

Kerryn,

 

 

Here is a solution to the password problem that I have found.  Others here who are much wiser than I will not recommend it and I have not tried it yet; but I think I'm going to.  The software that you download will create a bootable CD that one would used to boot the computer in question.  A program, supposedly, comes up that allows you to do things with your password.  One of them is to remove it.

 

It's kind of a last resort thing for me; but it's the only way I will be able to access this computer.  Others say to reinstall windows; but I don't know of a computer today that comes with an install CD.  I assume there are many packages of this type; but the one I downloaded can be found at:

 

https://www.isumsoft.com/windows-password-refixer/

 

Good luck.

 

Howard

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

From: Kerryn Gunness via GroupsIo

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 6:06 PM

Subject: Re: [nvda] password remover

thanks brian

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 7:00 PM

Subject: Re: [nvda] password remover

Kerryn,

          No, it will not.

          Passwords exist for a reason:  the security of the owner and their data.  It is incumbent on those setting passwords to do what they require to have access to them if they cannot remember them.  Password security (as in the ability to manipulate them by the admin) has gotten progressively tighter over the years, and for good reason.

          In the case of a Windows 10 computer if one does not have the password you can reinstall Windows 10.  You can also extract data from the hard drive using another computer and connecting it as an external drive.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.

          ~ H.L. Mencken, AKA The Sage of Baltimore

 

 

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

From: Howard Traxler

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 8:38 PM

Subject: Re: [nvda] password remover

Sorry folks, I know this does not relate to NVDA, but it's my response to Kerryn.

 

Kerryn,

 

 

Here is a solution to the password problem that I have found.  Others here who are much wiser than I will not recommend it and I have not tried it yet; but I think I'm going to.  The software that you download will create a bootable CD that one would used to boot the computer in question.  A program, supposedly, comes up that allows you to do things with your password.  One of them is to remove it.

 

It's kind of a last resort thing for me; but it's the only way I will be able to access this computer.  Others say to reinstall windows; but I don't know of a computer today that comes with an install CD.  I assume there are many packages of this type; but the one I downloaded can be found at:

 

https://www.isumsoft.com/windows-password-refixer/

 

Good luck.

 

Howard

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

From: Kerryn Gunness via GroupsIo

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 6:06 PM

Subject: Re: [nvda] password remover

thanks brian

 

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

From: Brian Vogel

To: nvda@nvda.groups.io

Sent: Sunday, June 10, 2018 7:00 PM

Subject: Re: [nvda] password remover

Kerryn,

          No, it will not.

          Passwords exist for a reason:  the security of the owner and their data.  It is incumbent on those setting passwords to do what they require to have access to them if they cannot remember them.  Password security (as in the ability to manipulate them by the admin) has gotten progressively tighter over the years, and for good reason.

          In the case of a Windows 10 computer if one does not have the password you can reinstall Windows 10.  You can also extract data from the hard drive using another computer and connecting it as an external drive.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.

          ~ H.L. Mencken, AKA The Sage of Baltimore

 

 

Hi Gene!

Thanks a lot for this!

I already have an account on Github, but I did not know where to even start!

This will help a lot!

David Moore

Sent from Mail for Windows 10

 

From: Gene New Zealand
Sent: Sunday, June 10, 2018 8:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Feed back on creating a ticket in git hub with nvda

 

Hi guys

 

I am putting together a tutorial on making a ticket for nvda in git hub. I know there are users here who do not know how to create one or even where to go or what to do.

 

I know when i do it I put in as much info as i can so hopefully it can be fixed. I just do not want to over do it and make it confusing if they do not have to do it when doing a ticket.

This is in draft so for give any mistakes.

 

Is there stuff i should put into it that i might of left out remember it is for a new user.

 

I will paste in what i have done so far so it can be moved around and is in draft or parts added or deleted.

 

Reporting an issue/bug report to NVACCESS

 

Where to go to issue a bug to be fixed

 

 

If you are a user of the NVDA screen reader wheather you use the next snap shot alfa code, the Master snap shot beata code or the stable version of NVDA that is released to the public, if you come across a bug it can be reported at the following web page at https://github.com/nvaccess/nvda/issues

 

Getting a Git hub account or simply signing in

 

To report any issues to be fixed you must have a Git Hub account.  .

If you do not have a Git Hub account you will need to go to the sign up link then press the enter key. It will ask you for a user name, email address, password and once done locate the create a account button then press the space bar or enter key for it to be created.

If you already have a account it is just a matter of locating the sign in link and entering your details to log into git hub.

 

 

After you have signed into git hub

 

 

After you have signed into git hub to report a issue on your page you will have some links and buttons and headings. The first button is a search button, the second a create new button, the third a view profile and more button, and a sign out button.

Searching for a issue on git hub

 

 

Before you report a issue/bug report to NVACCESS you will need to do a search to see if any one else has reported the bug. If one can not be found then you will need to open a new new issue. This is a button.

 

 

There are some other buttons there but the one you want is new issue button. Press the enter key on it and a new section will come up and ask you the following.

 

You can arrow through the page to see all the sections.

 

Press the enter key on this button and a new section will appear. You can arrow up and down this page to get all the information there or jump around with B for buttons

 

As you go down the page you will hear the following.

This may depend if you arrow down the page or jump down by buttons. If you jump down by buttons you will hear the following. For example add header text button, add bold text button, add atalic text button, insert a quote button, insert code button, add a link button, add a bulleted list button, add a numbered list button, add a task list button, insert a reply button, Directly mention a user or team, Reference an issue or pull request, browse button, submit new issue button.

You may find it easier to arrow through rather than use single letter navigation keys to get all of the information.

 

They will need to know the following In the header text edit area what the issue is. For example

 

Under the ### Steps to reproduce:

> A list of the steps you take to demonstrate the problem.

> 

> Example:

> 

> 1. Open Chrome

> 2. Browse to www.google.com

> 3. Type "Hello"

> 4. Notice an error sound when enter is pressed.

 

> Please also remember to attach a zip of any files required to reproduce the issue.

 

### Expected behavior:

> Tell us what should happen.

 

### Actual behavior:

> Tell us what happens instead.

 

They will also need to know the NVDA version wheather it is a next-14027,c80e529f

Snap shot, or a master snap shot with its version number. Also wheather it is a portable or installed version of NVDA.

 

They may need other information such as if it was > Example: Running in a VM

 

Windows version:

> Example: Windows 10 Version 1607 Build 14393.1066

 

### Other questions:

 

Does the issue still occur after restarting your PC?

 

Have you tried any other versions of NVDA?

> Please list them and the result

 

Browse…

No files selected.

Attach files by dragging & dropping, selecting them, or pasting from the clipboard. 

 

Under this section would be where you would post your NVDA log.

 

Make sure under the general settings in NVDA it is set to Logging level: debug

 

 

After you have filled in the information that that they require locate the submit new issue button and your ticket will be created.

Please note

 

 

For NVACCESS to try and track down any bugs to be fixed you need to have the steps to recreate the problem you are having. Make sure your Logging level: is set to debug is set under the General settings in NVDA. You can also obtain the log which it produces from the Tool.. view log section in NVDA. A log will be produced after you press the enter key on the view log menu. Press the ALT key until a menu drops down then arrow down to you hear NVDA say save log as then press the ENTER key. NVDA will default to the file name then it is a matter of tabbing until you hear a location to save to you are happy with such as the Desk top then shift/tabbing back to the save button then pressing the enter key on the save button.

 

  

For more information on using Git Hub with a screen reader which goes beyond making a ticket please go to the following link at http://bats.fyi/2016/08/19/mastering-github-with-a-screen-reader-part-1/

 

 

 

 

 

 

 

Gene nz

 

 

Hi guys

I am putting together a tutorial on making a ticket for nvda in git hub. I know there are users here who do not know how to create one or even where to go or what to do.

I know when i do it I put in as much info as i can so hopefully it can be fixed. I just do not want to over do it and make it confusing if they do not have to do it when doing a ticket.

This is in draft so for give any mistakes.

Is there stuff i should put into it that i might of left out remember it is for a new user.

I will paste in what i have done so far so it can be moved around and is in draft or parts added or deleted.

Reporting an issue/bug report to NVACCESS

Where to go to issue a bug to be fixed

If you are a user of the NVDA screen reader wheather you use the next snap shot alfa code, the Master snap shot beata code or the stable version of NVDA that is released to the public, if you come across a bug it can be reported at the following web page at https://github.com/nvaccess/nvda/issues

Getting a Git hub account or simply signing in

To report any issues to be fixed you must have a Git Hub account.  .

If you do not have a Git Hub account you will need to go to the sign up link then press the enter key. It will ask you for a user name, email address, password and once done locate the create a account button then press the space bar or enter key for it to be created.

If you already have a account it is just a matter of locating the sign in link and entering your details to log into git hub.

After you have signed into git hub

After you have signed into git hub to report a issue on your page you will have some links and buttons and headings. The first button is a search button, the second a create new button, the third a view profile and more button, and a sign out button.

Searching for a issue on git hub

Before you report a issue/bug report to NVACCESS you will need to do a search to see if any one else has reported the bug. If one can not be found then you will need to open a new new issue. This is a button.

There are some other buttons there but the one you want is new issue button. Press the enter key on it and a new section will come up and ask you the following.

You can arrow through the page to see all the sections.

Press the enter key on this button and a new section will appear. You can arrow up and down this page to get all the information there or jump around with B for buttons

As you go down the page you will hear the following.

This may depend if you arrow down the page or jump down by buttons. If you jump down by buttons you will hear the following. For example add header text button, add bold text button, add atalic text button, insert a quote button, insert code button, add a link button, add a bulleted list button, add a numbered list button, add a task list button, insert a reply button, Directly mention a user or team, Reference an issue or pull request, browse button, submit new issue button.

You may find it easier to arrow through rather than use single letter navigation keys to get all of the information.

They will need to know the following In the header text edit area what the issue is. For example

Under the ### Steps to reproduce:

> A list of the steps you take to demonstrate the problem.

> 

> Example:

> 

> 1. Open Chrome

> 2. Browse to www.google.com

> 3. Type "Hello"

> 4. Notice an error sound when enter is pressed.

> Please also remember to attach a zip of any files required to reproduce the issue.

### Expected behavior:

> Tell us what should happen.

### Actual behavior:

> Tell us what happens instead.

They will also need to know the NVDA version wheather it is a next-14027,c80e529f

Snap shot, or a master snap shot with its version number. Also wheather it is a portable or installed version of NVDA.

They may need other information such as if it was > Example: Running in a VM

Windows version:

> Example: Windows 10 Version 1607 Build 14393.1066

### Other questions:

Does the issue still occur after restarting your PC?

Have you tried any other versions of NVDA?

> Please list them and the result

Browse…

No files selected.

Attach files by dragging & dropping, selecting them, or pasting from the clipboard. 

Under this section would be where you would post your NVDA log.

Make sure under the general settings in NVDA it is set to Logging level: debug

After you have filled in the information that that they require locate the submit new issue button and your ticket will be created.

Please note

For NVACCESS to try and track down any bugs to be fixed you need to have the steps to recreate the problem you are having. Make sure your Logging level: is set to debug is set under the General settings in NVDA. You can also obtain the log which it produces from the Tool.. view log section in NVDA. A log will be produced after you press the enter key on the view log menu. Press the ALT key until a menu drops down then arrow down to you hear NVDA say save log as then press the ENTER key. NVDA will default to the file name then it is a matter of tabbing until you hear a location to save to you are happy with such as the Desk top then shift/tabbing back to the save button then pressing the enter key on the save button.

For more information on using Git Hub with a screen reader which goes beyond making a ticket please go to the following link at http://bats.fyi/2016/08/19/mastering-github-with-a-screen-reader-part-1/

Gene nz