Le dimanche 23 août 2009 à 11:54 -0400, Willie Walker a écrit :
So...I'd like to appeal to the yelp developers to keep the accessible
solution turned on by default for 2.28 while we continue our work
towards WebKit a11y for GNOME 3.0.
Let me warn you that downstream, we are getting short
that accessibility is
a core value of GNOME.
Until WebKit a11y is sufficient to provide access to the GNOME apps that
will use it, I think we need to stick with the accessible solution for
now. In other words, I think we need to flip your statement above
around. That is, the GNOME modules will ship
developers to keep the accessible
solution turned on by default for 2.28 while we continue our work
towards WebKit a11y for GNOME 3.0.
Done. Yelp 2.28 will use Gecko.
Willie, I have a number of documentation-related things I'd
like to discuss with some accessibility experts. Two things
come
is a critical component of the
GNOME platform.
So...I'd like to appeal to the yelp developers to keep the accessible
solution turned on by default for 2.28 while we continue our work
towards WebKit a11y for GNOME 3.0.
Will
On Sat, 2009-08-22 at 23:22 +0100, Olivier Le Thanh Duong wrote:
On Thu, Aug 20
to the
platforms they came from.
In other words, access to documentation is a critical component of the
GNOME platform.
So...I'd like to appeal to the yelp developers to keep the accessible
solution turned on by default for 2.28 while we continue our work
towards WebKit a11y for GNOME 3.0.
Done. Yelp
On Thu, Aug 20, 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
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
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 plugin), empathy.
and will there be alternatives for people
On Thu, 2009-08-20 at 16:27 +0200, Andre Klapper 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.
Hi there. Yelp maintainer here. Who exactly decided to
use
Hey,
On Thu, 2009-08-20 at 09:21 -0500, Shaun McCance wrote:
Yelp will not be using WebKit for 2.28, but it will almost
certainly use it for 2.30/3.0, unless there are serious
problems we can't iron out. That includes accessibility
issues. Please keep us posted.
Is there any specific
I'll leave it to the Yelp maintainer to answer that question. But FWIW,
it took (what felt like) quite a while to have accessible help for the
GNOME desktop -- a topic which was regularly raised on the Orca users
list. Now we have it. I think it would be a shame to take this valuable
tool away
On Thu, 2009-08-20 at 11:44 -0300, Gustavo Noronha Silva wrote:
Hey,
On Thu, 2009-08-20 at 09:21 -0500, Shaun McCance wrote:
Yelp will not be using WebKit for 2.28, but it will almost
certainly use it for 2.30/3.0, unless there are serious
problems we can't iron out. That includes
Am Donnerstag, den 20.08.2009, 09:42 -0500 schrieb Shaun McCance:
On Thu, 2009-08-20 at 16:27 +0200, Andre Klapper wrote:
According to the jhbuild 2.28 moduleset:
devhelp, epiphany, seed, yelp.
Hi there. Yelp maintainer here. Who exactly decided to
use the webkit branch in that
Shaun McCance wrote:
This means that anybody running 2.27.x from jhbuild has
been unable to use the new Mallard stuff, which is the
single most noteworthy thing in Yelp 2.28.
The modulesets were using webkit for a while, as it was the easiest
way to get webkit support exposed, but switched
Am Donnerstag, den 20.08.2009, 09:50 -0500 schrieb Shaun McCance:
I was busy working on Mallard support for 2.28, and didn't
have time (or make time) to review the WebKit stuff. And
now I consider it to be way too late in the release cycle
for this kind of change.
I agree it's late in the
On Thu, 2009-08-20 at 09:50 -0500, Shaun McCance wrote:
I was busy working on Mallard support for 2.28, and didn't
have time (or make time) to review the WebKit stuff. And
now I consider it to be way too late in the release cycle
for this kind of change.
I can easily agree with that
On Thu, 2009-08-20 at 23:29 +0200, Josselin Mouette wrote:
Le jeudi 20 août 2009 à 09:50 -0500, Shaun McCance a écrit :
Is there any specific reasons why it will not use WebKit for 2.28? I
understand we have little time for real world testing, but it would be
useful to understand whether
Maciej Stachowiak wrote:
4) Accessibility. This is only implemented in the Mac port currently.
We are moving the core accessibility code to be cross-platform, which
should make it fairly straightforward to hook it up to ATK or other
accessibility APIs. Sometimes ARIA is mentioned
Do I remember plans to have a directory of accessible web apps?
Did it ever happen?
Steve
--
Steve Lee
--
Open Source Assistive Technology Software
web: fullmeasure.co.uk
blog: eduspaces.net/stevelee/weblog
___
desktop-devel-list mailing list
1. Using DHTML to create desktop UI's is here, today, now. It has
become very popular. Nonetheless, it is inaccessible because the
semantics of the markup is either wrong or neutral with respect to the
UI it is encoding. A specific example is where a div element can be a
menu, a menu item,
. ARIA is becoming a major component in any accessible
web application. It's not something in the distant future. It would be
premature to crown webkit as the GNOME engine for all purposes until
this is properly addressed. Nonetheless, for basic document viewing,
like Yelp, Webkit could be a good
I agree about the strong a11y foundation being the necessary start, but
WebKit might save work down the road by planning for ARIA now.
Victor, I don't understand your comment about the UI interaction model.
I think that affects things on the AT end but not so much how ARIA is
exposed via
We inject the ARIA markup and other enhancements as needed from
the core Reader product.
Most of these attributes are added at runtime, not in static
markup, since Reader is a very dynamic Web Application -- it's
*not* a document.
Also, in general, we will only emit ARIA markup to clients that
. It's not something in the distant future. It would be
premature to crown webkit as the GNOME engine for all purposes until
this is properly addressed. Nonetheless, for basic document viewing,
like Yelp, Webkit could be a good solution, providing it has accessible
structured document support
Hi Maciej,
Maciej Stachowiak wrote:
On Apr 1, 2008, at 3:44 PM, Maciej Stachowiak wrote:
On Apr 1, 2008, at 12:13 PM, David Bolter wrote:
Hi Maciej,
Thanks very much for providing this information. I have a brief
comment about your accessibility section below:
This wording Sometimes
On Apr 2, 2008, at 8:14 AM, David Bolter wrote:
Hi Maciej,
Maciej Stachowiak wrote:
On Apr 1, 2008, at 12:13 PM, David Bolter wrote:
Hi Maciej,
Thanks very much for providing this information. I have a brief
comment about your accessibility section below:
This wording Sometimes
On Apr 2, 2008, at 1:51 PM, T.V Raman wrote:
We inject the ARIA markup and other enhancements as needed from
the core Reader product.
Most of these attributes are added at runtime, not in static
markup, since Reader is a very dynamic Web Application -- it's
*not* a document.
Also, in
Hi Maciej,
Thanks very much for providing this information. I have a brief comment
about your accessibility section below:
Maciej Stachowiak wrote:
Hello GNOMErs,
Some of you may remember me from back in my GNOME development days.
These days I work on WebKit, an open source Web content
agree with David. ARIA is becoming a major component in any accessible
web application. It's not something in the distant future. It would be
premature to crown webkit as the GNOME engine for all purposes until
this is properly addressed. Nonetheless, for basic document viewing,
like Yelp, Webkit
On Apr 1, 2008, at 3:44 PM, Maciej Stachowiak wrote:
On Apr 1, 2008, at 12:13 PM, David Bolter wrote:
Hi Maciej,
Thanks very much for providing this information. I have a brief
comment about your accessibility section below:
This wording Sometimes ARIA is mentioned in the context of
30 matches
Mail list logo
