[Existing app][Changelog Panel] Close keyboard and screen-reader gaps

[kryputh]

Summary

Improve the existing Changelog Panel surface. This issue is intentionally scoped to existing app code and should not introduce a new standalone tool or unrelated feature.

Current area

changelog entries, panel visibility, read state, release grouping, and user-facing change summaries

Relevant paths

• src/features/changelog/ChangelogPanel.tsx
• src/features/changelog/useChangelog.ts
• src/features/changelog/data.ts

Goal

make the existing changelog panel useful for release comprehension and contributor handoff.

Work focus

Audit the existing surface for keyboard flow, focus order, visible focus, ARIA naming, reduced-motion behavior, and screen-reader clarity. Fix gaps in place without changing the core workflow.

Acceptance criteria

• All interactive controls are reachable and operable from the keyboard.
• Focus order matches the visual reading order and does not trap users unexpectedly.
• Icon-only controls have accessible names and stateful controls expose current state.
• Reduced-motion or non-animated fallback behavior is respected where motion exists.

Scope guardrails

• Keep the work inside the relevant existing app/module paths above unless a small shared helper is clearly justified.
• Do not add a new V1/V2 tool folder for this issue.
• Do not use real user data, secrets, private keys, or live customer mail.
• Keep copy and UI aligned with the Stealth Mail safety, speed, and sender-control positioning.

Suggested validation

• Run the most relevant unit or e2e tests for the touched area.
• Run �un x tsc --noEmit and �un run lint when the local environment supports the project dependency install.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.

[MoscowDev]

I'd like to take this issue.

I'll audit the Changelog Panel specifically for accessibility gaps across keyboard interaction, focus order, ARIA semantics, and reduced-motion handling without changing the existing feature behavior.

My approach will include:

• Verifying full keyboard operability for all interactive elements (navigation, toggles, expansion controls).
• Ensuring focus order follows the visual reading order without unexpected jumps or traps.
• Adding accessible names for icon-only or ambiguous controls using appropriate ARIA attributes.
• Confirming that stateful controls expose their current state to assistive technologies.
• Reviewing reduced-motion preferences to ensure animations or transitions degrade gracefully.
• Running targeted checks with unit/e2e coverage where applicable to ensure accessibility behavior is preserved.

The goal is to improve accessibility compliance and usability for keyboard and screen-reader users while keeping the existing changelog workflow unchanged.

[MoscowDev]

I'd like to take this issue.

I'll audit the Changelog Panel specifically for accessibility gaps across keyboard interaction, focus order, ARIA semantics, and reduced-motion handling without changing the existing feature behavior.

My approach will include:

• Verifying full keyboard operability for all interactive elements (navigation, toggles, expansion controls).
• Ensuring focus order follows the visual reading order without unexpected jumps or traps.
• Adding accessible names for icon-only or ambiguous controls using appropriate ARIA attributes.
• Confirming that stateful controls expose their current state to assistive technologies.
• Reviewing reduced-motion preferences to ensure animations or transitions degrade gracefully.
• Running targeted checks with unit/e2e coverage where applicable to ensure accessibility behavior is preserved.

The goal is to improve accessibility compliance and usability for keyboard and screen-reader users while keeping the existing changelog workflow unchanged.

[nelly439]

I’ll take this on. I’ll audit ChangelogPanel.tsx, useChangelog.ts, and data.ts for accessibility gaps including keyboard navigation flow, focus management, ARIA labeling, and reduced-motion handling. I’ll apply targeted fixes in-place (no workflow or architecture changes), ensuring all interactive elements are keyboard accessible, focus order matches visual order, and icon-only/stateful controls expose proper accessible names and states. I’ll also verify screen-reader clarity for grouped releases and read/unread states. A short PR note will summarize the accessibility improvements and any UX-critical fixes, with no changes outside the existing changelog module.