a11y: `quarto create project blog` scaffold has images with no alt text and icon-only navbar links with no name
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
- 72/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- markdown, typescript, yaml
- Ambito
- accessibility, tooling
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- JavaScript
- Stelle
- 6.1k
- Fork
- 478
- Merge medio
- 17h 26m
- PR unite (30g)
- 126
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di quarto-dev/quarto-cli
-
enhancement localization
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
quarto-dev/quarto-cli#15268 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
html maintenance
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
quarto-dev/quarto-cli#15261 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement websites
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
quarto-dev/quarto-cli#15255 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
quarto.json.decode does not raise on invalid JSON, so pcall cannot catch itForse già presa @sogav21 l’ha presa 3 giorni fa. Apertabug lua
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
quarto-dev/quarto-cli#15226 ·
I maintainer di solito rispondono entro 1 giorno
-
arrow-dark gives region markers a light band that fails contrastForse già presa @vav7 l’ha presa 2 giorni fa. Apertaaccessibility bug themes
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
quarto-dev/quarto-cli#15222 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di quarto-dev/quarto-cli
Issue simili
-
Upgrade listener stays on a custom server after close when `preClose` is setForse già presa @RaphaelFakhri l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
fastify/fastify-websocket#388 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
DietrichGebert/ponytail#1343 ·
I maintainer di solito rispondono entro 1 giorno
-
cleanup
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
swombat/souls-house#770 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno