After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 615770 - [blocked] Create an Orca script for Jokosher
[blocked] Create an Orca script for Jokosher
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.30.x
Other All
: Normal enhancement
: FUTURE
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-14 18:36 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-08 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joanmarie Diggs (IRC: joanie) 2010-04-14 18:36:19 UTC
A user has requested that we provide support in Orca for sound editing tools, including Jokosher. [1] A Jokosher developer has since indicated commitment to accessibility and a desire to improve it in Jokosher wherever possible. [2] Therefore, we should create an Orca script for Jokosher.

[1] http://mail.gnome.org/archives/orca-list/2010-April/msg00278.html
[2] http://mail.gnome.org/archives/orca-list/2010-April/msg00305.html
Comment 1 Joanmarie Diggs (IRC: joanie) 2010-04-17 21:41:52 UTC
Happily, the bulk of Jokosher is quite accessible.

Using version 0.11.5 from bzr, I've identified the following problems which impact Orca and/or its users:

1. The timeline is not keyboard accessible. Tim Miao has already filed bugs for this: https://bugs.launchpad.net/jokosher/+bug/484071 and https://bugs.launchpad.net/jokosher/+bug/484106

2. The widget in which one can change the time format is not keyboard focusable or toggle-able. I have opened a new bug for this issue: https://bugs.launchpad.net/jokosher/+bug/565603

3. In the New Project dialog, we're missing a LABEL_FOR/LABALLED_BY relationship pair between the "Folder" label and combo box. I have opened a new bug for this issue: https://bugs.launchpad.net/jokosher/+bug/565611

In terms of creating a Jokosher-specific script for Orca, there's really not a lot that needs doing. (Yay!) 

One thing that did jump out at me is that we should provide a bit more context so that the user knows when he/she is on the toolbar versus on a button associated with an instrument -- and which instrument. Depending on the fixes for the aforementioned bugs, it may prove useful (or necessary) to do some additional custom handling.

I'm marking this bug as "blocked" because the primary purpose of an audio editor is, of course, to enable editing of audio. :-) Until the timeline is keyboard accessible, editing audio with Jokosher is not really accessible to Orca users.
Comment 2 Joanmarie Diggs (IRC: joanie) 2010-04-18 18:40:19 UTC
In order to present the instrument context as described above, we need the expected AtkRelation pair set. I've opened a new bug for this issue:
https://bugs.launchpad.net/jokosher/+bug/566139
Comment 3 Joanmarie Diggs (IRC: joanie) 2010-04-18 19:26:44 UTC
We currently cannot indicate when a user has (de)selected an audio event in Jokosher (which one does by moving focus to it and pressing Return). In order to do so, we need the expected event and change in the AtkStateSet. I've opened a new bug for this issue:
https://bugs.launchpad.net/jokosher/+bug/566164
Comment 4 Joanmarie Diggs (IRC: joanie) 2010-04-18 21:14:22 UTC
We will need a reliable way to identify the timeline and the audio events. There will also be times where we want to present a single detail about in relation to an accessible event (e.g. the new start time of an audio event which was just moved). Right now, all of this information is exposed in the accessible name. It would be much better if we could get the details via object attributes. I've opened a new bug for this issue:
https://bugs.launchpad.net/jokosher/+bug/566233
Comment 5 Joanmarie Diggs (IRC: joanie) 2010-04-18 21:36:03 UTC
A request for object:property-change:accessible-value events has just been filed here: https://bugs.launchpad.net/jokosher/+bug/566248

(Mike, I know you acknowledged this and added it to your to-do list when I mentioned it on the Orca list. Thanks! But at that time, I hadn't noticed that we weren't getting these events when the user moves the position within the timeline. Plus I don't think we always want to get those events; just sometimes.... :-) So to be on the "safe side," I went ahead and filed it.)
Comment 6 Joanmarie Diggs (IRC: joanie) 2018-02-08 12:47:03 UTC
Closing blocked bugs because we need the issue fixed in the blocker.