New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility for Visually Impaired - Work with Orca Screen Reader #3393

Open
abhijithb21 opened this Issue Sep 9, 2018 · 6 comments

Comments

Projects
None yet
5 participants
@abhijithb21

abhijithb21 commented Sep 9, 2018

I'm submitting a…

[ ] Bug
[x] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

Not at all working with screen reader.

Expected Behavior

When screen reader is active visually impaired persons shall be able to listen to the contents in the i3bar. They should be able to navigate through the items and the screen reader announces the item on which the focus is on. In DEs like GNOME or MATE people use Alt + Super + S key to toggle screen reader. Then they use some shortcut specified by the DE to switch focus between panels. In each panel they use arrow key to navigate. Technically what we need (IMHO) is i3bar and dmenu to communicate with the ATSPI (https://developer.gnome.org/libatspi/stable/AtspiAccessible.html).

Reproduction Instructions

Environment

Output of i3 --moreversion 2>&-:

i3 version: 


Logfile URL:
- Linux Distribution & Version:
- Are you using a compositor (e.g., xcompmgr or compton):

@i3bot i3bot added the enhancement label Sep 9, 2018

@Airblader Airblader added the 4.15 label Sep 10, 2018

@Airblader

This comment has been minimized.

Show comment
Hide comment
@Airblader

Airblader Sep 10, 2018

Member

Thanks for reporting this! I think a11y is a topic that i3 currently doesn't cover in a meaningful way, but I'm definitely open to changing that. It would be great if we could gain some insight on the details of what this particular change would require in i3bar (or maybe some type of prototype).

Small note:

dmenu to communicate with the ATSPI

dmenu isn't developed by i3.

Member

Airblader commented Sep 10, 2018

Thanks for reporting this! I think a11y is a topic that i3 currently doesn't cover in a meaningful way, but I'm definitely open to changing that. It would be great if we could gain some insight on the details of what this particular change would require in i3bar (or maybe some type of prototype).

Small note:

dmenu to communicate with the ATSPI

dmenu isn't developed by i3.

@abhijithb21

This comment has been minimized.

Show comment
Hide comment
@abhijithb21

abhijithb21 Sep 10, 2018

I do not have much idea regarding that but I am subscribed to Orca mailing list. Since you are interested in implementing a11y I shall share the link to this issue in the list. It is very active and I am sure someone will respond soon.

abhijithb21 commented Sep 10, 2018

I do not have much idea regarding that but I am subscribed to Orca mailing list. Since you are interested in implementing a11y I shall share the link to this issue in the list. It is very active and I am sure someone will respond soon.

@abhijithb21

This comment has been minimized.

Show comment
Hide comment
@abhijithb21

abhijithb21 Sep 11, 2018

Untill now, all I could get from the list is that a developer StormDragon fixed a11y for Ratpoison(http://www.nongnu.org/ratpoison/), another tiling minimalistic window manager. Let me see if I can get in touch with him.
Meanwhile, GNOME has a wiki on a11y - https://wiki.gnome.org/Accessibility.

abhijithb21 commented Sep 11, 2018

Untill now, all I could get from the list is that a developer StormDragon fixed a11y for Ratpoison(http://www.nongnu.org/ratpoison/), another tiling minimalistic window manager. Let me see if I can get in touch with him.
Meanwhile, GNOME has a wiki on a11y - https://wiki.gnome.org/Accessibility.

@orestisf1993

This comment has been minimized.

Show comment
Hide comment
@orestisf1993

orestisf1993 Sep 11, 2018

Member

developer StormDragon fixed a11y for Ratpoison

https://github.com/stormdragon2976/strychnine

But I think it doesn't modify ratpoison's status bar to communicate with atspi.

I think we'd need to play with Glib to implement this.

Member

orestisf1993 commented Sep 11, 2018

developer StormDragon fixed a11y for Ratpoison

https://github.com/stormdragon2976/strychnine

But I think it doesn't modify ratpoison's status bar to communicate with atspi.

I think we'd need to play with Glib to implement this.

@pvagner

This comment has been minimized.

Show comment
Hide comment
@pvagner

pvagner Sep 11, 2018

I am also one of the interested users thus my development related suggestions are just observations of behaviour rather than true development experience.
I'd say accessibility should be implemented gradually into projects such as i3. Initial inspiration should be gathered by looking at window managers such as mate/marco or gnome/metacity. Initially it would be huge step forward if icons signalling window changes (such as when pressing alt+tab) were communicated to assistive tools via at-spi.
If i3 has some internal widget like components then perhaps it might be possible to look into mapping these widgets to ATK roles and slowly implementing relevant ATK interfaces for those one at a time. For static UI components such as buttons, icons this may not be too difficult I hope.
For the rest better knowledge of i3 inner workings and accessibility experience are essential I guess.

pvagner commented Sep 11, 2018

I am also one of the interested users thus my development related suggestions are just observations of behaviour rather than true development experience.
I'd say accessibility should be implemented gradually into projects such as i3. Initial inspiration should be gathered by looking at window managers such as mate/marco or gnome/metacity. Initially it would be huge step forward if icons signalling window changes (such as when pressing alt+tab) were communicated to assistive tools via at-spi.
If i3 has some internal widget like components then perhaps it might be possible to look into mapping these widgets to ATK roles and slowly implementing relevant ATK interfaces for those one at a time. For static UI components such as buttons, icons this may not be too difficult I hope.
For the rest better knowledge of i3 inner workings and accessibility experience are essential I guess.

@abhijithb21

This comment has been minimized.

Show comment
Hide comment
@abhijithb21

abhijithb21 Sep 12, 2018

I guess most of the i3bar is text. Icons come into play when an application is running on background and it stays minimized at i3bar. Eg: Kazam screen recorder.

abhijithb21 commented Sep 12, 2018

I guess most of the i3bar is text. Icons come into play when an application is running on background and it stays minimized at i3bar. Eg: Kazam screen recorder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment