Evaluation Form Alerts

[r-bartlett-gsa]

User Story

As a challenge manager, in order to successfully setup an evaluation form for my challenge, I would like the system to display helpful alerts to inform me of errors, changes, or anything else that might require my attention.

USWDS guidance for alerts

Acceptance Criteria:

• An error message is displayed at the top of the form create/edit page; it indicates the number of errors and lists errors in order as they appear
  • Error messages are descriptive of what the user needs to provide:
    • Provide [form field label] - for input fields
    • Select [form field label] - for radio buttons
    • Weight for all criteria must add up to 100
    • Criteria points/weight cannot exceed []
      
  • Inline error validation message is relevant to the form field and matches the error message at the top of the page (replacing "can't be blank")
• When a form is successfully saved, the user is sent back to the challenges dashboard page with a success message displayed at the top
  • The message indicates the challenge title/phase for which the form was saved
    
• 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)