Use HTML details where appropiate
Open
Nobody has claimed this yet.
1. to develop
design
enhancement
feature: accessibility
good first issue
help wanted
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
I came across https://dev.to/isfotis/html-details-is-awesome-1c20 today.
It would probably make sense we use this where possible (comments I guess?, maybe other places).
The awesome thing is accessibility comes for free on this.
CC: @nextcloud/designers @nextcloud/accessibility
Contributor 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.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the linked HTML details article and the existing comment and other expandable UI locations, then determine which areas are suitable and how accessibility behavior should be verified. Done means the agreed applicable interfaces use HTML details consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100