Description
Users disputing a hold need a clear path to submit an appeal. Design an appeal-submission form with reason categories, free-text explanation, attachment slots, and a confirmation screen with expected review timeline.
Requirements and context
- Must be accessible (WCAG 2.1 AA), responsive, and documented in the design system
- Should be consistent with existing patterns and easy to review
- Relevant code:
src/components/ComplianceHoldBanner.tsx
- Form must autosave draft locally and warn on exit
Suggested execution
- Fork the repo and create a branch
git checkout -b uiux/compliance-appeal-form
- Implement changes
- Design the form fields and attachment slots
- Specify autosave chip and unsaved-changes warning
- Draft the confirmation screen with timeline
- Validate accessibility and responsive assumptions
Test and commit
- Run checks
npm run lint and component/visual tests
- Cover edge cases
- Large attachments, offline draft recovery, RTL text
- Include screenshots/before-after and accessibility (axe) notes
Example commit message
design: compliance appeal form
Guidelines
- Minimum 95 percent test coverage
- Clear documentation
- Timeframe: 96 hours
Description
Users disputing a hold need a clear path to submit an appeal. Design an appeal-submission form with reason categories, free-text explanation, attachment slots, and a confirmation screen with expected review timeline.
Requirements and context
src/components/ComplianceHoldBanner.tsxSuggested execution
git checkout -b uiux/compliance-appeal-formTest and commit
npm run lintand component/visual testsExample commit message
design: compliance appeal formGuidelines