Link to issue number:

See #14610 (comment),

Summary of the issue:

Sometimes, people open PRs as a draft as required but do not seem to know that they need to transition it to "Ready for review" so that someone at NVAccess look at it.

In the PR template we can read:

Please initially open PRs as a draft. See https://github.com/nvaccess/nvda/wiki/Contributing

But nothing on when it should be set "Ready for review".

Description of user facing changes

See modified file.

Description of development approach

Updated the PR template.

Testing strategy:

• Copy the .md in GitHub's comment area and previsualize it to check that the md syntax is correct, i.e. the modified text does not appear since it is in a comment tag.
• Check when merged.

Known issues with pull request:

None

Change log entries:

None

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
• Security precautions taken.