Add section on add-on store to the Quick Start Guide in the User Guide

[Qchristensen]

Link to issue number:

N/A

Summary of the issue:

Request from users for more initial documentation on getting around the Add-on store.
This PR adds a section to the Quick Start Guide (in the user guide) on the add-on store.

Description of user facing changes

New sub-topic in the Quick Start Guide section of the User Guide "Add-on Store" after existing section 2.4 Preferences and before 2.5 Community.

Description of development approach

Testing strategy:

Known issues with pull request:

none

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

[seanbudd]

Thanks @Qchristensen - generally looks good to me

[seanbudd]

It might be worth mentioning what fields you can search by (add-on ID, display name, publisher, author or description)

[Qchristensen]

Suggested change

	The list changes while typing the search, once done, press ``tab`` to go to the filtered list of add-ons.
	The search field can contain information including the add-on ID, display name, publisher, author or description.
	The list changes while typing the search, once done, press ``tab`` to go to the filtered list of add-ons.

[seanbudd]

This section seems more or less identical to AddonStoreFilterSearch, perhaps it's just worth moving that section here?

[Qchristensen]

Similar, but I think worth mentioning in both places - in fact, there shouldn't be much in the quick start guide which ISN'T replicated elsewhere, albeit reworded.

mistaken approval

[gerald-hartig]

Suggested change

	As with any software, it is important to be confident in the developer of an add-on before using it.
	As with any software, it is important to be confident in the developer of an add-on before using it.
	You can do this by researching their reputation (eg. how long have they been contributing, look for user feedback in the NVDA user or add-on groups), verifying that the add-on is regularly updated, and seeking community feedback through the forums or social media.

[Qchristensen]

We should probably mention the "Community reviews" here?

I'm also not sure we should add too much more here when we don't actually mention this in 13.2 - perhaps we should expand on this in 13.2 and add a brief mention here that "As with any software, it is important to be confident in the developer of an add-on before using it. Section 13.2.1 contains tips on researching add-ons and authors, such as community reviews"?

[gerald-hartig]

That sounds like a better solution.

[Qchristensen]

I have created PR #16510 to add @gerald-hartig's suggestions to the main add-on section. I'd like to propose that PR be accepted at the same time or before this one, so the following makes sense:

Suggested change

	As with any software, it is important to be confident in the developer of an add-on before using it.
	As with any software, it is important to be confident in the developer of an add-on before using it.
	Please refer to [Installing Add-ons #AddonStoreInstalling] for ways to verify add-ons prior to installation.

[Qchristensen]

We don't give instructions like this through most of the user guide (that's more a training module area). I feel saying something like this is needed here until #16485 is implemented (if that were implemented, I think we could drop this line). In the meantime, I've suggested"reading text" which links to the quick start guide topic of that name - https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ReadingText Otherwise we could say "Use the Say all, or navigation keys"?

Suggested change

	Use the reading or ``arrow keys`` to read the full description.
	Use the [reading text #ReadingText] or ``arrow keys`` to read the full description.

[XLTechie]

@Qchristensen I'm not sure "use the reading text" makes sense. It's like "Use the force", without there being a force. :-)

I get that you mean it to be read "Use the reading text keys, or the arrow keys", but even that sounds awkward since "reading text keys" aren't a thing.
"reading keys", okay, as a general shorthand for "review or object nav keys", but "reading text keys"? Hmmm.

[Qchristensen]

I would like an excuse to write "Use the force" in the user guide somewhere! Happy to accept a change here - I was originally thinking of saying use "Say all", but that is just one of any number of keys you COULD use to read text with. I don't think there are (many, or any?) other examples of this kind of instruction in the User Guide, as it's not how it is written. If we could have NVDA read that whole text field on focus it would negate the need to give any specific instruction here :) I wasn't keen to leave it unsaid though as it is easy to get to that description field, have it read one line and not know whether there is more or that you need to specifically read it if there is.

I just had a look in Basic Training and I mention "Reading keys" or "Reading and navigation keys" in a couple of places.

[lukaszgo1]

Perhaps this is more of a discussion for #16485 but for me NVDA reports that this field is multiline, which pretty clearly indicates there may be more than one line there. Why it is a problem in the add-on store specifically and not in many other places - when tabbing into an multiline edit field on web pages for example?

[Qchristensen]

This PR has been superseded by #16553 against the md file rather than the t2t file. I believe I've incorporated all the suggestions made to date. Please make any future suggestions against the new PR.