Repository navigation
fix: improve landing metadata contrast - #147
Merged
Merged
Conversation
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.
Small metadata on the public landing rendered at approximately 3.0:1 contrast on solid backgrounds. Raise its existing white opacity to 55% while preserving type sizes, layout, illustrations, navigation, and signed-in behavior.
Validation: the two existing Home tests pass; Biome and the production build pass. Compiled browser checks at 390, 768, and 1440px measure at least 6.2:1 for the sampled solid-background metadata, preserve keyboard CTA focus under reduced motion, and show no horizontal overflow. All three screenshots were visually reviewed. Gradient-backed labels were reviewed visually rather than given a numeric contrast certification.
The existing dependency gate blocked release. Update Vite 8.1.5→8.1.6 for GHSA-587h-7wmj-h5pm. Remove the unused Vercel build-tool package, retaining the two legacy handlers through type-only Node HTTP/request/response annotations. Declare the already resolved Node typings directly as a development dependency. The removed ts-morph chain carried unpatched braces (GHSA-vfj7-8cjw-p6xm). The second braces path comes from Excalidraw's Sass1.51; target only that parent with Sass1.79.6, which uses chokidar4. The app imports Excalidraw's distributed CSS, not Sass sources, and its distributed CSS hash is unchanged. No new production dependency, API behavior change, audit exception, or threshold change. Fresh audit reports zero critical/high; existing moderate/low findings remain.