Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Get Started page has four h1 headings (WCAG 1.3.1)

Abierto Apto para principiantes
#2,133 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
84/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
html, markdown

Línea de trabajo

Empieza inspeccionando los encabezados Markdown en _get_started/installation/mac.md, _get_started/installation/linux.md y _get_started/installation/windows.md; después, reproduce el problema con la consulta proporcionada para la consola del navegador en la página Get Started. Se considera terminado cuando la página renderizada tiene un h1, los tres encabezados de instalación aparecen como elementos h2 y la apariencia visual de la página no ha cambiado.

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

Descripción

🕋 Website

The Get Started page renders four <h1> elements, so the document has four competing top-level headings instead of one.

https://pytorch.org/get-started/locally/

h1  Get Started
h1  Installing on macOS
h1  Installing on Linux
h1  Installing on Windows

The three install headings come from this repo, and each opens with a markdown #:

  • _get_started/installation/mac.md
  • _get_started/installation/linux.md
  • _get_started/installation/windows.md

Those files are included into a page that already carries its own h1, so the # becomes a second, third and fourth top-level heading rather than a section heading under it.

Why it matters

Headings are how screen reader users navigate a long page. Most screen readers offer "jump to next heading" and a heading list, and both rely on the levels describing a real outline. Four h1s say the page has four separate documents in it, so the outline stops being useful for exactly the page a new user is most likely to be reading carefully while installing something.

This is WCAG 2.2 1.3.1 Info and Relationships, Level A.

To Reproduce

  1. Go to https://pytorch.org/get-started/locally/
  2. Run in the console:
[...document.querySelectorAll('h1')].map(h => h.textContent.trim())
  1. Four headings are returned rather than one.

Expected behavior

One h1 per page. The three install headings become ##, which puts them under "Get Started" where they belong and leaves the rendered page looking the same.

Two things I could not determine from outside

Both are about the page chrome rather than the content, and I suspect they are not owned by this repo, so I am asking rather than reporting:

  1. There are two role="contentinfo" landmarks on every page I checked, one on div.nectar-global-section.before-footer and one on #footer-outer. There should only be one, otherwise landmark navigation offers two "footers".
  2. The homepage h1 is "JOIN US", which is a conference banner rather than a description of the page.

Both look like they come from the WordPress theme wrapping the Jekyll content, not from this repository. If that is right, I would be glad to know where they should be raised instead.

Happy to open a pull request for the # to ## change if that is useful.

Lenguaje dominante
HTML
Estrellas
286
Forks
318
Merge medio
5 d 18 h
PR fusionados (30 d)
4

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 pytorch/pytorch.github.io

Todos los issues de pytorch/pytorch.github.io

Issues similares

Más issues de Accessibility

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.