nextcloud / nextcloud/contacts

Make sure, that all headings in html structure taking place and have a right order

Open
#2,778 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: contacts
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 accessibility issue.

Please make sure, that all appearance of heading in html taking place and have a right order.
Example (other app):

image

there are issues with the headings on several pages:

  • Headings aren’t structured correctly to match the information structure
  • In some places, headings skip levels
  • Some headings aren’t marked up as such in the code
  • Some content that aren’t headings are coded using heading-elements

Please check all modal windows and sidebars

Expected behavior

Sometimes heading is wrong. Please check / correct

Actual behavior

Heading is there and have a correct order

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

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 auditing the heading structure across the Contacts app's pages, modal windows, and sidebars, using the reported accessibility concerns as the checklist. Compare heading levels and markup with the information structure, including cases where headings are skipped, missing, or used for non-heading content. Done means the affected views have a logical, complete heading hierarchy.

Written by the indexing model from the issue text.

Assessment

Tech stack
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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.