Date   

Re: NVDA's handling of checkboxes especially in Google Chrome

Steve Nutt
 

This is where JAWS has the edge.  It has semi auto mode, which means it will behave like NVDA does now, or auto mode, which means that a press of the down arrow from an edit box will switch back on browse mode.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 16 November 2021 17:24
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

This discussion illustrates the major flaw in the way automatic switching of modes is implemented.  Modes aren’t automatically switched when you down arrow from forms mode to browse mode.  If you are in forms mode and you up or down arrow, you will remain in forms mode.  Thus, you will not move from where you are.  If you tab you will move and the mode will automatically switch.  This is a built-in bias that encourages tabbing through forms, which is often the behavior you miss content by doing.  I’m not saying that is the intent of the design, but that is an important effect. 

 

To be consistent and not encourage tabbing over arrowing, automatic switching should occur when you up and down arrow as well as when you tab.  Making this change would eliminate my major objection to automatic switching.

 

Gene

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

Sent: Tuesday, November 16, 2021 11:06 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Let's see.
I'm in Firefox with NVDA, I just checked my window and it is maximized
(I went into the system menu and maximize is unavailable so that must
mean the window is already maximized). So I scroll down the page.
There's the email address box. Sometimes, when I try to arrow down
past the email address box, it tries to autofill it. So perhaps it's
trying to autofill your password box (it doesn't do this for me). So
maybe your step would be more like this; maybe get out of the password
box input mode, whether NVDA+Space or pressing Escape, either one, so
now you're on the password box without being in it, and then arrow
down, and it reads the word "remember me". Or, if it's easier, arrow
up from the "log in" button.

On 11/16/21, Brian Vogel <britechguy@...> wrote:
> On Tue, Nov 16, 2021 at 11:53 AM, Tyler Zahnke wrote:
>
>>
>> Firefox does not read whether the checkbox is checked or not, it's
>> just the words "remember me" are being read if I arrow down from the
>> password box,
>
> -
> Truly, I am not trying to be difficult, but I do not understand exactly what
> you mean or are doing.  If I'm sitting in the password box, in Firefox,
> using down arrow does not get me out of that box.
>
> There is something specific about the exact sequence of steps you are using
> that I am not hitting upon in my experimentation.  I can't replicate the
> success you've had even with just the announcement of "Remember Me" unless I
> use "the sighted way" with the mouse.  I'd like to be able to replicate your
> experience for my own education, and how you do this may be relevant to
> other situations.
> --
>
> Brian - Windows 10, 64-Bit, Version 21H1, Build 19043
>
> *The ignorance of one voter in a democracy impairs the security of all.*
>
> ~ John F. Kennedy
>
>
>
>
>
>




Re: NVDA's handling of checkboxes especially in Google Chrome

Steve Nutt
 

Brian, I’m surprised that wasn’t the first thing you tried, being a screen reader tutor.

 

You should know that arrowing down in a password box won’t automatically invoke browse mode.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: 16 November 2021 17:19
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Tyler,

That worked.  Forcing NVDA out of focus mode and into browse mode prior to down arrowing from the password edit box does get, "Clickable, remember me," announced when using Firefox.  And hitting either the spacebar or enter toggles the remember me checkbox from off to on for the first press and does the standard off, on, off, on with any subsequent presses.

And the lack of that behavior under Chromium based browsers is consistent.  A down arrow from the password box after going back into browse mode takes you straight to the, "By continuing," line.

I still suspect this has to do with what each respective browser does with respect to the hidden attribute.  It appears that under Chomium browsers, that attribute is persistent, while in Firefox for some reason it's not.  And if that's the case, and it may not be, then either Firefox or Chrome/Chromium-based browsers are wrong about how they are handling that object.  This is not something that should be inconsistent, and my gut tells me that Firefox is misbehaving.  But those far better versed than myself both in what web browsers are supposed to honor as far as what gets exposed to a screen reader based upon attributes and what NVDA itself is doing "under the hood" would have to speak to that.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: NVDA's handling of checkboxes especially in Google Chrome

Steve Nutt
 

I prefer Chrome for PDF files, but again, it’s subjective.

 

Chrome seems to expose headings better than Edge on the PDFs I’ve tried.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 16 November 2021 16:34
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

I’ll add that even if I use Firefox as my main browser, I’ll still use Edge to read PDF files.  I haven’t done any systematic comparison but there are some people who say that Edge does better reading them. 

 

I recently tried reading one PDF file in Firefox and there were problems where words were joined together at times.  Perhaps line breaks weren’t recognized.  But Edge read the document properly.  That’s just one example but that, and the comments I’ve seen on the subject lead me to believe that it may well be that Edge may read PDF files better than other browsers. 

 

Gene

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

Sent: Tuesday, November 16, 2021 10:13 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

I’d be interested in whether others find it slow.  This may just be my experience, but Firefox seems to me to be much faster than it used to be.  I’ve started using it a lot more and I’m considering using it as my main browser.

 

Gene

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

From: Steve Nutt

Sent: Tuesday, November 16, 2021 3:32 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

It’s just a shame that Firefox is so slow compared with Chrome, certainly on all my machines it is.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Sackrider
Sent: 16 November 2021 00:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

        I have an example of whear fire fox will and nvda will see somthng but chrome brousers don't.  The audio of the lions magazine in both edge and chrome there is no down it all button but in fire fox there is a down it all button.  I am not surprised about other things that fire fox sees that chrome brousers don't this is why I say that for the blind chrome based brousers are kind of usless junk and this is the reason that I use internet explorer for as long as I did as it was not a chrome based brouser.  I have windows 11 and there is no more internet explorer so I had to find a nonchrome based brouser and thats why i am using fire fox as my default brouser.

Brian Sackrider

On 11/15/2021 5:12 PM, Gene wrote:

I am increasingly finding cases where Firefox either sees things or does things that Chrome doesn’t when used with NVDA.  I don’t use JAWS and my demo is far too old to evaluate whether the same things occur.  But I think the question of whether Chrome-based browsers are working properly with sites in terms of accessibility should be systematically addressed.

 

Here are two examples:

First is this article from The New York Times;.

If you are at the top of the page and press s to move by separator, you will immediately move to cards giving background information on the story.

In Firefox, you see, at the end of the card, a button for previous card, unavailable since you are on the first card, and a button for next card.

Activating this button works.  It moves you to the next card.

To easily get to this card in a proper position to read it, press page up, then s for separator.

The previous and next card buttons both work correctly for this card and, I assume, for all other cards.

 

I tested with Chrome and Brave and neither of these Chrome-based browsers saw either button. I could read the first card below the separator but no buttons are displayed.


I’ve recently been looking up material on occasion using the Encyclopedia Britannica online.  When reading with Firefox, the page being read automatically shows new material as you move down it.  Firefox shows this new material when it appears.  Chrome-based browsers don’t. 

This article is an example:

 

Search from the top of the page for the word nervous.  If you down arrow in Firefox, the text continues after some items, perhaps three or four.  Chrome-based browsers don’t load new material at least not accessibly to screen-readers.

 

Chrome-based browsers don’t see comments on Youtube pages where videos are streamed.  Firefox does.  Because the page changes as you move down it, you have to move down the page to see the comments.  You can’t just search for the word comment to get to the section.

 

I’ll add that all these comments are for my specific machine but I expect they will be generally experienced.  Verification, however, is necessary.

 

Are these problems with Chrome, with NVDA, or both?  I suspect that these problems are not improper implementation of accessibility.  Those questions, however, would require technically knowledgeable investigation to be resolved.

 

Gene

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

From: Gene

Sent: Monday, November 15, 2021 11:00 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Since Firefox sees the checkboxes, I don’t know that its valid to assume what the problem is and that it is improper design.  Also, there may be cases where you will hear explanatory text that accompanies a structure read if you tab into the structure rather than move to it in some other way.  I haven’t compared Chrome-based and not Chrome-based browsers in these cases but again, is this improper design or just the complexity of design?

 

Gene

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

From: Jackie

Sent: Monday, November 15, 2021 10:55 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Yeah well, I'm not trying to be obscene here, but it's because the web
designers didn't use checkboxes that expose themselves, or, perhaps to
put it just a bit more succinctly, expose their state. & it is a royal
pita, & it's not unique to NVDA, though having said thus, sometimes
Jaws actually allows labeling of these graphics, whereas NVDA doesn't.
& it's not an issue specific to Chrome, either. It's actually called a
"clickable element" as opposed to a checkbox. Sighted folks generally
cant distinguish these from standard checkboxes, but they sure create
problems for us.

On 11/15/21, Tyler Zahnke mailto:programmer651@... wrote:
> Hello NVDA community! Why does NVDA not read some checkboxes in Google
> Chrome? NVDA reads a lot of them, but some sites have a "remember me"
> checkbox on their login screen that just says "clickable"; when you
> press Enter where it says clickable, the box checks, but NVDA doesn't
> tell you this. I have seen websites that contain both accessible and
> inaccessible checkboxes, why is this? And several times (I have a
> memory of seeing this on the login screen of Palai), it doesn't read
> some of the checkboxes, such as "remember me", at all. It actually got
> to the point where I thought they had removed the checkbox from their
> site because it completely didn't read it, but users of other devices
> claimed they still saw the checkbox, but several of us Chrome and NVDA
> users noticed the missing checkbox. And as soon as I tried the same
> site with Firefox and NVDA, I saw the checkbox, but it said "remember
> me clickable" and therefore, though you could check and uncheck it,
> NVDA wouldn't tell you, while on Chrome, NVDA skips over the box. This
> was a problem with a website that I actually had to help out as far as
> accessibility; their site had some regular checkboxes on the form and
> screen readers could read it just fine, but then some checkboxes said
> "clickable" or didn't say anything at all, yet the Enter key worked on
> them but the screen reader didn't say. I've probably seen variations
> on this issue for a few years, some checkbox not displaying in Chrome.
> Often I would try it again with Firefox, and at least in the
> checkbox-related cases, it usually worked. And in the case of the
> website I helped make accessible, I even looked at the HTML for the
> checkboxes, and even the inaccessible checkboxes were still coded like
> checkboxes though they may have had some extra styling on them. So
> what's the deal with checkboxes?
>
>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com



Re: NVDA's handling of checkboxes especially in Google Chrome

Steve Nutt
 

I find it considerably slower than Chrome on many websites. But I have no scientific evidence to back it up.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 16 November 2021 16:13
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

I’d be interested in whether others find it slow.  This may just be my experience, but Firefox seems to me to be much faster than it used to be.  I’ve started using it a lot more and I’m considering using it as my main browser.

 

Gene

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

From: Steve Nutt

Sent: Tuesday, November 16, 2021 3:32 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

It’s just a shame that Firefox is so slow compared with Chrome, certainly on all my machines it is.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Sackrider
Sent: 16 November 2021 00:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

        I have an example of whear fire fox will and nvda will see somthng but chrome brousers don't.  The audio of the lions magazine in both edge and chrome there is no down it all button but in fire fox there is a down it all button.  I am not surprised about other things that fire fox sees that chrome brousers don't this is why I say that for the blind chrome based brousers are kind of usless junk and this is the reason that I use internet explorer for as long as I did as it was not a chrome based brouser.  I have windows 11 and there is no more internet explorer so I had to find a nonchrome based brouser and thats why i am using fire fox as my default brouser.

Brian Sackrider

On 11/15/2021 5:12 PM, Gene wrote:

I am increasingly finding cases where Firefox either sees things or does things that Chrome doesn’t when used with NVDA.  I don’t use JAWS and my demo is far too old to evaluate whether the same things occur.  But I think the question of whether Chrome-based browsers are working properly with sites in terms of accessibility should be systematically addressed.

 

Here are two examples:

First is this article from The New York Times;.

If you are at the top of the page and press s to move by separator, you will immediately move to cards giving background information on the story.

In Firefox, you see, at the end of the card, a button for previous card, unavailable since you are on the first card, and a button for next card.

Activating this button works.  It moves you to the next card.

To easily get to this card in a proper position to read it, press page up, then s for separator.

The previous and next card buttons both work correctly for this card and, I assume, for all other cards.

 

I tested with Chrome and Brave and neither of these Chrome-based browsers saw either button. I could read the first card below the separator but no buttons are displayed.


I’ve recently been looking up material on occasion using the Encyclopedia Britannica online.  When reading with Firefox, the page being read automatically shows new material as you move down it.  Firefox shows this new material when it appears.  Chrome-based browsers don’t. 

This article is an example:

 

Search from the top of the page for the word nervous.  If you down arrow in Firefox, the text continues after some items, perhaps three or four.  Chrome-based browsers don’t load new material at least not accessibly to screen-readers.

 

Chrome-based browsers don’t see comments on Youtube pages where videos are streamed.  Firefox does.  Because the page changes as you move down it, you have to move down the page to see the comments.  You can’t just search for the word comment to get to the section.

 

I’ll add that all these comments are for my specific machine but I expect they will be generally experienced.  Verification, however, is necessary.

 

Are these problems with Chrome, with NVDA, or both?  I suspect that these problems are not improper implementation of accessibility.  Those questions, however, would require technically knowledgeable investigation to be resolved.

 

Gene

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

From: Gene

Sent: Monday, November 15, 2021 11:00 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Since Firefox sees the checkboxes, I don’t know that its valid to assume what the problem is and that it is improper design.  Also, there may be cases where you will hear explanatory text that accompanies a structure read if you tab into the structure rather than move to it in some other way.  I haven’t compared Chrome-based and not Chrome-based browsers in these cases but again, is this improper design or just the complexity of design?

 

Gene

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

From: Jackie

Sent: Monday, November 15, 2021 10:55 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Yeah well, I'm not trying to be obscene here, but it's because the web
designers didn't use checkboxes that expose themselves, or, perhaps to
put it just a bit more succinctly, expose their state. & it is a royal
pita, & it's not unique to NVDA, though having said thus, sometimes
Jaws actually allows labeling of these graphics, whereas NVDA doesn't.
& it's not an issue specific to Chrome, either. It's actually called a
"clickable element" as opposed to a checkbox. Sighted folks generally
cant distinguish these from standard checkboxes, but they sure create
problems for us.

On 11/15/21, Tyler Zahnke mailto:programmer651@... wrote:
> Hello NVDA community! Why does NVDA not read some checkboxes in Google
> Chrome? NVDA reads a lot of them, but some sites have a "remember me"
> checkbox on their login screen that just says "clickable"; when you
> press Enter where it says clickable, the box checks, but NVDA doesn't
> tell you this. I have seen websites that contain both accessible and
> inaccessible checkboxes, why is this? And several times (I have a
> memory of seeing this on the login screen of Palai), it doesn't read
> some of the checkboxes, such as "remember me", at all. It actually got
> to the point where I thought they had removed the checkbox from their
> site because it completely didn't read it, but users of other devices
> claimed they still saw the checkbox, but several of us Chrome and NVDA
> users noticed the missing checkbox. And as soon as I tried the same
> site with Firefox and NVDA, I saw the checkbox, but it said "remember
> me clickable" and therefore, though you could check and uncheck it,
> NVDA wouldn't tell you, while on Chrome, NVDA skips over the box. This
> was a problem with a website that I actually had to help out as far as
> accessibility; their site had some regular checkboxes on the form and
> screen readers could read it just fine, but then some checkboxes said
> "clickable" or didn't say anything at all, yet the Enter key worked on
> them but the screen reader didn't say. I've probably seen variations
> on this issue for a few years, some checkbox not displaying in Chrome.
> Often I would try it again with Firefox, and at least in the
> checkbox-related cases, it usually worked. And in the case of the
> website I helped make accessible, I even looked at the HTML for the
> checkboxes, and even the inaccessible checkboxes were still coded like
> checkboxes though they may have had some extra styling on them. So
> what's the deal with checkboxes?
>
>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com



Re: NVDA's handling of checkboxes especially in Google Chrome

Steve Nutt
 

I don't see anything wrong with this page using Chrome.

All the best

steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tyler Zahnke
Sent: 16 November 2021 15:56
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

The example I had on my mind when I wrote was the sign-in page for the payment/digital currency website Palai.
https://palai.org/u/sign_in
In fact, I assumed that the "remember me" feature had been erased from the page, until I noticed that it worked on Firefox. Well, I analyzed the HTML code for the sign-in page and found out I was able to change the URL so it is checked by default.
https://palai.org/u/sign_in?user[remember_me]=1
Point being, Firefox shows "remember me" (as a clickable item, not as a checkbox), while in Chrome it doesn't see it at all, as if it just isn't there.

On 11/16/21, Brian Vogel <britechguy@...> wrote:
On Mon, Nov 15, 2021 at 07:09 PM, Brian Sackrider wrote:


for the blind chrome based brousers are kind of usless junk
-
Assertions like this are, quite simply, foolish and incorrect. The
predominant browser in the world right now is Chrome, and there's
ample evidence of blind people using it on every blind-tech-focused
group out there.

It is a truism that certain sites will "play better" with specific
browsers at times. And that translates over to how screen readers
"play with" those sites using those browsers.

If you give a specific URL on which others can experiment, there might
be a lot more information forthcoming about that particular page, and
those analogous to it, under the different browsers. I know you said
Lions Magazine, but that's too vague.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043

*The ignorance of one voter in a democracy impairs the security of
all.*

~ John F. Kennedy






Re: Improvements to the caps lock key and the NVDA key

 

I have personally not had any issue with it.

To be honest the fact the capslock key does what it does makes me know nvda is working.

If I hit it twice then hit it twice again I know nvda is working.

If I hit it 4 times or so and nothing then I know something has frozen up.

If I hit it by mistake I know it won't trigger which is good because I type really fast on this mechanical.



On 17/11/2021 6:00 pm, Rowen Cary wrote:

This topic has aroused heated discussions, and I may think that this issue is indeed worthy of discussion. In addition, I can use the two keyboard layouts of NVDA proficiently. This theme is only to improve NVDA and make it better. If I offend anyone, I apologize, we can continue the discussion or open an Issue on Github.


nvda and gmail in basic html

Michael Micallef at FITA
 

Dear NVDA Users,

 

I have a minor difficulty and I sincerely appreciate some help.

 

I'm using the gmail in basic html view and when I try to move between the messages using the up/down arrows, the nvda reports the foll9owing:

 

row 7 column 1

row 8 column 1 etc etc,

 

 

How in the world I can stop NVDA from saying the rows and columns in gmail basic html, as a speech synthesizer i'm using the eloquence.

 

thanks in advance,


Re: recent problems using NVDA to read google docs/sheets?

Sally Kiebdaj
 

Hi there,

I'm running Google Chrome Version 96.0.4664.45 (Official Build) (64-bit) and NVDA 2021.2.

Pressing escape doesn't help, sorry I didn't mention I had already tried that. 

NVDA announces "application, group" which I don't remember it doing before. However, the focus, according to my sighted partner, is in the spreadsheet cells like usual. 

Has anyone else been seeing something like this?

Thanks!
Sally 

On Tue, Nov 16, 2021 at 5:01 PM Nimer Jaber <nimerjaber1@...> wrote:
Hello Sally,

Which browser are you using where this difficulty occurs? Which version of NVDA?

Next time you open a doc, after the doc has loaded, and you can't seem to access it, try pressing esc and let us know what happens.

Thanks.

On Tue, Nov 16, 2021 at 6:30 AM Sally Kiebdaj <fiddle.pup@...> wrote:
Hello, 

I can no longer read google docs or sheets on my work laptop and noticed that I need to press Tab a few extra times on my personal laptop to focus and read a doc or sheet. However, two weeks ago, I was using google docs and sheets with no problems on either machine. After the page fully loaded and I made sure browse mode was off, my focus was already in the doc or sheet content and I was able to read.

Has anyone experienced new problems reading the contents of google docs or sheets in the last 10 days? 

Does anyone know about recent G Suite updates that might be causing this? 

If not, are there known NVDA settings problems that might be causing this?

I'm not sure how to start troubleshooting this so would welcome all suggestions!

Thanks,
Sally 



--
Best,

Nimer Jaber

Registered Linux User 529141.
http://counter.li.org/

To find out about a free, open-source, and versatile screen reader for Windows, visit nvaccess.org

You can follow @nimerjaber on Twitter for the latest technology news.

Thank you, and have a great day!


Re: shopping at instacart

Hope Williamson
 

Well I do this with my other screen reader and everything works fine for
me. That being said, you might want to try a different browser, maybe
that will help.

On 11/16/2021 6:38 AM, Howard Traxler wrote:
When shopping at instacart, in the past each product listing had only
one button; that was a button to add it to the cart.  Today I find
every line in a listing is a button.  Can no longer just navigate by
button and pass up all the chatter.  The whole thing is much too
chatty now.  Did I mistakenly make some change in my NVDA or did the
website change.  It'll sure make shopping less fun.

Howard




Re: Improvements to the caps lock key and the NVDA key

Rowen Cary
 

This topic has aroused heated discussions, and I may think that this issue is indeed worthy of discussion. In addition, I can use the two keyboard layouts of NVDA proficiently. This theme is only to improve NVDA and make it better. If I offend anyone, I apologize, we can continue the discussion or open an Issue on Github.


Re: nvda vocalizer & eloquence synthesizer plugin

Viris g. Rodríguez <vgr.09.15@...>
 

Thanks for that. Sorry for the message I sent before.


----- Original Message -----
From: Shaun Everiss
To: nvda@nvda.groups.io
Date: Tuesday, November 16, 2021 15:02
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

60 dollars from atguys and last I looked vocaliser is 120 dollars on atguys.

Eloquence supports just about every language you can think of well basically if you used eloquence before then it supports a lot of languages.

Vocaliser does to but in the sapi version you can choose between low or high quality and can download them as you will.



On 17/11/2021 7:08 am, Viris g. Rodríguez wrote:

Just out of curiosity, How much does Eloquence cost? I would like to buy it. Also I was wondering how many languages it supports.
Thanks in advance.

----- Original Message -----
From: Chris via groups.io
To: nvda@nvda.groups.io
Date: Tuesday, November 16, 2021 06:28
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

Free upgrades, no more to pay once you have bought the licence thats it

 

 

 

 

From: Michael Micallef at FITA
Sent: 16 November 2021 12:19
To: nvda mailing list (nvda@nvda.groups.io)
Subject: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

Hi NVDA Users,

 

I'm planning to buy the nvda Eloquence & vocalizer synthesizer add-on for nvda from codefactory. Does any knows if the future upgrades for these two synthesizers are free or paid, and how much usually costs the upgrades?

 
.

_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#89793) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

NVDA Topics on Groups.io - https://nvda.groups.io/g/nvda/topics | NVDA Archive Search Page on Groups.io - https://nvda.groups.io/g/nvda/search

NVDA is developed by NV Access in collaboration with the community.
Get NVDA from: https://www.nvaccess.org/
Your continued donations help keep NVDA development going strong. Donate at: https://www.nvaccess.org/donate
Get NVDA add-ons at: https://addons.nvda-project.org/
Other links:
NVDA on Facebook: https://www.facebook.com/group.php?gid=8601265515 Your Subscription | Contact Group Owner | Unsubscribe [vgr.09.15@...]

_._,_._,_


Re: nvda vocalizer & eloquence synthesizer plugin

Viris g. Rodríguez <vgr.09.15@...>
 

Thanks to all for responding. But I just want Eloquence. Is it possible to buy it without vocalizer?
Sincerely.


----- Original Message -----
From: Shaun Everiss
To: nvda@nvda.groups.io
Date: Tuesday, November 16, 2021 14:36
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

Free, however due to versions and how things go on, I would buy the vocaliser and eloquence sapi packages.

I think you can buy both from atguys to which was where I got the sapi one from.

Its well worth having them though.



On 17/11/2021 1:19 am, Michael Micallef at FITA wrote:

Hi NVDA Users,

 

Im planning to buy the nvda Eloquence & vocalizer synthesizer add-on for nvda from codefactory. Does any knows if the future upgrades for these two synthesizers are free or paid, and how much usually costs the upgrades?

_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#89789) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

NVDA Topics on Groups.io - https://nvda.groups.io/g/nvda/topics | NVDA Archive Search Page on Groups.io - https://nvda.groups.io/g/nvda/search

NVDA is developed by NV Access in collaboration with the community.
Get NVDA from: https://www.nvaccess.org/
Your continued donations help keep NVDA development going strong. Donate at: https://www.nvaccess.org/donate
Get NVDA add-ons at: https://addons.nvda-project.org/
Other links:
NVDA on Facebook: https://www.facebook.com/group.php?gid=8601265515 Your Subscription | Contact Group Owner | Unsubscribe [vgr.09.15@...]

_._,_._,_


Re: NVDA's handling of checkboxes especially in Google Chrome

Gene
 

Generalizing from one person’s experience when discussing performance is not valid.  I don’t know what in your system causes slow opening of the program.  On my system, it doesn’t open more slowly than other browsers, or if it does, not enough to matter.  Others may have different experiences.
 
As for NoScript, are you saying the interface is worse using Firefox than other browsers? 
 
And while ads are not blocked by default, as they generally are not blocked by browsers, using UBlock Origin (spelling) will do so and it is easy to install add-ons.
 
In short, many people may have formed views of Firefox some time ago and those views may no longer be valid.
 
Gene

-----Original Message-----
Sent: Tuesday, November 16, 2021 2:55 PM
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome
 

I have been using firefox for ages now.

And recently after waterfox started going down the toilet, I have updated to the latest firefox.

So the biggest issue, no noscript or at least I don't care for the new interface but thats just about it.

The only gripe is that firefox is a little slow to start of late like 30 seconds a load.

It always says unknown when it opens but then its fine once loaded and its really not a big gripe in any case.

My only thing I miss is that waterfox seemed to be able to block youtube adds by default.

I know, I really should pay for youtube at least the basic level so I can make them go I mean I do listen to it a lot but even so.

 

 

On 17/11/2021 5:13 am, Gene wrote:
I’d be interested in whether others find it slow.  This may just be my experience, but Firefox seems to me to be much faster than it used to be.  I’ve started using it a lot more and I’m considering using it as my main browser.
 
Gene
-----Original Message-----
From: Steve Nutt
Sent: Tuesday, November 16, 2021 3:32 AM
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome
 

It’s just a shame that Firefox is so slow compared with Chrome, certainly on all my machines it is.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io mailto:nvda@nvda.groups.io On Behalf Of Brian Sackrider
Sent: 16 November 2021 00:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

        I have an example of whear fire fox will and nvda will see somthng but chrome brousers don't.  The audio of the lions magazine in both edge and chrome there is no down it all button but in fire fox there is a down it all button.  I am not surprised about other things that fire fox sees that chrome brousers don't this is why I say that for the blind chrome based brousers are kind of usless junk and this is the reason that I use internet explorer for as long as I did as it was not a chrome based brouser.  I have windows 11 and there is no more internet explorer so I had to find a nonchrome based brouser and thats why i am using fire fox as my default brouser.

Brian Sackrider

On 11/15/2021 5:12 PM, Gene wrote:

I am increasingly finding cases where Firefox either sees things or does things that Chrome doesn’t when used with NVDA.  I don’t use JAWS and my demo is far too old to evaluate whether the same things occur.  But I think the question of whether Chrome-based browsers are working properly with sites in terms of accessibility should be systematically addressed.

 

Here are two examples:

First is this article from The New York Times;.

If you are at the top of the page and press s to move by separator, you will immediately move to cards giving background information on the story.

In Firefox, you see, at the end of the card, a button for previous card, unavailable since you are on the first card, and a button for next card.

Activating this button works.  It moves you to the next card.

To easily get to this card in a proper position to read it, press page up, then s for separator.

The previous and next card buttons both work correctly for this card and, I assume, for all other cards.

 

I tested with Chrome and Brave and neither of these Chrome-based browsers saw either button. I could read the first card below the separator but no buttons are displayed.


I’ve recently been looking up material on occasion using the Encyclopedia Britannica online.  When reading with Firefox, the page being read automatically shows new material as you move down it.  Firefox shows this new material when it appears.  Chrome-based browsers don’t. 

This article is an example:

 

Search from the top of the page for the word nervous.  If you down arrow in Firefox, the text continues after some items, perhaps three or four.  Chrome-based browsers don’t load new material at least not accessibly to screen-readers.

 

Chrome-based browsers don’t see comments on Youtube pages where videos are streamed.  Firefox does.  Because the page changes as you move down it, you have to move down the page to see the comments.  You can’t just search for the word comment to get to the section.

 

I’ll add that all these comments are for my specific machine but I expect they will be generally experienced.  Verification, however, is necessary.

 

Are these problems with Chrome, with NVDA, or both?  I suspect that these problems are not improper implementation of accessibility.  Those questions, however, would require technically knowledgeable investigation to be resolved.

 

Gene

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

From: Gene

Sent: Monday, November 15, 2021 11:00 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Since Firefox sees the checkboxes, I don’t know that its valid to assume what the problem is and that it is improper design.  Also, there may be cases where you will hear explanatory text that accompanies a structure read if you tab into the structure rather than move to it in some other way.  I haven’t compared Chrome-based and not Chrome-based browsers in these cases but again, is this improper design or just the complexity of design?

 

Gene

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

From: Jackie

Sent: Monday, November 15, 2021 10:55 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Yeah well, I'm not trying to be obscene here, but it's because the web
designers didn't use checkboxes that expose themselves, or, perhaps to
put it just a bit more succinctly, expose their state. & it is a royal
pita, & it's not unique to NVDA, though having said thus, sometimes
Jaws actually allows labeling of these graphics, whereas NVDA doesn't.
& it's not an issue specific to Chrome, either. It's actually called a
"clickable element" as opposed to a checkbox. Sighted folks generally
cant distinguish these from standard checkboxes, but they sure create
problems for us.

On 11/15/21, Tyler Zahnke mailto:programmer651@... wrote:
> Hello NVDA community! Why does NVDA not read some checkboxes in Google
> Chrome? NVDA reads a lot of them, but some sites have a "remember me"
> checkbox on their login screen that just says "clickable"; when you
> press Enter where it says clickable, the box checks, but NVDA doesn't
> tell you this. I have seen websites that contain both accessible and
> inaccessible checkboxes, why is this? And several times (I have a
> memory of seeing this on the login screen of Palai), it doesn't read
> some of the checkboxes, such as "remember me", at all. It actually got
> to the point where I thought they had removed the checkbox from their
> site because it completely didn't read it, but users of other devices
> claimed they still saw the checkbox, but several of us Chrome and NVDA
> users noticed the missing checkbox. And as soon as I tried the same
> site with Firefox and NVDA, I saw the checkbox, but it said "remember
> me clickable" and therefore, though you could check and uncheck it,
> NVDA wouldn't tell you, while on Chrome, NVDA skips over the box. This
> was a problem with a website that I actually had to help out as far as
> accessibility; their site had some regular checkboxes on the form and
> screen readers could read it just fine, but then some checkboxes said
> "clickable" or didn't say anything at all, yet the Enter key worked on
> them but the screen reader didn't say. I've probably seen variations
> on this issue for a few years, some checkbox not displaying in Chrome.
> Often I would try it again with Firefox, and at least in the
> checkbox-related cases, it usually worked. And in the case of the
> website I helped make accessible, I even looked at the HTML for the
> checkboxes, and even the inaccessible checkboxes were still coded like
> checkboxes though they may have had some extra styling on them. So
> what's the deal with checkboxes?
>
>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com




Re: NVDA's handling of checkboxes especially in Google Chrome

Pauline Smith <paulinesmithh@...>
 

Firefox began running at a snail's pace on my computer. I liked using it well enough when it behaved.

Pauline
 

Sent from my iPod

On Nov 16, 2021, at 12:41 PM, Brian Sackrider <bsackrider55@...> wrote:



    Fire fox is much faster than chrome my sighted friend told me that.  Sites come up much quicker in fire fox than they do in chrome.

Brian Sackrider

On 11/16/2021 4:32 AM, Steve Nutt wrote:

It’s just a shame that Firefox is so slow compared with Chrome, certainly on all my machines it is.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Sackrider
Sent: 16 November 2021 00:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

        I have an example of whear fire fox will and nvda will see somthng but chrome brousers don't.  The audio of the lions magazine in both edge and chrome there is no down it all button but in fire fox there is a down it all button.  I am not surprised about other things that fire fox sees that chrome brousers don't this is why I say that for the blind chrome based brousers are kind of usless junk and this is the reason that I use internet explorer for as long as I did as it was not a chrome based brouser.  I have windows 11 and there is no more internet explorer so I had to find a nonchrome based brouser and thats why i am using fire fox as my default brouser.

Brian Sackrider

On 11/15/2021 5:12 PM, Gene wrote:

I am increasingly finding cases where Firefox either sees things or does things that Chrome doesn’t when used with NVDA.  I don’t use JAWS and my demo is far too old to evaluate whether the same things occur.  But I think the question of whether Chrome-based browsers are working properly with sites in terms of accessibility should be systematically addressed.

 

Here are two examples:

First is this article from The New York Times;.

If you are at the top of the page and press s to move by separator, you will immediately move to cards giving background information on the story.

In Firefox, you see, at the end of the card, a button for previous card, unavailable since you are on the first card, and a button for next card.

Activating this button works.  It moves you to the next card.

To easily get to this card in a proper position to read it, press page up, then s for separator.

The previous and next card buttons both work correctly for this card and, I assume, for all other cards.

 

I tested with Chrome and Brave and neither of these Chrome-based browsers saw either button. I could read the first card below the separator but no buttons are displayed.


I’ve recently been looking up material on occasion using the Encyclopedia Britannica online.  When reading with Firefox, the page being read automatically shows new material as you move down it.  Firefox shows this new material when it appears.  Chrome-based browsers don’t. 

This article is an example:

 

Search from the top of the page for the word nervous.  If you down arrow in Firefox, the text continues after some items, perhaps three or four.  Chrome-based browsers don’t load new material at least not accessibly to screen-readers.

 

Chrome-based browsers don’t see comments on Youtube pages where videos are streamed.  Firefox does.  Because the page changes as you move down it, you have to move down the page to see the comments.  You can’t just search for the word comment to get to the section.

 

I’ll add that all these comments are for my specific machine but I expect they will be generally experienced.  Verification, however, is necessary.

 

Are these problems with Chrome, with NVDA, or both?  I suspect that these problems are not improper implementation of accessibility.  Those questions, however, would require technically knowledgeable investigation to be resolved.

 

Gene

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

From: Gene

Sent: Monday, November 15, 2021 11:00 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Since Firefox sees the checkboxes, I don’t know that its valid to assume what the problem is and that it is improper design.  Also, there may be cases where you will hear explanatory text that accompanies a structure read if you tab into the structure rather than move to it in some other way.  I haven’t compared Chrome-based and not Chrome-based browsers in these cases but again, is this improper design or just the complexity of design?

 

Gene

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

From: Jackie

Sent: Monday, November 15, 2021 10:55 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Yeah well, I'm not trying to be obscene here, but it's because the web
designers didn't use checkboxes that expose themselves, or, perhaps to
put it just a bit more succinctly, expose their state. & it is a royal
pita, & it's not unique to NVDA, though having said thus, sometimes
Jaws actually allows labeling of these graphics, whereas NVDA doesn't.
& it's not an issue specific to Chrome, either. It's actually called a
"clickable element" as opposed to a checkbox. Sighted folks generally
cant distinguish these from standard checkboxes, but they sure create
problems for us.

On 11/15/21, Tyler Zahnke <programmer651@...> wrote:
> Hello NVDA community! Why does NVDA not read some checkboxes in Google
> Chrome? NVDA reads a lot of them, but some sites have a "remember me"
> checkbox on their login screen that just says "clickable"; when you
> press Enter where it says clickable, the box checks, but NVDA doesn't
> tell you this. I have seen websites that contain both accessible and
> inaccessible checkboxes, why is this? And several times (I have a
> memory of seeing this on the login screen of Palai), it doesn't read
> some of the checkboxes, such as "remember me", at all. It actually got
> to the point where I thought they had removed the checkbox from their
> site because it completely didn't read it, but users of other devices
> claimed they still saw the checkbox, but several of us Chrome and NVDA
> users noticed the missing checkbox. And as soon as I tried the same
> site with Firefox and NVDA, I saw the checkbox, but it said "remember
> me clickable" and therefore, though you could check and uncheck it,
> NVDA wouldn't tell you, while on Chrome, NVDA skips over the box. This
> was a problem with a website that I actually had to help out as far as
> accessibility; their site had some regular checkboxes on the form and
> screen readers could read it just fine, but then some checkboxes said
> "clickable" or didn't say anything at all, yet the Enter key worked on
> them but the screen reader didn't say. I've probably seen variations
> on this issue for a few years, some checkbox not displaying in Chrome.
> Often I would try it again with Firefox, and at least in the
> checkbox-related cases, it usually worked. And in the case of the
> website I helped make accessible, I even looked at the HTML for the
> checkboxes, and even the inaccessible checkboxes were still coded like
> checkboxes though they may have had some extra styling on them. So
> what's the deal with checkboxes?
>
>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com




Re: nvda vocalizer & eloquence synthesizer plugin

Sarah k Alawami
 

I have the add on that has both, , I think the 60 dollar one.  I don’t use them outside of NVDA so for me the 60 dollars  was worth it.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Tuesday, November 16, 2021 1:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

60 dollars from atguys and last I looked vocaliser is 120 dollars on atguys.

Eloquence supports just about every language you can think of well basically if you used eloquence before then it supports a lot of languages.

Vocaliser does to but in the sapi version you can choose between low or high quality and can download them as you will.

 

 

On 17/11/2021 7:08 am, Viris g. Rodríguez wrote:

Just out of curiosity, How much does Eloquence cost? I would like to buy it. Also I was wondering how many languages it supports.
Thanks in advance.

----- Original Message -----
From: Chris via groups.io
To: nvda@nvda.groups.io
Date: Tuesday, November 16, 2021 06:28
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

Free upgrades, no more to pay once you have bought the licence thats it

 

 

 

 

From: Michael Micallef at FITA
Sent: 16 November 2021 12:19
To: nvda mailing list (nvda@nvda.groups.io)
Subject: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

Hi NVDA Users,

 

I'm planning to buy the nvda Eloquence & vocalizer synthesizer add-on for nvda from codefactory. Does any knows if the future upgrades for these two synthesizers are free or paid, and how much usually costs the upgrades?

 
.


Re: Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

 

On Tue, Nov 16, 2021 at 03:57 PM, Dan Beaver wrote:
Sorry Brian, I wasn't meaning to sound critical about the choice. 
-
Dan,

No criticism taken, nor offense.  That's why I started with, "I get that."

There is no right or wrong when it comes to personal preference.  I just wanted to give the background and my rationale for wanting it on at that moment.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: nvda vocalizer & eloquence synthesizer plugin

 

60 dollars from atguys and last I looked vocaliser is 120 dollars on atguys.

Eloquence supports just about every language you can think of well basically if you used eloquence before then it supports a lot of languages.

Vocaliser does to but in the sapi version you can choose between low or high quality and can download them as you will.



On 17/11/2021 7:08 am, Viris g. Rodríguez wrote:
Just out of curiosity, How much does Eloquence cost? I would like to buy it. Also I was wondering how many languages it supports.
Thanks in advance.

----- Original Message -----
From: Chris via groups.io
To: nvda@nvda.groups.io
Date: Tuesday, November 16, 2021 06:28
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

Free upgrades, no more to pay once you have bought the licence thats it

 

 

 

 

From: Michael Micallef at FITA
Sent: 16 November 2021 12:19
To: nvda mailing list (nvda@nvda.groups.io)
Subject: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

Hi NVDA Users,

 

I'm planning to buy the nvda Eloquence & vocalizer synthesizer add-on for nvda from codefactory. Does any knows if the future upgrades for these two synthesizers are free or paid, and how much usually costs the upgrades?

 
.


Re: Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

Dan Beaver
 

Sorry Brian, I wasn't meaning to sound critical about the choice.  I was just inserting my feelings about the dialog when I shouldn't have.  I should have simply answered and not vented. :)


Dan Beaver

On 11/16/2021 3:46 PM, Brian Vogel wrote:
On Tue, Nov 16, 2021 at 02:50 PM, Dan Beaver wrote:
I hate the dialog myself so I always leave it unchecked.
-
I get that, but when debugging becomes necessary, it's really handy to turn it on so you can choose one of the restart options that you need.

In today's case, I wanted to restart with add-ons disabled, but ended up manually disabling them before restarting because I had not located this option in a timely manner.  It's a heck of a lot quicker to just restart with add-ons disabled.

Now I'll know how to toggle this if someone else were to have chosen to turn it off.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 

-- 
Dan Beaver (KA4DAN)


Re: NVDA's handling of checkboxes especially in Google Chrome

 

I have been using firefox for ages now.

And recently after waterfox started going down the toilet, I have updated to the latest firefox.

So the biggest issue, no noscript or at least I don't care for the new interface but thats just about it.

The only gripe is that firefox is a little slow to start of late like 30 seconds a load.

It always says unknown when it opens but then its fine once loaded and its really not a big gripe in any case.

My only thing I miss is that waterfox seemed to be able to block youtube adds by default.

I know, I really should pay for youtube at least the basic level so I can make them go I mean I do listen to it a lot but even so.



On 17/11/2021 5:13 am, Gene wrote:
I’d be interested in whether others find it slow.  This may just be my experience, but Firefox seems to me to be much faster than it used to be.  I’ve started using it a lot more and I’m considering using it as my main browser.
 
Gene
-----Original Message-----
From: Steve Nutt
Sent: Tuesday, November 16, 2021 3:32 AM
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome
 

It’s just a shame that Firefox is so slow compared with Chrome, certainly on all my machines it is.

 

All the best


Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Sackrider
Sent: 16 November 2021 00:10
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

        I have an example of whear fire fox will and nvda will see somthng but chrome brousers don't.  The audio of the lions magazine in both edge and chrome there is no down it all button but in fire fox there is a down it all button.  I am not surprised about other things that fire fox sees that chrome brousers don't this is why I say that for the blind chrome based brousers are kind of usless junk and this is the reason that I use internet explorer for as long as I did as it was not a chrome based brouser.  I have windows 11 and there is no more internet explorer so I had to find a nonchrome based brouser and thats why i am using fire fox as my default brouser.

Brian Sackrider

On 11/15/2021 5:12 PM, Gene wrote:

I am increasingly finding cases where Firefox either sees things or does things that Chrome doesn’t when used with NVDA.  I don’t use JAWS and my demo is far too old to evaluate whether the same things occur.  But I think the question of whether Chrome-based browsers are working properly with sites in terms of accessibility should be systematically addressed.

 

Here are two examples:

First is this article from The New York Times;.

If you are at the top of the page and press s to move by separator, you will immediately move to cards giving background information on the story.

In Firefox, you see, at the end of the card, a button for previous card, unavailable since you are on the first card, and a button for next card.

Activating this button works.  It moves you to the next card.

To easily get to this card in a proper position to read it, press page up, then s for separator.

The previous and next card buttons both work correctly for this card and, I assume, for all other cards.

 

I tested with Chrome and Brave and neither of these Chrome-based browsers saw either button. I could read the first card below the separator but no buttons are displayed.


I’ve recently been looking up material on occasion using the Encyclopedia Britannica online.  When reading with Firefox, the page being read automatically shows new material as you move down it.  Firefox shows this new material when it appears.  Chrome-based browsers don’t. 

This article is an example:

 

Search from the top of the page for the word nervous.  If you down arrow in Firefox, the text continues after some items, perhaps three or four.  Chrome-based browsers don’t load new material at least not accessibly to screen-readers.

 

Chrome-based browsers don’t see comments on Youtube pages where videos are streamed.  Firefox does.  Because the page changes as you move down it, you have to move down the page to see the comments.  You can’t just search for the word comment to get to the section.

 

I’ll add that all these comments are for my specific machine but I expect they will be generally experienced.  Verification, however, is necessary.

 

Are these problems with Chrome, with NVDA, or both?  I suspect that these problems are not improper implementation of accessibility.  Those questions, however, would require technically knowledgeable investigation to be resolved.

 

Gene

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

From: Gene

Sent: Monday, November 15, 2021 11:00 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Since Firefox sees the checkboxes, I don’t know that its valid to assume what the problem is and that it is improper design.  Also, there may be cases where you will hear explanatory text that accompanies a structure read if you tab into the structure rather than move to it in some other way.  I haven’t compared Chrome-based and not Chrome-based browsers in these cases but again, is this improper design or just the complexity of design?

 

Gene

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

From: Jackie

Sent: Monday, November 15, 2021 10:55 AM

Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome

 

Yeah well, I'm not trying to be obscene here, but it's because the web
designers didn't use checkboxes that expose themselves, or, perhaps to
put it just a bit more succinctly, expose their state. & it is a royal
pita, & it's not unique to NVDA, though having said thus, sometimes
Jaws actually allows labeling of these graphics, whereas NVDA doesn't.
& it's not an issue specific to Chrome, either. It's actually called a
"clickable element" as opposed to a checkbox. Sighted folks generally
cant distinguish these from standard checkboxes, but they sure create
problems for us.

On 11/15/21, Tyler Zahnke mailto:programmer651@... wrote:
> Hello NVDA community! Why does NVDA not read some checkboxes in Google
> Chrome? NVDA reads a lot of them, but some sites have a "remember me"
> checkbox on their login screen that just says "clickable"; when you
> press Enter where it says clickable, the box checks, but NVDA doesn't
> tell you this. I have seen websites that contain both accessible and
> inaccessible checkboxes, why is this? And several times (I have a
> memory of seeing this on the login screen of Palai), it doesn't read
> some of the checkboxes, such as "remember me", at all. It actually got
> to the point where I thought they had removed the checkbox from their
> site because it completely didn't read it, but users of other devices
> claimed they still saw the checkbox, but several of us Chrome and NVDA
> users noticed the missing checkbox. And as soon as I tried the same
> site with Firefox and NVDA, I saw the checkbox, but it said "remember
> me clickable" and therefore, though you could check and uncheck it,
> NVDA wouldn't tell you, while on Chrome, NVDA skips over the box. This
> was a problem with a website that I actually had to help out as far as
> accessibility; their site had some regular checkboxes on the form and
> screen readers could read it just fine, but then some checkboxes said
> "clickable" or didn't say anything at all, yet the Enter key worked on
> them but the screen reader didn't say. I've probably seen variations
> on this issue for a few years, some checkbox not displaying in Chrome.
> Often I would try it again with Firefox, and at least in the
> checkbox-related cases, it usually worked. And in the case of the
> website I helped make accessible, I even looked at the HTML for the
> checkboxes, and even the inaccessible checkboxes were still coded like
> checkboxes though they may have had some extra styling on them. So
> what's the deal with checkboxes?
>
>
>
>
>
>


--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com




Re: Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

 

On Tue, Nov 16, 2021 at 02:50 PM, Dan Beaver wrote:
I hate the dialog myself so I always leave it unchecked.
-
I get that, but when debugging becomes necessary, it's really handy to turn it on so you can choose one of the restart options that you need.

In today's case, I wanted to restart with add-ons disabled, but ended up manually disabling them before restarting because I had not located this option in a timely manner.  It's a heck of a lot quicker to just restart with add-ons disabled.

Now I'll know how to toggle this if someone else were to have chosen to turn it off.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 

7401 - 7420 of 97012