Search behavior stories

[nicolebrennan]

At a glance

Identifying what is uniquely government about search and what we know about how people interact with our government info systems.

In order to identify what is uniquely government about search, we are piecing together what we know about how people interact with our government info systems

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

Scenario:

Given
when
...

### then...
- [ ] https://github.com/GSA-TTS/jemison/issues/166
- [ ] https://github.com/GSA-TTS/jemison/issues/168
- [ ] https://github.com/GSA-TTS/jemison/issues/174
- [ ] https://github.com/GSA-TTS/jemison/issues/172
- [ ] https://github.com/GSA-TTS/jemison/issues/173

Shepherd

• Product shepherd: Nicole Brennan
• UX shepherd: Nicole Brennan

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.

[nicolebrennan]

Meeting with DK to review baseline behaviors and initial personas.