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

revealjs speaker view: Layout select has no accessible name

Abierto Apto para principiantes
  • ¿Algo no está bien?
#15,159 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@jooyoungseo ya está trabajando en esto.

Desde el 22/10/2026.

  • #15164 de @jooyoungseo — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
65/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
html, javascript
Área
accessibility, frontend

Línea de trabajo

Empieza por el marcado de la vista del ponente incluido en src/resources/formats/revealjs/reveal/plugin/notes/speaker-view.html y compáralo después con la incidencia de reveal.js enlazada en el informe. Asigna al selector de diseño nativo un nombre accesible estable, conservando su semántica nativa y la visibilidad del foco del teclado, y mantén sincronizados los bundles de notas generados. El trabajo estará terminado cuando el selector exponga su propósito por separado del valor seleccionado.

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

Descripción

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

Lenguaje dominante
JavaScript
Estrellas
6.1k
Forks
471
Merge medio
21 h 50 min
PR fusionados (30 d)
105

Preparar el entorno

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 quarto-dev/quarto-cli

Todos los issues de quarto-dev/quarto-cli

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.