Alexander Surkov | 11 Dec 22:35 2014
Picon

specialized dialog roles

Hi. ATK as IAccessible2 both have bunch of roles for specialized dialogs like color chooser dialog [1], [2]. I'm curious if there's any application on Linux today for these roles. In case of IAccessible2 we never used those in Firefox following IA2 spec. However Chrome uses those roles for control elements rather than for their associated dialogs, and Jamie from NVDA thinks it's reasonable [3]. I'm curious if it makes sense to follow this example.

Thanks.
Alexander.
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Michael Pozhidaev | 5 Dec 05:43 2014
Picon

How to choose the suitable event in AT-SPI

Hello all,

I got a question regarding choosing the most relevant event for the
particular user action. When the user does something (presses the key or
anything else) his/her action usually yields the several events which go
through registryd and are transmitted to AT. The problem is how to
choose among them the most preferable one? We can collect them and do
the selection but for that we should be sure that know them all and for
the last user action there will no events any more. This require a some
sort of transactions or packets and I am wondering is there any way to
ensure that we got everything for the last user action? Maybe my
approach is wrong and I would be thankful if somebody can help me to
understand what I should do with that.

Speaking "the most preferable event" I mean the most relevant event to
construct a user feedback. For example, when the user presses keys in
the editable text, the events reflecting caret move and text changing arrive.
Among them we need the text changing one while caret move is very
confusing because it could be caused just by pressing the arrows.

Thank you in advance! 

--

-- 
Michael Pozhidaev. Tomsk, Russia.
Russian info page: http://www.marigostra.ru/
English info page: http://www.marigostra.com/
Juanjo Marín | 30 Nov 23:23 2014
Picon
Picon

Some notes about the status of the keyboard navigation in GNOME 3.14

I've been learning how users can interact to GNOME using just the keyboard, after reading Peter Vágner
email to the (a11y) mailing list. Reading the documentation [2], the main shortcuts for keyboard
navigation in applications are: 

1) Tab: Moves keyboard focus between different controls. Shift+Tab does the same in the reverse order. 

2) Ctrl+Tab: moves between groups of controls and can also break out of a control that uses Tab itself, such
as a text area. Shift+Ctrl+Tab does the same in the reverse order. 

3) Arrows keys: Move selection between items in a single control, or among a set of related controls. 

It seems to me there some inconsistencies, or at least the definition of control, group of controls and
items are fuzzy in practice. Some cases to explain this: 

gnome-control-center: What I expect is three groups of controls: find, Personal, Hardware and System.
However, the Ctrl+Tab doesn't work as I expected. In this application, Tab behaves as I expected Ctrl+Tab
should do. This means that find, Personal, Hardware and System are controls instead of groups and there
are only two groups controls: find and everything else. The arrow keys allow me to move between all the the options.

Online accounts: This is tricky. The item selected from the list on the left determines the content of the
right panel. The current keyboard navigation layout doesn't convey this relationship IMHO. The user
starts in the first item of the list, pressing Tab moves the focus to the add button and pressing Tab again
moves the focus to the controls on the right related to the item selected on the list. IMHO this behaviour is
confusing. To convey this relationship, I guess that pressing Tab should move the focus to the controls
related to the item selected on the list. However, this fix is not totally perfect, because the minus
button for removing this account (and related of the selected item on the list), it is not the following
button focused by pressing Tab, though it can be reached by pressing the left arrow. 

gnome-calculator: It works ok, except that there aren't any group of controls. I think it makes sense to
have the following groups: calculator selector, calculator display and the keys. I like the fact I can
navigate the keys with tab or using the arrows keys, but also you can use Ctrl+Tab, and this is not as good
IMO. 

Region and Language: I focus in the language menu here. You can navigate the items of the list using Tab or the
arrows keys. I find strange the fact the enter key doesn't work to activate the "more language" option and
you have to press the space key instead. The language menu after pressing the "more languages" options is
pretty similar to the previos menu. It has much more language-items and a search control. The navigation
in the items is pretty similar, using Tabs or arrows keys. It is weird that the scroll of the list don't
follow the item selected in the list, so the selected item can be out of view easily. 

In general terms, I think that the keyboard navigation will benefit of a better definition of control
groups. This is something that it has to be done along with the design of the interface, so I think it
deserves a section in the HIG and mentioned in other sections. I take as granted that this can be done with
the current version of GTK+. I think that the user should be able to reach linearly all the controls shown in
the interface by pressing Tab (except when it is necessary to use Ctrl+Tab to  break out of a control that
uses Tab itself). You can also navigate controls using the arrows, it becomes very handy when the group of
controls have grid (or sort-of) layout. And finally, items in lists and similar can me reached by using the
arrows, and unless the items can be considered a control itself, Tab shouldn't work here IMO. 

Another issue I think it deserves some attention is that accelerators are not shown in the menus of in
certain redesigned applications like gedit. And, in general, accelerators are not shown in the
Application Menus. Also, the use of buttons in the new design usually means as well that accelerators for
those options are not shown. In previous/old designs, buttons usually were a way to help mouse oriented
users to easy access to frequently used options, and those options were also in the menus with their
accelerators. In the new designs, the buttons are usually the only way that those options are shown in the
interface. They only way I can think of to show accelerators in buttons is by adding this info in the
tooltips, but currently they only shown briefly desc of the action assigned to the button. My opinion is
that accelerators must be shown because they really encourage users to learn how to use the applications
using only the keyboard. I think it is good idea not to shown accelerators if not keyboard is detected, but,
if detected, they must be shown by default. And related to this, GTK+ deprecated the support for changing
accelerators since 3.10. This maybe is not a great lost, because it is supposed that most common
accelerators are standarised by the HIG [4]. However it could be useful in certain situations, for
example, when an option doesn't have any accelerator, adapt applications to other envs or personal
needs, etc. 

I hope this message can help to get some debate and eventually take some actions to improve the situation :-)

Cheers,

-- Juanjo Marín 

[1] https://mail.gnome.org/archives/gnome-accessibility-list/2014-October/msg00001.html 
[2] https://help.gnome.org/users/gnome-help/stable/keyboard-nav.html.en 
[3] https://git.gnome.org/browse/gtk+/commit/?id=2d79334bb069224966b3dcd8456967c9800e8fd0 
[4] https://developer.gnome.org/hig/stable/keyboard-input.html.en
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Mike Gorse | 25 Nov 01:18 2014

ANNOUNCE: at-spi2-core 2.15.2 released

At-spi2-core 2.15.2 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.15/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.

What's changed in AT-SPI 2.15.2
===============

* Make the documentation of ATSPI's STATE_ACTIVE consistent with that of
   ATK's (bgo#740274).

* Add ATSPI_ROLE_STATIC and update documentation for ATSPI_ROLE_TEXT
   (bgo#740340).

* gi-annotations: get_relation_set returns a array of AtspiRelation

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus

How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi <at> lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk
Daiki Ueno | 25 Nov 00:07 2014
Picon

caribou 0.4.16

Caribou is a text entry and UI navigation application.
This is an unstable release towards GNOME 3.16.

News
====
- Stop using deprecated accessibility events ("focus:*")
- Bug 739837 - Allow label overwrite in keyboard layout
- Bug 739716 - Add more keys to label_map
- Bug 739711 - Escape key does not work in us layout.
- Bug 739526 - Some buttons do not have a label.
- Bug 722634 - [regression] build failure: ImportError: No module named 'caribou_settings'
- Translation updates (Punjabi, Nepali, Slovak)

Contributors
============
Daiki Ueno
Raphael Freudiger

Translations
============
A S Alam (pa)
Dušan Kazik (sk)
Pawan Chitrakar (ne)

Download
========
https://download.gnome.org/sources/caribou/0.4/caribou-0.4.16.tar.xz (398K)
  sha256sum: 8e70090f9cf64e3b42f6995e3228ab1f38a438687d13e2aa9497925a2a6b1d32

Regards,
--

-- 
Daiki Ueno
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Magdalen Berns | 22 Nov 20:29 2014

Java ATK Wrapper unimplented methods

Hi list,

Without fully testing each one I went through the java-atk-wrapper code and have been able to identify the following methods and interfaces as being unimplemented or as having an implementation which is incomplete:

Action:
get_localized_name
set_description
Component:
add_focus_handler
get_mdi_zorder
get_alpha
remove_focus_handler
Document Interface (not yet implemented):
get_document_type
get_document
get_attribute_value
get_attribute_value
get_attributes
get_locale
get_current_page_number
get_page_count
EditableText:
set_run_attributes
HyperlinkImpl:
TODO Currently Not fully documented by ATK
Image:
get_image_locale
set_image_description
StreamableContent (not yet implemented and may not have java equivalent):
get_n_mime_types
content_get_mime_type
content_get_stream
content_get_uri
Table:
set_caption
set_row_description
set_column_description
set_row_header
set_column_header
set_summary
add_column_selection
add_row_selection
TableCell (not yet implemented):
get_column_span
get_column_header_cells
get_position
get_row_span
get_row_header_cells
get_row_column_span
cell_get_table
Text:
set_free
attribute_register
attribute_get_name
attribute_for_name
attribute_get_value
Value:
get_minimum_increment
get_range
get_sub_ranges
get_value_and_text
set_value

For now it would be useful to get some feedback on what might be a good idea to focus on implementing. Alejandro has indicated the text interface as quite important so I am thinking this might be the best place to start but I am a bit concerned about what I am seeing with the focus stuff too. I am also quite keen to further investigate what's happening with the Windows interface signals in jawobject.c. Generally, I am interested in what the first impressions on this are so far, before going ahead with a strategy on addressing some of these implementations for java-atk-wrapper.

Magdalen

_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Alejandro Piñeiro | 12 Nov 16:24 2014

my atspi examples available

Hello,

recently Joanmarie asked me if I had any atspi example written in 
javascript, and I started to search my disorganized folder of custom 
scripts, and I also found several examples most of them written in C 
(libatspi), and one in javascript (libatspi with gobject introspection).

Right now there aren't any similar thing on any official repository, so 
I cleaned them up and uploaded on a private github repository:
https://github.com/infapi00/atspi-examples

They are basic stuff like list the available accessible applications, 
dump the accessibility hierarchy of a given app and print out the 
current selected/focused accessible object on each state change.

The next immediate tasks would be have equivalent examples of the 
current C ones written in javascript and python examples (both using 
pyatspi2 and gobject introspection). Then we could think on adding more 
examples.

Although they need some more cleaning, I think that it would be worth to 
eventually move them to a gnome repository. Initially I was thinking on 
putting them directly at at-spi2-core repository, but that would prevent 
to add non-C examples without complicating too much the configure. So I 
think that if they become part of a gnome repository, it should be also 
independent of at-spi2 repository. Would be somewhat similar to 
gnome-shell and gnome-shell extensions. Opinions?

BR

--

-- 
Alejandro Piñeiro (apinheiro <at> igalia.com)

_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
ssuk hyun kim | 3 Nov 06:42 2014
Picon

AT-SPI in Upstart

I have created an application that get informations of firefox using AT-SPI and c++ and worked.
But it doesn't work while runs as upstart not an application despite the same source code.

The reason is atspi_init() returns error 2.

I wrote the conf file of upstart like this:

description "firefoxurl daemon"
start on runlevel [2345]
stop on  runlevel [!2345]
script
    exec /opt/GetCurrentUrlOfFirefox
end script

Can someone tell me how to use at-spi in Upstart?
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Mike Gorse | 28 Oct 02:03 2014

ANNOUNCE: at-spi2-core 2.15.1 released

At-spi2-core 2.15.1 is now available for download at:

http://download.gnome.org/sources/at-spi2-core/2.15/

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in C and a wrapper
for Python.

What's changed in AT-SPI 2.15.1
===============

* Fix some issues with the accessibility bus configuration (bgo#722738).

* Documentation for AtspiTableCell is now built.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.a11y.org/d-bus

How can I contribute to AT-SPI2?
================================

We need help testing with Gnome accessibility technologies, improving
performance, and generally tying up loose ends.  The above-referenced page
contains a list of known issues that should be fixed.

IRC   : #a11y on Gimpnet
E-Mail: accessibility-atspi <at> lists.linux-foundation.org

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk
Daiki Ueno | 24 Oct 06:02 2014
Picon

caribou bugs after 3.14

Hello,

As mentioned in the yesterday's meeting, quite a few bugs (either
upstream/downstream) have been filed against caribou, after 3.14.

Those are exposed after caribou switched to D-Bus activation:
https://bugzilla.gnome.org/show_bug.cgi?id=683712

After the change, /usr/libexec/caribou (which uses at-spi2-core) is
always launched at gnome-shell startup, even for a short-lived 'gdm'
user session.  That seems to hit some corner-cases.

Mike fixed an issue right before 3.14:
https://bugzilla.redhat.com/show_bug.cgi?id=1138934#c26

However, there are more coming:
https://bugzilla.redhat.com/show_bug.cgi?id=1148362
https://bugzilla.gnome.org/show_bug.cgi?id=738662

and perhaps unrelated one:
https://bugzilla.gnome.org/show_bug.cgi?id=738497

I can think of two options to mitigate the situation:

1. Fix all corner-cases
2. Delay the caribou invocation in gnome-shell, until it is really needed

It's tempting to do 2, but probably 1 would be the right way.  What do
people think?  Any help would be appreciated.

Thanks,
--
Daiki Ueno
Magdalen Berns | 21 Oct 11:11 2014

Re: Some maintenance hints (Re: java-atk-wrapper 0.30.7)

Hi Alejandro,

Thanks for your email. With those two releases I was just going on what Ke Wang seemed to be doing and what I know of Semantic version control.[1] Also, I just wanted to make sure I had understood the technicalities of the correct procedure for releases rightly, after just having made 0.30.6, added the ChangeLog file and fixed a minor build bug. So essentially, I can see your point and I definitely won't be able to keep up that pace for releasing, (even if I wanted to)! :-).

In the long run I'll be keeping an eye on the other modules like at-spi2-atk to try to get a feel for what should trigger a release.

Kind regards,
Magdalen


_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel <at> gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

Gmane