fix(a11y): improve landing preview contrast - #22
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
file-sharer | 40e9a8e | Aug 15 2026, 07:06 PM |
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
1 participant
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.
Summary
Encryptedlabel and message timestamp.success-inktokens and preserve the existing accent-muted semantic token.Why
The production landing baseline exposed two contrast failures in the inert visual preview: the success label and the timestamp rendered with opacity over the accent bubble. The new semantic colors calculate to 4.66:1 light / 8.65:1 dark for the success label and 4.74:1 light / 5.03:1 dark for the timestamp.
Lighthouse evidence
Production baseline scores are ordered
Performance / Accessibility / Best Practices / SEO:/: desktop94 / 95 / 100 / 100; mobile90 / 95 / 100 / 100./security/: desktop100 / 100 / 100 / 100; mobile had one72 / 100 / 100 / 100outlier, followed by two100 / 100 / 100 / 100runs./app: desktop100 / 100 / 100 / 58; mobile94 / 100 / 100 / 58.On the current local build, the public routes reached Accessibility, Best Practices, and SEO 100 on both viewports. The landing page measured Performance 94 desktop / 79 mobile with CLS 0.132 / 0.094. Performance and CLS did not reach 100; synthetic runs showed substantial variability, so no score was falsified and no UX trade-off was introduced to optimize a nondeterministic result. A font-display hypothesis was tested and removed because it did not improve CLS.
The
/appSEO score of 58 is intentional: the authenticated shell is markednoindex/nofollowand must not be indexed as a public page.Validation
pnpm lint— passed (127 files)pnpm typecheck— passedpnpm test— passed (web 138 tests, worker 292 tests)pnpm build— passedgit diff --check— passedVisual evidence
Before:
After: