fix(ui): extend readability and accessibility beyond overview - #66
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Follow-up to #64 (already merged). That PR improved the shared typography and palette across 37 files. Several everyday controls still hid useful text or lacked keyboard and assistive-technology support: truncated AI templates/options, dimmed missing-data explanations, invisible editor focus, and settings dialogs without focus containment.
Changes
Before / After
Before is current main
f820cf2, including #64. Both sides use the actual Vue browser preview at 1440 × 1000, English, 100%. The capability screenshot uses test-only empty entries, with no account or health readings.Hand to AI
Missing-data explanations
Privacy dialog
Validation
npm run build; 109 existing frontend tests; 33 function/capability tests.Review notes and screenshot context