Progreso en los problemas de accesibilidad del lector de pantalla para usuarios habituales en los foros?

sam · 10 Junio, 2021 01:00

Acabo de realizar este cambio (en vivo en meta en unos 20 minutos)

github.com/discourse/discourse

A11Y: Adjust heading rules on topic lists (#13353)

master ← list-accessibility

merged 12:59AM - 10 Jun 21 UTC

SamSaffron

+3 -3

Previously due to "rowheader" role we would read out topic titles twice. This a…djusts it so we apply the heading role only to the topic link. In turn this makes navigation through topic lists more accurate (h) only lands you on topic links. It also reduces the amount of duplicate reading NVDA does. Before: Topic title link new topic link support link b481 link 19h link 2 button... After: Topic title link This reduces noise, up and down once you land on a topic link can give you more context.

¿Podrías decirme cómo te funciona? @thoeg

Tema		Respuestas	Vistas
A11Y: topic lists do not have headings for each topic UX accessibility	9	341	8 Noviembre 2024
Issue 1: Broken Heading Navigation / DOM Manipulation Bug accessibility , screen-reader	12	535	6 Noviembre 2025
Discourse with a screen reader UX accessibility , screen-reader	137	11628	23 Febrero 2024
Accessibility software and discourse Feature	51	12266	9 Mayo 2015
Accessibility audit and shepherd for making improvements UX accessibility	22	5836	26 Abril 2018

Progreso en los problemas de accesibilidad del lector de pantalla para usuarios habituales en los foros?

Temas relacionados