Reporting a number of accessibility issues raised by axe-core on quarto blogs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- accessibility, web-dev
Research direction
Start with the quarto-accessibility-reprex example and inspect the axe-core warnings on its rendered site. Compare the generated output with accessibility-fixes.html and the changes enabled at _quarto.yml line 17; done means the reported accessibility warnings are addressed without breaking the blog pages and posts.
Written by the indexing model from the issue text.
Description
I have:
- searched the issue tracker for similar issues
- installed the latest version of Quarto CLI
- formatted my issue following the Bug Reports guide
Bug description
This issue is to report a number of accessibility warnings generate by axe-core on quarto websites, especially postings pages and blog posts. Tagging @cscheid since we had some back and forth about this on bsky.
A small self-contained example is available at: https://github.com/alexpghayes/quarto-accessibility-reprex
The axe-core warnings can be viewed at https://alexpghayes.github.io/quarto-accessibility-reprex/
I came across these warnings/issues while working to make my personal blog (https://github.com/alexpghayes/quarto-blog/) more accessible. Since I had a little understanding of what's happening in the background, I asked Gemini and Claude to resolve the accessibility issues for me. They produced the file: https://github.com/alexpghayes/quarto-accessibility-reprex/blob/main/accessibility-fixes.html. I include this file not as a bug fix or solution suggestion but merely as additional documentation. Uncommenting https://github.com/alexpghayes/quarto-accessibility-reprex/blob/main/_quarto.yml#L17 to enable the fixes resolves many, but not all, of the accessibility issues in the included reprex.
Steps to reproduce
No response
Actual behavior
No response
Expected behavior
No response
Your environment
No response
Quarto check output
Quarto 1.9.37
[✓] Checking environment information...
Quarto cache location: /home/alex/.cache/quarto
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.8.3: OK
Dart Sass version 1.87.0: OK
Deno version 2.4.5: OK
Typst version 0.14.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.9.37
Path: /opt/quarto/bin
[✓] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
Chrome Headless Shell: (not installed)
VeraPDF: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /usr/local/texlive/2025/bin/x86_64-linux
Version: 2025
[✓] Checking Chrome Headless....................OK
Using: Chrome found on system
Path: /usr/bin/google-chrome
Source: PATH
[✓] Checking basic markdown render....OK
[✓] Checking R installation...........OK
Version: 4.5.3
Path: /opt/R/4.5.3/lib/R
LibPaths:
- /home/alex/R/x86_64-pc-linux-gnu-library/4.5
- /opt/R/4.5.3/lib/R/library
knitr: 1.51
rmarkdown: 2.31
[✓] Checking Knitr engine render......OK
[✓] Checking Python 3 installation....OK
Version: 3.10.13 (Conda)
Path: /home/alex/anaconda3/bin/python
Jupyter: 5.5.0
Kernels: python3, sklearn0.24, lottery
[✓] Checking Jupyter engine render....OK
[✓] Checking Julia installation...
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from quarto-dev/quarto-cli
-
binder bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
quarto-dev/quarto-cli#14907 · 3 comments ·
-
brand bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
quarto-dev/quarto-cli#14891 ·
-
brand bug html revealjs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
quarto-dev/quarto-cli#14882 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
quarto-dev/quarto-cli#14875 ·
-
Percent scripts: accept raw-string (r""") and '''-delimited markdown cells, as jupytext writes them Openengines-jupyter enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
quarto-dev/quarto-cli#14850 · 2 comments ·
All issues in quarto-dev/quarto-cli
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
ecosystem wording
Difficulty 1/5 Under an hour Newbie friendliness 90/100
matrix-org/matrix.org#3649 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·