Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

revealjs speaker view: Layout select has no accessible name

Fermée Adaptée aux débutants
  • Quelque chose ne va pas ?
#15,159 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Une pull request liée a déjà été fusionnée.

  • #15164 par @jooyoungseo — fusionnée

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
65/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
html, javascript
Domaine
accessibility, frontend

Piste de recherche

Commencez par le balisage de la vue présentateur fourni dans src/resources/formats/revealjs/reveal/plugin/notes/speaker-view.html, puis comparez-le au problème reveal.js lié dans le rapport. Donnez au sélecteur de disposition natif un nom accessible stable, tout en préservant sa sémantique native et la visibilité du focus clavier, et gardez les bundles de notes générés synchronisés. Le travail est terminé lorsque le sélecteur expose sa fonction séparément de sa valeur sélectionnée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

bug revealjs

Bug description

The speaker-view Layout dropdown has no programmatic accessible name.

This reproduces in a default Quarto revealjs deck as well as standalone upstream reveal.js 6.0.2. This is a downstream tracking report for the bundled notes plugin, not a Quarto-only regression.

Steps to reproduce

  1. Save the following as speaker.qmd and run quarto preview speaker.qmd.
  2. Advance past the title slide to First slide, then press S to open speaker view. Wait until the previews and speaker notes are visible.
  3. In the speaker-view window, inspect the layout select and the four top-level panel containers using browser accessibility/DOM tools. For the layout issue, focus the select and change its selected option using the keyboard.
---
title: Speaker view accessibility reproduction
format: revealjs
---

## First slide

First slide content.

::: {.notes}
Speaker notes for the first slide.
:::

## Second slide

Second slide content.

::: {.notes}
Speaker notes for the second slide.
:::

No custom filters, extensions, themes, or author CSS are used. The tested deck was rendered with quarto render speaker.qmd and served by a local HTTP static server.

Actual behavior

The visible label is a separate span, not a programmatic label for the native select:

<span class="speaker-layout-label">Layout: Default</span>
<select class="speaker-layout-dropdown">
  <option value="default">Default</option>
  <option value="wide">Wide</option>
  <option value="tall">Tall</option>
  <option value="notes-only">Notes only</option>
</select>

In the running speaker window, the select has no id, associated label, aria-label, aria-labelledby, or title; select.labels.length is 0. Its selected value is present, but that does not supply the control's purpose/name ("Layout"). With the select focused, ArrowDown changes its value from default to wide, and the visible text changes to "Layout: Wide". This is an accessible-name defect, not a claim that the native select or its options are entirely unavailable to every screen reader.

The select also has computed opacity: 0 and overlays the visible span. Opacity alone is not evidence that a control is excluded from a browser accessibility tree; the defect here is the missing label association.

Expected behavior

Give the native select a programmatically associated, stable accessible name such as "Layout" (e.g., a label with for/id or aria-labelledby pointing to an appropriate label). Preserve native select semantics and expose its selected value separately from its purpose. Verify keyboard focus visibility while retaining the custom visual styling.

Please incorporate the corresponding upstream fix into the bundled notes plugin (or backport as appropriate), keeping generated notes bundles synchronized.

Your environment and verification scope

Quarto CLI 1.11.5 (prerelease), bundling reveal.js 5.1.0 according to the generated reveal.js header. The installed speaker-view.html matches the current quarto-cli main source at 517944ddc441a64d66f18b90b51c7a9d3c1af5b8 after normalizing line endings/trailing whitespace. Runtime testing used the installed build, not a separately built main checkout.

Windows, Chromium-based Aside Browser (user agent Chrome/153.0.0.0). Verified through live DOM inspection, browser snapshots, and keyboard interaction. No JAWS/NVDA/VoiceOver speech-output session was run; this report does not assert a particular spoken utterance or behavior across all screen readers.

Source

Bundled speaker-view markup.

Quarto check output (relevant excerpt)

Quarto 1.11.5
Pandoc version 3.10.0: OK
Dart Sass version 1.101.0: OK
Deno version 2.7.14: OK
Typst version 0.15.1: OK
Checking versions of quarto dependencies: OK
Checking Quarto installation: OK
Version: 1.11.5
CodePage: 1252

Searched existing open and closed issues; no matching speaker-view report was found.

Upstream report

https://github.com/hakimel/reveal.js/issues/3951

Langage dominant
JavaScript
Étoiles
6.1k
Forks
471
Merge moyen
16 h 41 min
PR mergées (30 j)
102

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de quarto-dev/quarto-cli

Toutes les issues de quarto-dev/quarto-cli

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.