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
Context Sensitive Help in NVDA Dialogs #7757
Comments
This sounds like a good idea. Happy to accept a PR for this, though I would suggest the work is split into 3 PR's one for each of the points listed under expected behaviour. |
If we want to use context sensitive help from the user guide, I belief it would help a lot if we'd show the user guide in a ui.browseableMessage |
@ThomasStivers commented:
It seems like pulling up the entire user guide and pointing to specific sections for each control might be a more intensive process. I have thought for some time that NVDA help in the form of a long document, while extremely useful, is becoming less manageable from a usability perspective. I would encourage NVAccess to consider a modular approach to help and documentation that could support tutorial work as well as the current set of user documentation. |
Hi, overall, this is similar in scope to (now discontinued) Control Usage Assistant add-on with help on NVDA options added. CC @derekriemer
|
Explicit anchors to section headings in the user guide for use by context help. Part of issue #7757
Fixes #7757 Fixes #8354 Supersedes PR #8355 Add initial support for opening the user guide at a particular section based on the context when the user presses F1 (in NVDA dialogs). For the sake of simplicity, this is done by opening the user guide in the browser. Unfortunately, this results in a lot of unnecessary verbosity. However, this is still quicker for the user than manually opening the user guide separately (also in a browser) and navigating to the chosen section manually. Co-authored-by: ThomasStivers <thomas.stivers@gmail.com> Co-authored-by: Leonard de Ruijter <leonardder@users.noreply.github.com>
Fixes nvaccess#7757 Fixes nvaccess#8354 Supersedes PR nvaccess#8355 Add initial support for opening the user guide at a particular section based on the context when the user presses F1 (in NVDA dialogs). For the sake of simplicity, this is done by opening the user guide in the browser. Unfortunately, this results in a lot of unnecessary verbosity. However, this is still quicker for the user than manually opening the user guide separately (also in a browser) and navigating to the chosen section manually. Co-authored-by: ThomasStivers <thomas.stivers@gmail.com> Co-authored-by: Leonard de Ruijter <leonardder@users.noreply.github.com>
* Context help: - Added missing helpId in some dialogs/panels - Fixed some helpId - Added calls to self.bindHelpEvent - Fixed parameters (anchor) of some calls to self.bindHelpEvent * Changed the behaviour with voice settings: - if the setting is a standard setting, go to the paragraph that describes this specific setting in User Guide - if the setting is not standard, i.e. specific to a third-party synth, go to speech settings in the User Guide * Rewrite rate boost paragraph as per review comments. Fixes #7757 Follow-up of #11456 No change log entry required. Co-authored-by: Reef Turner <reef@nvaccess.org>
Steps to reproduce:
Expected behavior:
Actual behavior:
Currently NVDA's preferences dialogs do not have a help button and do not respond to the F1 key. The NVDA User Guide explains NVDA's dialogs and controls in detail, but new users find it daunting to locate information quickly.
Similar issues which this is not:
The text was updated successfully, but these errors were encountered: