Re: [orca-list] improve irssi support

[Janina Sajka <janina rednote net>]

Tyna is correct. Speakup is not at all object oriented, so no AT-SPI
support whatsoever.

It's purely a console/terminal screen reader, i.e. whatever row/column
grid you've set resolution to. Personally, I use the app screen with
Speakup, so am not directly on the TTY console. My resolution gives me
65 rows by 175 columns.

One can define zones of this grid for special access, but there's no
facility to load special scripts based on what app might be running as
the old DOS screen readers (like asap and vocal-eyes) used to do.

On the other hand, there's tremendous capibility in bash, and many, many
apps that work very well from a console tty--and arguably better from a
screen session in that tty.

Since Linux doesn't limit how many tty console sessions you can launch,
whyworry about irssi under Orca? Why not simply Alt+Ctrl+FN whatever to
switch to the tty where you're running irssi with Speakup?

Personally, I have 24 tty consoles defined. The Left Alt gets me to the
first 12, and the right Alt gets me 13-24. Yes, I do use them all, quite
systematically, actually.

tia

Janina

Janina

Tyna Pelletier-Bilodeau writes:
> Hi,
> speakup is a pure console screen reader, so no it can't really use at-spi2,
> unless it also handles tty in some ways I'm not aware of
> Thanks
>
> Joanmarie Diggs a écrit :
> > Hi Tyna.
> >
> > On 06/23/2017 10:58 AM, Tyna Pelletier-Bilodeau wrote:
> >
> > [...]
> >
> > > As far as I know, all irssi is using is terminfo, I don't know why
> > > speakup works so well with it and yet orca does not, but I'd like it if
> > > support could be improved.
> > Is speakup using AT-SPI2 for this presentation?
> >
> > The reason I ask is that the information we get via AT-SPI2 is mostly
> > accessible-text change events -- and not events that are clear. Often,
> > when new text comes in, the event is not for just the newly-inserted
> > text; there's a text deletion event removing a bunch of text followed by
> > an insertion of a bunch of text, and Orca has to play "Guess what
> > changed and why." Furthermore, Orca doesn't know you're in irssi, or
> > vim, or less, or.... So the guessing game is pretty challenging. On top
> > of all of that, there are a few bugs in VTE's accessible-text
> > implementation (e.g. when you ask for the line, do you get the right
> > line and offsets?). That also has to be taken into account in the
> > guessing game.
> >
> > --joanie
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org

-- 

Janina Sajka,   Phone:  +1.443.300.2200
                        sip:janina asterisk rednote net
                Email:  janina rednote net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa