Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Pick a real app/website screen (a checkout, a settings page, a signup form) and run a structured HEURISTIC EVALUATION against Nielsen's 10 heuristics. For each issue: name the heuristic violated, describe the problem, and rate its severity. Then redesign the screen (low-to-mid fidelity wireframe or mockup) fixing the top issues, and justify each change in usability terms — not 'prettier'. Include at least one accessibility fix (e.g. color not used alone, sufficient contrast).
Issues correctly mapped to specific Nielsen heuristics; severity rated; problems are real usability issues, not taste.
Wireframe/mockup fixes the top issues; each change justified by usability (hierarchy, error prevention, recognition over recall, etc.).
At least one concrete a11y improvement (contrast meets WCAG AA, meaning not conveyed by color alone, keyboard/focus considered).
Clear before/after with rationale a stakeholder could follow.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Heuristic evaluation + redesign of a real screen ## Goal Pick a real app/website screen (a checkout, a settings page, a signup form) and run a structured HEURISTIC EVALUATION against Nielsen's 10 heuristics. For each issue: name the heuristic violated, describe the problem, and rate its severity. Then redesign the screen (low-to-mid fidelity wireframe or mockup) fixing the top issues, and justify each change in usability terms — not 'prettier'. Include at least one accessibility fix (e.g. color not used alone, sufficient contrast). ## Acceptance criteria - [ ] Heuristic rigor: Issues correctly mapped to specific Nielsen heuristics; severity rated; problems are real usability issues, not taste. - [ ] Redesign quality: Wireframe/mockup fixes the top issues; each change justified by usability (hierarchy, error prevention, recognition over recall, etc.). - [ ] Accessibility: At least one concrete a11y improvement (contrast meets WCAG AA, meaning not conveyed by color alone, keyboard/focus considered). - [ ] Communication: Clear before/after with rationale a stakeholder could follow. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.