:root { --me-pink: #BE5B8F; --me-pink-accessible: #8E2F63; --me-grey: #706F6F; --me-grey-light: #9D9D9C; --me-pink-tint: #f7ecf3; /* --- text colour ------------------------------------------------------ Client decision, 2026-07-31: headings and body text this plugin renders are black, and where that text is interactive it lightens to grey on hover. Every `color:` declaration that used to name a pink now names one of these two, so the decision lives in one place rather than in ninety. --me-ink #000000 on white is 21:1. --me-ink-hover #6C6C6C is 5.25:1 on white and 4.56:1 on --me-pink-tint. --me-ink-hover is NOT --me-grey (#706F6F), which is what this started as and what every other body-text grey in the plugin still is. #706F6F is 5.01:1 on white but only **4.35:1 on --me-pink-tint** — under AA — and the tint is exactly where several of these hovers land: the account tabs, the pagination links, the "auction not started" button, the gallery's Clear control all swap to a tint background on hover at the same moment the text goes grey. Measured, not estimated: the first draft of this used --me-grey and the contrast check on staging caught it. #6C6C6C is the lightest grey that clears 4.5:1 on the tint, on white, and on the green "Winning!" badge. Holding its own value also keeps the two apart on purpose: retuning the plugin's body-text grey should not silently flatten the hover state of every link on the site into no-change-at-all. That is a live risk here — the lot titles and the "auction not started" buttons already RESTED at --me-grey, so they had to move to --me-ink for their hover to be visible at all. Pink is NOT retired. It is still the plugin's structural colour: card borders, the tint behind a table head or a hovered tab, the filled current-page pill, the keyboard focus ring. Only text changed. */ --me-ink: #000000; --me-ink-hover: #6C6C6C; /* --- the auction blue ------------------------------------------------ The live auction's own colour. It lived in auction-bid.css, scoped to `.me-auction-panel, .noty_bar`, for as long as the bid panel was the only thing that used it. The lot cards now need it too — a running lot's "Bid now" button is the same action as the panel's Bid button and has to be the same colour — and a card is nowhere near a `.me-auction-panel`, so it belongs here where both stylesheets can reach it. THE TEAL IS GONE (client decision, 2026-07-31: "remove the teal colour from everywhere on the auction, we can replace it with the blue"). It was #4EAAB9, and it was never able to carry text anyway — 2.7:1 on white, short even of the 3:1 a UI component needs — so every teal-on-white rule was already falling back to this blue. Now the surfaces match the text. --me-auction-blue #38519b 7.7:1 with white. Text, buttons, borders. --me-auction-blue-dark #2b3f78 11:1 with white. Hovers and the darker of two blues in one notice. --me-auction-blue-tint #eaeef7 a surface, never text. */ --me-auction-blue: #38519b; --me-auction-blue-dark: #2b3f78; --me-auction-blue-tint: #eaeef7; /* "This went your way" — the "Winning!" badge on a lot card, and the notice that says a bid landed. #1E6B3A on #E7F4EC is 5.8:1. It exists because retiring the teal collapsed two meanings into one: the bid-landed notice was teal and the general info notice was blue, and with the teal gone they became the same notice. Green is the honest answer rather than a second blue — this site already uses exactly this green for exactly this meaning on the lot cards, so it is one definition serving both rather than a new colour. */ --me-auction-success: #1E6B3A; --me-auction-success-tint: #E7F4EC; /* The surface a control lightens to when you point at it. Client decision, 2026-07-31, the other half of "the pink on hover should change to a grey": the tab, button, Clear control and page link that used to wash pink under the pointer wash grey instead. --me-pink-tint keeps every RESTING use it had (the table head, the clinic badge, a search highlight, the artist initials placeholder) — only hover moved. */ --me-grey-tint: #F2F2F2; } /* --- the filter hide utility ------------------------------------------- MeShared.setFilteredVisibility() marks a filtered-out item with these classes (and the `hidden` attribute). This is the rule that makes that mean anything, and it lives HERE — in the one stylesheet every other stylesheet in this plugin declares as a dependency — rather than in me-shared.css where it started. WHY IT MOVED. On the 97-lot gallery it was simply absent. `auction-listing.css` depends on this token file; me-shared.css was declared as a dependency of the listing SCRIPT, and scripts and styles are separate registries, so the stylesheet holding this rule never loaded on that page. The filter ran correctly, set the classes correctly, announced "23 lots shown" correctly — and every one of the 97 lots stayed on screen, because `li.product` carries an author-origin `display: flex` from this plugin that outranks the user agent's `[hidden] { display: none }`. A search that reports a count while showing everything is worse than no search. Putting it on the token handle makes that class of failure impossible: a block cannot use this plugin's CSS without loading this file, so it cannot use MeShared's filter without loading this rule. me-shared.css depends on this file too, so nothing that had the rule before has lost it. `!important` is deliberate and was already so: this utility has to beat the scoped card and grid rules that give those items their display in the first place (`.x-col .me-faqs .me-faq-card`, 0,3,0; `.woocommerce ul.products li.product.product-type-auction`, 0,4,2). Nothing weaker wins against both. */ .me-resource-hidden, .me-faq-hidden, .x-col .me-resource-hidden, .x-col .me-faq-hidden { display: none !important; }