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
Force browse mode on demand for broken ARIA applications #2023
Comments
Comment 1 by jteh on 2012-01-03 11:09 You can always use object navigation to move around and focus elsewhere, whether in browse mode or otherwise. |
Comment 2 by camlorn on 2013-02-18 18:32 |
Comment 3 by pitermach on 2013-02-18 20:02 |
Comment 4 by pitermach on 2013-02-18 20:02 |
Comment 5 by erion on 2013-02-18 20:28 |
Comment 6 by jteh on 2013-02-18 22:16 |
Comment 7 by egogi on 2013-02-19 10:41 |
Comment 8 by camlorn on 2013-02-19 18:49 |
Comment 9 by egogi on 2013-02-19 19:01 |
Comment 10 by jteh (in reply to comment 8) on 2013-02-20 23:31
Web sites.
Yahoo! Mail and Google Docs both use the application role correctly.
That defeats the whole point of the application role for sites which implement it correctly. Breaking sites that implement this correctly to work around sites which don't is unacceptable and encourages poor authoring.
NVDA never searches for labels. If the control isn't labelled, it remains as such. Searching for labels can be inaccurate, which can mislead the user with potentially dire consequences.
This doesn't make sense. The whole point of the application role is to specify that something should be treated like a normal application, not a document. That's precisely what NVDA does when the role is used. |
Comment 11 by camlorn on 2013-02-22 04:18 1: Little information is sometimes worse than no information at all, and my statements about how I perceive nvda internals to work are made without having yet looked at the code. I really need to do that at some point. |
Comment 12 by Druify on 2013-06-28 22:11 |
Comment 13 by Q on 2013-07-30 03:22 |
Comment 14 by driemer.riemer@... (in reply to comment 13) on 2013-07-30 04:56
|
Comment 15 by jteh on 2013-07-30 05:49 In case someone else wants to take a stab at this before i get time, one way of doing this is as follows:
|
Comment 17 by James Teh <jamie@... on 2013-10-29 04:02
Changes:
|
Comment 18 by jteh on 2013-10-29 04:04 |
Comment 19 by Michael Curran <mick@... on 2013-12-13 03:34
|
Comment 20 by Michael Curran <mick@... on 2014-01-06 07:23
Changes:
|
Comment 21 by mdcurran on 2014-01-06 07:33 |
Comment 22 by leonarddr on 2014-01-06 17:56 |
Comment 23 by jteh on 2014-01-06 22:59 |
Reported by parham on 2012-01-03 07:47
The application mode (my own on-the-spot term for the mode NVDA goes into when encountering elements with the aria role of application) should be a toggle, meaning that I can disable it if I want. Right now, pressing NVDA+ctrl+space takes me out of that mode (E.G. in TinyMCE editor), but pressing down arrow puts me back to that mode. If I need to access the controls outside the editor, I have to repeatedly press the down arrow, nvda+ctrl+ctrl+space, and so forth. Most of these editors also make the "tab" key output a tab character, so tabbing passed this editors is not an option.
The text was updated successfully, but these errors were encountered: