Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatic suggestions in the address fields in www.gmail.com compose message are not read by NVDA #5676

Closed
sumandogra opened this issue Jan 13, 2016 · 9 comments
Closed

Automatic suggestions in the address fields in www.gmail.com compose message are not read by NVDA #5676

sumandogra opened this issue Jan 13, 2016 · 9 comments
Assignees
@michaelDCurran
Labels
blocked close/worksforme GoogleWork

Comments

@sumandogra
Copy link

NVDA remains silent and does not give any info bout the automatic suggestions in the address fields in the compose message of www.gmail.com.
Steps to reproduce:

  1. Open www.gmail.com.
  2. Login to your account.
  3. Press ALT+C to open compose message window.
  4. Go to the address edit field, To, Cc.
  5. Type in a few characters for the address already resent in the contacts list.
  6. No automatic suggestions are read.
  7. TAB to input and address. No information is read by NVDA
@jcsteh
Copy link
Contributor

jcsteh commented Jan 13, 2016 via email

@sumandogra
Copy link
Author

It does not work in internet explorer.

From: James Teh [mailto:notifications@github.com]
Sent: Wednesday, January 13, 2016 3:57 PM
To: nvaccess/nvda nvda@noreply.github.com
Cc: sumandogra sumandogra6@gmail.com
Subject: Re: [nvda] Automatic suggestions in the address fields in www.gmail.com compose message are not read by NVDA (#5676)

What browser? Works fine for me in Firefox.

—
Reply to this email directly or view it on GitHub #5676 (comment) . https://github.com/notifications/beacon/AHIIBvXIv65kHJ8TUpTwAwXpgnL8bmNcks5pZh3ogaJpZM4HD0jk.gif

@nvaccessAuto
Copy link

Incubated in b718586.

@jcsteh jcsteh added this to the 2016.2 milestone Feb 1, 2016
@nvaccessAuto
Copy link

Incubated in 47daf9a.

@nvaccessAuto
Copy link

Incubated in c078fcc.

@jcsteh
Copy link
Contributor

jcsteh commented Apr 7, 2016

@sumandogra: What version of Internet Explorer were you testing with? While we did fix a problem with NVDA switching to browse mode incorrectly when address suggestions appear, even without this fix, suggestions still get read for us. Could you please re-test this with both master and next branches? If you can still reproduce this, a log file at level input/output would be useful.

jcsteh pushed a commit that referenced this issue Apr 13, 2016
@michaelDCurran @jcsteh
In Internet Explorer and other MSHTML controls, moving focus to certa…
9e944f1 
…in controls (specifically, where aria-activedescendant is used) no longer incorrectly switches to browse mode. This occurred, for example, when moving to suggestions in address fields when composing a message in Gmail.

MSHTML NVDAObject: expose focusable and focused states if this object is the active descendant of the focus as IE fails to do this itself. This code was moved from shouldAllowIAccessibleFocusEvent into states.
Re #5676.
@jcsteh jcsteh removed this from the 2016.2 milestone Apr 13, 2016
@jcsteh
Copy link
Contributor

jcsteh commented Apr 13, 2016

This fix addresses one issue, but we couldn't reproduce the original report, so leaving open for now pending a response from @@sumandogra.

jcsteh pushed a commit that referenced this issue Apr 29, 2016
@michaelDCurran @jcsteh
In Internet Explorer and other MSHTML controls, moving focus to certa…
615f6b2 
…in controls (specifically, where aria-activedescendant is used) no longer incorrectly switches to browse mode. This occurred, for example, when moving to suggestions in address fields when composing a message in Gmail.

MSHTML NVDAObject: expose focusable and focused states if this object is the active descendant of the focus as IE fails to do this itself. This code was moved from shouldAllowIAccessibleFocusEvent into states.
Re #5676.
@jcsteh jcsteh removed the incubating label May 3, 2016
@feerrenrut feerrenrut mentioned this issue Sep 20, 2017
Closed
@bhavyashah
Copy link

bhavyashah commented Aug 19, 2018 •
edited

@sumandogra Could you please respond to @jcsteh's request for a status update in #5676 (comment)?

@jcsteh jcsteh added the blocked label Aug 19, 2018
@Adriani90
Copy link
Collaborator

I cannot reproduce this issue in IE11 and the author seems not to be available anymore. Closing this issue for now as works for me. If someone reports it again we can reopen it. Thanks.

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

@michaelDCurran michaelDCurran

Labels
blocked close/worksforme GoogleWork
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jcsteh @sumandogra @michaelDCurran @nvaccessAuto @bhavyashah @Adriani90