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

[Accessibility & Polish] Term picker accessible name

Open Beginner friendly
  • Is something wrong?
#779 0 comments 0 reactions 1 assignee View on GitHub

@wilkinsonjacob is already working on this.

Since Oct 13, 2026.

  • #880 by @wilkinsonjacob — open

Assessment

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

Research direction

Read src/components/TermSelector.tsx, focusing on Select.Trigger and CaretUpDownIcon, then follow the setup in docs/getting-started/setup.md. Add the accessible name "Term" and hide the decorative caret from assistive technology; verify keyboard selection using the listed keys and run pnpm lint and pnpm typecheck. Done when the trigger has the right name, the current term remains visible, and the checks pass.

Written by the indexing model from the issue text.

Description

good first issue polish

What to build

Give the semester selector a name that a screen reader can announce. Students should hear what this control selects and be able to change semesters with the keyboard.

Files

Steps

  1. Add aria-label="Term" to Select.Trigger and aria-hidden to its caret icon.
  2. Preserve value/onValueChange and displayed term text.
  3. Check keyboard selection and the trigger name in accessibility tools.

Example

Choosing Spring 2027 with the keyboard updates the existing provider exactly as before.

Check it works

Record the observed result or a screenshot in the pull request.

References

Assign yourself before starting, or comment to claim the issue. Project setup.

Dominant language
TypeScript
Stars
19
Forks
94
No merged PRs in 30d

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 DevDogsUGA/DogDays

All issues in DevDogsUGA/DogDays

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.