-
-
Notifications
You must be signed in to change notification settings - Fork 632
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
"Browse mode" is not turned on when the ARIA role of DOCUMENT is detected #1452
Comments
Comment 1 by jteh on 2011-04-12 00:07 This probably sort of worked before #277 was fixed because we didn't care about ARIA applications inside buffers back then, which was incorrect. We actually need to render a separate buffer for the document inside the application. Thus, it also needs #990 to be fixed so we don't render the application inside its parent document. |
Comment 2 by vtsaran on 2011-04-13 05:26 |
Comment 3 by jteh on 2011-04-13 05:32 |
Comment 4 by jteh on 2011-04-28 03:38 This does actually work in Firefox 3.6. It doesn't work in Firefox 4 because you can't call IAccessible::accChild on an object which is not a real document. In this case, the document is fake (by setting its role using ARIA), so accChild fails. |
Comment 6 by jteh on 2011-05-10 06:43 It does not work if the document is an ARIA document (@ROLE="document"). Test case: http://public.yahoo.com/kloots/aria/app-doc-switch.html |
Comment 8 by jteh on 2011-06-09 07:45 ARIA documents work as of Firefox 6 (not yet released), as MozillaBug:653607 has been fixed. We'll address #990 separately, as it isn't necessary if the top level document is an application. |
Comment 9 by jteh on 2011-06-09 07:45 |
Reported by vtsaran on 2011-04-11 23:30
When NVDA detects the role of DOCUMENT, the "Browse Mode" should be turned on giving controls to the virtual buffer. Currently, NVDA announces that the role is present, but does not do anything abut this.
Seems like it's a regression because I remember this working in 2010.1 or earlier.
The text was updated successfully, but these errors were encountered: