Hi Owen:
Many thanks to the GNOME Shell team for writing this and the WIKI page. It is
very promising to see accessibility included in the roadmap. I have a few
questions:
1) I believe accessibility should be a requirement for GNOME Shell for GNOME 3.
Does the presence of it in the roadmap
Hi Stormy:
Neat!
Do you (or someone) have specific examples of pages where this has been done?
For example, the URL of a page as well as a pointer to the source code behind
that URL that's maintained somewhere in git?
Thanks,
Will
On Jan 26, 2010, at 2:50 PM, Stormy Peters wrote:
Thanks
of some sort, but I'm not sure what to use.
Thanks!
Will
On Jan 26, 2010, at 4:24 PM, Stormy Peters wrote:
On Tue, Jan 26, 2010 at 2:01 PM, Willie Walker william.wal...@sun.com wrote:
Hi Stormy:
Neat!
Do you (or someone) have specific examples of pages where this has been done
(Hrm, I'm obviously late ;-))
:-)
As a potential solution, we can modify the AT-SPI/CORBA *.desktop
file to key off of a new gconf key,
/desktop/gnome/interface/at-spi-corba. The existing
/desktop/gnome/interface/accessibility key will be used everywhere
else as normal, but this new key will
Sorry for the late reply to this. I'm curious how closed captioning
and/or subtitles will be rolled into this. Do you video folks have any
thoughts?
I'm also curious if we might also want to consider some sort of gconf
setting that says give me closed captioning that any video player can
applet and the {Sticky/Slow}Keys feedback keyboard applet)
would need to be ported.
Will
On Mon, 2009-11-02 at 20:15 -0500, Willie Walker wrote:
Hi Owen:
Many thanks for making this a formal proposal for comments. I think we
all want to get behind GNOME Shell as a nice whiz-bang feature
FYI...regarding Memphis a11y...
Will
---BeginMessage---
On Mon, 2009-11-02 at 10:20 -0500, Willie Walker wrote:
External dependencies: gmime, vala, Memphis (for libchamplain), libdb
(already approved).
Memphis is quite unaccessible. It generates an opaque image from
OpenStreetMap data
Hi All:
Here's some really simple questions that all new module proposers should
be able to answer for accessibility (note that this applies to things
that expose a GUI). It's not an exhaustive analysis by any means, but
it will capture some of the most blatant failures. It's so simple,
Hi Owen:
Many thanks for making this a formal proposal for comments. I think we
all want to get behind GNOME Shell as a nice whiz-bang feature to make
people want to move to GNOME 3. With the magnification support going
into GNOME Shell, the accessibility team is also building in a
dependency
Thanks Shaun!
Epiphany and Evolution also both respond to F7 to enable
caret navigation. (And, by the way, though Yelp stores
this in GConf, it also responds to F7.) We're seeing
more and more applications use an HTML renderer for core
parts of their interfaces, such as Gwibber, and Empathy
Hi All:
We're slated to have the AT-SPI/D-Bus stuff in place for 2.29.2. Things
are chugging away and looking positive. I have some questions about
some approaches we are going to take and would like some opinions and
advice for how to do it better if your stomach is weakened by the
Due to others hardcoding the string atk-bridge in their code (e.g.,
Firefox and OOo), the GTK+ a11y module has to be named atk-bridge. We
could ask Firefox and OOo to not hardcode the name, but we'd end up in a
versioning hell with external apps not tied to the GNOME release schedule.
So, I'd
Alberto Ruiz wrote:
2009/10/21 Willie Walker william.wal...@sun.com:
Due to others hardcoding the string atk-bridge in their code (e.g.,
Firefox and OOo), the GTK+ a11y module has to be named atk-bridge. We
could ask Firefox and OOo to not hardcode the name, but we'd end up in a
versioning
Hi Andre:
Distros that think that webkit a11y is not good enough in 2.28 are
free to ship older module versions that do not depend on webkit, or
(better) put additional manpower on fixing the remaining webkit a11y
issues. ;-)
I hear you, but this seems to go against the idea that
the discussion to the
gnome-accessibility-list (while I'll do in a follow up).
Many many thanks for being supportive of accessibility. You rock.
Will
Shaun McCance wrote:
On Sun, 2009-08-23 at 11:54 -0400, Willie Walker wrote:
Thanks everyone! Based upon the responses, I think the gap that would
Hi All:
Immediately after releasing Orca v2.27.91 today, I branched Orca for
gnome-2-28. The gnome-2-28 branch will be used for the remainder of the
GNOME 2.28.x cycle and all new work will take place on master.
Thanks everyone!
Will
___
, 2009 at 3:27 PM, Andre Klapperak...@gmx.net wrote:
Am Donnerstag, den 20.08.2009, 08:40 -0400 schrieb Willie Walker:
Which projects are going to use it
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
And under suggests (no hard dependency):
anjuta (for devhelp
Hi All:
I'm trying to assess the impact WebKit a11y is going to have on GNOME
in 2.28.
Which projects are going to use it and will there be alternatives for
people to use Gecko-based technology if WebKit a11y isn't quite soup
yet for 2.28?
Note that this is not a slam on the very hard
, I'm confident that when that list of bugs
has been addressed I'll be able to implement support. My concern (again)
is discovering additional issues at that point and it being too close to
the 2.28 release to do anything about them.
--joanie
On Tue, 2009-07-14 at 09:43 -0400, Willie Walker wrote
Just to chime in here - based upon our experiences with Gecko,
accessibility support for browsers is no trivial task. Xan and Joanie
have been hammering away at an impressive pace so far.
Joanie, Xan - what do you think it would take to hit 2.28? Would more
people from the WebKit internals
Vincent Untz wrote:
Willie: do you have any idea when the a11y team would be able to give a
+1 for webkit? Being able to know it's okay as soon as possible would
definitely help us organize things.
I'm CC'ing Joanie, who'll be the person doing most of the work on the
assistive technology side
to
the help and support of Joanmarie and Willie Walker we have identified
many new issues that we have either already fixed or that we'll
continue working on. You can see the meta-bug recently opened by
Joanmarie to track all the forthcoming a11y progress here:
https://bugs.webkit.org/show_bug.cgi?id=25531
, if the response is overwhelming, should we
consider making separate BOFs?
Will
Willie Walker wrote:
I'm really excited about GNOME 3.0. There are a lot of great ideas that
people have come up with.
As people work on new GUI designs, I request that people engage the
GNOME accessibility team
For the accessibility portion, here's some strawman stuff that will be
solidified soon (I hope):
1) Luke Yelavich at Canonical is planning on looking at speech
dispatcher as a proposed replacement for gnome-speech. If he gets
support from his management to do the work and is successful at
I'm really excited about GNOME 3.0. There are a lot of great ideas
that people have come up with.
As people work on new GUI designs, I request that people engage the
GNOME accessibility team on their designs. Accessibility is a big
selling point for GNOME and I'd really hate to see it take
Hi All:
Orca has branched for gnome-2-26. The branches/gnome-2-26 branch will
be used for continued GNOME 2.26.x release and trunk will be used for
the GNOME 2.27.x release series.
Will
___
desktop-devel-list mailing list
Vincent Untz wrote:
Hi all,
Here's a list of modules that didn't see a release since quite some
time. It'd be nice to be sure that they either had no change at all, or
that someone rolls a tarball for 2.26.0 in 10 days.
Note that if there's no news for a module before March 16th, the release
Hi All:
The ditching of Bonobo goes beyond AT-SPI. It also has an impact on
gnome-speech and gnome-mag. This is a fair amount of work to pull off
and we currently have a dearth of resources to do the work.
We're not at the uh oh, we're completely screwed point yet, however.
The good thing
SPI_ methodsAccessible* methods
dasher 5 9
mousetweaks 7 22
gok 15 78
libcspi 29 230
A subset approach makes a lot of sense. I also wonder, however, if just
doing
+1 -- I'm very excited about this. Many thanks to the people involved
who have the energy and courage to pull this off.
Will
On Feb 10, 2009, at 8:48 AM, Luis Villa wrote:
On Tue, Feb 10, 2009 at 4:14 AM, Ara Pulido a...@ubuntu.com wrote:
Hello,
We are proud to announce that a new GNOME
Someone on the Orca list mentioned something about gnome.org having no
TXT record:
[etha...@moiraine ~]$ host -t txt gnome.org
gnome.org has no TXT record
I don't know what a TXT record is, so I'm not sure how that would help.
But, the user certainly seemed adamant that gnome.org
Believe me, if I had direct control over it, I'd hire Joanie in an
instant. She's an awesome contributor and is the type of person every
project needs.
Will
Joanmarie Diggs wrote:
For whatever it's worth:
Joanmarie Diggs works for Sun on accessibility (mostly Orca).
I happen to be a
Some ideas for better handling of notifications can be found here:
http://live.gnome.org/AlternativeNotificationsUI
it looks nice, but where would immediate-action-required notifications
be shown? Things like 'your battery is about to die'?
Stay-on-top, non-focus-stealing dialogues without any
Hi Alp:
I'm not sure what you think is being underestimated here. Instead of
throwing our hands in the air and despairing at the size of the task,
my company (Nuanti Ltd.) and I made the decision to make WebKit GTK+
accessibility happen early in 2008.
I'm certainly not throwing my hands up
For me, one of the most important problems we face with WebKit is its
lack of accessibility support right now. I have a great fear that Alp
may have grossly underestimated the scope of the work. I have some
confidence, however, that the WebKit folks who were at GNOME Boston
should be able to do
I would *love* to see this bug get fixed:
http://trac.galago-project.org/ticket/91
Will
On Thu, 2008-11-06 at 19:43 +0100, Cosimo Cecchi wrote:
On Thu, 2008-11-06 at 17:00 +0100, Vincent Untz wrote:
I'm more worried about the fact that there has been no release since
early 2007 (if I'm
hasty here. If we going to switch let's do it for the right reasons.
[1] https://developer.mozilla.org/en/ARIA_User_Agent_Implementors_Guide
cheers,
David
Willie Walker wrote:
For me, one of the most important problems we face with WebKit is its
lack of accessibility support right now. I
Hi Jeff:
My assumption is that http://live.gnome.org/RoadMap contains the plans
and that projects should add to this if they haven't created their road
maps yet.
Hope this helps,
Will
On Mon, 2008-11-03 at 17:57 +0800, Jeff Cai wrote:
Hi,
Could I get the information if not considering the
Hi All:
We just branched Orca for GNOME 2.24. I forgot to do this when we
released Orca v2.24.0 (D'Oh!). orca/branches/gnome-2-24 starts with
Orca v2.24.1, which was created today.
Will
___
desktop-devel-list mailing list
While I disagree with Brian's assessment (I think he tends to lean more
to the 'it's OK as long as an able-bodied sysadmin can configure the
system for the disabled user' side than the 'let the user be
independent' side), I'll support the decision nonetheless.
Will
Vincent Untz wrote:
Le
Brian Cameron wrote:
I'm not sure this is a really important regression. You can configure
the new GDM to always launch various AT programs as needed. The main
lost feature is that users cannot launch AT programs on demand.
I'm curious who the you is you can configure. The important thing
, à 17:23 -0400, Willie Walker a écrit :
Well...hmm...if I read the answers correctly, I think what I'm
hearing
is that there are a lot of great ideas, but they aren't done yet. If
this is the case, then I think this sounds like a regression.
I see nobody jumping in to say it's not a regression
without jumping through hoops.
Will
Vincent Untz wrote:
Le mercredi 10 septembre 2008, à 09:39 -0400, Willie Walker a écrit :
Hi:
I asked this earlier, but I might have missed the response. Have the
accessibility issues been resolved with the new GDM? In particular,
does accessible
Hi:
I know Jon McCann and company did some proactive work to include
accessibility in the redesign (thanks Jon!), but I'm not sure what the
status of that is. If they can show that accessible login works, along
with the keyboard/mouse/dwell gesturing mechanisms to launch assistive
Gestures are definitely a very good way to launch the assistive
technologies. The work Jon McCann and company are doing with
gnome-session and gdm should also make the gestures available in a
logged-in session as well.
Thanks!
Will
On Wed, 2008-08-06 at 17:29 +0200, Patryk Zawadzki wrote:
On
there, :-)
Will
Willie Walker wrote:
PS - Bug/RFE logged here:
http://bugzilla.gnome.org/show_bug.cgi?id=545849.
If there are other specific problems that people know about, I really
encourage them to log bugs. Otherwise, the team will likely not know
about them and they will likely go unfixed. The current
Yuan, is *very* good and is remarkable in his abilities
to diagnose and resolve problems.
Will
On Thu, 2008-07-31 at 17:56 -0400, Willie Walker wrote:
Wow - that polling really does bite. :-( Looks like it's been in there
for 6 years!
http://svn.gnome.org/viewvc/at-spi/trunk/registryd
Excellent discussion so far. I'm going to write up a summary shortly.
Just to clarify one thing, though, especially since this has come up
more than once (at least in e-mail to me):
The only downside I found when using GNOME with a11y enabled on my
system was that somehow the mousekeys were
there shouldn't be any created.
I've cc'd Mark Doffman for his imput as he's probably got the most
experience profiling current AT-SPI behaviour.
Rob
Willie Walker wrote:
The way accessibility support works is that GTK+ loads accessibility
modules (gail and atk-bridge) if it detects
Willie Walker wrote:
Excellent discussion so far. I'm going to write up a summary shortly.
Here's what I'm seeing from this good discussion:
PRIMARY ARGUMENTS AGAINST ENABLING A11Y BY DEFAULT:
---
1) Performance. From recent tests, it does
Wow - that polling really does bite. :-( Looks like it's been in there
for 6 years!
http://svn.gnome.org/viewvc/at-spi/trunk/registryd/deviceeventcontroller.c?revision=326view=markup
To me, it kind of seems rather inefficient for the prototypical use case
of mouse motion events, which is to
From Li Yuan regarding a11y:
Accessibility is a problem for conduit. The GUI is simple, but the
left tree view doesn't support keyboard navigation well. Also one has
to drag some items to the right sync area, there is no way to do this
by keyboard. And the sync area is not accessible. I
work.
Thanks again for your consideration for accessibility!
Will
John Stowers wrote:
On Wed, 2008-07-30 at 07:37 -0400, Willie Walker wrote:
From Li Yuan regarding a11y:
Accessibility is a problem for conduit. The GUI is simple, but the
left tree view doesn't support keyboard navigation well
Hi All:
I recently had a nice discussion with the release team about the
viability of enabling accessibility (i.e., the AT-SPI infrastructure) by
default for GNOME. As a result of that discussion, I'm approaching the
broader GNOME community with a proposal to do this. :-)
Accessibility
Alexander Jones wrote:
Isn't this a distro decision?
Ultimately, I guess the value for any gconf setting in
schemas/desktop_gnome_interface.schemas can be whatever a distro wants
it to be. What I'm proposing, however, is that the default value that
we choose for GNOME is that accessibility
on by
default: it's far easier for someone without a disability to turn it off
than it is for a person with a disability to turn it on.
Will
Mathias Hasselmann wrote:
Am Mittwoch, den 30.07.2008, 13:11 -0400 schrieb Willie Walker:
Alexander Jones wrote:
Isn't this a distro decision
Hi All:
I just want to send out a reminder to let you know GNOME Outreach
Program: Accessibility stuff is still underway and that there are still
tasks available: http://www.gnome.org/projects/outreach/a11y/.
We had some really good interest in the documentation task and Vincent
Alexander, a
Accessibility
=
In the last few weeks we've started to look at formal accessibility
support for document navigation and manipulation. The first WebCore
patches have landed and we intend to provide AT-SPI accessibility for
the 2.24 release. This is partly in response to requests
Hi All:
Just my 2 cents here:
I would definitely object to WebKit being the de facto rendering engine
if it did not support accessibility. In addition, as WebKit
accessibility work is done, I recommend looking at the existing AT-SPI
implementation done in Gecko as a potential model for how
I'm retitling this because I was just deleting GSOC mail -- my inbox is
flooding and I needed to do some drastic filtering. Many thanks to
Behdad for seeing this message and thinking of me. :-)
For HTML accessibility, the best support is provided by the Gecko engine
that's in Firefox 3.
(the accessible thing) about GNOME and its technology, is
ARIA the best approach to make dynamic web site accessible to GNOME
users? and how do I test those ARIA roles on GNOME?
On Thu, Feb 28, 2008 at 5:40 PM, Willie Walker[EMAIL PROTECTED] wrote:
I'm retitling this because I was just
Hi All:
With the release of Orca v2.21.92, we've branched Orca for GNOME 2.22.
The Orca v2.21.92 sources represent the beginning of the branch
(svn.gnome.org/svn/orca/branches/gnome-2-22).
Thanks everyone!
Will
___
desktop-devel-list mailing list
David Bolter wrote:
To my mind, adding regression tests is like spending 1 hour to save 100.
Definitely. :-) It also gives me piece of mind when a refactor is
done, and it never forgets those special cases that we sometimes forget
about when doing manual testing. You can also build them up
Hey All:
Just a quick note -- Eitan Isaacson and I have GNOME accessibility
articles published in the March 2008 Linux Journal. Mine is on Orca and
Eitan's is on Accerciser. This is exciting stuff to me because it helps
get our GNOME accessibility story out to a large range of mainstream
Hey All:
Great discussion so far. I just want to add something about why
regression testing is important to me. In the Orca project, we have a
regression test suite that we use regularly. It helps give us great
sanity checking that our changes and bug fixes don't introduce new
problems.
Hi All:
I might be opening a big can of worms with this question, and I
apologize if someone is already working in this space and I just don't
know it.
What is the automated testing strategy for GUIs in GNOME? Is there a
well defined way to create a 'make test' target and have it do the
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,
Carlos:
It's been a pleasure to work with you over the past year. Your work on
gnome-mag is greatly appreciated and we're going to miss your energy.
Do you have any maintainers in mind and/or ideas for where to take
gnome-mag? For example, thoughts about where we can fit things in the
space
Thanks Matthias!
I think the main thing to remember is that the settings may seem too
finely granular for people who don't have to use them. But, the
granularity allows the target user to fine tune their experience to get
the most effective experience and highest throughput.
Will
Matthias
to be
adjustable and what the numerical ranges should be.
Will
Calum Benson wrote:
On 1 Nov 2007, at 12:45, Willie Walker wrote:
Anyway, my main point is to ask real users about what tasks they
typically want to accomplish with mouse keys. Then, figure out the best
UI that provides the user
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,
we support the module proposal, though we also recommend working with
the GNOME
Hey All:
Just wanted to drop a note regarding the GNOME Boston Accessibility
Summit. Many thanks for letting us have the room to hammer away on
problems and planning, and many thanks to Owen Taylor for all the work
he did.
I think the GNOME Boston Accessibility Summit went very very well
, then 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
look
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:24 PM -0400 10/1/07, Willie Walker
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 Alex:
Thanks for sending out this call for input. :-)
Being able to reliably interact with the gnome-panel and its applets via
the keyboard alone would be a major boost to its usability.
Thanks again!
Will
On Mon, 2007-09-24 at 04:00 +0100, Alex Jones wrote:
Hi list
What do we want
Willie,
Le lundi 24 septembre 2007, à 10:01 -0400, Willie Walker a écrit :
Hi Alex:
Thanks for sending out this call for input. :-)
Being able to reliably interact with the gnome-panel and its applets via
the keyboard alone would be a major boost to its usability.
Care
this in
the earliest version possible since it is a small but fairly significant
fix.
The above is the opinion of Willie Walker and I with Li Yuan's consent.
Those two are not easy to me: the code changes seem okay, but I know
nothing about this code base so I can't know if it can have
Hi All:
The pychecker fixes from earlier this week were the result of us looking
hard at some impending Firefox changes. Thanks for letting us get those
in. :-) Now for the real problem...
We've been working with the Firefox team and the AT-SPI maintainers on
an approach to allow applications
We tested and tested and could not find any regressions. Thanks
everyone! Committed per the patch.
Will
On Thu, 2007-09-13 at 17:27 +0200, Frederic Crozat wrote:
Le jeudi 13 septembre 2007 à 17:06 +0200, Vincent Untz a écrit :
Le jeudi 13 septembre 2007, à 10:33 -0400, Willie Walker a écrit
Hi All:
In prepping for a different problem we're investigating with the Firefox
team, we've been running pychecker on the Orca sources.
We came across two serious problems. The first is that one of our
scripts (the one for nautilus) was importing a module that no longer
exists. The second
Thanks everyone! Committed the patch to exactly as it was given to you.
Will
On Wed, 2007-09-12 at 18:05 +0200, Vincent Untz wrote:
Le mercredi 12 septembre 2007, à 17:03 +0200, Frederic Crozat a écrit :
Le mercredi 12 septembre 2007 à 10:52 -0400, Willie Walker a écrit :
Hi All
Hi All:
Ever since we moved to SVN, I've really been missing the *checkout*
feature that we used to have with the old web interface to CVS. With
the *checkout* feature, I was able to maintain documentation in our CVS
module and just point people to the *checkout* path. For example:
Well now, how simple is that? I had been beating my head against the
wall for months trying to figure out the magical incantation only to
find it was too simple.
Thanks everyone!
Will
On Fri, 2007-08-24 at 10:19 -0700, Brad Taylor wrote:
I've not been able to figure the equivalent of this
Sorry to send this to desktop-devel, but I recall this error coming up
at a talk at GUADEC. Someone from the audience yelled THAT'S BEEN
FIXED!!!:
GThread-ERROR **: GThread system may only be initialized once.
aborting...
We have people pinging us on the Orca list about this,
I fully support the inclusion of accerciser. Members of the Orca team
have been using it with good success, and it's accessible to boot.
Furthermore, the maintainer(s) have migrated it to the new pyatspi
bindings, which alleviates any concerns I had.
Will
On Mon, 2007-07-30 at 23:09 +0200,
Hi All:
With the release of Orca v2.19.6, we've branched Orca for GNOME 2.20.
The Orca v2.19.6 sources represent the beginning of the branch
(svn.gnome.org/svn/orca/branches/gnome-2-20), and we will soon be
starting some aggressive refactoring work on the trunk.
Between now and the release of
Hi All:
At CSUN in March, Peter Parente and I sat down to talk about a unified
Python wrapper for the AT-SPI: http://live.gnome.org/GAP/PythonATSPI
The main goals were:
* To create a single Python wrapper for AT-SPI reusable across all
Python assistive technologies and test tools for
Quick question: How hard would it be for you (as project maintainers)
to make a list of major user-oriented changes in your module (since
the last stable release) and send it to gnome-doc-list by feature
freeze? This would include things like changes to the interface, new
features and how
Pete - I see that the accerciser module still uses a *.zip file of code
zipped up from LSR. This seems a little strange to me. For GNOME 2.20,
I think it is important to get rid of this *.zip file and migrate to the
new 'official' Python bindings for AT-SPI that you and I are working on
for
.
Thanks!
Will
On 4/3/07, Willie Walker [EMAIL PROTECTED] wrote:
Pete - I see that the accerciser module still uses a *.zip file of code
zipped up from LSR. This seems a little strange to me. For GNOME 2.20,
I think it is important to get rid of this *.zip file and migrate to the
new
Hi:
Making it accessible would be rather nice too... it hasn't worked well
with high contrast themes for years[1], and I'm guessing screenreaders
can't do much with it either.
Thanks for bringing this up, Calum! Orca definitely has issues with it:
Hi Claudio:
Categories=GNOME;GTK;Utility;Accessibility;
Hm, that's because of the 'Utility' category. If you remove it, orca
will appear only under the Accessibility menu. Don't know why dasher
uses both, though.
Thanks! With this line, things end up looking good:
Hi:
I need a little hand-holding on this one for Orca. :-( Orca
(http://live.gnome.org/Orca) is a screen reader for people with visual
impairments. When I build/install Orca from SVN on Ubuntu using the
existing orca desktop file, it ends up in the
Applications-Accessibility menu.
I
Sure and:
Rich Burridge
Joanmarie Diggs
Lynn Monsanto
Thanks!
Will
Bill Haneman wrote:
Hi Vincent:
I've never been included in the Gnome contributors' list. I reckon it's
about time!
Bill Haneman
also
Carlos Eduardo Rodrigues Di\xf3genes
Li Yuan
Harry Lu
David Bolter
Padraig
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
, Willie Walker wrote:
Hi All:
This has festered for a little bit without further comment, so I'd like
to poke it one more time to try to get this in for the GNOME 2.17.2
tarballs. Please speak up if you disagree and/or don't like the
proposed patch (and you have a constructive alternative
://bugzilla.gnome.org/show_bug.cgi?id=362457
Thanks!
Will
On Sat, 2006-10-14 at 19:18 -0400, Willie Walker wrote:
Hi All:
As part of the GNOME Boston 2006 Accessibility Summit, and as part of
the larger GNOME testing discussions, we would like to propose that
accessibility is enabled by default
be able to work up a patch that does the right thing? It
might save us a lot of time.
Thanks!
Will
On Tue, 2006-10-17 at 08:48 +0200, Alexander Larsson wrote:
On Mon, 2006-10-16 at 14:20 -0400, Willie Walker wrote:
I'm not sure I understand the question, but you can manually get and set
the key
a11y by setting the key to False. I hope
this addresses the concern you raised.
Will
On Mon, 2006-10-16 at 13:10 +0200, Alexander Larsson wrote:
On Sun, 2006-10-15 at 20:32 -0400, Willie Walker wrote:
I'd say that the best way to do this is like the code for G_DEBUG,
just check gnome version
1 - 100 of 115 matches
Mail list logo
