Hi Tristan,
The MVC pattern has been around a long time but your suggestion of
moving UI into its own process is quite intriguing. The marshalling of
data, and the need for a really tight response to user actions, are
going to be pain points I think. Still worth some real investigation.
Are you lo
ail server Alp -- really. Did you get the invites to join our
user agent ARIA implementor group calls? Apple showed up.
> From an advocacy point of view, David Bolter has some ideas on how we
> can increase the profile of web accessibility outside the Mozilla
> bubble which he'll be s
Hi Behdad,
Yes, ATK support is separate. My point is that a "Grade A" browser
should support Web2.0 accessibility. WebKit doesn't yet, so I'm raising
that as an issue.
cheers,
David
Behdad Esfahbod wrote:
> David Bolter wrote:
>
>> Well I think the eleph
Well I think the elephant in the room here is WAI-ARIA support for
accessible DHTML (i.e. accessible Web2.0 applications). Last I checked
this work is being done for WebKit by Apple engineers, and a Google
engineer. Although the Firefox accessibility hackers have trail blazed
this work and even pro
Frederic Peters wrote:
> Richard Hult wrote:
>
>
>>> WebKit/GTK+ is the new GTK+ port of the WebKit, an open-source web
>>> content engine that powers numerous applications such as web browsers,
>>> email clients, feed readers, web and text editors, and a whole lot
>>> more.
>>>
>> Was th
GNOME should be accessible "out of the box", and I'd enjoy being able to
tell people it is... so a big +1 from me.
cheers,
David
Willie Walker wrote:
Hi All:
I recently had a nice discussion with the release team about the
viability of enabling accessibility (i.e., the AT-SPI infrastructure)
Thanks for the quick metrics Mark, they are helpful.
Nice to see no extra CPU load... and RAM is cheap and users are
priceless, and we aren't talking about a lot of extra RAM it seems.
cheers,
David
Mark Doffman wrote:
Hi everyone,
Rob Taylor wrote:
Hmm, my take here is that the current AT-S
Tristan Van Berkom wrote:
On Thu, Jul 17, 2008 at 3:09 PM, Jonh Wendell <[EMAIL PROTECTED]> wrote:
Hi, folks.
This is just a warning about translator names in NEWS file:
You should get the translator name from the "Last Translator" field in
the .po file, not from po/Changelog. Sometimes the
Hi Alp,
You might also find Aaron Leventhal a valuable resource.
cheers,
David
Alp Toker wrote:
> Vincent Untz wrote:
>
>>> Accessibility
>>> =
>>>
>>> In the last few weeks we've started to look at formal accessibility
>>> support for document navigation and manipulation. The fi
ontent using normal means
>> (e.g., arrowing, page up/down, etc.) as well as text selection and
>> cut/copy/paste support.
>
> Scrolling read-only content and focus navigation are built-in,
> including the newly minted support for tabIndex.
>
>
> On Apr 16, 2008, at 7
Hi Alp,
Thanks very much for this detailed information. I have a couple of
questions inline regarding accessibility:
Alp Toker wrote:
> You may already have heard that the WebKit/GTK+ developers have been
> exploring options for a release cycle. Here I'm going to outline our
> plans in a littl
Hi Maciej,
Reposting with the correct URL...
Maciej Stachowiak wrote:
> 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:
>>>
>&g
Maciej Stachowiak wrote:
> 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
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
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 br
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
Hi Shaun,
A quick note about WebKit and ARIA inline below:
Shaun McCance wrote:
> On Thu, 2008-02-28 at 12:40 -0500, Willie Walker wrote:
>
>> 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
>> Beh
Hi Shaun,
Shaun McCance wrote:
> On Thu, 2008-02-28 at 08:18 -0500, Luis Villa wrote:
>
>> One followup, one other suggestion, one followup.
>> On Tue, Feb 26, 2008 at 2:49 PM, Luis Villa <[EMAIL PROTECTED]> wrote:
>>
>>> * "widgets": Vista, OSX, and KDE4 all have widgets/gadgets/Kthingie
Hi Benjamin.
Regarding #4 (compositing effects), please note this thread:
http://mail.gnome.org/archives/gnome-accessibility-list/2008-February/msg00066.html
We will soon be announcing a call for proposals for tasks such as this.
Perhaps you should monitor the gnome-accessibility list for a coup
To my mind, adding regression tests is like spending 1 hour to save 100.
Perhaps what we need is a regression test
evangelist/documentation/mentor? Will, I really appreciated your phone
call last year answering my questions about the Orca test harness. It
sounds like a really great setup, altho
"In app" was the wrong phrase actually but you know what I mean :)
D
David Bolter wrote:
> To add some worms... there are also the in app GUI testing frameworks,
> such as Windmill and Selenium (for browsers).
>
> cheers,
> David
>
> Willie Walker wrote:
>> H
To add some worms... there are also the in app GUI testing frameworks,
such as Windmill and Selenium (for browsers).
cheers,
David
Willie Walker wrote:
> 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 jus
+1
I'd like to have this discussion too; especially to include the onBoard
folks. (Some thoughts I've had around this:
http://mindforks.blogspot.com/2006/12/gok.html)
It has been hard to get new developer involvement in GOK; a large C
program that has seen many hands, but there have been contr
That was painful to read.
David
Peter Parente wrote:
> Hello all,
>
> Yesterday, IBM decided to change strategies with respect to GNOME
> accessibility:
>
> http://www-03.ibm.com/developerworks/blogs/page/schwer
>
> Under this new plan, IBM is no longer supporting development of LSR,
> Accercise
If it is indeed "very much more usable", then you have my vote as long
"usable" includes "accessible".
http://developer.gnome.org/projects/gap/
cheers,
David Bolter
Thomas Wood wrote:
> Dear Community,
>
> The gnome-control-center hackers have been hard
Willie Walker wrote:
> OK - I'll answer my own question - this approach doesn't seem to do what
> we want. In testing and testing with this, the problem is that some
> assistive technologies depend upon the existence and value of the key
> itself: if it's not enabled, they let the user know and th
Will,
Yes.
As we see more and more software consuming the at-spi interfaces (gui
testing tools, screen readers, on-screen keyboards, at-poke, gui event
loggers) it just makes sense to get as much testing coverage as
possible. Let's fix the bugs in the development releases.
cheers,
David
W
Hi I'm going to cross post to gnome-accessibility-devel as this is
somewhat high priority I think. We really need a response on how to
proceed to fix this one. Is this new API change going to stick? How
will GOK maintain compatability with new/old versions of libwnck?
(preprocessor directiv
28 matches
Mail list logo
