Search Results page has improper heading hierarchy

Abierto
  • ¿Algo no está bien?
#5,500 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
angular, typescript
Área
accessibility, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
180
Forks
577
Merge medio
2 d 1 h
PR fusionados (30 d)
100

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DSpace/dspace-angular

Todos los issues de DSpace/dspace-angular

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.