stride3d/stride

tag the unlabeled buttons in the launcher

Open

#321 aperta il 10 gen 2019

Vedi su GitHub
 (3 commenti) (2 reazioni) (1 assegnatario)C# (886 fork)batch import
area-GameStudioarea-Launcherenhancementgood first issue

Metriche repository

Star
 (6001 star)
Metriche merge PR
 (Merge medio 10g 11h) (22 PR mergiate in 30 g)

Descrizione

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!

Guida contributor