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

[BUG] Custom text-based hyperlinks are not fully keyboard and screen-reader accessible

Abierto
  • ¿Algo no está bien?
#5,458 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
accessibility, desktop

Línea de trabajo

Start by reproducing the links in Package Details and the Settings > General and Manage telemetry settings views with keyboard navigation and a screen reader. Trace the Avalonia UI definitions for these three areas; no specific file or test is named in the issue. Done means every listed link is focusable in order, activates with keyboard and UI Automation, and behaves consistently with mouse input.

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

Descripción

bug
Please confirm these before moving forward
  • I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions.
  • This issue is about a bug (if it is not, please use the correct template).
UniGetUI Version

2026.3.0

Windows version, edition, and architecture

Windows 11

Describe your issue

Several custom text-based hyperlinks in the Avalonia UI are not fully accessible from the keyboard or with screen readers.
I found this issue in three areas:

  1. Package Details, including links such as:
  • Homepage
  • License URL
  • Manifest URL
  • Installer URL
  • Release notes URL
  • Download installer
  1. Settings > General > "Become a translator"
  2. Telemetry settings > "More details about the shared data and how it will be processed"
Steps to reproduce the issue

Package Details links

  1. Open a package's details window.
  2. Navigate to one of the text links, for example:
  • Homepage
  • License
  1. Attempt to activate the link using normal keyboard interaction or a screen reader.
  2. The control does not provide the same reliable activation behavior as a standard hyperlink/button control.

Become a translator

  1. Open UniGetUI.
  2. Go to Settings > General.
  3. Navigate through the page using Tab.
  4. Notice that "Become a translator" is skipped.
  5. With NVDA(or other screen reader), locate the text using object navigation and press it.
  6. The link is not activated.

Telemetry details link

  1. Open Settings > General.
  2. Activate Manage telemetry settings.
  3. Navigate through the dialog using Tab.
  4. Notice that "More details about the shared data and how it will be processed" is skipped.
  5. With NVDA(or other screen reader), locate the object using object navigation.
  6. Press it, nothing is opened.

Expected behavior
All interactive links should provide consistent keyboard and assistive-technology behavior.
In particular:

  • Interactive links should be keyboard focusable.
  • They should appear in the expected keyboard navigation order.
  • Enter and space should activate a focused hyperlink.
  • Screen readers should be able to invoke the control using the standard UI Automation action.
  • A control exposed as Hyperlink through UI Automation should expose a usable action and not report "No action".
  • Mouse, keyboard, and assistive-technology users should all be able to perform the same operation.
UniGetUI Log
No relevant UniGetUI runtime error was observed. This appears to be a keyboard/UI Automation accessibility issue rather than an application error.
Package Managers Logs
N/A — this issue is unrelated to package manager operations.
Relevant information

#1767

Screenshots and videos

No response

Lenguaje dominante
C#
Estrellas
26.3k
Forks
939
Merge medio
23 h 24 min
PR fusionados (30 d)
63

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 Devolutions/UniGetUI

Todos los issues de Devolutions/UniGetUI

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.