E-mail List Archives
Thread: Working With Buttons
Number of posts in this thread: 3 (In chronological order)
From: David Russell
Date: Wed, Apr 19 2023 11:32AM
Subject: Working With Buttons
No previous message | Next message →
Hello WebAim,
I am completing a registration forum on the website: draft2digital.com
as a self-publishing author.
The "interview"(part of the financial information provision) is begun
by pressing the enter key on the line that says, "Button interview."
However, when pressing enter, the interview is not accessed.
I understand an option is to use the function return key. If this is
correct, where would the "function return" key be on a querty
keyboard?
NVDA is my screen reader, Google Chroame my browser of choice.
Is utilizing FireFox an option for cases like this?
Thanks for your help in advance.
--
David C. Russell
= EMAIL ADDRESS REMOVED =
From: Mike Herchel
Date: Wed, Apr 19 2023 11:40AM
Subject: Re: Working With Buttons
← Previous message | Next message →
I just tested it using Chrome and I was able to hit enter and launch the
interview process using normal keyboard navigation.
For what it's worth, the site doesn't seem very accessible at all. There
are many missing focus states
-Mike Herchel
On Wed, Apr 19, 2023 at 1:32 PM David Russell < = EMAIL ADDRESS REMOVED = >
wrote:
> Hello WebAim,
>
> I am completing a registration forum on the website: draft2digital.com
> as a self-publishing author.
> The "interview"(part of the financial information provision) is begun
> by pressing the enter key on the line that says, "Button interview."
> However, when pressing enter, the interview is not accessed.
> I understand an option is to use the function return key. If this is
> correct, where would the "function return" key be on a querty
> keyboard?
> NVDA is my screen reader, Google Chroame my browser of choice.
> Is utilizing FireFox an option for cases like this?
>
> Thanks for your help in advance.
>
> --
> David C. Russell
> = EMAIL ADDRESS REMOVED =
> > > > >
From: Steve Green
Date: Wed, Apr 19 2023 12:30PM
Subject: Re: Working With Buttons
← Previous message | No next message
I can replicate the issue using NVDA and Chrome. The website does indeed have a lot of accessibility issues, but this particular one appears to be an NVDA bug. When you click the Register button, a dialog is displayed, containing the terms of service. The div element containing the dialog has the attribute role="dialog", which you would expect.
JAWS 2021 reads the contents of the dialog exactly as you would expect, but NVDA does not. It announces the presence of the dialog, but does not read its contents. It behaves as if the dialog had the attribute aria-hidden="true", but it does not. It doesn't help that the "aria-labelledby" attribute has been spelled incorrectly, so neither screen reader announces the name of the dialog.
NVDA does read the contents of the dialog if you either add the attribute tabindex="-1" to the div element or remove the role="dialog" attribute. Neither of these should be necessary. Of course the attribute tabindex="-1" is required for proper keyboard navigation without a screen reader, but its absence should have no effect on NVDA.
Steve Green
Managing Director
Test Partners Ltd