A task's box should be named with a date written in its line

Open Beginner friendly
#268 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

In features/tasks/index.js, inspect how NAMED determines which line tokens contribute words to a task box's name. Add the date token there and cover the example in features/tasks/tasks.test.js. Done means the box is named “Call on November 10, 2026”; run that test file to verify it.

Written by the indexing model from the issue text.

Description

accessibility bug good first issue

A task's box is named by its line's words, so a screen reader hears what it's for. A date written in the line is left out of that name.

- [ ] Call on date:2026-11-10[]

To repeat: open this, and Tab to the box, or look at its name in the browser's accessibility tree.

What happens: the box is named "Call on".

What should happen: "Call on November 10, 2026", as the date is said on the page.

Suggested fix: features/tasks/index.js names a box from its line's tokens, and keeps a list of the token types other features draw that have words of their own (NAMED). The date's token isn't in it. Adding the date's token there, with a test in features/tasks/tasks.test.js, fixes this case.

Underneath, each new feature with words has to join that list, which is a list in tasks of other features' tokens (#141's rule). A way for a feature to say what its token is called, so tasks needn't name it, would end that; that larger change isn't needed to fix this one.

Found in the 0.0.4 release review (#80).

Dominant language
JavaScript
Stars
0
Forks
1
Avg merge
2d 4h
Merged PRs (30d)
26

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 jzheaux/reader

All issues in jzheaux/reader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.