At some point, we need to investigate XInput2 and what it brings to the
table. For now, ignore that text and pay no attention to the man
behind the curtain. The DeviceEventController should behave properly
independent of what underlying method (e.g., GTK hooks, XEvIE, XInput2)
is used. Of co
Hi Francesco:
Thanks for your work!
Would it be possible to add checks to the code to make it either conditionally
compile/link for CORBA or D-Bus, or link against both and have it choose at
runtime?
Will
On Feb 9, 2010, at 4:52 AM, Francesco Fumanti wrote:
> Hi,
> Mousetweaks is an assisti
Hi:
Under the docs/doc-set directory, you will find some internals.{pdf,html} files
that provide an overall description of the internals. This document is a
little out of date, but the high level ideas are still much the same.
Also, under src/orca/acss.py, you will find a definition for an ACS
Hi Li, Mark:
Orca currently listens for object:children-changed events to determine when
applications are removed from the desktop. We could listen for
application-removed, though (I didn't know about this event).
Will
On Dec 17, 2009, at 9:34 PM, Li Yuan wrote:
> Hi Mark,
>
> Yes, for 3, p
Hi Halim:
GNOME 2.29.x is going to be unstable for some time as we go through the
migration to D-Bus. For now, assume you should only use it for testing
and not day-to-day work.
I believe the impact of the "check using PID to check that the
application using pyatspi does not call itself" mo
Hi All:
I need your help evaluating new modules for accessibility.
At http://live.gnome.org/TwoPointTwentynine/ExternalDependencies and
http://live.gnome.org/TwoPointTwentynine/Desktop you'll find a list of
modules being proposed for inclusion into GNOME 2.30. Some of these
modules may have
You explicitely named Firefox. But I assume that it applies also to the
other browsers? Or am I wrong?
Well...Firefox is currently the only browser that really supports the
AT-SPI. As the WebKit work progresses, then it too should support the
password role. Note also that some of this also b
Francesco Fumanti wrote:
GUI-based password entry fields *should* support the AT-SPI
ROLE_PASSWORD_TEXT role. If they don't, it's a bug in the application.
Does this also include the password entry fields in web pages?
It should. If it doesn't, it's a bug either in the web app for Firefox.
Hi Francesco:
GUI-based password entry fields *should* support the AT-SPI
ROLE_PASSWORD_TEXT role. If they don't, it's a bug in the application.
Prompts in the terminal are not easily detected as far as we've been
able to tell. If you can come up with something for them, I'd be
interested.
Andrés:
I'm not really sure of the utility of the ATK_STATE_ARMED state. The
only place I can think of right now might be enabling some sort of audio
cue (e.g., an ignited fuse sizzling away). We've not really ventured
into audio deeply, though.
Will
Andrés G. Aragoneses wrote:
Hi.
I ma
Hi Halim:
There is still some work to do to make at-spi2 work with assistive
technologies such as Orca. Without digging into the complete stack
trace below, I suspect you might be running into the reentrancy issue
that still needs to be resolved.
Discussions of the work remaining to be do
Hi Matthias:
Many thanks for being proactive about accessibility. Do you have a
small demo app that shows these new features?
Will
On 05/05/09 16:19, Matthias Clasen wrote:
GTK+ has been growing some new things lately:
* icons in entries
* scale marks
* links in labels (soon)
I'd apprec
Hi Sam:
Since the clipboard doesn't necessarily manifest itself as a visual GUI
object, it's not something that would be exposed via the AT-SPI.
Instead, you can interact with the clipboard using the standard GTK+
mechanisms. Here's the class in Python:
http://www.pygtk.org/pygtk2reference/
Sorry - the xsettings related bug is here:
http://bugzilla.gnome.org/show_bug.cgi?id=535827.
(Bugzilla was so slow today that I gave up waiting for it before I sent
the last message).
Will
On Apr 6, 2009, at 8:52 AM, Willie Walker wrote:
Hi Eitan:
The xsettings change was made late in the
Hi Eitan:
The xsettings change was made late in the 2.24 cycle, and the
associated gconf property is now what determines whether or not the
GTK+ a11y modules are loaded or not. To allow people to prevent a11y
from being activated, a couple changes were made to GAIL and the
bridge:
NO_GAIL:
I think tying the speech solution to a layer such as PulseAudio is a
mistake. Instead, the speech solution should be able to sit on top of
whatever audio solution is provided by the OS.
Will
Eitan Isaacson wrote:
Hi,
(note: practical suggestions follow philosophical contemplations)
Screen
Yeah Luke! Thanks so much. I look forward to reading your draft soon.
Will
Luke Yelavich wrote:
Hi all
As you all may be aware, there are plans to deprecate bonobo et al for GNOME
3.0. One area of GNOME's accessibility technology that is affected by this
deprecation is gnome-speech, which i
Hi Mark:
Nice writeup -- thanks for doing it. :-)
- The 'Collection' and 'StreamableContent' interfaces still need to be
implemented. Some code has been written but is currently not built and
has not been tested.
The Collection interface is indeed used by assistive technologies. When
it wo
Hi Samuel:
AT-SPI is undergoing a transition from CORBA to D-Bus, most likely for
GNOME 3.0. The work is being tracked here:
http://linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus
libcspi is one of the things that has yet to be done because the port
will require a fair amoun
To dismiss a menu, I *think* you should be able to synthesize an
"Escape" keypress/keyrelease.
Will
Quiring, Sam wrote:
Greetings,
Using AT-SPI accessible operations I can click on menus and submenus and
cause the drop-down menu to be exposed. If the last operation performed
is to click o
As far as I know, the cspi has not been marked for deprecation. The
framework which AT-SPI currently depends upon (e.g., Bonobo), however,
has and is why the work to move AT-SPI to D-Bus is being done.
Will
Quiring, Sam wrote:
Greetings,
I am having a problem reconciling Ariel Rios's email
Good luck!
Will
Quiring, Sam wrote:
Hi Will,
I'm not at liberty to say anything. Sorry.
-Sam
-Original Message-
From: william.wal...@sun.com [mailto:william.wal...@sun.com]
Sent: Thursday, February 12, 2009 11:57 AM
To: Quiring, Sam
Cc: gnome-accessibility-devel@gnome.org
Subject:
Heh - you haven't said much. :-) Are you saying you can and will give
back by way of source? If so, that will be great and I look forward to
your contributions.
Will
Quiring, Sam wrote:
I didn't say I could not give back by way of source.
-Original Message-
From: william.wal...@s
Hmm...if you cannot give back by the way of source code, perhaps you can
help the community by updating and improving the documentation? That
would be very useful.
Will
Quiring, Sam wrote:
Hi Will,
I get your questions. I'm not at liberty to say.
-Sam
-Original Message-
From: wil
Quiring, Sam wrote:
Is this documented somewhere?
It's kind of documented. The Accessibility_Accessible interface extends
the Bonobo::Unknown interface:
http://svn.gnome.org/svn/libbonobo/trunk/idl/Bonobo_Unknown.idl.
There's some ref counting docs here:
http://svn.gnome.org/svn/libbonobo
Hi Sam:
Is it the desire of open source software developers to only help open
source usages of the software?
For the open source culture, my general opinion is that the
accessibility community is very small with very few resources. This
leaves more room for cooperation than competition, and
PS - Are you ready to let the world know what your mystery project is
yet? A fear I have is that we may all be spending lots of time helping
you develop a proprietary product. That might be a bummer for us open
source folks.
Will
Quiring, Sam wrote:
Greetings,
My application uses AT-SPI
If I understand your question correctly, to be guaranteed equality
between separate events, you need to explicitly ref() the object.
Will
Quiring, Sam wrote:
Greetings,
My application uses AT-SPI to examine an application. Suppose the
target application has a check box on it. If the targe
Hmm...the orca-list might be the wrong place to have this discussion.
gnome-accessibility-devel (CC'd) might be better.
A Google search for "request_code 153 minor_code 3" yielded this page,
which seems to point fingers at the XEvIE extension:
http://archive.netbsd.se/?ml=xorg-team&a=2008-
Hi Michael:
Thanks for the response, and nice hearing from you. :-)
:-) I think Mark is advocating a position close to what I tend to think
is optimal. AFAICS there are not a vast number of accessibles on (or
near) the screen at any one time, and exposing them all allows for
extremely
Hi Mark:
The following is going to sound wishy-washy. The main thing is that
I'm on the fence about this and think we really need a good performance
analysis to determine which way to go. I'm CC'ing Michael Meeks for a
number of reasons and hope he can also provide some insight.
What w
Hi Jeff an everyone:
The AT-SPI/D-Bus work is being tracked at
http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus,
and it includes a plan to migrate CSPI to D-Bus.
IMO, doing this work in Python is a lot easier than doing it in C, so
that's why we're seeing more and m
Thanks! I opened a new bug for you:
http://bugzilla.gnome.org/show_bug.cgi?id=563173
Will
On Wed, 2008-12-03 at 14:21 -0500, Omair Majid wrote:
> This is a patch for the java-access-bridge in gnome
> (http://live.gnome.org/Java%20Access%20Bridge). Using a swing
> JTextField, if a user selects
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Nagappan A
Sent: Wednesday, November 19, 2008 1:23 PM
To: Willie Walker
Cc: gnome-accessibility-devel@gnome.org; Quiring, Sam
Subject: Re: [g-a-devel] Unknown CORBA exception?
Hi Will,
This happens in most of the Ubuntu / RHEL systems, some of
>
>
> ______
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Nagappan A
> Sent: Wednesday, November 19, 2008 1:23 PM
> To: Willie Walker
> Cc: gnome-accessibility-devel@gnome.o
Hi Sam:
I wonder if the application is misbehaving. Try looking at the desktop
via accerciser and see what it shows. In addition, in your code, try
printing the accessible name of each object as you get it. It might
provide some insight into which application might be the source of the
problem.
Hi Mike:
As was suggested by Li Yuan, the first view looks a lot like one of the
gtk-demo demos. In particular, the "Tree View"->"Tree Store" demo:
http://master.gnome.org/~wwalker/Screenshot-CardPlanningSheet.png
In accerciser, this shows up as a "tree table" with a very flat
hierarchy. T
sure you show off single switch scanning... and UI Grab...
> word completion... we can talk offline.
>
> cheers,
> davidb
> Dave Neary wrote:
> > Hi Willie,
> >
> > Willie Walker wrote:
> >
> >> http://master.gnome.org/~wwalker/dwell-click.avi
>
of what's available and not meant to be
instructional videos.
Will
On Thu, 2008-09-11 at 18:18 +0200, Dave Neary wrote:
> Hi there,
>
> Willie Walker wrote:
> > I think the idea of stock presentations and demos (something you
> > proposed earlier this year) is an awe
Ha...well...this is an area of delight and confusion, I think. There's
FOCUSABLE, ENABLED, and SENSITIVE.
If I understand them correctly:
1) SENSITIVE means whether it's grayed or not
2) ENABLED means that if you can interact with it, it will actually do
something (versus just being a button
Hi Mike:
I added a quick call to self.printAncestry(obj) in Orca's
default.py:presentTooltip method. It appears as though the tooltip is a
top level object with no parent and no relations. I might have expected
to see a RELATION_TOOLTIP_FOR relation, but we handle it gracefully in
Orca none
Hi Dave:
I think the idea of stock presentations and demos (something you
proposed earlier this year) is an awesome idea.
I need to ramp back up on this stuff soon as well since I will be doing
a few presentations in the coming months. I'm more than willing to put
my stuff under some sort o
Now that this bug has been fixed for 2.24, we may have gotten rid of one
of the last remaining barriers to enabling a11y by default:
http://bugzilla.gnome.org/show_bug.cgi?id=524263
Will
Peter Korn wrote:
> Hey Willie,
>
> Regarding #5 below - enabling accessibility on the desktop: I think
Hi All:
The ARIA live-region concept might be applicable here:
http://developer.mozilla.org/en/docs/AJAX:WAI_ARIA_Live_Regions
With respect to automatically reading static text, Orca has some code to
do this, and it does so in a number of places. We 'dialed down' the
aggressiveness of Orca's
I agree that things are a little confusing right now. I'm not sure I've
fully understood/appreciated the motivation for why things are the way
they currently are. This might be a good opportunity to clarify,
improve, or both. :-)
I think there are a bunch of different problems to think about:
Hi Andres:
From http://bugzilla.gnome.org/show_bug.cgi?id=169488#c28:
"I'll have to live on for at least 2.22, since we don't plan to do a gtk
release before next guadec."
Hope this helps,
Will
Andrés G. Aragoneses wrote:
> Hi all,
>
> I've just read this news:
>
> http://blogs.sun.com/wwa
Steve Lee wrote:
> On 17/12/2007, Willie Walker <[EMAIL PROTECTED]> wrote:
>> o Look at the role of the event source. Passing this along in the event
>> would prevent a round trip.
>
> Doesn't the EventDetails expansion cover this? It appears to be
> o
Hi All:
I still need to catch up on all this mail. It's all good stuff, and I'm
excited to see intelligent and cooperative conversation going on. In
the meantime...
>> Having said that, it'd be great to build an understanding of what
>> people do synchronously during event emission & can
Hi Carlos:
Unless the colorblind applet wants to use AT-SPI, it shouldn't need the
Accessibility typelib. I just took a cursory glance at the code, and it
seems as though loading the Accessibility typelib is not needed.
Unless the person doesn't have AT-SPI support installed in their
machine,
Hi Rob:
Though I helped create the Java accessibility API proper, I'm not quite
sure how the CORBA stuff is handled. I've only worked on a few bugs in
the java-access-bridge (see
http://svn.gnome.org/svn/java-access-bridge/trunk), it's still a slight
bit beyond me.
It's probably obvious, but
I definitely like the mockups -- nice work!
Regarding the mouse keys settings, one needs to take into consideration
that the target users of this are people with differing physical
abilities who may need finer control over the parameters. This might
possibly result in more knobs and dials, but
Hi Luke:
I'll be in the area (I live just over the border in New Hampshire) and
would be happy to come down for a day.
Will
Luke Yelavich wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all
> - From reading a summary of the recent Boston summit, I don't remember seeing
> anythi
It would probably also be good to carry the discussion on the
gnome-accessibility-devel or gnome-accessibility lists, too, since those
folks are going to be the ones most affected by the changes. ;-)
Will
Murray Cumming wrote:
> On Fri, 2007-10-12 at 18:08 +0200, Jens Granseuer wrote:
>
>>
ecially those that made it possible to have it demoed during that
> event.
>
>
> At 2:24 PM -0400 10/8/07, Willie Walker wrote:
>> We discussed MouseTweaks at the summit at think it definitely looks
>> like it provides great functionality for the intended users. Overall
perhaps the
server extension idea is not that important.
Thanks!
Will
PS - Your video really helped a lot with the understanding of why
MouseTweaks is important and useful.
Willie Walker wrote:
> Hi Francesco:
>
> No problem with replying late - I happen to be up late. :-) I took a
and useful
tool, and your recordmydesktop video demo of it was great.
I've added it to the agenda for today and will bring it up for discussion.
Thanks for the effort!
Will
Francesco Fumanti wrote:
> Hello,
>
>
> First of all, sorry for replying so late.
>
>
> At 3:2
Francesco:
If you know of anyone that might even be remotely related to MouseTweaks
and could talk about it (e.g., demo, use cases, remaining work, etc.),
I'd be
really happy to add it to the agenda for the accessibility summit.
I'd also like to hear more about onBoard and future plans for it.
Hi Luke:
First of all, I say "Hear, hear!" The audio windmill is something
people have been charging at for a long time. Users who rely upon
speech synthesis working correctly and integrating well with the rest of
their environment are among those that need reliable audio support most
critically
Hi All:
These have been a very busy 6 months for the Orca team. When I look
back on where we were 6 months ago, I'm amazed at how far we've come.
Thanks everyone for your support and contributions. Orca is truly a
community project and I feel lucky to be involved with it.
For the very brave of
Hi Michael:
From
http://mail.gnome.org/archives/gnome-accessibility-list/2007-June/msg0.html:
"Development on LSR as a screen reader for GNOME will cease."
Will
On Fri, 2007-09-14 at 11:11 +0200, Michael Zacherle wrote:
> Hi all,
>
> is there someone out still developing LSR, or is everybo
Hi All:
We had a really good GNOME Accessibility Summit last year where we got
to know each other and had some really good ideas with some good
positive follow through. As a result, we're going to do the
accessibility summit again this year on October 6th, with spillover to
October 7th if needed.
I'm not sure of the logistics of a phone in possibility. They ALWAYS
are very difficult when there are a large number of people in one room
and a few on the phone. In my experience, we can easily spend more time
with getting the call set up and "I can't hear you" problems than we do
actually bein
On Wed, 2007-08-29 at 15:14 -0300, Carlos Eduardo Rodrigues Diógenes
wrote:
> > * Eliminating the Bonobo dependency from accessibility stuff in GNOME.
> > Note that this doesn't necessarily equate to eliminating CORBA.
>
> I really have no idea how much impact this would cause. I learned only
>
Hi Carlos:
This is a very timely discussion to have since there are a bunch of
thoughts on many people's minds right now. These include the following:
* Eliminating the Bonobo dependency from accessibility stuff in GNOME.
Note that this doesn't necessarily equate to eliminating CORBA.
* Und
> I've more or less finished the Enhanced Zoom plugin for Compiz, and it
> is able to do much of what orca already does.
Yeah! Do you have a pointer for where I can grab an eZoom to play with
on Gutsy? In addition, do you have a user base that you've been working
with? I'd like to read the arch
The problem seems to be gone on the latest Gutsy version that I have, so
I assume it was fixed.
Will
On Fri, 2007-08-10 at 22:47 +0800, Li Yuan wrote:
> Don't know the logic in Python. They can't call function like
> g_thread_init?
>
> Li
>
>
> 2007/8/10,
There was a time where I think there was an underlying problem in pygtk.
If I recall correctly, merely doing an "import gtk" in python and
nothing else seemed to elicit this message. As such, there was little a
Python application could do to avoid this.
Will
On Fri, 2007-08-10 at 22:07 +0800, Li
e:
> Hello William,
>
> Am Dienstag, den 12.06.2007, 09:14 -0400 schrieb Willie Walker:
> > I say sticking with something that matches given patterns and names
> > might be a good thing. How about just pyatspi? Maybe just including it
> > with libatspi and not making i
Hi Daniel:
> Am Dienstag, den 12.06.2007, 07:42 -0400 schrieb Willie Walker:
> > http://live.gnome.org/GAP/PythonATSPI gives more information on these
> > bindings. A big difference between pyatspi and pyspi is that pyspi
> > requires the AT-SPI cspi layer (potentially to b
Hi:
http://live.gnome.org/GAP/PythonATSPI gives more information on these
bindings. A big difference between pyatspi and pyspi is that pyspi
requires the AT-SPI cspi layer (potentially to be deprecated) whereas
pyatspi doesn't.
Hope this helps,
Will
On Tue, 2007-06-12 at 11:55 +0200, Daniel
Hey All:
Just a couple comments...
I believe Speech2Text is using the Julius
(http://julius.sourceforge.jp/en_index.php?q=en/index.html) engine,
which seems to be a decent system geared towards dictation tasks.
An interesting and related project is VoxForge
(http://www.voxforge.org/), which is
Hey Pete:
> I see there is some interest on Bugzilla related to some recent
> patches for pyorbit that Gustavo Carneiro and I created. The fixes
> prevent live Java accessibles from acting and appearing as CORBA null
> objects. I'm posting links to the reports on the list for people who
> might be
> The current AT-SPI architecture with its CORBA dependency cannot be used by
> Qt
> applications for various technical reasons
My understanding is that it's not technical, but more philosophical.
Will
___
Gnome-accessibility-devel mailing list
Gnom
Hi:
There's some troubleshooting information for gnome-speech here:
http://live.gnome.org/Orca/GnomeSpeech
In addition, I'd recommend you migrate to Orca
(http://live.gnome.org/Orca) from Gnopernicus since Orca has replaced
Gnopernicus as the screen reader for GNOME as of GNOME 2.16.
Hope t
Per the instructions at http://live.gnome.org/MaintainersCorner, we have
created a new branch of Orca for GNOME 2.18.
Note to you wonderful translators who are still working away, I'm not
sure of the appropriate svn terminology to describe the revisions at the
time I made the branch. Here's t
fox paragraph or other element inside a
> webpage that is not interactive and compare it with an element that is
> interactive but currently grayed.
>
> Pete
>
> On 3/2/07, Willie Walker <[EMAIL PROTECTED]> wrote:
>> Thanks! These help. Let's focus on the SENSITIVE
Thanks! These help. Let's focus on the SENSITIVE state as a means to
do what you want. I verified all these examples using at-poke.
> 1) The user tabs to the Close button in the gedit settings dialog. In
> this case, we might say the name of the button, the role of the
> button, and the mnemon
Hi Peter:
> So how does Orca distinguish the case of some interactive widget being
> disabled from some widget that can never be enabled? Does Orca say
> disabled in both cases?
Can you enumerate some actual use cases? Concrete examples might make
this discussion easier.
Thanks!
Will
>> Of
I would prefer to remain with what gail does; I view it as the reference
implementation of the AT-SPI. Changing the behavior of an established
meaning and implementation to accommodate a difference in a new API for
a different platform (IAccessible2) seems odd to me. It also seems like
someth
Orca v2.17.92 is out (release announcement attached). We're getting
down to the last throes of GNOME 2.18, and there's a hard code freeze on
March 5th, which is one week from today.
If you can please test Orca v2.17.92 soon and get us feedback on really
really bad stuff (especially bad stuff
I'll vote that action names as they are exposed right now should not be
localized. If there is a desire to provide a localized form in the
future, new API should be introduced for the purposes of keeping
backwards compatibility.
Thanks!
Will
Steve Lee wrote:
> My response was more exposition
Hi Jatinder:
I'm not sure about Solaris 9 and Solaris 10, but you do get the
gnome-speech packages with the Solaris Express releases as of at least
build 55 (and maybe earlier): http://www.opensolaris.org/os/downloads/
Instead of Festival, the FreeTTS speech synthesis package and the
gnome-speec
cation from naming pundits if so
desired. ;-)
Will
On Fri, 2007-01-19 at 11:59 -0500, David Bolter wrote:
> Hi Will, I'm glad you are using your expertise here :-)
>
> FWIW I'm glad Aaron is kicking at the apple cart... we really should
> make sure it is solid.
>
>
Here's the Javadoc from AccessibleState in the Swing toolkit:
http://java.sun.com/j2se/1.4.2/docs/api/javax/accessibility/AccessibleState.html#ENABLED
If I recall correctly from when I helped define/write the Java
Accessibility API almost 10 years ago(!), it corresponds directly to the
value set
> So Orca does not care about STATE_ENABLED? In gok we accept either
> sensitive _or_ enabled as worthy of providing access to for our users.
> In gok we have to err on that side though... as we are a different
> animal (non-aquatic actually).
Well...just like you, we tend to look at both. T
ed for IA2.
>
> Can we think of concrete examples in GTK or other widget sets. Or are
> we trying to model something that may be theoretically possible but is
> never actually realised?
>
> Steve
>
> On 1/19/07, Willie Walker <[EMAIL PROTECTED]> wrote:
> > > >
> > I don't believe any of the users of IA2 or ATK or using STATE_SENSITIVE
> > to mean anything other than STATE_ENABLED.
> > For one, no one understands it. Second, it's not actually useful because
> > if somethings greyed out it should not react to user input. As David
> > Bolter says, the UI de
Hi:
This is a known problem in the unstable (i.e., 2.17.x) releases and has
hopefully been fixed for the upcoming 2.17.4 release.
Thanks!
Will
On Thu, 2006-12-07 at 14:22 +, Halim Sahin wrote:
> Hello,
> I noticed a bug in orca that affects the reading
> of some text in the flat reviewmode
> > Note that accessibility friendly distributions such as Ubuntu, however,
> > probably could choose to just always keep accessibility enabled in the
> > default schema.
> >
>
> Which would turn accessibility on by default for all users also in
> stable releases, right? I think we are still a
tributions such as Ubuntu, however,
probably could choose to just always keep accessibility enabled in the
default schema.
Will
On Mon, 2006-11-27 at 12:55 +0100, Henrik Nilsen Omma wrote:
> Willie Walker wrote:
> > FYI...this took some effort and some good teamwork, but accessibility is
FYI...this took some effort and some good teamwork, but accessibility is
now enabled in GNOME development releases by default. Yeah!
http://bugzilla.gnome.org/show_bug.cgi?id=362457
Will
___
Gnome-accessibility-devel mailing list
Gnome-accessibilit
Hi Henrik:
See also the following RFE that was opened as a result of the Boston
Summit: http://bugzilla.gnome.org/show_bug.cgi?id=362457
It's along the lines of enabling a11y by default, and the GNOME Boston
attendees seemed to be in majority opinion that this was a good thing to
do for developme
Hi Bill:
> Does the problem only happen when the mouse/pointer is near the blink
> cursor, or is the problem present even when the pointer is not close?
It seems to happen regardless of where the pointer is. :-(
Will
___
Gnome-accessibility-devel ma
Hi Aaron:
On Tue, 2006-10-03 at 10:52 -0400, Aaron Leventhal wrote:
> Here is the current plan for exposing selection in documents -- please
> let me know if there is a better way:
>
> 1. Any object which has any part in the document selection will have
> STATE_SELECTED, which will allow the co
Hi Luca:
The server file you're attempting to run is data for Bonobo activation
and is not intended to be run.
There's some information on debugging speech on this page:
http://live.gnome.org/Orca/GnomeSpeech
What happens when you run freetts-synthesis-driver?
Will
On Sun, 2006-09-24 at
t; Just in case anyone wonders, I'm not at all a bottleneck
> keeping better
> keyboard navigation out of Firefox. I recently gave
> ownership of that
> module over to Mozilla, because I'm too busy improving core
> accessibility API support to handle much else. That s
Hi Aaron:
Thanks for sending this on. Look like good work. In the keyboard
section, I notice there's a link to the following:
http://www.mozilla.org/support/firefox/keyboard
One thing that I think is very important to include is keyboard
traversal and caret navigation of the web content its
Hi Carlos:
I'm not sure I understand completely about where things are. Are you
able to:
0) Make sure no servers are running
1) Run your new server by hand from one window
2) Run test-speech and connect to your new server
If so, it seems like the bonobo activation stuff is at fault. You might
SynthesisDriver_Festival:proto0.3
> 3: OAFIID:GNOME_Speech_SynthesisDriver_Speech_Dispatcher:proto0.3
>
> but when i select the first appears this "Attempting to activate
> OAFIID:GNOME_Speech_SynthesisDriver_Loquendo:proto0.3.
> Server could not be initialized."
>
> What can i do?
>
> Best reg
Hi Olaf:
> I am getting the impression that the GNOME accessibility developers do not
> care about making it easier to implement interoperability with Qt and KDE,
> and would instead like push a libbonobo-based AT-SPI version into the LSB and
> make people believe that all full-featured assisti
1 - 100 of 112 matches
Mail list logo
