Link to issue number:

N/A

Summary of the issue:

There is no set of standards or guide when writing documentation for the "User Guide".

Description of user facing changes

The intended audience for this PR is NVDA contributors.
NVDA developers now have suggested formatting for key commands and feature flags.

Feature flag documentation suggests using definition lists.
The default CSS formatting for definition lists is not ideal, the term and definition are listed on separate lines. There is no text formatting, the only indication that a term is linked to a definition is an indentation in front of the term.

This is an example of default formatting:

Example of new formatting, where all text is smaller and italicised, terms are bold and definitions are on the same line as the term.
FireFox/Chrome:

Mobile:

Description of development approach

Created a style guide document

Testing strategy:

Tested rendering the user guide with #13131

Known issues with pull request:

Change log entries:

Code Review Checklist:

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