nextcloud / nextcloud/contacts
Semantic HTML errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Describe the bug
No response
Steps to reproduce
This is an accessibility issue.
There are some validation errors regarding code semantics that doesn’t follow the standard.
Make sure, that
- Elements have complete start and end tags.
- Elements are nested according to their specifications.
- Elements do not contain duplicate attributes.
- Any IDs are unique.
- li-elements are inside of ul/ol-elements.
Expected behavior
Semantic is right.
Actual behavior
Sometimes semantic is wrong.
Contact version
4.1.1
Operating system
No response
PHP engine version
No response
Web server
No response
Database
No response
Operating system
No response
List of activated Apps
Contacts
Nextcloud Signing status
No response
Configuration report
No response
Additional info
No response
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 does not identify a page, component, or file. Start by reproducing the Contacts interface and running an HTML validator against its rendered markup, then trace any reported elements to the relevant frontend source. Done means the reported semantic and accessibility validation errors are resolved, including valid nesting, tags, attributes, IDs, and list structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100