-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
User Guide: Document braille shorthands for controls such as dlg and tv #4130
Comments
Comment 1 by nvdakor on 2014-05-09 22:02 |
Comment 2 by nvdakor on 2014-05-09 22:22
|
Comment 5 by Mesar Hameed <mesar.hameed@... on 2014-08-27 10:01
Changes:
|
Comment 6 by jteh on 2014-08-27 12:33
|
Comment 7 by Mesar Hameed <mesar.hameed@... on 2014-08-27 18:50
|
Comment 8 by Mesar Hameed <mesar.hameed@... on 2014-09-05 10:02
Changes:
|
Comment 9 by jteh on 2014-09-06 00:19 |
Comment 10 by jteh on 2014-09-06 01:17 |
Comment 11 by surfer0627 on 2014-12-25 07:36 versus: source/braille.py Translators: Displayed in braille when an object (e.g. a tree view item) is expanded.controlTypes.STATE_EXPANDED: _("-"), Translators: Displayed in braille when an object (e.g. a tree view item) is collapsed.controlTypes.STATE_COLLAPSED: _("+"), |
Comment 12 by jteh on 2015-01-06 03:59 |
Comment 13 by surfer0627 (in reply to comment 12) on 2015-01-06 06:20 |
Comment 14 by jteh on 2015-01-06 06:31 |
Comment 15 by jteh on 2015-01-06 06:34 |
Comment 16 by surfer0627 (in reply to comment 15) on 2015-01-06 06:57 |
Reported by nvdakor on 2014-05-07 22:35
Hi,
Just like other screen readers, NVDA provides braille shorthands for controls such as dialog (dlg), treeview (tv) and such. Although a seasoned braille user may be able to pick up easily, this may confuse new users who are getting started with screen reading software and braille in general. One suggestion posted on the NvDA list is to document braille shorthands for controls such as dlg for dialog in the user guide to help beginners learn different shorthands used by NVDA.
Tahnks.
Blocking #4142
The text was updated successfully, but these errors were encountered: