On Mon, Mar 19, 2018 at 10:19 AM, Samuel Thibault
wrote:
> Hello,
>
> Samuel Thibault, on lun. 05 mars 2018 16:17:24 +0100, wrote:
> > Some dialog boxes use labels for static information, e.g. printer
> > status, replace result, etc. For the screen reader to properly
> > understand that, it shou
On Mon, Feb 26, 2018 at 5:49 AM, Samuel Thibault <
samuel.thiba...@ens-lyon.org> wrote:
> Hello,
>
> So, I also saw the removal of generic modules.
>
> Unfortunately we currently need it for implementing perfect zoom feature
> :)
>
> The context is that visual-impaired users need magnification of
On Mon, Mar 7, 2016 at 12:02 PM, Shaun McCance wrote:
> Will WebKit pick this up automatically, or should I teach Yelp to honor
> this setting?
I don't think webkit will pick this up automatically, no.
___
gnome-accessibility-devel mailing list
gnome-ac
Hi,
I've added a GTK+ setting in
https://git.gnome.org/browse/gtk+/commit/?id=c9371f6a185fe1fef1669ffb52a4c4964478042a
that turns on 'caret mode' deskop-wide. This was a longstanding
request from the accessibility team.
To make this really useful, we need an X setting to back this up,
which requi
On Mon, Nov 25, 2013 at 8:18 AM, Piñeiro wrote:
>
> As I've said to Joanie and API in Montreal, we probably need a
> privileged Wayland interface for ATs to obtain global information like the
> pointer position and the surface under the pointer. This will be needed to
> support some of orcas fun
Hey Magdalen,
thanks for bringing this discussion to the lists. I tried to read it all,
but failed somewhere in the middle... but I think what I've read so far is
enough to reply meaningfully.
> yeah I didn't see your mail until now. Sorry. Francesco and I haven't
> really talked about the futur
As part of the ongoing GNOME Wayland porting effort, the GNOME
accessibility (a11y) team has been looking into what it would take to make
our existing a11y tools (ATs) and infrastructure work under Wayland.
Most a11y features will probably end up being implemented in the
compositor:
- input tweak
On Tue, Oct 15, 2013 at 9:58 AM, Piñeiro wrote:
> The question is: Where (by whom) should this be implemented? We have some
> initial thoughts on this:
>
> 1. Application toolkits should implement atk_component_get_mdi_zorder()
> for non-top-level windows. This is because the existing API [1] ex
I've been asked to present my thoughts on accessibility in GNOME,
again. After some discussions and some playing with orca in GNOME
3.2.1, here's what I have come up with. Again, this is largely my
opinions, and not meant as an attack.
The current state of accessibility in GNOME
--
As another quick update:
Last weekend, I've completed the factory removal, and I have now
merged the a11y branch into master. There's of course a lot more work
to be done, but this is a nice first milestone.
Points of notice: the toolkit attribute has changed its value from
'gail' to 'gtk', and at
Another week gone by, time for another status update on the a11y branch of GTK+.
- We have more tests in tests/a11y:
* a tree-performance test that compares populating a large treeview
with / without accessibles
* a text test that checks most of the AtkText interface for labels,
entries and
No, there is no such plan in the short term. I was just trying to clarify
how things will fit together.
On Jun 20, 2011 8:59 AM, "Piñeiro" wrote:
> On 06/20/2011 06:18 AM, Matthias Clasen wrote:
>> I think we should probably give a quick status update.
>
> Thanks for th
I think we should probably give a quick status update.
In the last week, Benjamin and I have started to implement the outlined plan.
Achievements so far:
- Code has been moved from modules/other/gail to gtk/a11y
- Gail is no longer a module, but gets compiled into GTK+ proper. You
still need to
On Tue, Jun 7, 2011 at 11:08 AM, Piñeiro wrote:
>
> 4) Is also an awesome plan (proper shared libgailutil replacement).
A very quick-and-dirty sketch of this can be found in the drop-gail branch:
http://git.gnome.org/browse/gtk+/tree/gtk/gtkpango.h?h=drop-gail&id=0e11f6eb18bf75a0b4420dc60e57ad1
On Mon, Jun 6, 2011 at 11:17 AM, Piñeiro wrote:
>> I don't think we can treat that as a first step and hold off on doing
>> any other fixes until that migration is done. The migration is a
>> significant undertaking, and will not be finished for 3.2.
>
> Sorry, I didn't want to say that we shoul
On Sat, Jun 4, 2011 at 8:44 PM, Piñeiro wrote:
>
> About this specific case it is about improve the documention:
>
> http://developer.gnome.org/atk/stable/AtkObject.html#AtkObject--accessible-name
>
> Or something else?
Well, more than that, really.
We need to know for each widget what the prop
On Wed, Jun 1, 2011 at 7:48 PM, Piñeiro wrote:
> On 05/10/2011 04:28 PM, Benjamin Otte wrote:
> In fact, IMHO, some of the issues pointed by Benjamin would be solved by
> this [2] and the gail migration, but lets not talk about it. As I said,
> those are long term tasks, and the fact is that the
On Fri, May 13, 2011 at 12:15 PM, Piñeiro wrote:
> On 05/13/2011 05:47 PM, Piñeiro wrote:
>>
>> The magnifier requires it for focus-tracking. As I said Joseph was
>> planning
>> to try to use some at-spi functionalities on the gs magnifier. As right
>> now
>> at-spi2 python bindings are created wi
On Thu, May 12, 2011 at 5:25 AM, Piñeiro wrote:
> On 05/11/2011 02:57 PM, Benjamin Otte wrote:
>
> Well most of the paragraphs were already answered by Brian, but I would like
> to add a comment here.What concerns me a lot is that there is only very few
> applications
>
>> that actually make use o
On Wed, May 11, 2011 at 11:09 AM, Brian Cameron
wrote:
> Another example is that the ATK abstracts common characteristics of
> widgets in a way that is useful to AT programs. All widgets that deal
> with text (labels, entry fields, combo boxes, etc.) all implement the
> same AtkText interfaces,
I think we should come to a decision on this one.
Could my fellow release team members chime in here, maybe ?
My vote goes to removing the menuitems that rely on toolkit
accessibility (screenreader and onscreen keyboard), but keeping the
menu.
___
gnome-
On Mon, Mar 7, 2011 at 6:32 PM, William Jon McCann
wrote:
> No, it was agreed by many that we were not in a position where we can
> turn on a11y by default for 3.0. There is hopefully no debate at all
> over that. You can't have *Universal* Access without it. I am
> committed to providing true
On Mon, Mar 7, 2011 at 4:31 PM, William Jon McCann
wrote:
> Bottom line: universal access in the shell is a 3.2 feature - provided
> the work gets done to meet our minimum requirements of stability,
> performance, and design.
Also, this is the first time I ever hear universal access being
demote
On Mon, Mar 7, 2011 at 4:33 PM, Matthias Clasen
wrote:
> On Mon, Mar 7, 2011 at 4:31 PM, William Jon McCann
> wrote:
>
>
> And you get to make the rules for what is good enough for disabled
> users of GNOME ? I couldn't agree with this attitude more strongly.
And of cour
On Mon, Mar 7, 2011 at 4:31 PM, William Jon McCann
wrote:
>
>> I think we should make try to make things work as well as we can for
>> 3.0 and promise to do better for 3.2. And yes, that will mean making
>> compromises and accepting an on-screen keyboard that may not follow
>> the design vision
On Mon, Mar 7, 2011 at 2:25 PM, Owen Taylor wrote:
> So, basically, our options are:
>
> * Leave the menu completely as is, fix everything up as well as possible;
> this will mean that people testing GNOME 3 may have bad experiences
> with some of the options.
>
> * Remove the worst working
Hey,
I've spent some time yesterday working on the HighContrast.
LowContrast and Inverse themes. I thought I should post a quick note
about a11y themes in GNOME 3, so people know what things currently
work, what things don't, and where things live.
The Contrast control in the universal access pan
On Tue, Feb 22, 2011 at 4:55 AM, Li Yuan wrote:
> OK. I made a patch for GtkArrowAccessible. Do we want to open a bug
> to keep all the patches and review them one by one or just commit them
> first?
>
> I saw you remove "g_return*" calls, and also macros like "GAIL_IS_IMAGE".
> I am not sure why.
On Mon, Feb 21, 2011 at 11:18 PM, Li Yuan wrote:
> I think the plan makes sense. Just one question, what do we get from
> port GtkAccessible to use AtkGObjectAccessible?
> AtkGObjectAccessible's parent is AtkObject anyway. I thought
> AtkGObjectAccessible is designed for objects which are not GtkW
On Mon, Feb 21, 2011 at 2:18 PM, Piñeiro wrote:
> Like a bug per widget to move, or the work will be done just on this
> git branch?
I think just working on the branch is going to be more straightforward.
> If we move gail to gtk, why maintain the factories?
>
> Some people opposed to use the f
I've spent some time this weekend starting to explore how moving gail
implementations into gtk 1-by-1 will work in practice. I didn't get
very far (GtkWidget, GtkContainer and GtkImage), but the exercise
proves very useful for spotting all the things that should be
straightened out in the gail impl
On Thu, Feb 17, 2011 at 12:23 PM, Piñeiro wrote:
>
> So probably we could study that. Anyway, in the same way, right now I
> don't see how this would better that the option proposed by Matthias.
Oh, I think having the option of implementing the a11y interface in
the widget itself would be great
On Thu, Feb 17, 2011 at 11:55 AM, Piñeiro wrote:
> 1 of 4 is failing. Could you elaborate why this theorical points have
> "failed miserably"?
In my view, keeping the a11y implementation in their separate module
ghetto is a failure in terms of maintenance, performance, and
robustness. We just do
On Thu, Feb 17, 2011 at 11:22 AM, Piñeiro wrote:
>
> Ok, so you are proposing a change more deep that I thought.
>
> You are proposing to forget this "proxy" approach on the accessibility
> support. As far as I understand you are proposing to implement the ATK
> interfaces directly on GTK, so inst
On Thu, Feb 17, 2011 at 9:54 AM, Emmanuele Bassi wrote:
> On Thu, 2011-02-17 at 09:43 -0500, Matthias Clasen wrote:
>
>> The current state of affairs cannot be useful for anybody.
>
> let's also look at the state of Atk's API, and what's required to do to
>
On Thu, Feb 17, 2011 at 10:03 AM, Piñeiro wrote:
>
> Although move the gail implementation to gtk has his advantages, why
> this would be better that just fix them directly on gail? One of the
> big problems here is the lack of resources, so doing the move would
> add a extra work that could be u
Hey,
I've spent the last night poring through gail bugs and code, and came
to the conclusion that we need to face the tough reality that the
state of a11y in GTK+ is sadly declining. There were years old patches
in bugzilla which fix pretty obvious bugs; on top of that, I've fixed
at least one bu
On Tue, Oct 26, 2010 at 1:04 PM, Bastien Nocera wrote:
> On Tue, 2010-10-26 at 18:31 +0200, Piñeiro wrote:
>>
>> > The only big change is that enabling a11y in GSettings will now
>> change
>> > the GTK+ modules list on the fly. I'd expect quite a few bits of
>> code
>> > breaking if they monitor t
I may be missing something, but at-spi2-atk-0.1.5 doesn't build here.
There's a bunch of atk_is_foo calls in collection-adaptor.c which I
cannot find anywhere...
Matthias
___
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel@gnome.org
htt
Here is another observation, from looking at the code:
the atk-adaptor in at-spi2-atk inherited a horrible misfeature from
at-spi's atk-bridge: it uses atexit to do 'cleanup' at exit. This is
causing the most painful problems, see
https://bugzilla.redhat.com/show_bug.cgi?id=537843
As Owen eloque
Hey,
after months of ignoring the coming revolution in the a11y world, I've
finally sat and down and created initial packages of the at-spi2 stack
for Fedora last night [1], and wanted to share some
initial impressions I got from playing with them for a few minutes.
The good news first: I did get
On Thu, May 7, 2009 at 5:09 AM, Li Yuan wrote:
>>
>> Ok, I can explore that idea. Filed as
>> http://bugzilla.gnome.org/show_bug.cgi?id=581605
>> for now.
>>
>
> I think this is a good idea.
I had a look at it. Unfortunately, the entry icon api doesn't really
make this possible. We only have ico
On Wed, May 6, 2009 at 9:23 AM, Matthias Clasen
> In general, I think hypertext sounds about right. I think I got the
> keynav for this about right, similar to caret browsing in firefox.
>
I've now committed the links-in-labels work to GTK+ master.
There is a demo in gtk-demo,
Adding gnome-accessibility-devel back to the CC...
On Wed, May 6, 2009 at 10:15 AM, Eitan Isaacson wrote:
> There is the Firefox awesomebar, but I can't figure out how to activate
> the star/unstar and "subscribe to feed" functions through the keyboard.
> Does anybody?
Well, the action is 'Book
On Wed, May 6, 2009 at 4:39 AM, Eitan Isaacson wrote:
>
> Wow, it's an entry that does everything!
Indeed. I had toyed with the idea of codenaming 2.16 "big entry" ...
> The first question I have is, does it have keyboard support?
Not really. What kind of keyboard support would you envision, k
On Tue, May 5, 2009 at 4:32 PM, Willie Walker wrote:
> Hi Matthias:
>
> Many thanks for being proactive about accessibility. Do you have a small
> demo app that shows these new features?
Lets see, gtk-demo in GTK+ 2.16 has an example that covers many of the
entry icon features, under Entry > Se
GTK+ has been growing some new things lately:
* icons in entries
* scale marks
* links in labels (soon)
I'd appreciate some review of these from the a11y perspective, and
some advice on how we can make them work better with ATs.
These features have landed in GTK+ due to popular demand, so they
On Wed, 2008-05-07 at 12:35 -0400, Chuck Anderson wrote:
> I did notice that the text that Orca is reading is less than helpful.
> First of all, it says nothing at all when the login window is ready to
> be used. It doesn't start reading until I click something on the
> login widget. Second,
On Mon, 2008-05-05 at 14:34 -0500, George Kraft wrote:
>
> Perhaps someone could start a wiki at http://live.gnome.org/GAP/gestures
> and create three columns of what to start which which gestures. For
> example:
>
> =
> Action GNOME
Hey guys,
I've looked today at what it would take us to make the a11y tools that
were running on the login screen carry over into the session, and I'm
coming away somewhat disillusioned about the state of our a11y
support...
Here are some of the issues I found while quickly looking at the a11y
ta
(ccing Kjartan, since he did the last few gnome-canvas releases)
At the Gnome summit, Bill Haneman approached Owen and me again about
moving the a11y implementation from gail into GTK+. This was discussed a
number of times already, but it never happened. We hope to achieve a
number of things by th
On 7/26/06, Fernando Herrera <[EMAIL PROTECTED]> wrote:
> Humm I'm seeing a problem here. What about GNOME/GTK+ applications
> launched outside a gnome-session? (for example people using KDE).
>
> They won't get the gtk-modules XSETTING and then they won't be accesible at
> all.
>
> I guess that
On 7/25/06, Bill Haneman <[EMAIL PROTECTED]> wrote:
> A better solution would be to use an XSETTING for a11y instead of just a
> gconf key, so that apps could detect it w/o a gconf dependency. This
> has been discussed in the past and seems to me it would have been better
> than ripping the gnome_
On Mon, 2006-06-26 at 16:46 +0100, Bill Haneman wrote:
> > I also note that the icon view a11y implementation has been
> > broken for a long time. This code has been accepted into GTK+
> > under the premise that we would get help with maintaining it.
>
> I didn't know there was any a11y code in g
Are we serious about a11y ?
A few weeks ago, I asked about a11y gaps in new GTK+ feature,
but I never heard anything back, except from our QA people, who
try to use the a11y framework for automated testing.
So I finally sat down last night and wrote minimal a11y
support for GtkAssistant myself l
(cc'in g-a11y-devel)
On 5/8/06, Willie Walker <[EMAIL PROTECTED]> wrote:
Hi Mattias:
Thanks for thinking of a11y. We need more developers like you to take
this kind of proactive approach. :-)
Does the NEWS document for GTK+ 2.9.0 provide a complete list of the new
widgets and has gtk-demo (o
With GTK+ 2.9.0 out of the door, it would be great if people interested
in accessibility could check that the new widgets in GTK+ play nicely
with the a11y framework.
Thanks, Matthias
___
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel
At the request of Bill H. I have committed a "fix" for bug 337239
(immediate segfaults on x86_64), which made the segfaults go away
on x86_64. Unfortunately, as I have only now noticed, it makes the
same code segfault on i386...
At this point, I'm pretty much out of ideas and out of time to
dig fu
> > >
> I have vague memory that modules not getting arguments is intentional
> rather than an oversight ... that we discussed it at the point of the
> GOption switch and decided it was fundamentally busted and
> unsupportable.
>
> I may just be inventing that memory...
>
> Regards,
>
On 2/7/06, michael meeks <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2006-02-07 at 09:24 -0500, Matthias Clasen wrote:
> > > Unfortunately - the introduction of GOption clobbered all
> > > GtkModule
> > > argument passing; and ensures that no GtkModul
On 2/7/06, michael meeks <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> So - I've been chasing a rather interesting bug:
>
> "GNOME hangs on login with a11y enabled"
>
> Of course - clobbering the proximate cause: gnome-session activating
> vino-server synchronously wor
Is atk 1.9.0 an official release ?
It seems that is has neither been announced nor tagged in cvs, but
I do see tarballs...
Matthias
___
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel@gnome.org
http://mail.gnome.org/mailman/listinfo/gn
62 matches
Mail list logo
