a11y: `quarto create project blog` scaffold has images with no alt text and icon-only navbar links with no name
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
- 72/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- markdown, typescript, yaml
- Área
- accessibility, tooling
Línea de trabajo
Start with the blog scaffold content in src/project/types/website/website.ts and the template src/resources/projects/website/templates/blog/_quarto-blog.ejs.yml. The scaffold files to edit are about.qmd, posts/post-with-code/index.qmd, posts/welcome/index.qmd and the navbar in _quarto.yml, where the GitHub and Bluesky icon links need aria-label. Done when quarto create project blog, render and quarto call axe report no image-alt or link-name findings.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The blog scaffold from quarto create project blog fails WCAG 2.x Level A
right after it is created. It has three images with no alternative text and
two icon-only navbar links with no accessible name. The templates already
support all the fixes. The scaffold content does not use them.
New authors copy the scaffold as their model, so it should show the
accessible pattern.
Reproduce (Quarto 1.11.5)
quarto create project blog blog
quarto render blog
quarto call axe blog/_site
axe-core 4.10.3, 4 pages, 1440x900 and 320x568:
| Rule (WCAG) | Element | Source in scaffold |
|---|---|---|
image-alt (1.1.1) |
<img class="about-image"> on about.html |
about.qmd: image: profile.jpg, no image-alt |
image-alt (1.1.1) |
listing thumbnail, Post With Code | posts/post-with-code/index.qmd: image: "image.jpg", no image-alt |
image-alt (1.1.1) |
<img> in Welcome post body, and its listing card |
posts/welcome/index.qmd:  |
link-name (2.4.4, 4.1.2) |
both listing thumbnail links (an image link with no alt has no name) | follows from the two rows above |
link-name (2.4.4, 4.1.2), role-img-alt (1.1.1) |
navbar GitHub and Bluesky links, every page | _quarto.yml: - icon: github / - icon: bluesky with no text or aria-label |
Proposed scaffold changes
All in src/project/types/website/website.ts (blog scaffold content) and
src/resources/projects/website/templates/blog/_quarto-blog.ejs.yml.
_quarto.yml:
navbar:
right:
- about.qmd
- icon: github
href: https://github.com/
aria-label: GitHub
- icon: bluesky
href: https://bsky.app/
aria-label: Bluesky
about.qmd:
image: profile.jpg
image-alt: "A stick figure drawn in light against a dusk sky"
posts/post-with-code/index.qmd:
image: "image.jpg"
image-alt: "City lights across Earth at night, seen from orbit"
posts/welcome/index.qmd:
{fig-alt="A laptop, a cup of coffee, a notepad and a phone on a wooden desk"}
Result
The same scan with all four changes: every image-alt, link-name and
role-img-alt finding is cleared (10 findings → 0). The findings that
remain have their own issues: listing category contrast (#14381) and the
best-practice landmark and heading-order findings
(#14375/#14377/#14384/#14605).
Other quarto create scaffolds
We checked the 1.11.5 project templates (default, website, book,
manuscript, confluence). Only the blog sets image: or uses icon-only
navbar items. The book scaffold copies cover.png into the project, but
its _quarto.yml does not set cover-image, so nothing renders it. When
an author adds cover-image, they need cover-image-alt too. This is
outside the scope of this issue.
Related
- #14828:
navbar: tools:/sidebar: tools:with onlyicon:get
aria-label="". That path is a different template (navtools.ejs).
The blog'snavbar: right:items go throughnavitem.ejs/navicon.ejs.
There,aria-label:already works, but there is no fallback when it is
not set. The icon-name fallback proposed in #14828 should also cover
this path. This issue only changes the scaffold, so the blog is correct
with or without that fallback. - #7979 (closed 2023-12): added
image-altsupport to about pages. The
scaffold was not updated to use it. - #7028: listing image alt.
- Lenguaje dominante
- JavaScript
- Estrellas
- 6.1k
- Forks
- 476
- Merge medio
- 17 h 7 min
- PR fusionados (30 d)
- 112
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de quarto-dev/quarto-cli
-
enhancement websites
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
quarto-dev/quarto-cli#15255 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Website announcement dismiss control cannot be reached or used with a keyboardPosiblemente ocupada @Xander-AJ la tomó hoy. Abiertoaccessibility bug websites
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
quarto-dev/quarto-cli#15235 ·
Los mantenedores suelen responder en 1 día
-
quarto.json.decode does not raise on invalid JSON, so pcall cannot catch itPosiblemente ocupada @sogav21 la tomó hace 2 días. Abiertobug lua
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
quarto-dev/quarto-cli#15226 ·
Los mantenedores suelen responder en 1 día
-
arrow-dark gives region markers a light band that fails contrastPosiblemente ocupada @vav7 la tomó hace 1 día. Abiertoaccessibility bug themes
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
quarto-dev/quarto-cli#15222 ·
Los mantenedores suelen responder en 1 día
-
bug code-annotation
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
quarto-dev/quarto-cli#15215 ·
Los mantenedores suelen responder en 1 día
Todos los issues de quarto-dev/quarto-cli
Issues similares
-
neutral:fix
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
wazuh/wazuh-documentation#10611 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
remotion-dev/remotion#12905 ·
Los mantenedores suelen responder en 1 día
-
Money fields reject amounts that aren't multiples of $500, so Find cliffs silently does nothingAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
PolicyEngine/cliff-watch#44 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día