Create User Journey for AT Developers

[richnoah]

As an AT Developer, I need to have a defined journey in the ARIA-AT App.

[s3ththompson]

Please find a draft of AT Developer user journeys from @isaacdurazo on the User Journeys 2022 wiki page.

There following 3 scenarios are ready for feedback and prioritization discussion:

• Review a Candidate Test Plan with no failing assertions
• Raise an Issue for a Candidate Test Plan with failing assertions
• Review a Candidate Test Plan after issues have been resolved

Note: @isaacdurazo and I are planning to add additional context to these user journeys this week to capture the existing capability gap and provide a starting point for prioritization.

[s3ththompson]

cc @mcking65 @jscholes @SamuelHShaw

[isaacdurazo]

Additional context has been added to these User Journeys to capture existing gaps in them and suggestions for changes to improve them.

[SamuelHShaw]

@s3ththompson @isaacdurazo @richnoah

Here is PAC's Feedback on User Journeys

User Persona: Test Admin

1. Under "Phase 3: Candidate Test Plan Review" -> "Scenario 4: Promote a Draft Test Plan to Candidate Test Plan", the Precondition reads "When at least two testers have fully executed a Test Plan in at least one browser"

As far as we know, our current approach is that a test plan can only be promoted to Candidate status after being completed by at least two testers, in one browser with each supported assistive technology.

Is this understanding correct, and if so, does the wording of these user journeys need to be updated?

2. Under "Phase 4: Recommended Test Plan Reporting" -> "Scenario 5: Promote a Candidate Test Plan to Recommended Test Plan", the precondition reads "The test plan has been in the Candidate phase for at least 120 days and no issues have been open for it."

The grammar in this sentence makes its meaning ambiguous. If it is implying that no issues have been opened (past tense), then the intent is not correct. It is acceptable for issues to be opened, and then closed, within the 120-day period, permitting the test plan to move to Recommended status no matter how many open issues there may have been.

3. For the same scenario, the second step of choosing a test plan seems to be missing.  The steps imply that the user will activate the "Mark as Recommended" button for the entire queue.

4. Under the same phase, but in "Scenario 6: Publish a Recommended Test Plan Report", in the section: User Journey gaps and/or suggested changes:

"Ability to let AT Developers promote a Candidate Test Plan to Recommended"...is listed as a potential change, but we don't understand why. It is the role of the Test Admin to move plans through testing phases, not assistive technology vendors who shouldn't have admin access on the system.

[isaacdurazo]

@SamuelHShaw sorry for my late response and thanks for the feedback. I have addressed it all in the user journeys.