Support sub-documents in Chrome #5818

Closed
jcsteh opened this Issue Mar 17, 2016 · 6 comments

Projects

None yet

3 participants

@jcsteh
Contributor
jcsteh commented Mar 17, 2016

In Chrome, NVDA doesn't handle, for example, a document inside a dialog inside another document. This requires a change to NVDA, but I also think it's going to need a change to accChild in Chrome.

@jcsteh jcsteh added the GoogleWork label Mar 17, 2016
@jcsteh jcsteh self-assigned this Mar 17, 2016
@derekriemer
Collaborator

For an example of this, see the login dialog on twitter where pressing
nvda+space doesn't put you out of focus mode in the dialog I think.

On 3/16/2016 7:56 PM, James Teh wrote:

In Chrome, NVDA doesn't handle, for example, a document inside a
dialog inside another document. This requires a change to NVDA, but I
also think it's going to need a change to accChild in Chrome.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#5818


Derek Riemer
  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

@derekriemer
Collaborator

Ignore that last comment. I forgot to look at who filed the issue and assumed that example would be needed (when it probably didn't need to be given).

Sent from my heavily encrypted iPhone.
Please disregard errors as this is a smaller device.

On Mar 16, 2016, at 19:56, James Teh notifications@github.com wrote:

In Chrome, NVDA doesn't handle, for example, a document inside a dialog inside another document. This requires a change to NVDA, but I also think it's going to need a change to accChild in Chrome.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

@jcsteh
Contributor
jcsteh commented Mar 17, 2016
@jcsteh
Contributor
jcsteh commented Mar 18, 2016

This does require a fix in Chrome. Filed Chromium issue 595959.

@jcsteh jcsteh added a commit that referenced this issue Mar 18, 2016
@jcsteh jcsteh In Google Chrome and Chrome-based browsers, documents within dialogs …
…or applications can now be read in browse mode. Also, you can now force NVDA to switch to browse mode in web dialogs or applications.

Fixes #5818.
681147e
@nvaccessAuto

Incubated in 314591c.

@jcsteh
Contributor
jcsteh commented Apr 13, 2016

This does require a fix in Chrome. Filed Chromium issue 595959.

Now fixed.

@jcsteh jcsteh added a commit that referenced this issue Apr 13, 2016
@jcsteh jcsteh In Google Chrome and Chrome-based browsers, documents within dialogs …
…or applications can now be read in browse mode. Also, you can now force NVDA to switch to browse mode in web dialogs or applications.

Fixes #5818.
ab6c2e2
@jcsteh jcsteh added a commit that closed this issue Apr 29, 2016
@jcsteh jcsteh In Google Chrome and Chrome-based browsers, documents within dialogs …
…or applications can now be read in browse mode. Also, you can now force NVDA to switch to browse mode in web dialogs or applications.

Fixes #5818.
676b246
@jcsteh jcsteh closed this in 676b246 Apr 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment