Bruno Aníbal Prieto González
toggle quoted messageShow quoted text
Hi, this problem is old, I created an issue some time ago notifying
the problem, as I found it in several React libraries, even in the W3C
example, so it is definitely a NVDA problem.
If you want to support with a comment, here is the link:https://github.com/nvaccess/nvda/issues/12266
Thanks, best regards
2021-08-23 20:30 GMT-04:00, Jackie <firstname.lastname@example.org>:
Brian, the problem is that the attribute being used is an on-click
attribute. Thus, the control is neither a link, a button, a checkbox,
a radio--in essence, although it may supposed to represent or simulate
1 of these things, and a sighted person may find it indistinguishable,
if the control doesn't announce itself as being clickable, we won't
know that it indeed is.
On 8/23/21, bestuiexperience <email@example.com> wrote:
I see some advantages to announcing "clickable". In the example with the
listbox it only says "clickable" when in browse mode because when the
is in focus mode, the control will automatically become activated as
opposed to when in browse mode, the control needs first be activated
it can be used.
On Mon, Aug 23, 2021 at 6:23 PM Brian Vogel <firstname.lastname@example.org> wrote:
On Mon, Aug 23, 2021 at 06:08 PM, Jonathan COHN wrote:
IMHO, whenever you encounter a screen reader saying "clickable", it
the web developer has not used ARIA to let the end user know the
type of control you are working with and is therefore a failure of the
Can't disagree with you there.
I have never really understood, really, why even "clickable" is
or preferable for the vast majority of screen reader users beyond those
are absolute beginners with a computer.
At this stage in history I presume, regardless of visual status, that
computer users know exactly what it is that needs to be activated to
an action to occur versus an edit box, which you just fill in. Almost
everything is "clickable" when it comes down to it: Links, buttons,
dropdown lists, and the list goes on and on. The need to "click" to
something happen is the rule, not the exception.
I seem to recall when "clickable" started to be announced, and it was
a couple of years ago unless I'm wrong (and I could be). It always
me as "auditory clutter" that's not telling most users anything they
But this is another thing where I am quite sure others would argue, and
vehemently, that I am crazy to say that. It's another example of what I
mean by defaults need to be chosen and defaults are not always to a
user's liking. If you can tweak things to turn on/off announcement of
things like "clickable" then I'm perfectly happy to learn how to do
Brian - Windows 10, 64-Bit, Version 21H1, Build 19043
Nothing in all the world is more dangerous than sincere ignorance and
~Martin Luther King, Jr.
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
email@example.com 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