Submission Detail Page Updates - Evaluator

[r-bartlett-gsa]

User Story

As an evaluator, in order to effectively accomplish all tasks associated with evaluating submissions assigned to me, I would like evaluation workflows to be consistent in design and styles with other eval site features.

Acceptance Criteria:

• When an evaluator clicks on a submission ID or evaluate button, they are sent to the submission detail view that consist of the submission information and evaluation form assigned to the challenge
• Page H1 is Challenge Title (if it's a phased challenge, the phase is indicated in the H1)
• Page H2 is "Submissions [ID]"
• The evaluator can minimize submission information section, or open it in a new tab
  • On desktop the arrow button to minimize the submission information sticks on the screen as the evaluator scrolls the page
• The Evaluator can recuse themselves from evaluating the submission
  • Recusal link displayed at the bottom of submission information as a wanning alert and if selected displays a modal requiring an evaluator to confirm their choice
    • If confirmed, an evaluator is sent to the submission list page with a success alert message displayed confirming that they were recused from the evaluation
• Evaluation form is updated to display calculated scores for each scale option
• The form indicates required fields and validates the input for errors
  • This follows the same error validation designs and message styles as form creation from (for example, instead of "can't be blank" the error message says "Please provide your feedback", "Please provide your score")
• Designs (colors, fonts, labels, etc) match wireframes in Figma: https://www.figma.com/design/sLkJM1Ua9Zu3HW2h4mVdgr/Challenge.gov-Eval-(Updated-01%2F27%2F25)?node-id=7003-153455&t=G2WnCXJa1OXhZSU3-1

Definition of Done

Doing (dev team)

• Code complete
• Code is organized appropriately
• Any known trade offs are documented in the associated GH issue
• Code is documented, modules, shared functions, etc.
• Automated testing has been added or updated in response to changes in this PR
• The feature is smoke tested to confirm it meets requirements
• Database changes have been peer reviewed for index changes and performance bottlenecks
• PR that changes or adds UI
  • include a screenshot of the WAVE report for the altered pages
  • Confirm changes were validated for mobile responsiveness
• PR approved / Peer reviewed
• Security scans passed
• Automate accessibility tests passed
• Build process and deployment is automated and repeatable
• Feature toggles if appropriate
• Deploy to staging
• Move card to testing column in the board

---

Staging

• Accessibility tested (Marni)
  • Keyboard navigation
  • Focus confirmed
  • Color contrast compliance
  • Screen reader testing
• Usability testing: mobile and desktop (Tracy or Marni)
• Cross browser testing - UI rendering is performant on below listed devices/browsers (Tracy or Marni)
  • Windows/Chrome
  • Windows/Edge
  • Mac/Chrome
  • Mac/Safari
  • iOS/Safari
• AC review (Renata)
• Deploy to production (production-like environment for eval capability) (dev team)
• Move to production column in the board

---

Production

• User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
• PO / PM approved (Renata)
• AC is met and it works as expected (Renata)
• Move to done column in the board (Renata)