Date   

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

 


Re: 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,

 

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
 

In the settings under general about 3 tabs down the list there is a checkbox that says show exit options when exiting NVDA.  Check it to see the exit dialog or uncheck it to stop showing the dialog.  I hate the dialog myself so I always leave it unchecked.


Dan Beaver

On 11/16/2021 2:37 PM, Brian Vogel wrote:
Hello All,

I have just encountered a situation while assisting another member of the group that I have never encountered before, and none of my NVDA mojo seems to be able to solve the issue.

Under all other circumstances I've ever dealt with, when you attempt to exit NVDA the Exit NVDA dialog appears, the "What would you like to do?," question is announced, and then the combo box with the options to Exit, Restart, Restart with add-ons disabled, and [at least for betas] Restart with debug logging enabled being the 4 choices.  Then there are the OK and Cancel buttons.   This behavior happens whether I use NVDA + Q or NVDA + N, X as my method of invoking exit.

On this particular machine, NVDA just exits, with no exit dialog presented, and apparently has been doing this for some years.  We just installed NVDA 2021.3beta2, and it occurs with this version, too.  This makes me very strongly suspect that there is some obscure NVDA setting, somewhere, that one can set to make NVDA always exit when the exit keystrokes are entered, but I'll be darned if I can find where it is.

If someone knows what needs to be tweaked in order to bring back the NVDA Exit dialog, please share.
--

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)


how to get the dialog box on nvda+q when exiting

mike mcglashon
 

Okay my friend:

 

I went into nvda menus and I found the checkbox that says “show options on nvda exit” it is a checkbox;

Nvda+n to go to menu,

Then preferences,

Then settings,

Then under general from the combo box,

Tab three times,

(the first is language,

Second tab is save configuration on exit,

And “show exit options” checkbox, I checked it;

Now it asks me what I want to do on nvda+q exit;

 

Please advise as you like.

 

Mike M.

 

Mike mcglashon

Email: Michael.mcglashon@...

Ph: 618 783 9331

 


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

 

Thank you, gentlemen.  I really don't know how I missed this.  I somehow got hung up on the entry above it about saving configuration and selectively overlooked it.

Apparently the default setting, as shipped, is ON/checked and it got set to OFF/unchecked at some unspecified point in the past.
--

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: Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

Chris
 

Try nvda general settings and > show exit options

Make sure its checked

 

From: Brian Vogel
Sent: 16 November 2021 19:37
To: nvda@nvda.groups.io
Subject: [nvda] Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

 

Hello All,

I have just encountered a situation while assisting another member of the group that I have never encountered before, and none of my NVDA mojo seems to be able to solve the issue.

Under all other circumstances I've ever dealt with, when you attempt to exit NVDA the Exit NVDA dialog appears, the "What would you like to do?," question is announced, and then the combo box with the options to Exit, Restart, Restart with add-ons disabled, and [at least for betas] Restart with debug logging enabled being the 4 choices.  Then there are the OK and Cancel buttons.   This behavior happens whether I use NVDA + Q or NVDA + N, X as my method of invoking exit.

On this particular machine, NVDA just exits, with no exit dialog presented, and apparently has been doing this for some years.  We just installed NVDA 2021.3beta2, and it occurs with this version, too.  This makes me very strongly suspect that there is some obscure NVDA setting, somewhere, that one can set to make NVDA always exit when the exit keystrokes are entered, but I'll be darned if I can find where it is.

If someone knows what needs to be tweaked in order to bring back the NVDA Exit dialog, please share.
--

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: Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?

Gene
 

It is in the general settings and it is a check box.  The text says, Show exit options when exiting.
 
Gene

-----Original Message-----
Sent: Tuesday, November 16, 2021 1:37 PM
Subject: [nvda] Quitting NVDA - The standard "what do you want to do" dialog with combo box is not appearing. Why?
 
Hello All,

I have just encountered a situation while assisting another member of the group that I have never encountered before, and none of my NVDA mojo seems to be able to solve the issue.

Under all other circumstances I've ever dealt with, when you attempt to exit NVDA the Exit NVDA dialog appears, the "What would you like to do?," question is announced, and then the combo box with the options to Exit, Restart, Restart with add-ons disabled, and [at least for betas] Restart with debug logging enabled being the 4 choices.  Then there are the OK and Cancel buttons.   This behavior happens whether I use NVDA + Q or NVDA + N, X as my method of invoking exit.

On this particular machine, NVDA just exits, with no exit dialog presented, and apparently has been doing this for some years.  We just installed NVDA 2021.3beta2, and it occurs with this version, too.  This makes me very strongly suspect that there is some obscure NVDA setting, somewhere, that one can set to make NVDA always exit when the exit keystrokes are entered, but I'll be darned if I can find where it is.

If someone knows what needs to be tweaked in order to bring back the NVDA Exit dialog, please share.
--

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

 


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

 

Hello All,

I have just encountered a situation while assisting another member of the group that I have never encountered before, and none of my NVDA mojo seems to be able to solve the issue.

Under all other circumstances I've ever dealt with, when you attempt to exit NVDA the Exit NVDA dialog appears, the "What would you like to do?," question is announced, and then the combo box with the options to Exit, Restart, Restart with add-ons disabled, and [at least for betas] Restart with debug logging enabled being the 4 choices.  Then there are the OK and Cancel buttons.   This behavior happens whether I use NVDA + Q or NVDA + N, X as my method of invoking exit.

On this particular machine, NVDA just exits, with no exit dialog presented, and apparently has been doing this for some years.  We just installed NVDA 2021.3beta2, and it occurs with this version, too.  This makes me very strongly suspect that there is some obscure NVDA setting, somewhere, that one can set to make NVDA always exit when the exit keystrokes are entered, but I'll be darned if I can find where it is.

If someone knows what needs to be tweaked in order to bring back the NVDA Exit dialog, please share.
--

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

Gerardo Corripio
 

Here in Mexico it’s about $1400mxn hoever I got it not directly from Code Factory, but thought an online store “ATGuys” for $69usd. And yes I use Eloquence as my default voice too.

Gera
Enviado desde mi iPhone SE (2nd Generation) de Telcel

El 16 nov 2021, a la(s) 12:09 p.m., zvonimir stanečić, 9a5dsz <zvonimirek222@...> escribió:



Hi,

Eloquence and vocalizer package costs 59 euros.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Viris g. Rodriguez
Sent: Tuesday, November 16, 2021 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

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: nvda vocalizer & eloquence synthesizer plugin

zvonimir stanečić, 9a5dsz <zvonimirek222@...>
 

Hi,

Eloquence and vocalizer package costs 59 euros.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Viris g. Rodriguez
Sent: Tuesday, November 16, 2021 7:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda vocalizer & eloquence synthesizer plugin

 

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: nvda vocalizer & eloquence synthesizer plugin

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

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 (#89738) | 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: More granular reporting of font/style information?

Luke Robinett
 

Makes sense. Yeah I did set up a config profile for it but I didn’t know I could assign a hot key to it. That is nifty! I’ll play around with that and see if that gets me close enough to what I need. Thanks

On Nov 15, 2021, at 7:36 PM, Quentin Christensen <quentin@...> wrote:


There isn't currently a way to separate announcement of strikethrough from other font attributes.

The options I can think of (unless there is an add-on with more granularity?) are basically:

- Create an issue on: https://github.com/nvaccess/nvda/issues outlining the need and use case
- See if your team can change the way they report changes
- If the page doesn't have a lot of other font attribute changes, another option is to set a configuration profile with font attributes enabled, and assign it a keystroke so that you can enable that configuration easily.

See our recent In-process blog article on using Configuration Profiles: https://www.nvaccess.org/post/in-process-19th-august-2021/#Profiles
Here's an older blog post which covered using Input gestures: https://www.nvaccess.org/post/in-process-24th-july-2018/#InputGestures

Kind regards

Quentin.

On Tue, Nov 16, 2021 at 9:46 AM Luke Robinett <lukelistservs@...> wrote:
Hi,
I need to know when text on a particular website has been formatted as strikethrough. I found that if I enabled the font attributes setting from the document formatting tab of NVDA settings this reports the strikethrough attribute, but it also reports all other attributes of fonts, which is way too much information. I just need to know when something is strikethrough because this is how my development team indicates a requirement that no longer needs to be considered when I’m reviewing a ticket. Is there a way to tell NVDA to only announce if the strike through attribute is present but otherwise behave as normal? If not, I may need to work with my team to get them to capture the information in a different way. I just prefer not to have to change everybody else’s processes if I can fix it on my end. Thanks.






--
Quentin Christensen
Training and Support Manager


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

 

On Tue, Nov 16, 2021 at 12:41 PM, Brian Sackrider 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
-
This can and does vary, widely, based upon a large number of factors.

I have not found any one browser consistently faster, for all pages all the time, than most others.  They all try to claim that they are in benchmarks, but what most of us do in day-to-day use is nothing at all like the benchmark tests.

And I've loved Firefox, and still use it daily, alongside Edge, Brave, Vivaldi, and sometimes Chrome.
--

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

Gene
 

That is one person’s experience and it can’t be generalized from.  Then there is the vfactor of accessibility.  It may be that the accessibility components that work with and in screen-readers changes which browsers load the fastest from sighted experience.
 
Gene

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

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

 

On Tue, Nov 16, 2021 at 12:32 PM, Gene wrote:
Sighted people don’t just see input fields and I strongly believe that blind people shouldn’t put themselves at a disadvantage by just tabbing, as many blind people do, through unfamiliar forms.
-
While I'm 100% in agreement with you, as my last message indicated, this is a choice.  Whether it's by changing screen reader defaults, choosing to do a Read All from the top of the page either before or after tabbing around or after a control you've landed in, it is a choice by the user about whether they do, or do not, review the page content.

There is no way this can be changed by changing default screen reader behavior.  It's something a screen reader user must learn to do and choose to do, regardless of the "how" based on the way they have their screen reader settings configured.

There is some "information blackout" that is terribly, terribly hard to overcome.  But just doing a page review, once, on a new-to-you page you will be visiting again and again and again is always a good idea.  Mind you, I'm talking pages that don't change.  Something like a newspaper is something you're likely to do a broader review on anyway, but still the "quick and dirty" perusal will likely be using either headings or links to get today's lay of the land.
--

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

Brian Sackrider
 

    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's handling of checkboxes especially in Google Chrome

 

On Tue, Nov 16, 2021 at 12:24 PM, Gene wrote:
If you tab you will move and the mode will automatically switch.
-
No, Gene, it doesn't.  Tab shoots you to the next control you can interact with, and you're still in forms mode.  When you hit the end of the page it will circle back to the top.

The login page being discussed is short enough that a brute force tabbing doesn't take much more than 30 seconds, tops, but I do not go into browse mode unless I force it.

And, no matter what you do, you can miss content.  In the vast majority of cases, when you're dealing with an online form, and a login screen is really just that, the things of highest import are the various controls you can interact with (and that, of course, are defined as visible).

I know that you have a predisposition to not liking automatic mode changing, and that's fine, but for most users, most of the time, maximum efficiency in traversing the things they can interact with is of primary importance.  That's one reason, among many, that folks should NOT explore an unfamiliar page for the first time strictly by brute force tabbing.  There will always be other information available that you should know about before acting on that page for the first time.

And in the case of this specific login page, it matters not one bit whether you're in browse mode and do a "read all" or are down arrowing on the page in a Chromium-based browser.  The Remember Me control is not being announced, and until I hear otherwise I have to believe that's because the attribute for hidden is turned on and that the browser is honoring it at all times for Chromium-based browsers and selectively honoring it in Firefox.

As far as your objections go, and I'm not saying they're wrong, it is still a classic case of no matter what defaults are chosen, someone is not going to like them.  These defaults have been in place for years, the default state can be shut off, and the default behavior is pretty much exactly the same in JAWS.  This is a case where this consistency across products is so well known that messing with the defaults now is just not a good idea.
--

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

Gene
 

You never know when you may see text between form fields instructing you on how to fill out this or that field or giving information on what you are about to fill out.  Sighted people don’t just see input fields and I strongly believe that blind people shouldn’t put themselves at a disadvantage by just tabbing, as many blind people do, through unfamiliar forms.
 
Gene

-----Original Message-----
Sent: Tuesday, November 16, 2021 11:22 AM
Subject: Re: [nvda] NVDA's handling of checkboxes especially in Google Chrome
 
Yeah, even in 2005 when NVDA didn't exist, no matter what screen
reader I was using, I always went into focus mode for input elements,
and as soon as I was done filling it, went to browse mode to keep
reading; I guess I just like looking at the sites I visit, but perhaps
that's just me.

On 11/16/21, Brian Vogel <britechguy@...> wrote:
> 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
>
>
>
>
>
>




10101 - 10120 of 99695