v2.1.2 — Scanner-reported accessibility fixes

Clears the two critical issues a third-party scanner still reported on the live page running 2.1.1. Both are real, and one was introduced by 2.1.1.

Focus order semantics (10 elements). The scrollable category lists got tabindex=0 and role="group" in 2.1.1. group reads correctly, but a focusable scroll container is only permitted to be application, main or region — so all ten lists traded one failure for another. They are now role="region", which keeps the accessible name and satisfies both rules.

Colour contrast (7 elements). These were nodes axe reports as indeterminate rather than failing, because the content is a single digit or a lone glyph. Measured by hand, two genuinely failed: the event count badge painted a hardcoded white number on the raw category colour, giving 4.32:1 on the mid greens and 3.54:1 on the greys against a required 4.5:1.

The badge number now uses a new --wpcc-cat-fg, computed at render time against the colour the badge actually paints. White is kept wherever it already passed, so most badges look unchanged; where it did not, the category colour is darkened toward black rather than dropping to a flat black. Worst case across all 17 live categories is now 4.53:1.

Count badges also read as "5 events" instead of a bare "5" to screen readers.

Verified at zero violations with focus-order-semantics enabled, across light, dark, desktop and mobile, using the live site's real event feed.

Download wpcalendarcats.zip below, or update in place from Plugins if you are already on 2.1.0 or later.