Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Bill Haneman
Hi Chris: Zero-conf is of course the ideal, glad you've achieved it for SOK. I am hoping that by using Xevie (via at-spi-registryd - since Xevie only allows ONE client per session :-( and at-spi-registryd needs XEvie for its own purposes), we can change GOK so that the default out-of-the-box

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Olaf Jan Schmidt
[ Bill Haneman ] Olaf implied that there was a concern with XEvie interfering with the core pointer. No, I meant to say that interfering with the core pointer is the intended behaviour for most use cases of on-screen keyboards - but not for all. It is perfectly fine if you do not target those

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Bill Haneman
On Thu, 2006-08-17 at 11:40, Olaf Jan Schmidt wrote: [ Bill Haneman ] Olaf implied that there was a concern with XEvie interfering with the core pointer. No, I meant to say that interfering with the core pointer is the intended behaviour for most use cases of on-screen keyboards - but

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Olaf Jan Schmidt
[ Bill Haneman ] Actually, my point is that this affects ALL use cases of on-screen keyboards. I don't see why this should be the case. Imagine a case where an on-screen keyboard is used for entering text in another language - not as a keyboard replacement, and without need to work within

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Bill Haneman
On Thu, 2006-08-17 at 12:05, Olaf Jan Schmidt wrote: [ Bill Haneman ] Actually, my point is that this affects ALL use cases of on-screen keyboards. I don't see why this should be the case. Imagine a case where an on-screen keyboard is used for entering text in another language - not

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Bill Haneman
Hi Olaf: On Wed, 2006-08-16 at 21:23, Olaf Jan Schmidt wrote: [ Bill Haneman ] That strikes me as a surprising statement. Of course it depends on what you mean by partially sighted. The people I am familiar with for example have light allergy. Large bright areas on the screen hurts

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Willie Walker
Hi All: We need to choose a day for the meeting, and develop an agenda - please log in to the wiki and add your suggestions. If there's enough support for this idea, we can dedicate a room to it - it might be useful to nominate a chair person to maintain the wiki page and run the meeting.

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread invisible ink
quote who=Willie Walker I'm happy to volunteer to be chair for this meeting and have support from my management to spend time on it. Sweet, thanks Willie - no one else has stepped up, so it looks like you've got the gig! This is where my facilitation ends and yours begins. ;-) Let me know if I

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Henrik Nilsen Omma
Chris Jones wrote: Keyboard are primarily used as text input devices. Almost all other functions can be handled by the pointer input including the menus. If the menus are too small a target to hit one possible work around would be to increase the font size. I think we should start

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Aaron Leventhal
What is the exact day for it? I only see one day event here: http://live.gnome.org/Boston2006/AccessibilitySummit I want to try and have a Mozilla hack fest tacked on to it as well, for a few days of coding together. Anyone who works on Mozilla or on an AT hooking into Mozilla is invited --

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Willie Walker
Hey Aaron: I think this would be useful. From an OS platform standpoint, we're definitely lacking in compelling web accessibility. We all realize this and we all agreed earlier this year to center on Firefox 3 as our primary focus for web accessibility. You and the extended Firefox 3 teams

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Anna Marie Dirks
Hi Everyone, I have been working to setup various ATs to complement my usability lab, which is coincidentally about 200 meters from the Summit location. It would be fantastic to have you all over to the lab for a visit. I'd like to discuss the role of usability testing in the context of

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Bill Haneman
It's really great to have such broad interest in Accessibility at the Summit. I'd love to include the lab visit. I think it should be on a separate day, however, since it could take a lot of time and lead to rather wide-ranging discussions. Looks like our one day is already getting pretty full.

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Bill Haneman
On Thu, 2006-08-17 at 13:06, Willie Walker wrote: Hi All: We need to choose a day for the meeting, and develop an agenda - please log in to the wiki and add your suggestions. One think that I'd really like to present, and which fortunately I have extensive materials ready for, is a

Re: GNOME Accessibility Team Meeting @ Boston Summit?

2006-08-17 Thread Aaron Leventhal
I'm still unclear as to what day it actually is! Is it before or after the general Gnome summit? Anne, I would really enjoy visiting your lab. Bill's suggestion of a 2nd day works for me. - Aaron Bill Haneman wrote: It's really great to have such broad interest in Accessibility at the

Re: [Kde-accessibility] KDE Accessibility - sorry, off topic.

2006-08-17 Thread Peter Korn
Hi Chris, On 17/08/06, Bill Haneman [EMAIL PROTECTED] wrote: I think the 'simple' or 'common' cases you are thinking about are mostly text entry. For text entry you are right that the 'normal' use of the pointer (plus focus rejection logic) would work, but it would not work correctly