A task's box should be named with a date written in its line
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
- Domain
- accessibility, frontend
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
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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 3/5 1-2 days Newbie friendliness 60/100
Maintainers usually reply within 1 day
Similar issues
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
accessibility good first issue languages
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 2 days
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100