heading structure in deck
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
The headings don’t skip levels here, but they don’t match the logical structure of the content. To take an example the heading “Kommande kort” isn’t related to the different lists on the overview page, “Today”, “Tomorrow” and such. In the middle of this list, there is also a hidden heading saying “Denna tavla är skrivskyddad” (“This board is read only”) which doesn’t make any sense as a heading.
In “Egna tavlor” the heading structure is even more illogical. “Börja skriva för att söka” is a heading by the search function, which isn’t needed and can be confusing for users, there’s a visually hidden heading “Släpp dina filer för att ladda upp” that is above all the cards in the structure. These texts are instructions, they should not be coded as headings.

When the flyout is open there is a problem with skipped heading levels, as it goes directly from a heading level 3 to one at level 5.
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
No files or tests are named. Start by locating the overview page and the “Egna tavlor” view, then inspect their heading structure with the flyout open; done means headings reflect the content hierarchy, instructional text is not coded as headings, and no levels are skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100