fix: restore admin bar contrast in Light scheme - #274
Conversation
▶ Preview in WordPress PlaygroundBoots a fresh WordPress with this PR's presence-api build, seeds 5 demo users, and drops you on the dashboard. Stress-test variant: 40 demo users · Built from |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @akira-in-tech. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
josephfusco
left a comment
There was a problem hiding this comment.
Hey @akira-in-tech, thank you for working on this. Confirmed this resolves the contrast issue.
One thing: please link a WordPress.org account so you get proper credit when this ships.
|
Thanks for confirming the fix and for the attribution reminder. I’ll take care of linking my WordPress.org account so the contribution is credited correctly. |


Summary
#50575e, which provides a 7.33:1 contrast ratio against the Light scheme's white submenuRoot cause
The presence admin bar styles used
#a7aaadfor secondary text regardless of the selected WordPress admin color scheme. That color works against the default dark submenu, but the Light scheme uses a white submenu and also gives the top-level count a low-contrast inherited color.The override is scoped to
.admin-color-light, so the existing appearance of the other admin color schemes is unchanged.Fixes #266
Validation
./vendor/bin/phpcs --standard=phpcs.xml.dist./vendor/bin/phpstan analyse --configuration=phpstan.neon.dist --memory-limit=2Gnpm run test:scripts— 54 passednpm test— 186 tests, 415 assertions, 5 skippednpm run test:e2e— 16 passedThe local wp-env run used
WP_ENV_CORE=WordPress/WordPress#7.0.3because the current latest-version resolver requested the not-yet-available7.0.4Git ref. The four wp-env-backed jobs fail before test execution for the same reason on the latestmainrun.Use of AI Tools
AI assistance: Yes
Tool(s): OpenAI Codex
Model(s): GPT-5
Used for: Implementation and regression-test drafting; the final diff and validation results were reviewed by the contributor.