Tichau/FileConverter

Some list and tree items do not expose their values to screenreaders

Open

#95 opened on Oct 29, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (14,357 stars) (871 forks)batch import
good first issuenew feature

Description

Within the interface of the program certain elements lack the necessary accessibility labels allowing blind users who rely on their screenreaders to figure out what their function is. In such a case either only the value a setting is set to is read or the items carry generic names that do not convey the significant information to the user such as "File Converter Preset Model. Examples of such items can be found in:

  • the list of configured conversion presets where instead of the preset names generic container names are read;
  • in the tree of available input formats, the expandable tree branches carry the same generic control names;
  • on the list of output formats, the different format items carry generic control names;
  • in the Application settings the sliders and checkboxes do not have any labels so they are announced but the user does not know what is being set.

A fix of those issues would be greatly appreciated.

Contributor guide

Tech stack
csharp
Domain
accessibilitydesktop
Issue type
accessibility
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C# basicsWindows UI accessibility
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue lists four specific areas: the conversion presets list, the input formats tree, the output formats list, and application settings sliders/checkboxes. Start by examining the UI code (likely in WPF or WinForms) to locate these components. Look for where accessibility properties are set or missing, and add appropriate AutomationProperties.Name or AccessibleName values to ensure screen readers announce the function of each element. Check for any existing patterns in the codebase for accessibility labeling to maintain consistency.