Buttons should not be hidden in certain states; need another pattern to offer better accessibility
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 106
- Forks
- 52
- Avg merge
- 13h 35m
- Merged PRs (30d)
- 10
Description
The pattern of hiding/showing buttons according to state is problematic in terms of accessibility. It might also not offer the best UX for users. I think toggling availability by changing color and using other cues are a better approach (and mark it semantically, using the disabled-attribute).
Some examples of this pattern:
- When offering controls for a resource: Is hidden until you hover with a mouse
- Save-button for sourcePane: I hidden until there are changes to be saved
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the resource controls and the sourcePane Save button, then inspect how their visibility changes with hover or unsaved changes. Done means the controls remain discoverable in each state, communicate availability accessibly, and use the disabled attribute when unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100