New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

+ / - buttons to open and collapse regions does not work with NVDA screen reader #32

Closed
HerinHentry opened this Issue Mar 22, 2018 · 6 comments

Comments

Projects
None yet
3 participants
@HerinHentry

HerinHentry commented Mar 22, 2018

Hi,

Looking into the page https://www.w3.org/WAI/beta/planning-and-managing/initiate/.
The + and - works fine with a mouse, keyboard. But, when NVDA is on it does not work. Checked in Chrome.

Can someone please try to reproduce the same in JAWS?

Thanks

@yatil yatil self-assigned this Mar 22, 2018

@yatil yatil added the bug label Mar 22, 2018

@yatil yatil added this to the Launch milestone Apr 13, 2018

@yatil

This comment has been minimized.

Member

yatil commented Apr 13, 2018

I was able to open the section using NVDA in Chrome (Windows 8.1), but not to close it. Need to closer investigate.

@charadani

This comment has been minimized.

charadani commented May 7, 2018

In my testings, the only way in which this components work reliably while NVDA is in use is by pressing the NVDA+F2 combination, which passes keyboard control back to the browser. Whenever this keystroke is pressed, or the screen reader is in focus mode, the component works reliably: it expands or collapses when The Enter or the Space key is pressed.

I tested it with NVDA 2018.1.1 and Chrome and Google Chrome Versión 66.0.3359.139

@yatil

This comment has been minimized.

Member

yatil commented May 7, 2018

@charadani Thanks for the feedback – Do you think that’s known to NVDA users? I have the feeling that websites can’t do much if NVDA doesn’t pipe the keystroke through to the browser.

@yatil

This comment has been minimized.

Member

yatil commented May 9, 2018

We decided to push this back to tackle once we have a better understanding of why NVDA is doing what it's doing. Currently, we are not getting any keyboard events when not in focus mode, so there is nothing that we can do right now.

@yatil yatil modified the milestones: Launch, Second Wave May 9, 2018

@yatil

This comment has been minimized.

Member

yatil commented Jul 25, 2018

I asked a screen reader user to give feedback on this.

@yatil yatil modified the milestones: Second Wave, Third Wave Jul 25, 2018

@yatil

This comment has been minimized.

Member

yatil commented Sep 5, 2018

We did not get any more feedback about this, so it seems to be usable. I’ll keep an eye on user feedback and see if it turns out to be a problem.

@yatil yatil closed this Sep 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment