You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Numbering of questions should be considered globally. It would be inconsistent for some sections of the questionnaire to be numbered, but not others.
This will greatly increase the difficulty in maintaining the questionnaire. Numbers will need to be consistent across the 4/8 sources of text (question en/fr as well as results en/fr, and duplication for Design vs. Implementation stage). Adding a question in early pages would require the questions in later sections to be renumbered? Using the page as a prefix to the question number might mitigate this effect somewhat, e.g. question 12.2 would be the 2nd question on page 12.
As an alternative, consider re-wording incomplete questions such as "Will this information be made publicly available" to include the appropriate context, e.g. "Will you make publicly available the documented processes in place to test datasets against biases and other unexpected outcomes?"
MrDeshaies
changed the title
AIA Formatting_Results Page_3
Linkage between questions is not obvious
Sep 21, 2020
#461 / #872 made progress on this, numbering questions sequentially. But the sub-questions still are not as obvious as could be, e.g. "Will you make this information publicly available" or "Please describe" (when other is selected). We could still improve this aspect.
Describe the bug - Décrivez le bogue
Under the Mitigation Measure section, the answers need to be numbered with dependent answers cascading.
For example:
3. Documented processes will be in place to test datasets against biases and other unexpected outcomes.
3 a. This information will be made publicly available.
To Reproduce - Pour reproduire
Steps to reproduce the behavior - Étape pour reproduire le comportement:
Expected behavior
All answers should be numbered along with their dependent (follow up answers)
The text was updated successfully, but these errors were encountered: