Files
Andrew Aquino f9867168ad fix(site/src/modules/notifications): make inbox mark as read buttons distinguishable (#32466)
Each unread inbox notification's "Mark as read" button now gets
`aria-describedby` pointing at the notification content, the same way
the action links do since #32317. Screen reader users can now tell which
notification each button marks. The label also changes to sentence case
to match "Mark all as read".

The sr-only "Unread" text used to sit inside the dot, which is `display:
none` on hover and focus-within. Screen readers lost the unread state
while a user was in the item. The text is now a sibling of the dot. The
button was already keyboard reachable on main (#31656), so this was the
part of DEQ-610 still open.

Closes DEQ-610
Closes DEQ-633

| Ticket | UI surface |
| --- | --- |
| [DEQ-610](https://linear.app/codercom/issue/DEQ-610) | Navbar bell >
Inbox popover, unread item "Unread" indicator (screen reader only, no
visual change) |
| [DEQ-633](https://linear.app/codercom/issue/DEQ-633) | Navbar bell >
Inbox popover, unread item "Mark as read" button
([screenshots](https://linear.app/codercom/issue/DEQ-633#comment-dcc113c9))
|

<details>
<summary>Grouping and decision log</summary>

- Both tickets cover the same element in `InboxItem.tsx`, so they ship
in one PR.
- DEQ-610's keyboard reachability
(`not-group-hover:not-group-focus-within:sr-only`) is already on main
from #31656. Verified in Storybook (`InboxItem` / `UnreadFocused`): on
main, `Unread` has no layout box while the item has focus; on this
branch it stays in the accessibility tree.
- DEQ-633 reuses `aria-describedby={contentId}` from #32317 and keeps
"Mark as read" as the name. Every button has the same name, and the
description tells them apart.
- Self-review (frontend-review, frontend-deep-review,
frontend-accessibility): the only should-fix was a test whose keyboard
assertions can't fail in jsdom. I cut it down to the
accessible-description assertion. No findings were dropped.

</details>

🤖 Generated by Coder Agents on behalf of @aqandrew.
2026-11-19 13:54:24 -08:00
..
…
…
…