[orca-list] Kate editor accessibility

[chrys at linux-a11y.org]

Howdy,

AFAIK Kate offers an VIM mode.  But i never used it so i cannot tell  
much about.

For Thunderbird there are several
  addons to behave like vim
http://vimperator.org/muttator

Even for firefox
https://addons.mozilla.org/de/firefox/addon/vimfx/

Cheers chrys

Zitat von Gary Kline <kline at thought.org>:

> =====
> Organization: Thought Unlimited.  Public service Unix since 1986.
> Of_Interest: With Thirty+ years  of service  to the  Unix  community.
>
> On Thu, Nov 01, 2018 at 01:49:26PM +0100, chrys wrote:
>> Howdy list,
>>
>> Joanie investigated the Kate issues for us. ill forward the results here.
>>
>> maybe we can see what we can do.
>>
>> cheers chrys
>>
> 	HI everyone,
>
> 	sincerely apoloogies if this this the wrong way or list to ask  the
> 	following question.  Due to a very rare disability, vi, nvi, vim,
> 	gvim are the onlyy editors I can use with my left hand.  --A brain
> 	surgery in the 1960's destroyed my right side.  I learnwed "vi" at
> 	Cal in the 1980s.   My system admin has me set up with/
> 	thunderbird.  its editoe is several times harder to use the
> 	mutt+vim.
>
> 	is there a way of settting up kate to emulate gvim?  --or can
> 	anyboody help me usse gvim and thunderbbird?  {Nutshell, I've use
> 	mail, mail, elm, and finally mutt.}  These all let me use vim or a
> 	clone.  WHen I have to use mail with a URL, since there is no xmutt,
> 	I have to bring up t'bitd and then go back to mutt.  I'd like to
> 	find an email client that can le me use some form of [g]vi[m]
>
> 	TIA,
>
> 	gary
>
>>
>> -------- Weitergeleitete Nachricht --------
>> Betreff: 	Re: [orca-list] Kate editor accessibility
>> Datum: 	Thu, 1 Nov 2018 12:35:22 +0100
>> Von: 	Joanmarie Diggs <jdiggs at igalia.com>
>> An: 	chrys <chrys at linux-a11y.org>
>> Kopie (CC): 	orca-list <orca-list at gnome.org>
>>
>>
>>
>> Hey Chrys.
>>
>> In answer to your questions:
>>
>> On 10/31/18 11:02 PM, chrys wrote:
>>
>> > Bug 1: Arrow up/ down will not interrupt orcas current speech output.
>> > maybe it looks like to additional content to orca instead of an line
>> > navigation. So ctrl needs to been pressed after every line change to
>> > interrupt speech. can you check why orca is not interrupting here on
>> > line change.
>>
>> When you use the arrow keys to move by line, Orca asks AT-SPI2 for the
>> line at offset. When I ask for a line of text, Kate responds with all
>> the text typed until I pressed Enter (i.e. a hard return) What Kate
>> should instead respond with is all the text on the visual line, which
>> ends at the point the text wrapped due to the window size. Make sense?
>>
>> > Bug 2. After doing arrow up / down start to navigate by char (arrow left
>> > / right) orca does repeat the previous line once instead of just speak
>> > the char. this only happen once and directly after an line navigation
>> > (arrow up/ down).
>>
>> It looks like Kate is not telling us about key presses and key releases;
>> only key releases. What we see from Gtk+, Gecko, etc. is an ordering
>> like this:
>>
>> Action 1:
>> Key press down
>> Caret moves one line down
>> Key release down
>>
>> Action 2:
>> Key press right
>> Caret move one char to the right
>> Key release right
>>
>> Action 3:
>> Key press right
>> Caret move one char to the right
>> Key release right
>>
>> What we're getting from Kate seems to be:
>>
>> Action 1:
>> Caret moves one line down
>> Key release down
>>
>> Action 2:
>> Caret move one char to the right
>> Key release right
>>
>> Action 3:
>> Caret move one char to the right
>> Key release right
>>
>> Orca uses a combination of the caret-moved events and the keyboard
>> events to try to figure out what the user is doing and, based on that,
>> figure out what to present. This combination is needed because a
>> keyboard event doesn't necessarily result in the caret moving, and
>> caret-moved events don't tell you why the move occurred; merely that the
>> caret is at a new location.
>>
>> So when a caret moved event comes in, Orca looks at the last key event
>> and determines what to present to you. In the Gtk+, Gecko, etc.
>> scenario, we know what arrow key you pressed before the caret moves so
>> we can guess correctly whether or not to present a line versus a
>> character. But Kate isn't telling us about key presses. So the last key
>> isn't what you just did; it's what you did one step back. It's only
>> after Orca presents the new caret's location that it is told what arrow
>> key you pressed.
>>
>> There may be some sort of hack I can add in Orca to work around this
>> issue. But the lack of key press events is a bug in Kate (or Qt or
>> whatever). And if they fix that bug, I believe Orca will start doing the
>> right thing automatically. Plus the more hacky guesswork I have to add
>> to Orca, the less reliable Orca will be. So do you think you can get
>> this fixed in Kate (or Qt or whatever)?
>>
>> --joanie
>
> --
>  Gary Kline  kline at thought.org  http://www.thought.org  Public Service Unix
>                 Thirty+ years of service to the Unix community.