Repository navigation
Updates to improve lighthouse accessibility score - #20275
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
coolguyzone
marked this pull request as draft
October 27, 2026 21:14
Contributor
|
Checks were inconclusive · Rollout details
The check did not reach a verdict. Mention |
coolguyzone
marked this pull request as ready for review
October 28, 2026 22:47
sergical
approved these changes
Oct 28, 2026
This branch was successfully deployed
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.
DESCRIBE YOUR PR
Fixes every weighted accessibility failure flagged by a Chrome mobile Lighthouse run against docs.sentry.io. Verified with Lighthouse 13 against a local dev server: mobile accessibility 81 → 100, desktop also 100, with no weighted failures left in either.
To verify: run mobile lighthouse scan on https://sentry-docs-git-coolguyzone-fixlighthouse-a11y.sentry.dev/
Noticeable UI changes:
Homepage inline links are now underlined — the most noticeable change.
The "or" divider pill is a deeper purple — #8d84d0 → #6a5fc1. Subtle but visible side by side.
The header "or" separator is darker and warmer — light purple-gray #bbadc6 → --gray-11. Desktop only (hidden md:inline).
Details:
src/components/platformFilter/) — the RadixCollapsible.Triggerwas renderingaria-expandedonto a plain<div>, and each card wrapped its chevron in an empty<button>with no accessible name (14 of each on the homepage). The trigger is now a real<button type="button">whose accessible name is the platform title, and the chevron is a<span>. Clearsaria-allowed-attrandbutton-name. This fixes genuinely broken keyboard and screen-reader behavior on the platform list, not just the score.aria-label="Toggle theme". The Radix tooltip suppliesaria-describedby, not an accessible name.color-mix(…, transparent 25%)rendered#8d84d0on#f6f5fb, a contrast ratio of 3.05:1. Nowvar(--accent-purple)at 4.82:1..seeAllLink) — these sit inline in body copy withtext-decoration: noneand only 1.16:1 contrast against the surrounding text, so color alone distinguished them. Now always underlined.var(--desatPurple10)on white is 2.08:1. Nowvar(--gray-11). This element ishidden md:inline, so it affects desktop only.Worth flagging for reviewers: the
desatPurple0–15scale inapp/globals.cssis not overridden in.dark, so no fixed step on it clears 4.5:1 in both themes (step 6 is 5.24 light / 3.39 dark; step 8 is 3.48 light / 5.12 dark). That's why the search separator moved to the theme-aware Radix--gray-11rather than a darker purple.Two things reviewers should eyeball in the preview, since Lighthouse only audits light mode: the two color changes are deliberate visual deltas (the search separator goes from muted purple to warm gray), and dark mode is unverified.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
EXTRA RESOURCES
🤖 Generated with Claude Code