aehrc / aehrc/smart-forms

Request all elements to have appropriate accessible names and roles assigned (accessibility)

Open
#1,735 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility awaiting ADHA
Dominant language
TypeScript
Stars
61
Forks
29
Avg merge
2d 22h
Merged PRs (30d)
19

Description

Is your feature request related to a problem? Please describe.
Raised by accessibility experts

All elements have appropriate accessible names and roles assigned.
Some interactive elements do not consistently expose their name, role, or value, making them difficult to identify and operate for users relying on assistive technologies.
For example:

  • The menu of assessment forms visually resembles clickable cards but is not announced as links or buttons by screen readers.
  • The “Clear” button (an “X” icon) in text input fields is inconsistently operable and announced. In the “Height” field, it is announced only as “button,” without a descriptive name.

Describe the solution you'd like
Recommendation by accessibility experts:

  • Ensure use of semantic HTLM and expose roles programmatically. Be sure to provide descriptive accessible names.
  • Ensure consistency across elements ensuring that text input fields have a "clear" button where appropriate and is keyboard accessible. Be sure to use aria-label to ensure that elements are announced correctly.

Describe alternatives you've considered
None

Additional context
None

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the assessment-form menu and the text input clear buttons, especially the “Height” field described in the issue. Audit their semantic elements, accessible names, roles, values, and keyboard behavior; the work is done when these controls are consistently identified and operable with assistive technologies.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.