stride3d/stride

tag the unlabeled buttons in the launcher

Open

#321 opened on Jan 10, 2019

View on GitHub
 (3 comments) (2 reactions) (1 assignee)C# (6,001 stars) (886 forks)batch import
area-GameStudioarea-Launcherenhancementgood first issue

Description

Hello guys,

I'm a blind developer, and for the complete use of a pc and development tools, the blind people must have to use assist technology software, in our case is a screen reader.

After a few checks with the xenko launcher (I can't test deeperli the xenko studio) apparently is a lot accessible, because is created with an accessible framework.

Witch framework is used to the gui of xenko launcher?

The most noticeable detail in the application, is that the majority of the buttons are unlaveled; so the screen reader can't read anything about that buttons; but other are completely tagged, like the button for show beta versions, report issues, discuss about xenko, etc.

The most important buttons that are unlaveled, are these for install / uninstall versions, the other that reports when you have some updates, etc.

So, can you improve these things? Isn't a hard task to do; various frameworks have special properties for their gui components for interacts directly with automation tools or assistive technologies.

For a first approach to the accessibility will a very good first step; and the option to use the framework directly into visual studio only with code make xenko a very, very good option to blind developers that want create games, and the HRTF feature into your xenko.audio lib... buf... I have a lot of time findinga good framework that supports directly HRTF and are accessible, and xenko come to me like a gold for a miner :)

Thanks so far guys!

Contributor guide

Tech stack
csharp
Domain
accessibility
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.
1-3 hours
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.
mostly clear
Prerequisites
basic C# knowledgefamiliarity with WPF UI frameworkunderstanding of screen reader accessibility
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue requests adding accessible labels to unlabeled buttons in the Stride Launcher. The launcher UI is likely built with WPF (common for .NET desktop apps). First, locate the launcher's XAML files (e.g., in the Stride.Launcher project). Identify buttons missing AutomationProperties.Name or equivalent accessibility properties. Existing tagged buttons (e.g., 'Show Beta Versions') can serve as a pattern. Add descriptive labels for install/uninstall buttons and update notification buttons. Test with a screen reader to verify. No linked PRs or maintainer comments detailing scope were provided, so the fix is straightforward but requires attention to all unlabeled buttons.
tag the unlabeled buttons in the launcher · stride3d/stride#321 | Good First Issue