> I don't believe anything has been taped or put on line. I could post my
> slides if you are interested.
>
> Will
That would be appreciated. Would you put them at Scribd or is there a
better option?
--
Steven
___
gnome-accessibility-list mailing li
On 25 February 2010 01:21, Eitan Isaacson wrote:
> No promises, but note-to-self. We should tape our presentations at CSUN.
Related to that I'd like to do a couple of audio interviews for OSS
Watch and they would be on a liberal CC licence.
Certainly I'll be chasing Willie, Eitan and Joanie and a
No promises, but note-to-self. We should tape our presentations at CSUN.
On Wed, 2010-02-24 at 20:00 -0500, Willie Walker wrote:
> I don't believe anything has been taped or put on line. I could post my
> slides if you are interested.
>
> Will
>
> On Wed, 2010-02-24 at 11:39 -0500, Steven Edwar
I don't believe anything has been taped or put on line. I could post my
slides if you are interested.
Will
On Wed, 2010-02-24 at 11:39 -0500, Steven Edwards wrote:
> > I recently gave a 2 hour talk on GNOME and GNOME accessibility to the
> > computer science department at RPI. We also worked wi
> I recently gave a 2 hour talk on GNOME and GNOME accessibility to the
> computer science department at RPI. We also worked with the HFOSS folks
> at Trinity College in Connecticut to bring GNOME and GNOME accessibility
> into their open source program.
>
> Will
Are any of your recent talks vie
> The building blocks of all our code as simple as possible to use and add
> accessibility so it isn't a chore for developers. Let's face it the
> majority of designers don't even consider accessibility even when they
> have people who need it on the team.
A very cool thing about GNOME is that
On 23 February 2010 17:51, Tom Masterson wrote:
> The building blocks of all our code as simple as possible to use and add
> accessibility so it isn't a chore for developers. Let's face it the
> majority of designers don't even consider accessibility even when they have
> people who need it on th
One of the problems I see as both an advocate and a developer is that
making things accessible is not as easy as it should be at least in linux.
You have to consciously add code to make it work. I am far from being a
fan of Microsoft but one thing they did right with Visual Studio was to
put a
> Looks like you've had success already.
>
> http://mairin.wordpress.com/2010/02/23/painless-accessibility-tips-for-gnome-designers-and-developers/
I still need to read this and get back to Mo to make sure what I thought
I was saying (and what I thought was important) and what she heard are
the s
On 23 February 2010 17:21, Willie Walker wrote:
> Education is key. Part of why I saw so much value in going to the GNOME
> Usability Hackfest was to spread the word and get accessibility
> considerations as close to the design as possible. It also needs to be
> done in a positive way to make th
Shaun, you rock :-).
Thx for your work.
You can read in my previous mail that i was not sure if the distributors can
decide which rendering engine yelp should use.
The last time I checked ubuntu yelp wasn't accessible.
So I thought this will be the next stable yelp for gnome 2.30.
@Samuel:
Check
[[[apologies if this seems like it was written one paragraph at a time
with no flow -- it was written one paragraph at a time while try to pay
attention in a meeting]]]
Education is key. Part of why I saw so much value in going to the GNOME
Usability Hackfest was to spread the word and get access
On Tue, Feb 23, 2010 at 09:16:25AM -0600, Shaun McCance wrote:
> This is just not true. The Yelp you get from gnome.org is
> based on Gecko. There is an experimental webkit branch in
> git. There have never been any releases from that branch.
> Despite this, Debian (and therefore Ubuntu) decided
+1 - Shaun "gets it". You rock, Shaun.
On Tue, 2010-02-23 at 09:56 -0600, Bryen M Yunashko wrote:
> On Tue, 2010-02-23 at 15:51 +, Steve Lee wrote:
> > Sean It's fantastic to hear from developers who are committed to the
> > accessibility of their projects and consider it as part of their
> >
On Tue, 2010-02-23 at 15:51 +, Steve Lee wrote:
> Sean It's fantastic to hear from developers who are committed to the
> accessibility of their projects and consider it as part of their
> roadmap. Awesome.
>
> Steve Lee
I concur. What can we do to get others to learn from your example,
Sean
Sean It's fantastic to hear from developers who are committed to the
accessibility of their projects and consider it as part of their
roadmap. Awesome.
Steve Lee
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
http://mail.gno
Hi Shaun.
On Tue, 2010-02-23 at 09:16 -0600, Shaun McCance wrote:
[...]
> If there's more I can do, please let me know. But I'm one of
> the developers that's firmly committed to accessibility,
Indeed you are. And I, for one, happen to appreciate that tremendously.
Take care. And thanks.
--joa
On Tue, 2010-02-23 at 10:29 +0100, Halim Sahin wrote:
> Hi,
> Here are my notes on this topic:
> Sometimes I can understand the frustrations come up with
> gnome-accessibility.
>
> Let me give you an example:
> It seems that yelp uses now webkit instead of gecko, which is realy bad
> for a11y.
> I
On 23 February 2010 14:32, Bryen M Yunashko wrote:
> On Tue, 2010-02-23 at 09:24 -0500, Willie Walker wrote:
>> > I encourage you to get more involved - it is the best way to make a
>> > difference.
>>
>> +1 :-) We need a strong advocate on the release team.
>>
> Do we educate those in the a11y c
On Tue, Feb 23, 2010 at 06:15:42AM -0600, Kenny Hitt wrote:
> Can you point me to documentation on requirements for participating
> on the release team? I can read the list archives, but can't post since
> I'm not a member.
> I don't have any formal training in accessibility, just a life time of
>
On Tue, 2010-02-23 at 09:24 -0500, Willie Walker wrote:
> > I encourage you to get more involved - it is the best way to make a
> > difference.
>
> +1 :-) We need a strong advocate on the release team.
>
> Will
>
>
So how do we do this? Not just to ensure strong a11y advocacy on the
release
> I encourage you to get more involved - it is the best way to make a
> difference.
+1 :-) We need a strong advocate on the release team.
Will
___
gnome-accessibility-list mailing list
gnome-accessibility-list@gnome.org
http://mail.gnome.org/mailman/
Kenny:
Can you point me to documentation on requirements for participating
on the release team?
http://live.gnome.org/ReleasePlanning/
I can read the list archives, but can't post since I'm not a member.
You do need to subscribe to the mailing list in order to post messages
to the forum
Hi.
On Tue, Feb 23, 2010 at 04:22:04AM -0600, Brian Cameron wrote:
>
> Kenny/Eitan:
>
> On 02/20/10 11:46 PM, Kenny Hitt wrote:
> >I'm not sure I've made my point, but I'll send this and see the result.
> >I've tried to keep this nice and helpful when
> >what I really want is to destroy the mon
Kenny/Eitan:
On 02/20/10 11:46 PM, Kenny Hitt wrote:
I'm not sure I've made my point, but I'll send this and see the result. I've
tried to keep this nice and helpful when
what I really want is to destroy the monitor of everyone on the Gnome board.
If you had to
use the Gnome I amn forced to
Samuel Thibault wrote:
> Halim Sahin, le Tue 23 Feb 2010 10:29:55 +0100, a écrit :
> > Most of the reported problems are pulseaudio related since 2 years :-(.
>
> Did they get reported on the Orca bug tracker, or on the pulseaudio bug
> tracker?
As a further question, did anybody ever identify t
Halim Sahin wrote:
> Ok I am not sure if gecko can be selected by the distributors but such
> decisions will break a11y on many distros.
> Webkit a11y isn't ready for enduser and the main help browser should not
> use it since it's ready to use with orca.
My recollection is that accessibility was
Halim Sahin, le Tue 23 Feb 2010 10:29:55 +0100, a écrit :
> Most of the reported problems are pulseaudio related since 2 years :-(.
Did they get reported on the Orca bug tracker, or on the pulseaudio bug
tracker?
Samuel
___
gnome-accessibility-list mail
Hi,
Here are my notes on this topic:
Sometimes I can understand the frustrations come up with
gnome-accessibility.
Let me give you an example:
It seems that yelp uses now webkit instead of gecko, which is realy bad
for a11y.
I have read some mail in orca/ubuntu list about yelp saying that this
doe
On 23 February 2010 04:48, Jason White wrote:
> More automated testing to find regressions would also be valuable. This,
> naturally, would be easiest in projects that already have test suites - they
> just have to write test cases to cover the accessibility API.
Test suits like LDTP and Dogtail
Samuel Thibault wrote:
> Jason White, le Mon 22 Feb 2010 16:27:53 +1100, a écrit :
> > The decision process doesn't have the same top-down control structure
> > that a proprietary operating system vendor can exercise.
>
> Mmm, Even free software projects do have such top-down control
> structures
On Mon, 2010-02-22 at 14:49 -0600, Kenny Hitt wrote:
> Hi.
> On Mon, Feb 22, 2010 at 11:53:24AM +0100, Samuel Thibault wrote:
> > Mmm, Even free software projects do have such top-down control
> > structures. For instance in Debian you're not supposed to leave an
> > architecture apart when you pa
Hi.
On Mon, Feb 22, 2010 at 11:53:24AM +0100, Samuel Thibault wrote:
> Mmm, Even free software projects do have such top-down control
> structures. For instance in Debian you're not supposed to leave an
> architecture apart when you package an application, and critical bugs on
> them are release-c
Le lundi 22 février 2010, à 11:53 +0100, Samuel Thibault a écrit :
> - in glade, some automatic tests could be done: for instance, if a
> button doesn't have _any_ text attached to it, glade could warn the
> developper.
Is there a bug opened for this? :-)
Vincent
--
Les gens heureux ne sont
Jason White, le Mon 22 Feb 2010 16:27:53 +1100, a écrit :
> The decision process doesn't have the same top-down control structure
> that a proprietary operating system vendor can exercise.
Mmm, Even free software projects do have such top-down control
structures. For instance in Debian you're not
Nolan Darilek, le Sun 21 Feb 2010 22:58:43 -0600, a écrit :
> I'm curious to know what issues you're
> having with GNOME that make it so vastly difficult in your situation,
Maybe not "vastly", but in the case of gnome-terminal not working, that
drops the whole lot of console applications, which
Steve Lee wrote:
> On 22 February 2010 05:27, Jason White wrote:
> > If user interfaces, including the free software/open-source community, are
> > headed toward an era in which a descendant of what we today call a "Web
> > browser" becomes the desktop, then what would make most sense is a
> >
On 22 February 2010 05:27, Jason White wrote:
> I actually think Gnome accessibility efforts are remarkably successful, given
> the limited resources available and the nature of the problems that need to be
> solved.
+1000
> If user
> interfaces, including the free software/open-source community
Hi.
On Sun, Feb 21, 2010 at 11:39:44PM -0600, Nolan Darilek wrote:
>
> Interesting, gnome-terminal has always worked fine for me. I do get
> occasional odd breakage, but usually only on the level of annoyance,
> and likely due to me using edge versions of certain apps and
> libraries. I wonder if
Nolan Darilek wrote:
> Interesting, gnome-terminal has always worked fine for me. I do get
> occasional odd breakage, but usually only on the level of annoyance,
> and likely due to me using edge versions of certain apps and
> libraries. I wonder if it may be a distribution issue? I know that
>
On 02/21/2010 11:18 PM, Kenny Hitt wrote:
Second, I think it's a very gloomy, pessimistic and vague view. What
Since I was apparently wrong about Apple, there doesn't appear to be any good
examples of success. That's sad.
Sad, not necessarily. At least accessibility is being viewed m
Kenny Hitt wrote:
> Hi. In my view, Gnome accessibility will never succeed. It will sometimes
> get close, but will never make it all the way. I came to this conclusion
> after using Gnome versions from2.2 through 2.28. I've seen several
> occasions where a change in Gnome broke accessibility.
Hi.
On Sun, Feb 21, 2010 at 10:58:43PM -0600, Nolan Darilek wrote:
> On 02/20/2010 11:46 PM, Kenny Hitt wrote:
> >Hi. In my view, Gnome accessibility will never succeed. It will sometimes
> >get close, but will
> >never make it all the way.
> >...
> >In the Apple approach, apps are required to b
On 02/20/2010 11:46 PM, Kenny Hitt wrote:
Hi. In my view, Gnome accessibility will never succeed. It will sometimes get
close, but will
never make it all the way.
...
In the Apple approach, apps are required to be accessible before being included
in the operating system.
So they've fixe
Hi. In my view, Gnome accessibility will never succeed. It will sometimes get
close, but will
never make it all the way.
I came to this conclusion after using Gnome versions from2.2 through 2.28.
I've seen several occasions
where a change in Gnome broke accessibility. Combine that with the fa
45 matches
Mail list logo
