Brand Projects: leave select mode with Escape and announce the count once

Open
  • Is something wrong?
#503 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
accessibility, frontend

Research direction

Start in components/projects/project-manager.tsx to find select mode and its bar, then check lib/projects/selection.ts for how the selection and count are held, and components/ui/dialog.tsx for how Escape is already handled. Done means Escape leaves select mode and clears the selection unless a dialog or menu is open, focus returns to the Select button, the live region updates once for a ten-project Shift range, and the end-to-end and axe checks pass.

Written by the indexing model from the issue text.

Description

accessibility area: projects difficulty: easy enhancement good first issue help wanted v2.0.0

Summary

Select mode has a Done button, but Escape does nothing, and the count in the status text updates on every toggle, which a screen reader reads again and again during a long range. Add Escape and settle the announcement.

Part of the 2.0.0 plan: fewer, better and fully tested studios, on a calmer and faster site.

Where to look

  • components/projects/project-manager.tsx (select mode and its bar)
  • lib/projects/selection.ts
  • components/ui/dialog.tsx: how Escape is handled elsewhere

Behaviour

  • Escape leaves select mode and clears the selection, unless a dialog or menu is open.
  • Announce the count after the changes settle, not on every checkbox in a long range.
  • Return focus to the Select button when the mode ends.

Acceptance criteria

  • An end-to-end test presses Escape and checks focus.
  • The live region updates once for a Shift range of ten projects (checked by counting its updates).
  • The axe scan passes in select mode.

Getting started: fork the repo, then pnpm install and pnpm dev (Node 22+, pnpm 11, no API keys). Before opening a PR, run pnpm typecheck && pnpm test && pnpm lint && pnpm format:check && pnpm check:dashes && pnpm build (CI fails on unformatted files, so pnpm format first). See CONTRIBUTING.md and the first contribution walkthrough.

Everything needed is in the repository. This doesn't need maintainer access, secrets or paid services. Comment below to claim it, and ask questions here any time.

Dominant language
TypeScript
Stars
11
Forks
3
Avg merge
5h 22m
Merged PRs (30d)
74

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/DesignHub

All issues in yakew7/DesignHub

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.