Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Settings flag chips and channel chips cannot be used from the keyboard

Open Beginner friendly
#154 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #203 by @yff124 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, react

Research direction

In website/src/SettingsView.jsx, search for saveSetting(k, val(k) and toggle(ch) to find both chip implementations. Read the nearby state and styling, then check website/test/clickableContent.test.mjs for the test pattern. Done when both chips are keyboard reachable buttons with aria-pressed, retain their appearance, toggle with Space or Enter, and a test asserts they are buttons.

Written by the indexing model from the issue text.

Description

accessibility good first issue

On the Settings page, the flag chips (<Box key={k} title={m.flags[k].help} onClick={() => saveSetting(k, …)}>) and the channel chips (<Box key={ch} onClick={() => toggle(ch)}>) are plain clickable boxes. They change real settings, but Tab never reaches them and they do not say whether they are on or off.

Where: website/src/SettingsView.jsx. Search for saveSetting(k, val(k) and toggle(ch).

Done when each chip is a ButtonBase (or <button type="button">) with aria-pressed reflecting its state, looks the same, and Tab plus Space/Enter toggles it.

Test: add a case to website/test/clickableContent.test.mjs (or a new *.test.mjs beside it) asserting the element is now a button.


Getting started: pip install -e ".[dev]", then python -m pytest -q (offline). UI work: cd website && npm ci && npm test (Node 22). See CONTRIBUTING.md. One small PR with the change (and its test, where there is one) is perfect.

Dominant language
Python
Stars
116
Forks
22
Avg merge
13h 21m
Merged PRs (30d)
53

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 ldbumble/taskuary

All issues in ldbumble/taskuary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.