nextcloud / nextcloud/calendar

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

Open
#4,267 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

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 behaviour

Heading is there and have a correct order

Calendar app version

3.3.2

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

No response

Database engine version

No response

PHP engine version

No response

Nextcloud version

No response

Updated from an older installed version or fresh install

No response

List of activated apps

No response

Nextcloud configuration

No response

Web server error log

No response

Log file

No response

Browser log

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 reviewing the calendar app's modal windows and sidebars, checking heading markup and hierarchy across the affected pages. Done means headings reflect the information structure, levels do not skip, headings use heading elements, and non-heading content does not use them.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.