nextcloud / nextcloud/collectives

Replace h2 in empty content with h1

Open
#513 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop accessibility bug ui/ux
Dominant language
JavaScript
Stars
195
Forks
51
Avg merge
1d 2h
Merged PRs (30d)
48

Description

On the initial landing page there is no heading of level one (h1). The landing page heading is h2 at the moment.

For good accessibility with screen readers it's recommended to not skip heading levels and therefore start with an h1:

it is important to not skip one or more heading levels. Doing so may create confusion, as the person navigating this way may be left wondering where the missing heading is.

Screenshot ("Collectives" is the h2):
Bildschirmfoto vom 2023-01-22 21-55-35

Originally posted by @mspae in https://github.com/nextcloud/collectives/issues/159#issuecomment-1381781103

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

No file or test is named. Start at the initial landing page and inspect the heading currently labelled “Collectives”; update the heading hierarchy so the page begins with an h1, then verify the rendered markup and screen-reader heading order.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.