Search Results page has improper heading hierarchy

Aperta
#5,500 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
50/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
angular, typescript

Direzione di ricerca

The payload does not name source files, so begin with the Search Results page and the components that render its filter sidebar, Advanced Search, and Settings sections, looking for where h3 and h4 are used before the page's h1. Reproduce by loading the search page and running a headings extension to list the outline. Done when the outline nests from one h1 Search Results, with the filter and settings sections as h2 and their subsections one level below, and the existing search tests still pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

accessibility bug component: Discovery needs discussion

Describe the bug

The Search Results page uses headings in an incorrect order. In the current structure, level 3 and level 4 headings appear before the main page heading, and the hierarchy is not logically nested.

From the screenshot, examples include:

H3: Filters
H3: Advanced Search
H4: Filter by
H3: Settings
H4: Sort By
H4: Results per page
H1: Search Results

This makes the heading structure confusing for screen reader users and keyboard users who rely on headings to understand the page layout and navigate efficiently.

Image

To Reproduce

Steps to reproduce the behavior:

  1. Go to the search page
  2. Use e.g. headings extension.

Expected behavior

The page should have a clear, hierarchical heading structure, for example:

H1: Search Results
H2: Filters
H3: Advanced Search
H3: Filter by
H2: Settings
H3: Sort By
H3: Results per page

The exact structure may vary, but heading levels should reflect the visual and semantic organization of the page.

Related

Past ticket to do similar header hierarchy resolution: https://github.com/DSpace/dspace-angular/issues/3071

Lingua principale
TypeScript
Stelle
180
Fork
577
Merge medio
2g 1h
PR unite (30g)
100

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DSpace/dspace-angular

Tutte le issue di DSpace/dspace-angular

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.