MonoGame Pipeline accessibility problems

MonoGame / MonoGame

One framework for creating powerful cross-platform games.

http://www.monogame.net

Other

11.3k stars 2.9k forks source link

MonoGame Pipeline accessibility problems #6707

Open alex19EP opened 5 years ago

alex19EP commented 5 years ago

hello. i am a blind developer. i trying to use MonoGame to create my games. for computer access i am using https://github.com/nvaccess/nvda/. currently there are sum accessibility problems with content pipeline which prevents me to fully embrace it's power.

it's not possible to navigate properties and build output windows using keyboard.
properties and build windows aren't exposed to screen-reader.

What version of MonoGame does the bug occur on:

MonoGame 3.7
and latest development branch.

What operating system are you using:

Windows

mrhelmut commented 5 years ago

Hey Alexandr,

Providing that I have the time to look into it and that Eto.Forms supports it, I'll check if I can add screen-reader support to the pipeline.

@cra0zy Do you happen to know if Eto supports automation properties? I know that WPF does and that filling them allows screen readers to work, but I can imagine that it's getting more complex in a multi target system like Eto.

alex19EP commented 5 years ago

@mrhelmut i am appreciate it. if you need help from accessibility standpoint feel free to ask me.

harry-cpp commented 5 years ago

Both Properties and BuildOutput controls are actually custom drawn controls, they are basically just a canvas control in reality.

alex19EP commented 5 years ago

@cra0zy Does it means that with current approach accessability implementation isn't possible?

mrhelmut commented 5 years ago

There should be ways. It's indeed more complicated but it should be possible to do something about this.