Re: visual impairment focused design
You can do that, of course. Same threhold concern applies, however. You'll find yourself responsible for AT-SPI/ATK support vs. inheriting it from a widget toolkit. You might want to be aware, for instance, that gtk3 is not that popular among Linux gui users. Evidence is the level of preference for Mate. Looking at the environments created by blind user specific spins like Vinux and Sonar would be instructive. Basically, the wider industry turned its back on end users first when IBM pulled out of Linux desktop development in 2006, and then when Oracle bought out Sun. The remaining players have been willing to let development slide, by and large. A few brave souls are keeping the basics going by continuing to maintain AT-SPI/ATK and Webkit support. If I've misrepresented a11y support on current Linux/Unix desktops, I'm sure others on list will correct my characterizations. I'm quite confident there's more to say about that. Janina Michal Koudelka writes: > Yes, I realize now it was not a wise choice of subject, sorry about that. > > I do not plan to make this an html5 app, I plan to use gtk3. At this moment > I did some very primitive prototyping using javascript and gjs but when I > start with real coding I will probably switch to vala or c#. > > 2016-11-26 2:44 GMT+01:00 Janina Sajka <jan...@rednote.net>: > > > Michal Koudelka writes: > > > The applications primary designed to fulfil needs of a specific person > > and > > > relatively small group of people. Of course it's supposed to be > > opensource > > > and available, but I admit that target group is quite specific > > > > > So, you're now saying your original post is overly broad? Should we be > > changing the Subject: line of this thread? > > > > > The requirements and specification are definitely not final, we are > > working > > > on possible user scenarios and so far I made only few ui prototypes in > > gjs > > > and I am trying to avoid of future issues, that's why I am exploring the > > > possibilities of gnome accessible technologies first. > > > > > > OK. For GNOME specifically, you need to use a toolkit that supports > > AT-SPI/ATK. Do anything else, and you're rolling your own for sure. > > > > I'm unaware whether any flavor of GNOME Javascript supports AT-SPI, or > > not. That's your threshold question if you're limiting yourself to this > > language. Webkit support is a great start, but insufficient, imo. > > > > Janina > > > > > > > > > > I want app to be usable on linux or other free unix like systems ;) Mac > > or > > > Win clone is not intention of mine. > > > > > > Thank you for input, any suggestions are more then welcomed ;) > > > > > > Michael > > > > > > 2016-11-26 0:17 GMT+01:00 Janina Sajka <jan...@rednote.net>: > > > > > > > Michal Koudelka writes: > > > > > I need to make an application which is not just supposed to be > > accessible > > > > > but designed specifically for people with visual impairment so it > > should > > > > > rely heavily on using speech synthesiser and braille refreshable > > display. > > > > > > > > > > > > > Your conclusion does not follow from your premise. This is illogical, > > > > i.e. you cannot assume that "people with visual impairment" all, or > > even > > > > predominently use either braille or screen reader technology. Some do, > > > > but it's actually a minority of users with visual impairments. There > > are > > > > far many more individuals who use their remaining vision with some kind > > > > of screen magnification, or even simply display attribute control. > > > > > > > > I strongly suggest your revisit the user scenarios and requirements of > > > > your application with your vendor. And, while doing so, you should > > > > explore why you actually need to control UI at this level. Why is > > > > following W3C guidance, specifically WCAG 2.0 and using ARIA 1.1 is > > > > insufficient. Perhaps you can answer this already, but it's not clear > > to > > > > me from your post that you've explored this. Frankly, I'm suspecting a > > > > beginner's mistake here, which would serve neither your vendor nor your > > > > userbase. > > > > > > > > Also, are you writing exclusively for Linux? Or, are you unsure of how > > > > to handle Linux in a cross-platform application? If the latter, all the > > > > more reason to a
Re: visual impairment focused design
Michal Koudelka writes: > The applications primary designed to fulfil needs of a specific person and > relatively small group of people. Of course it's supposed to be opensource > and available, but I admit that target group is quite specific > So, you're now saying your original post is overly broad? Should we be changing the Subject: line of this thread? > The requirements and specification are definitely not final, we are working > on possible user scenarios and so far I made only few ui prototypes in gjs > and I am trying to avoid of future issues, that's why I am exploring the > possibilities of gnome accessible technologies first. OK. For GNOME specifically, you need to use a toolkit that supports AT-SPI/ATK. Do anything else, and you're rolling your own for sure. I'm unaware whether any flavor of GNOME Javascript supports AT-SPI, or not. That's your threshold question if you're limiting yourself to this language. Webkit support is a great start, but insufficient, imo. Janina > > I want app to be usable on linux or other free unix like systems ;) Mac or > Win clone is not intention of mine. > > Thank you for input, any suggestions are more then welcomed ;) > > Michael > > 2016-11-26 0:17 GMT+01:00 Janina Sajka <jan...@rednote.net>: > > > Michal Koudelka writes: > > > I need to make an application which is not just supposed to be accessible > > > but designed specifically for people with visual impairment so it should > > > rely heavily on using speech synthesiser and braille refreshable display. > > > > > > > Your conclusion does not follow from your premise. This is illogical, > > i.e. you cannot assume that "people with visual impairment" all, or even > > predominently use either braille or screen reader technology. Some do, > > but it's actually a minority of users with visual impairments. There are > > far many more individuals who use their remaining vision with some kind > > of screen magnification, or even simply display attribute control. > > > > I strongly suggest your revisit the user scenarios and requirements of > > your application with your vendor. And, while doing so, you should > > explore why you actually need to control UI at this level. Why is > > following W3C guidance, specifically WCAG 2.0 and using ARIA 1.1 is > > insufficient. Perhaps you can answer this already, but it's not clear to > > me from your post that you've explored this. Frankly, I'm suspecting a > > beginner's mistake here, which would serve neither your vendor nor your > > userbase. > > > > Also, are you writing exclusively for Linux? Or, are you unsure of how > > to handle Linux in a cross-platform application? If the latter, all the > > more reason to answer the questions above persuasively. The > > W3C specs mentioned are carefully designed to support cross platform > > content delivery and interaction. In the case of ARIA, they're even > > reliably testable. > > > > Tip: You might want to look at the latest draft of the ARIA Authoring > > Practices Guide: > > http://www.w3.org/TR/wai-aria-practices/ > > > > > > I know I'm sounding critical, but I hope I'm actually helping you by > > better defining your problem and refining your focus appropriately. Good > > luck! We certainly do want more coders to be fluent with supporting a11y > > in their apps appropriately. > > > > Janina > > > > -- > > > > Janina Sajka, Phone: +1.443.300.2200 > > sip:jan...@asterisk.rednote.net > > Email: jan...@rednote.net > > > > Linux Foundation Fellow > > Executive Chair, Accessibility Workgroup: http://a11y.org > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > > Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa > > > > -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: visual impairment focused design
Michal Koudelka writes: > I need to make an application which is not just supposed to be accessible > but designed specifically for people with visual impairment so it should > rely heavily on using speech synthesiser and braille refreshable display. > Your conclusion does not follow from your premise. This is illogical, i.e. you cannot assume that "people with visual impairment" all, or even predominently use either braille or screen reader technology. Some do, but it's actually a minority of users with visual impairments. There are far many more individuals who use their remaining vision with some kind of screen magnification, or even simply display attribute control. I strongly suggest your revisit the user scenarios and requirements of your application with your vendor. And, while doing so, you should explore why you actually need to control UI at this level. Why is following W3C guidance, specifically WCAG 2.0 and using ARIA 1.1 is insufficient. Perhaps you can answer this already, but it's not clear to me from your post that you've explored this. Frankly, I'm suspecting a beginner's mistake here, which would serve neither your vendor nor your userbase. Also, are you writing exclusively for Linux? Or, are you unsure of how to handle Linux in a cross-platform application? If the latter, all the more reason to answer the questions above persuasively. The W3C specs mentioned are carefully designed to support cross platform content delivery and interaction. In the case of ARIA, they're even reliably testable. Tip: You might want to look at the latest draft of the ARIA Authoring Practices Guide: http://www.w3.org/TR/wai-aria-practices/ I know I'm sounding critical, but I hope I'm actually helping you by better defining your problem and refining your focus appropriately. Good luck! We certainly do want more coders to be fluent with supporting a11y in their apps appropriately. Janina -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: apps no longer accessible using gnome and orca
John: I just deleted another post on this topic from you, and then I relized I had a thought to share ... If I remember what you wrote correctly, apps are launching, but Orca doesn't appear to be getting the news. That really sounds like an issue with the AT-SPI bridge. Was that recently updated? Also, could you perhaps use lsof to chase down this problem? John Covici writes: > I have such a thing, but its just a directory, but maybe I could sort > on the time -- I will check. > > On Sat, 15 Oct 2016 19:45:42 -0400, > Janina Sajka wrote: > > > > Do you have a log of what was updated in cronological order? Working > > backwards might be one way to go. > > > > > > John Covici writes: > > > Down version of what? Gnome has many items, I can't just say go to > > > earlier version of gnome. Anyone have any ideas? > > > > > > On Sat, 15 Oct 2016 15:24:49 -0400, > > > Janina Sajka wrote: > > > > > > > > e.g. downversion > > > > > > > > John Covici writes: > > > > > Unrolling what exactly? If its not window manager what might it be? > > > > > > > > > > On Sat, 15 Oct 2016 14:06:56 -0400, > > > > > Janina Sajka wrote: > > > > > > > > > > > > I understand the attraction of gentoo. Why not get a custom build, > > > > > > with > > > > > > just the apps you want, and no more? Sounds cool--until important > > > > > > things > > > > > > break, at which point you're left with both pieces. > > > > > > > > > > > > I'm sorry, I have no gentoo specific understanding to offer. I can > > > > > > suggest some of the ordinary approaches available on other distros, > > > > > > such > > > > > > as unrolling to earlier versions until things again work. Yes, that > > > > > > can > > > > > > be very tedious, but isn't that part of the gentoo bargain? > > > > > > > > > > > > Maybe there are other gentoo users here who can validate your > > > > > > experience, or indicate their current success. But, gentoo users > > > > > > are so > > > > > > few and far between because of the high upfront cost of running > > > > > > gentoo. > > > > > > > > > > > > I know I'm being a bummer, John. But, I feel I've known you via > > > > > > these > > > > > > lists for long enough, that I'm willing to endure your ire. So, > > > > > > what is > > > > > > gentoo's recommended strategy for such situations? After all, > > > > > > breakage > > > > > > is surely inevitable in any human enterprise, including Linux. > > > > > > > > > > > > Janina > > > > > > > > > > > > John Covici writes: > > > > > > > Hi. I am using the gentoo distribution and its gnome overlay and > > > > > > > for > > > > > > > the last period (maybe a month or two) I find that no apps are > > > > > > > accessible using the orca screen reader. The apps actually run as > > > > > > > verified with eyeballs, but orca does not see them. I am running > > > > > > > the > > > > > > > latest accessibility framework from git as of about 4 days ago. > > > > > > > Apparently, orca is not receiving the window activate event and > > > > > > > it was > > > > > > > suggested to me that it might be the window manager. I am using > > > > > > > mutter 3.20.3, downgraded to 3.20.2, but no joy. > > > > > > > > > > > > > > Thanks in advance for any suggestions. > > > > > > > > > > > > > > -- > > > > > > > Your life is like a penny. You're going to lose it. The > > > > > > > question is: > > > > > > > How do > > > > > > > you spend it? > > > > > > > > > > > > > > John Covici > > > > > > > cov...@ccs.covici.com > > > > > > > ___ > > > > > > > gnome-accessibility-list mailing list > > > > > > > gnome-accessibility-list@gnome.org > > > &g
Re: apps no longer accessible using gnome and orca
The problem is that you don't know until you actually find the reason. I had a similar circumstance just a few weeks ago with my Asterisk server. I ran a standard upgrade of my Fedora server which put in 196 updated files--this after three weeks. Well, my Asterisk stopped working. It took me a week to figure out that I could no longer rely just on UDP, that I now needed to have it listen for TCP as well. I'm still uncertain which of the 196 updated apps pushed me into that, because it wasn't an Asterisk update that did it. Good luck, by the way. I hope you figure things out faster than I did with my phones. Except for my cell, I had no phones for the iterim. It was nasty. Janina John Covici writes: > I have such a thing, but its just a directory, but maybe I could sort > on the time -- I will check. > > On Sat, 15 Oct 2016 19:45:42 -0400, > Janina Sajka wrote: > > > > Do you have a log of what was updated in cronological order? Working > > backwards might be one way to go. > > > > > > John Covici writes: > > > Down version of what? Gnome has many items, I can't just say go to > > > earlier version of gnome. Anyone have any ideas? > > > > > > On Sat, 15 Oct 2016 15:24:49 -0400, > > > Janina Sajka wrote: > > > > > > > > e.g. downversion > > > > > > > > John Covici writes: > > > > > Unrolling what exactly? If its not window manager what might it be? > > > > > > > > > > On Sat, 15 Oct 2016 14:06:56 -0400, > > > > > Janina Sajka wrote: > > > > > > > > > > > > I understand the attraction of gentoo. Why not get a custom build, > > > > > > with > > > > > > just the apps you want, and no more? Sounds cool--until important > > > > > > things > > > > > > break, at which point you're left with both pieces. > > > > > > > > > > > > I'm sorry, I have no gentoo specific understanding to offer. I can > > > > > > suggest some of the ordinary approaches available on other distros, > > > > > > such > > > > > > as unrolling to earlier versions until things again work. Yes, that > > > > > > can > > > > > > be very tedious, but isn't that part of the gentoo bargain? > > > > > > > > > > > > Maybe there are other gentoo users here who can validate your > > > > > > experience, or indicate their current success. But, gentoo users > > > > > > are so > > > > > > few and far between because of the high upfront cost of running > > > > > > gentoo. > > > > > > > > > > > > I know I'm being a bummer, John. But, I feel I've known you via > > > > > > these > > > > > > lists for long enough, that I'm willing to endure your ire. So, > > > > > > what is > > > > > > gentoo's recommended strategy for such situations? After all, > > > > > > breakage > > > > > > is surely inevitable in any human enterprise, including Linux. > > > > > > > > > > > > Janina > > > > > > > > > > > > John Covici writes: > > > > > > > Hi. I am using the gentoo distribution and its gnome overlay and > > > > > > > for > > > > > > > the last period (maybe a month or two) I find that no apps are > > > > > > > accessible using the orca screen reader. The apps actually run as > > > > > > > verified with eyeballs, but orca does not see them. I am running > > > > > > > the > > > > > > > latest accessibility framework from git as of about 4 days ago. > > > > > > > Apparently, orca is not receiving the window activate event and > > > > > > > it was > > > > > > > suggested to me that it might be the window manager. I am using > > > > > > > mutter 3.20.3, downgraded to 3.20.2, but no joy. > > > > > > > > > > > > > > Thanks in advance for any suggestions. > > > > > > > > > > > > > > -- > > > > > > > Your life is like a penny. You're going to lose it. The > > > > > > > question is: > > > > > > > How do > > > > > > > you spend it? > > > > > > > > > > > > > >
Re: apps no longer accessible using gnome and orca
e.g. downversion John Covici writes: > Unrolling what exactly? If its not window manager what might it be? > > On Sat, 15 Oct 2016 14:06:56 -0400, > Janina Sajka wrote: > > > > I understand the attraction of gentoo. Why not get a custom build, with > > just the apps you want, and no more? Sounds cool--until important things > > break, at which point you're left with both pieces. > > > > I'm sorry, I have no gentoo specific understanding to offer. I can > > suggest some of the ordinary approaches available on other distros, such > > as unrolling to earlier versions until things again work. Yes, that can > > be very tedious, but isn't that part of the gentoo bargain? > > > > Maybe there are other gentoo users here who can validate your > > experience, or indicate their current success. But, gentoo users are so > > few and far between because of the high upfront cost of running gentoo. > > > > I know I'm being a bummer, John. But, I feel I've known you via these > > lists for long enough, that I'm willing to endure your ire. So, what is > > gentoo's recommended strategy for such situations? After all, breakage > > is surely inevitable in any human enterprise, including Linux. > > > > Janina > > > > John Covici writes: > > > Hi. I am using the gentoo distribution and its gnome overlay and for > > > the last period (maybe a month or two) I find that no apps are > > > accessible using the orca screen reader. The apps actually run as > > > verified with eyeballs, but orca does not see them. I am running the > > > latest accessibility framework from git as of about 4 days ago. > > > Apparently, orca is not receiving the window activate event and it was > > > suggested to me that it might be the window manager. I am using > > > mutter 3.20.3, downgraded to 3.20.2, but no joy. > > > > > > Thanks in advance for any suggestions. > > > > > > -- > > > Your life is like a penny. You're going to lose it. The question is: > > > How do > > > you spend it? > > > > > > John Covici > > > cov...@ccs.covici.com > > > ___ > > > gnome-accessibility-list mailing list > > > gnome-accessibility-list@gnome.org > > > https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > > > > -- > > > > Janina Sajka, Phone: +1.443.300.2200 > > sip:jan...@asterisk.rednote.net > > Email: jan...@rednote.net > > > > Linux Foundation Fellow > > Executive Chair, Accessibility Workgroup: http://a11y.org > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > > Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa > > > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectureshttp://www.w3.org/wai/apa ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: fedora 10 live cd
Chad: You're actually most of the way there. You need to start Orca by hand, by issuing the command 'orca' . Here's what to do: 1.) After you say 'y' to restart Gnome, waith a long time for the automated login to happen and the desktop to load. You'll not get audio feedback during this process, unfortunately. 2.) Press Alt+F2 to bring up the 'run command' dialog. You should hear the cd rom get accessed as this program will load from your cd rom. You can further confirm that it's loaded by pressing backspace. If, and only if, you hear your computer beep when you press backspace, go on to ... 3.) Type the word orca and press --enter-- . hth Janina Shaun McCance writes: On Wed, 2009-03-04 at 07:05 -0500, chad wrote: Hi i'm totally blind and i tried the fedora 10 live cd but having problems. I set up orca and it said accessability for gnome has just been enabled you need to log out and log in for the change to take effect. I pressed y for yes and i'm stuck can't log back in. Where does it bring you and is the password linux on the live cd? Hi Chad, You'll probably have better luck asking on gnome-accessibility-list. I've CC'd that list with your question. Accessibility folks, please CC Chad on responses. -- Shaun ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.; sip:jan...@capitalaccessibility.com Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: fedora 10 live cd
Hi Will and All: Let me ask this here before I take this issue to the Fedora Live CD list, where I'm also subscribed ... Booting the Fedora Live CD, one can launch orca from an Alt+F2 dialog, but this is the orca setup that requires gnome restart. My experience with it is that it talks as one would expect--if it talks, a question of audio driver support, I suppose. However, after gnome restarts, the user must again issue Alt+F2 and restart orca by hand. My experience is that, if the setup process works, one can successfully run the Fedora Live image with orca. But it seems unfortunate to have to reissue the Alt+F2 command. Shouldn't orca simply start on gnome restart? Is this a Fedora bug? Or a GNOME bug? I'm particularly interested as SpeakupModified.Org is looking at enhancing the Fedora Live image expressly for Orca mediated Fedora installations. Janina Willie Walker writes: Hi Chad: You might need to press Return to make the logout happen. It sounds like what might be happening is that a logout dialog is appearing and it's inaccessible because accessibility has not been enabled for the desktop to happen. Pressing Return should activate the OK button of this dialog. When all else fails, you can give the desktop the 3 finger salute: Ctrl+Alt+Backspace. This will kill the X server and take you back to the login screen. Will Shaun McCance wrote: On Wed, 2009-03-04 at 07:05 -0500, chad wrote: Hi i'm totally blind and i tried the fedora 10 live cd but having problems. I set up orca and it said accessability for gnome has just been enabled you need to log out and log in for the change to take effect. I pressed y for yes and i'm stuck can't log back in. Where does it bring you and is the password linux on the live cd? Hi Chad, You'll probably have better luck asking on gnome-accessibility-list. I've CC'd that list with your question. Accessibility folks, please CC Chad on responses. -- Shaun ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.; sip:jan...@capitalaccessibility.com Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility jan...@a11y.org Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Accessibility with numpad/arrowkeys
Hi, Bryen writes: On a related note: Where can I get a list of other Xorg keycombos to do these neat tricks (sans crash)? The soon to be Linux Foundation standard is specified at: http://a11y.org/kafs Janina -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Mouse scroll wheel/button and hand dexterity
Steve Lee writes: 2008/7/30 Janina Sajka [EMAIL PROTECTED]: We probably need to do better integrating the various customizations available. We also need to expand our existing specs where functionality is missing. The Open A11y group has finished a Keyboard I/O spec which goes only so far as what is in Xkb. Perhaps this is one use case for a future rev of the spec. I agree that this should be addressed in the interests of filling one of the gaps current provision and rounding out support. However this is largely an issue with *mouse* use so would that spec make a good home without a rename? Probably not. Also, I'm loathe to open a spec for one feature alone. There must be other use cases and issues that we've not covered. These we should actively collect to see where we need to work. I will bring this up on next Tuesday's Open A11y call to discover whether people think RFEs like this one belong on the existing Keyboard bugs Wiki, or a separate new Wiki for open issues. Either way, we can certainly use Open A11y resources at the Linux Foundation to start collecting these kinds of requests. Janina Steve -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Nokia to fund D-Bus based accessibility
Thanks, David. However, I must set the record straight. This one was all Rob. My efforts in Nokia were well behind him. Janina David Bolter writes: Janina, it is all so awesomely cool. Thanks for all your efforts behind the scenes. cheers, David Janina Sajka wrote: This truly is wonderful news. I personally can't wait to take some of those KDE apps for a spin with Orca, and I expect there will be KDE based AT that will now be able to do the same with Gnome, Open Office, and Firefox. But, there's one more aspect of this I wanted to mention. Will notes that AT-SPI on Dbus will give us the opportunity to add accessibility to small and embedded devices--cell phones, pdas, etc. During the recently concluded Linux Foundation Collaboration Summit we heard an estimate from IDC that Linux will drive approximately 50% of all such devices by 2012. So, we may be on the verge of an explosion of accessibility opportunities. And, to top it all off, KDE and QT get the benefit of AT-SPI based realtime automated testing, just like Dogtail and LDTP are doing via the current Corba based AT-SPI. How awesomely cool is that? Janina Willie Walker writes: This is indeed awesome news for the community, and it's great to see that the people who did the AT-SPI/DBus feasibility study are the ones that will be doing the work. Some of the major impacts of this work include: 1) Releasing accessibility from the shackles of the out-of-style CORBA/Bonobo technology and into the hip with-it DBus space. 2) Unifying accessibility infrastructure across KDE and GNOME, paving the way for users to be able to use one assistive technology to be used to access both desktops. 3) By shedding CORBA/Bonobo, it helps enable accessibility solutions to migrate to the small device and embedded space. All very exciting stuff! Will JGJones wrote: I came across this on Planet Gnome and thought it would be of interest if no-one heard of. Apologises if you all already know this and I'm a bit slow on the uptake :-) http://blog.floopily.org/2008/04/23/nokia-funds-d-bus-based-accessibility/ ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Nokia to fund D-Bus based accessibility
May I suggest we take an upcoming Open A11y teleconference to discuss how best to engage the community as this migration moves forward? What do you think? I suspect we have topics to consider: * What apps need to be rewritten that will not be covered by * CodeThink, e.g. gnome-speech, py-atspi, what else? How do we * move these in parallel? * How to test on small devices--Marc's offer sounds valuable as an * embedded test platform at the very least that can take us toward * a11y on small and embedded devices. If you don't know his Icon device, look at http://levelstar.com * How can we use this work to expand the community of a11y * developers in Gnome, KDE, Linux, etc.? Thoughts? The calendar is open at the moment. Janina Marc Mulcahy writes: Let's integrate it into the Icon. We'll do what we can to get that effort rolling. Marc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Janina Sajka Sent: Friday, April 25, 2008 9:41 AM To: Willie Walker Cc: gnome-accessibility-list@gnome.org Subject: Re: Nokia to fund D-Bus based accessibility This truly is wonderful news. I personally can't wait to take some of those KDE apps for a spin with Orca, and I expect there will be KDE based AT that will now be able to do the same with Gnome, Open Office, and Firefox. But, there's one more aspect of this I wanted to mention. Will notes that AT-SPI on Dbus will give us the opportunity to add accessibility to small and embedded devices--cell phones, pdas, etc. During the recently concluded Linux Foundation Collaboration Summit we heard an estimate from IDC that Linux will drive approximately 50% of all such devices by 2012. So, we may be on the verge of an explosion of accessibility opportunities. And, to top it all off, KDE and QT get the benefit of AT-SPI based realtime automated testing, just like Dogtail and LDTP are doing via the current Corba based AT-SPI. How awesomely cool is that? Janina Willie Walker writes: This is indeed awesome news for the community, and it's great to see that the people who did the AT-SPI/DBus feasibility study are the ones that will be doing the work. Some of the major impacts of this work include: 1) Releasing accessibility from the shackles of the out-of-style CORBA/Bonobo technology and into the hip with-it DBus space. 2) Unifying accessibility infrastructure across KDE and GNOME, paving the way for users to be able to use one assistive technology to be used to access both desktops. 3) By shedding CORBA/Bonobo, it helps enable accessibility solutions to migrate to the small device and embedded space. All very exciting stuff! Will JGJones wrote: I came across this on Planet Gnome and thought it would be of interest if no-one heard of. Apologises if you all already know this and I'm a bit slow on the uptake :-) http://blog.floopily.org/2008/04/23/nokia-funds-d-bus-based-accessib ility/ ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Nokia to fund D-Bus based accessibility
This truly is wonderful news. I personally can't wait to take some of those KDE apps for a spin with Orca, and I expect there will be KDE based AT that will now be able to do the same with Gnome, Open Office, and Firefox. But, there's one more aspect of this I wanted to mention. Will notes that AT-SPI on Dbus will give us the opportunity to add accessibility to small and embedded devices--cell phones, pdas, etc. During the recently concluded Linux Foundation Collaboration Summit we heard an estimate from IDC that Linux will drive approximately 50% of all such devices by 2012. So, we may be on the verge of an explosion of accessibility opportunities. And, to top it all off, KDE and QT get the benefit of AT-SPI based realtime automated testing, just like Dogtail and LDTP are doing via the current Corba based AT-SPI. How awesomely cool is that? Janina Willie Walker writes: This is indeed awesome news for the community, and it's great to see that the people who did the AT-SPI/DBus feasibility study are the ones that will be doing the work. Some of the major impacts of this work include: 1) Releasing accessibility from the shackles of the out-of-style CORBA/Bonobo technology and into the hip with-it DBus space. 2) Unifying accessibility infrastructure across KDE and GNOME, paving the way for users to be able to use one assistive technology to be used to access both desktops. 3) By shedding CORBA/Bonobo, it helps enable accessibility solutions to migrate to the small device and embedded space. All very exciting stuff! Will JGJones wrote: I came across this on Planet Gnome and thought it would be of interest if no-one heard of. Apologises if you all already know this and I'm a bit slow on the uptake :-) http://blog.floopily.org/2008/04/23/nokia-funds-d-bus-based-accessibility/ ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Time for another IRC meeting?
I can't remember whether I offered this before or not--but if it would be use to have a teleconference bridge, we can offer that opportunity as well. Janina Willie Walker writes: Hey All: Wow - these past few months really wore me out. There were a lot of deadlines all over the place, and they all seemed to happen at the same time. Those are behind us now (yeah), and I'm wondering if anyone would be interested in getting back on the #a11y channel on irc.gnome.org some time just to chat as a group. One thing I really want to see is more progress on the GNOME Outreach Program: Accessibility work. There's good work to be done, and we need good people: http://www.gnome.org/projects/outreach/a11y/ Will ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Dasher
Thanks, Bryen, for clarifying. I'm sorry I misunderstood. Of course it's appropriate to remove applications no longer serving the intended purpose for whatever reason. Janina Bryen writes: I certainly didn't mean to attempt to minimize the importance of Dasher with numerical values. I only meant to inquire whether it was still a viable tool to be used. In my opinion, all it takes is just one a11y user to say Yes I need it. to make it part of the default installation. Bryen On Wed, 2008-03-19 at 14:09 -0400, David Bolter wrote: Thanks Janina. Excellent point. And it is at the edges where innovation often happens. For the record, my concern about knowing the number of GOK users is that if there are resource decisions to be made that might impact them, it would be good to know the potential damage. It worries me that I don't have enough resources to give GOK the attention it deserves. That said I'm looking to mentor someone for a (co)maintainer role... cheers, David Janina Sajka wrote: Let's please not judge the value of Dasher, or any a11y package by number of users. This is a seriously slippery slope. By this reckoning a11y may as well go back into the closet. By definition, a11y is about edge cases, minimal user numbers, etc., etc. Else there would be no need for exception casing, because all applications would be tailored at screen readers, or at nonmouse input. A11y needs to be in the default package mix because it meets policy objectives, not because it is used by a majority of users. At the moment that includes Orca, Gok, and Dasher plus their dependencies. Janina Samuel Thibault writes: Steve Lee, le Wed 19 Mar 2008 06:57:04 +, a écrit : On 19/03/2008, Bryen [EMAIL PROTECTED] wrote: Is Dasher a useful tool that is still needed as part of a distro's default install? Is there any way we can get an idea of numbers of users? In Debian's popcon.debian.org, among 64688 votes, dasher was voted 363 times. Samuel ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Do we have an item for moving AT-SPI to DBus in the outreach program?
David Bolter writes: If I can find funding, do we have people in the community to (help) do it? I believe the proposal was to have CodeThink do the work. It appears Mozilla Foundation can fund part of the cost, but significant additional funding is still needed to proceed. It seems it may be necessary to cobble funding together from multiple sources, or find another development approach. Janina D Willie Walker wrote: Hi Li: Under the AT-SPI on DBus section on the GetInvolved page, there's a few links to Rob Taylor and Mark Duffman's wonderful work on the feasibility study. They did an awesome job and have created a proposed breakdown of tasks: http://live.gnome.org/GAP/AtSpiDbusInvestigation/MigrationBreakdown Overall, I think everyone agrees this is the right thing to do, and we're now looking for ways to fund the effort. So far, it looks like purse strings are kind of tight and/or pockets are empty. :-( We might need to start thinking about more creative ways to move forward. Do you have a proposal for how we can get unstuck? Will Li Yuan wrote: Hi, There have been a lot of discussions about the AT-SPI over DBus Feasibility Study. Seems to me that there is something need to implement in DBus and a lot of things need to be coordinated between accessibility infrastructure and DBus. It would be great that we can find someone who has DBus knowledge to work on this. Of course it would be greater that he can actually migrate AT-SPI to DBus :-) I saw Migrate Away From CORBA on http://live.gnome.org/Accessibility/GetInvolved http://live.gnome.org/Accessibility/GetInvolved#head-11a5ebf4f3e64822d07ccae6ccbbb54dec4ce948 , what's our plan? Thanks, Li ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing 64-Bit Speakup Modified Fedora
We're pleased to announce the release of new x86_64 installation media for the Speakup Modified Fedora Distribution. Once again we invite you to use our images and installation guidance to install Fedora 8, also known as Werewolf, using your hardware speech synthesizer and the Speakup screen reader on your 64-bit computing system. Downloadable images and documentation are available at our Internet address: http://SpeakupModified.Org You can also access our files using ftp or rsync with commands like: ftp://ftp.SpeakupModified.Org/speakupmodified/fedora/ rsync -l speakupmodified.org::speakupmodified The Speakup Modified Fedora provides: * installation media adapted expressly for those blind computer users who want to use the Speakup Linux screen reader to install a Fedora-style Linux on their computers. This means that the blind computer user will not require sighted assistance, and that the end result will be an installation that talks every time it is booted. * Other assistive technology including Brltty, Emacspeak, Espeak, * Gnome-Speech-Espeak, Orca, and the newly released Tiresias large-print fonts. It's all there--in the installation * images. * Fast and robust Internet connections on our hosted servers, so * that your downloads can proceed at maximum speed * Our acclaimed HOWTO to guide you through the installation * process, including setup for Fedora's accessible graphical desktop. * A mini-howto about using telnet to install Werewolf -- particularly * useful for users who do not have hardware speech synthesizers. * A yum repository so you can update your Speakup Modified Fedora * distribution the easy way--overnight in your sleep, for instance. * Additional accessible applications such as the new Firefox 3 Beta The newly released Fedora 8 is the most accessible Fedora yet. We're pleased we can once again facilitate your installation of Fedora without sighted assistance. Enjoy! The Speakup Modified Team -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: somewhat OT: a gnome build question
You'll find current devhelp and yelp conflict with Firefox 3. Basically, you get to choose between them. Since yelp isn't accessible, and since I don't need devhelp, my choice has been for the accessible Firefox--now in beta. I can't advise you on Epiphany specifically, but would suggest you leave it out until you get the rest of your environment working. PS: Gnome is now at 2.20.2. You might want to build that instead. Janina Alex Snow writes: Hi, Trying to build a copy of gnome-2.20.1 from source under slackware-12.0 to play with orca, and I run into a problem: Epiphany, Yelp, and Devhelp packages won't compile because they can't find gecko...the errors from the configure script say to install a firefox/mozilla/xulrunner dev package...What exactly is this looking for? I have a copy of firefox 3.0b1 installed under /opt/firefox, and the source tree available. How can I produce the development files needed by these programs from the mozilla source tree? ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing SpeakupModified Fedora Installation Media
We're pleased to announce the release of new installation media for the Speakup Modified Fedora Distribution. Once again we invite you to use our images and installation guidance to install Fedora Core 8, also known as Werewolf, using your hardware speech synthesizer and the Speakup screen reader. Downloadable images and documentation are available at our Internet address: http://SpeakupModified.Org You can also access our files using ftp or rsync with commands like: ftp://ftp.SpeakupModified.Org/speakupmodified/fedora/ rsync -l speakupmodified.org::speakupmodified The Speakup Modified Fedora provides: * installation media adapted expressly for those blind computer users who want to use the Speakup Linux screen reader to install a Fedora-style Linux on their computers. This means that the blind computer user will not require sighted assistance, and that the end result will be an installation that talks every time it is booted. * Other assistive technology including Brltty, Emacspeak, Espeak, Gnome-Speech-Espeak, and Orca. * It's all there--in the installation images. * Fast and robust Internet connections on our hosted servers, so * that your downloads can proceed at maximum speed * Our acclaimed HOWTO to guide you through the installation * process, including setup for Fedora's accessible graphical desktop. * A mini-howto about using telnet to install Werewolf -- particularly * useful for users who do not have hardware speech synthesizers. * A yum repository so you can update your Speakup Modified Fedora * distribution the easy way--overnight in your sleep, for instance. * Additional accessible applications such as the new Firefox 3 Beta The newly released Fedora Core 8 is the most accessible Fedora yet. We're pleased we can once again facilitate your installation of Fedora without sighted assistance. Enjoy! The Speakup Modified Team -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing SpeakupModified Fedora 8 Kernels Firefox RPMS
The SpeakupModified Fedora Distribution is pleased to announce key new RPM packages for the recently released Fedora 8, Werewolf. New RPMS for Fedora 7 are also now available and include: * The newly released Firefox 3 Beta * SpeakupModified 2.6.23 kernels * Our 2.6.23 kernel patch which Speakup enables current Linux * kernels and fixes the clipboard problem. Our thanks to Ed * Greenberg for this patch. As always, you can download our RPMS directly from our web site, via ftp, or via rsync. Better still, use yum with our repository to keep your Fedora stylishly up to date. http://SpeakupModified.Org While not yet available, we are again working to provide installation images for Fedora 8. Meanwhile, if you're like us and just can't wait to hear the Werewolf singing on your system, we invite you to follow our telnet instructions for accessible Fedora installation. Be certain also to note the Audio Caution posted on our web site. -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: accessible remote and 64 bit support
Hurst, Cody writes: ... wants to know, since he is going to get an insane machine, wants to know if orca will support 64 bit processors. I told him yes but just want to confirm. Thanks. I guess I don't know what an insane machine is. But, I'm running Orca quite happily on two different 64 bit systems. Only problem is to make sure to run 32-bit Firefox 3 for now. I don't think this is a11y related, btw. Janina ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: [orca-list] accessible login
://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: [orca-list] accessible login
? There also have been some useful a11y related bug fixes in GDM 2.20, so I would recommend using the latest greatest. The email below discusses Ubuntu. At the Gnome A11y Summit this weekend we verified that Suse is broken. My own experience indicates that Fedora 7 and Fedora 7.91 are broken. It would be helpful if people were to file bugs or explain on the [EMAIL PROTECTED] mail list what the problems are. I'd be happy to help. The GDM documentation at the following link has some help in the Accessibility section to explain how to debug some common accessibility issues with GDM: http://www.gnome.org/projects/gdm/docs.html Now that our assistive technologies have passed from mostly developmental software into the realm of usable tools for real people with disabilities, this situation is no longer tolerable. We must call on all distributions to institute procedures to insure that accessible login gets fixed and stays fixed. This will require regular testing, as there are many ways to break accessible login. There are some well known bugs/issues with accessibility. For example, it doesn't work so well with gdmgreeter and some AT programs. You probably need to switch to using gdmlogin if you really need to use an AT that can interact with the widgets. gdmgreeter would require some work to really support accessibility properly. It's main problem is the way it uses GnomeCanvas for building the theme, and the fact that it doesn't support keyboard navigation. Also, failsafe xterm isn't accessible. Perhaps GDM should be configurable so you could use it with gnome-terminal, which does support accessibility? gdmsetup is also not accessible, and probably can't be as long as it requires that you run it as root. Brian Willie Walker writes: Hi Guy: The last time I looked, accessible login was broken on Gutsy. I sent information off to the Ubuntu folks for tracking the problem down, but I'm not sure where they stand with it right now. There's some information on Accessible Login here: http://www.gnome.org/projects/gdm/docs/2.18/accessibility.html Hope this helps, Will PS - Accessible login does indeed work - I've tested it on OpenSolaris. Guy Schlosser wrote: Hey all, how do you enable accessible login in Gutsy? After I updated last night, I now have the login sound, but orca does not start automaticly. Any suggestions? Also, is there something that needs to be done in order to have Orca read items where you have to be root to administer? Finally, one last question. I noticed that firefox 3 was in the Gutsy universe repos. Why isn't that updated after alpha7. Alpha 8 has been released and a9pre is current. Thanks much in advance for any help. Thanks, Guy ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: [orca-list] accessible login
Accessible login appears to be broken on every Linux distribution. As Will points out, this is an issue with distributions. Nevertheless, it's a serious issue for accessibility. The email below discusses Ubuntu. At the Gnome A11y Summit this weekend we verified that Suse is broken. My own experience indicates that Fedora 7 and Fedora 7.91 are broken. Now that our assistive technologies have passed from mostly developmental software into the realm of usable tools for real people with disabilities, this situation is no longer tolerable. We must call on all distributions to institute procedures to insure that accessible login gets fixed and stays fixed. This will require regular testing, as there are many ways to break accessible login. Janina Willie Walker writes: Hi Guy: The last time I looked, accessible login was broken on Gutsy. I sent information off to the Ubuntu folks for tracking the problem down, but I'm not sure where they stand with it right now. There's some information on Accessible Login here: http://www.gnome.org/projects/gdm/docs/2.18/accessibility.html Hope this helps, Will PS - Accessible login does indeed work - I've tested it on OpenSolaris. Guy Schlosser wrote: Hey all, how do you enable accessible login in Gutsy? After I updated last night, I now have the login sound, but orca does not start automaticly. Any suggestions? Also, is there something that needs to be done in order to have Orca read items where you have to be root to administer? Finally, one last question. I noticed that firefox 3 was in the Gutsy universe repos. Why isn't that updated after alpha7. Alpha 8 has been released and a9pre is current. Thanks much in advance for any help. Thanks, Guy ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
A11y Summit--Aria Followup
Since we ended last Saturday's Gnome A11y session somewhat early, I decided to try for an earlier flight home. There wasn't one, so I sat at the gate at Logan poking around the Logan Airport wifi menus with Orca and a recent FF3 build. Furthermore, since I was disinclined to spend $8 to go read my email again, I looked mainly at the pages offered for free at Logan. I came to wish we had Aria enabled already. 1.) Did someone suggest we need Aria on the desktop? I concur. I was interrupted every few minutes by my battery applet giving me wildly inaccurate status reports. Since the applet is so patently inferior to acpitool on the console, I'll probably simply toss it out--as soon as I find it, but the real point is that this applet was being rude. The result of its rude Aria level interruptions was that I would lose my place in other content I was listening to. I never did figure out how to find my place and resume--I had to start over. 2.) Does BOS claim to conform to a1`1y web standards? Perhaps they do--I didn't analyze. However, I found several pages impossible to use, particularly those that display flight departures/arrivals. While I didn't check my supposition in the code (or via Lynx), I expect the data was being updated on the fly--a clear Aria candidate, I suspect. Not only couldn't I get any data, I couldn't even specify any filters via their dropdowns. Sorry I didn't save the URI. But, if you're at Logan, just bring up your wifi. You'll be there. Janina -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
TTSynth Is Available Again
Dear Friends: Shortly after we launched TTSynth a few weeks ago, we discovered that certain users were having problems downloading our software. We closed our doors tempporarily as a result, and spent the last week debugging these problems. We believe we have them well solved. Consequently, it is once again possible to purchase and download TTSynth. http://TTSynth.Com Of course we also provided packages through email to those few customers who experienced problems with our initial release. We believe there are now no outstanding issues. Specifically, we had two problems to fix in our automated download process: 1.) Customers using Internet Explorer on Microsoft Windows were unable to complete transactions. This is now fixed. 2.) Some customers using Debian or Ubuntu experienced failures due to a bug we uncovered in the earlier version of GNU TLS used on these two distributions. Of course it is very important that your Internet transaction is properly protected by SSL. This is now also fixed. Consequently, the premier Text To Speech (TTS) software synthesizer for Linux is once again available for immediate secure on line purchase and download using a credit card! Available Modules Include: * IBM's incomparable IBM TTS text to speech (formerly called ViaVoice) * Gnome-Speech patched for use with LSR and Orca * The TTSynth Speakup Bridge for screen reading with Speakup * ttsynth_say binary for the CLI or for use in scripts * Also supported by Emacspeak KTTS, and Speech Dispatcher Available Languages For Linux * Chinese * English * Finnish * French * German * Italian * Japanese * Portuguese * Spanish The best is also very affordable. Your first language license is only $40 USD and each additional language license is only $20 USD, when obtained at the same time. Use your credit card to purchase and download TTSynth now, and start enjoying the best software speech available for Linux today. Go to http://TTSynth.Com. We provide TTSynth in both .rpm and .deb packages to make it easy to install TTSynth on Fedora, Ubuntu, and most Linux distributions which utilize these package managers. TTSynth is a product of Capital Accessibility, LLC. -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
TTSynth Is Here At Last
The premier Text To Speech (TTS) software synthesizer for Linux is now available for immediate on line purchase and download using a credit card! http://TTSynth.Com Available Modules Include: * IBM's incomparable IBM TTS text to speech (formerly called ViaVoice) * Gnome-Speech patched for use with LSR and Orca * The TTSynth Speakup Bridge for screen reading with Speakup * ttsynth_say binary for the CLI or for use in scripts * Also supported by Emacspeak KTTS, and Speech Dispatcher Available Languages For Linux * Chinese * English * Finnish * French * German * Italian * Japanese * Portuguese * Spanish The best is also very affordable. Your first language license is only $40 USD and each additional language license is only $20 USD, when obtained at the same time. Use your credit card to purchase and download TTSynth now, and start enjoying the best software speech available for Linux today. Go to http://TTSynth.Com. We provide TTSynth in both .rpm and .deb packages to make it easy to install TTSynth on Fedora, Ubuntu, and most Linux distributions which utilize these package managers. TTSynth is a product of Capital Accessibility, LLC. -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: [orca-list] TTSynth Is Here At Last
Hi, Mike: Mike Pedersen writes: Hello Janina, does this now install and work correctly with the default libraries installed on ubuntu? Yes, though you may need additional pieces. For instance, I don't believe gnome-speech-ibmtts is available from Ubuntu repositories by default. We will be providing rpm and deb packages for gnome-speech-ibmtts, speech-dispatcher, speakup-connector, etc., over the next few days via our web site, and eventually via our repositories at SpeakupModified.Org, but only a very few package files are there as of this moment. However, all the sources are available either from us or at default locations. Janina Thanks muchh Mike On Thu, 2007-06-07 at 12:39 -0400, Janina Sajka wrote: The premier Text To Speech (TTS) software synthesizer for Linux is now available for immediate on line purchase and download using a credit card! http://TTSynth.Com Available Modules Include: * IBM's incomparable IBM TTS text to speech (formerly called ViaVoice) * Gnome-Speech patched for use with LSR and Orca * The TTSynth Speakup Bridge for screen reading with Speakup * ttsynth_say binary for the CLI or for use in scripts * Also supported by Emacspeak KTTS, and Speech Dispatcher Available Languages For Linux * Chinese * English * Finnish * French * German * Italian * Japanese * Portuguese * Spanish The best is also very affordable. Your first language license is only $40 USD and each additional language license is only $20 USD, when obtained at the same time. Use your credit card to purchase and download TTSynth now, and start enjoying the best software speech available for Linux today. Go to http://TTSynth.Com. We provide TTSynth in both .rpm and .deb packages to make it easy to install TTSynth on Fedora, Ubuntu, and most Linux distributions which utilize these package managers. TTSynth is a product of Capital Accessibility, LLC. -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: [g-a-devel] Status of IBM a11y
Ariel Rios writes: I am not very familiar with the ATK/AT-SPI implementations but I am aware that these implementations are not compatible with the KDE architecture, and a general move to DBUS has been often mentioned. The GNOME Mobile Embedded Initative could be the opportunity to implement ATK / AT-SPI over DBUS and finaly offer a general solution. For the record no one has stood in the way of a dbus at-spi implementation. However, while we have talked about it for years, mainly because there is strong aversion to Corba in the KDE community at least, no one has stepped up with an implementation even for testing. It should be clear that we cannot deliver accessibility to end users based on wishes or on theory. We need solid, reliable, working implementations. Until those are available in dbus, it would be irresponsible in the extreme to abandon the existing working Corba implementation. Given this obvious truth it's troubling to see Bonobo deprecated in Gnome-2.19. What is the meaning of that? If actions speak louder than words, how are we to understand a commitment to a11y in Gnome? Please be aware that moving into dbus might be a very hard task. Currently GNOME has a working a11y architecture while KDE has none. Do we want to move to an non existant architecture from one that works actually really well? Hear hear. I recognize I'm saying the same thing. But this is a critically important issue for a11y. Janina ariel http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: MIDI Sequencer
The competitive equivalent for Windows' Sonar/Cakewalk, Macintosh Digit Design, etc., is Ardour, not Audacity: http://ardour.org While ardour2 uses gtk2 to some degree, and while they've provided extensive keyboard shortcuts, they have unfortunately also crafted numerous custom widgets in their software. The news for midi is even worse. There is nothing other han a few simple console tools. The applications that sighted musicians and composers are using, Muse and/or PD, are written in older versions of QT--and even at that also rely on custom widgets. Frankly, it's a very sad state of affairs. Janina PS: For Linux music/sound apps, pages, and lists start with: http://linux-sound.org Bill Haneman writes: Thomas and Chris; In reply to your question regarding accessible wave editors, I believe audacity has been tested with Windows access technologies (on Windows, that is). Because audacity is written with the WxWindows toolkit (I believe that's what it's called), it doesn't yet take advantage of native Linux accessibility interfaces such as ATK. The latter would be a great project for someone to help the audacity team with, as they clearly are interested in making their project/product accessible. regards, Bill [EMAIL PROTECTED] wrote: Chris, First, I think we may be posting in the wrong mailing list. This is the gnome-accessibility-list, and even though I'm brand new to this mailing list, I suspect the list has more focus on the kind of accessibility described at http://en.wikipedia.org/wiki/Accessibility There are a *lot* of Gnome mailing lists, perhaps some kind person on this one could direct us to one that would be a better fit to our inquiry. I say our inquiry, because I don't have an *answer* for you--being very much in the same boat. (^_^) Recently, I switched over from Windows 2000 to Ubuntu. Under Windows I was using Anvil Studio. Now, I'm trying to find a good MIDI editor, MIDI sequencer, MIDI player, MIDI whatever, to use in Ubuntu--specifically the Gnome desktop of Ubuntu. There are lots of discussions about MIDI and other sound systems on the Ubuntu forums: Ubuntu Forums The Ubuntu Forum Community Main Support Categories General Help Music Composition in Linux? http://ubuntuforums.org/showthread.php?t=376531highlight=midi Ubuntu Forums The Ubuntu Forum Community Main Support Categories General Help Rosegarden: MIDI Playback http://ubuntuforums.org/showthread.php?t=371356highlight=midi But everything I've tracked down so far looks like either KDE only, or else refers to Timidity--which, so far as I know, is a command-line-only player-only. Since this is at least a Gnome list, could anybody out there point us in the right direction to find out about a *GNOME* MIDI sequencer? Please? -- Thomas A. McCloud MIDI Sequencer Chris Norman Tue, 06 Mar 2007 02:50:25 -0800 Hi all, I have got everything working on my ubuntu system, but am missing one thing. I want to be able to sequence (using MIDI), and edit and create wave files. Does anyone know of an accessible MIDI sequencer and / or an accessible wave editor? What, if any modifications do I need to make in order to get midi on my system? Cheers all, Chris. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Firefox 3 Crash Problem
I've just confirmed consistent crash behavior on FF3 with Orca or LSR which doesn't happen when I run the same FF3 without screen reading. I've further confirmed this on two sites, hilton.com and united.com. I'll provide my steps vis a vis looking for flights on United Airlines: * Go to united.com and tab to the form fields for flight searches. * Enter IAD and OSL in the From: and To: fields -- any airport * codes will do, actually. * Tab to the drop downs for selecting month and day for departure * and return. Pick reasonable dates, in my case April 20 and April * 28 respectively. * Tab to the Submit button. Everything else is at defaults. With Orca or LSR loaded and speaking, Minefield will crash when Submit is actuated. Intriguingly, restarting Minefield and selecting Restore previous session will display the search results as if Minefiled had not crashed. If Orca or LSR are not running, there is no crash--the search results display as one would expect. Please note that I have not set gnome-accessibility false when testing without screen readers. That variable is still set true. PS: I'm using ibmtts, if that helps. Janina -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Multilingual synthesis
Peter Parente writes: Maybe this is related, maybe not. There was a SoC project last year guessing language component for OpenOffice. For example see http://www.mail-archive.com/dev@lingucomponent.openoffice.org/msg00958.html There's also the universal encoding detector (http://chardet.feedparser.org/) based on code in Mozilla. Reusing the code makes sense where the license permits. But we should'nt be leaving this to huristic guessing technology. I've just raised this in our ODF A11y Wg. If we need ml, I'm sure we'll be able to add that for ODF 1.2 and beyond. -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Problem Package Removed
We regret one of the rpm packages released earlier this week at the Speakup Modified should not have been published. If you downloaded at-spi from the Speakup Modified this week, please go to any Fedora mirror site and retrieve both at-spi and at-spi-devel. Reinstalling this older version will fix the problems our packages created for both Orca and LSR. We apologize for the inconvenience. You can get the older versions at the following URL: ftp://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/ Once you have these files downloaded, use a command like the following to revert to this older version of at-spi: sudo rpm -Uv --oldpackage at-spi* -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundationhttp://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca Problem Package Removed
I'm wondering how I might go about trying to debug why my newer at-spi created problems. Essentially, the behavior was: Orca launched and spoke up to entering focus tracking, but no more. There was precious little in /var/log, unless the following actually explains this: In /var/log: pcscd: winscard.c:219:SCardConnect() Reader E-Gate 0 0 Not Found And, in Xorg.0.log, three messages of the type: Xorg: client 3 rejected from local host So, my question ... Is there some way to increase logging/verbosity to help in figuring out what's gone amiss? Janina Janina Sajka writes: We regret one of the rpm packages released earlier this week at the Speakup Modified should not have been published. If you downloaded at-spi from the Speakup Modified this week, please go to any Fedora mirror site and retrieve both at-spi and at-spi-devel. Reinstalling this older version will fix the problems our packages created for both Orca and LSR. We apologize for the inconvenience. You can get the older versions at the following URL: ftp://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/ Once you have these files downloaded, use a command like the following to revert to this older version of at-spi: sudo rpm -Uv --oldpackage at-spi* -- Janina Sajka, Phone: +1.202.595.;sip:[EMAIL PROTECTED] Partner, Capital Accessibility LLChttp://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com Chair, Open Accessibility [EMAIL PROTECTED] Linux Foundation http://a11y.org ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing New Packages at the Speakup Modified
We've expanded the packages provided at the Speakup Modified in order to serve your assistive technology Fedora Linux needs better than ever. As before, you can still use yum to install and upgrade orca, lsr, gnome-speech, the emerging accessible Firefox 3, and of course to get the latest and greatest Speakup enabled Fedora kernels. Our current rpms of these packages are as follows: firefox-3.0a3pre-2007021021_trunk gnome-speech-0.4.9 kernel-2.6.19 lsr-0.4.0 orca-2.17.91 And now, because Red Hat has not been upgrading and publishing them for Fedora Core 6, we're making available the following packages as well: atk-1.17.0 gail-1.17.0 at-spi-1.17.0 We're also pleased to provide the fully accessible Asterisk (and Zaptel) Vo/IP telephony packages! To add the SpeakupModified to your yum repositories do the following as root: rpm -iv http://speakupmodified.org/speakupmodified-release.rpm You will need do this only once. Thereafter, the Speakup Modified package repository will be one of the repositories yum checks when you install and upgrade your Fedora 6 packages. To install orca and lsr you would do: yum install orca lsr And, to get the latest Firefox you would do a more elaborate yum command--because Firefox is still alpha software. Issue the following all on one command line: yum --disablerepo='*' --enablerepo=speakupmodified-development upgrade firefox* Enjoy! -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing Updated Firefox 3 RPMs (Again)
The rpm builds of Firefox 3 available from the SpeakupModified-Development yum repository have been updated yet again. These rpms are for installations of Fedora Core 6 (Linux) or the forthcoming Fedora Core 7 currently under development. They are based on Mozilla downloades from January 3 and include current state-of-the-art accessibility support. You can retrieve both source and binary rpm packages via ftp, http, or rsync. But the best way to keep your Firefox 3 updated is to use yum. WARNING: This is an early alpha build of Firefox. It is known to conflict with yelp and devhelp. You will probably need to remove these, and perhaps other rpms in order to install Firefox 3. Please note also that support for Firefox 3 in both Orca and LSR is still under active development, as is also the accessibility support within Firefox itself. To use yum with the Speakup Modified Fedora rpm package repository, you must first configure your system to access our repository. You will need do this only once. Become root on your FC6 system and issue the following command: rpm -iv http://SpeakupModified.Org/speakupmodified-release.rpm Thereafter, to update Firefox 3, become root and issue the following command all on one line: yum --disablerepo='*' --enablerepo=speakupmodified-development update firefox -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing Updated Firefox 3 RPMs
The rpm builds of Firefox 3 available from the SpeakupModified-Development yum repository have been updated. These rpms are for installations of Fedora Core 6 (Linux) or the forthcoming Fedora Core 7 currently under development. They are based on Mozilla downloades from December 27 and include current state-of-the-art accessibility support. You can retrieve both source and binary rpm packages via ftp, http, or rsync. But the best way to keep your Firefox 3 updated is to use yum. WARNING: This is an early alpha build of Firefox. It is known to conflict with yelp and devhelp. You will probably need to remove these, and perhaps other rpms in order to install Firefox 3. Please note also that support for Firefox 3 in both Orca and LSR is still under active development, as is also the accessibility support within Firefox itself. To use yum with the Speakup Modified Fedora rpm package repository, you must first configure your system to access our repository. You will need do this only once. Become root on your FC6 system and issue the following command: rpm -iv http://SpeakupModified.Org/speakupmodified-release.rpm Thereafter, to update Firefox 3, become root and issue the following command all on one line: yum --disablerepo='*' --enablerepo=speakupmodified-development update firefox -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing Orca RPMs For FC6
We invite all users of Fedora Core 6 (FC6) to obtain current builds of Orca from our RPM repository at the Speakup Modified Fedora Distribution site. You can retrieve both source and binary rpm packages via ftp, http, or rsync. But the best way to keep your Orca updated is to use yum. To use yum with the Speakup Modified Fedora rpm package repository, you must first configure your system to access our repository. You will need do this only once. Become root on your FC6 system and issue the following command: rpm -iv http://SpeakupModified.Org/speakupmodified-release.rpm Thereafter, to update Orca, become root and issue this command: yum upgrade orca We have resumed building and publishing Orca rpms because the Orca rpms being built by Red Hat now require Python 2.5, and that imposes too many upgrade problems for most users at this time. The Red Hat Orca builds are part of development work aimed at the forthcoming release of Fedora Core 7 which will use Python 2.5. However, most users today will, we believe, prefer to stay with current Fedora releases which will continue to use Python 2.4 until FC7 is actually released sometime in mid 2007. Therefore, our Orca rpms will be built with Python 2.4 in order to keep the task of upgrading Orca simple and straight forward. -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Announcing Yum Support at the SpeakupModified
The SpeakupModified Fedora Distribution is pleased to announce support for package updates using yum. Now you can install and update your SpeakupModified packages the easy yum way. To enable the SpeakupModified yum repository, first execute the following command as root: rpm -iv http://speakupmodified.org/speakupmodified-release.rpm This command will install our GPG key and the SpeakupModified repository configuration files that yum uses. Thereafter, you can use yum to: * Upgrade to a Fedora kernel patched with Speakup like this: yum --disablerepo='*' --enablerepo=speakupmodified install kernel * Install one of our other rpm packages, lsr for instance, like * this: yum install lsr -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: ubuntu and software synthesiser
Hi, All: Willie Walker writes: Hi Henrik: Is there a way we can make this more user friendly? Are there licensing reasons why gnome-speech is compiled without DECtalk support or technical ones? If it's a question of some compile flags then I can ask our packagers to make a DECtalk-enabled version available. The issue is licensing. The problem is that the DECtalk header files are Fonix's intellectual property. As a result, one needs to have the DECtalk SDK installed on their machine to build the DECtalk driver (the gnome-speech build will automatically build the DECtalk driver if it finds the DECtalk SDK). If the Ubuntu distribution folks were able to get the DECtalk SDK on their production machines, then I think they'd be able to ship the gnome-speech driver for DECtalk and then direct users to the Fonix web site to purchase the DECtalk run time (one would need to check the DECtalk license to make sure it is OK to ship things built against the SDK -- I'm not a lawyer and I'm not qualified to interpret legal documents). We would like to provide you a similar wrapper for the forthcoming release of TTSynth, http://ttsynth.com, which in turns wraps ibmtts, formerly and more popularly known as Viavoice. In fact, the gnome-speech-ibmtts rpm on our web site does exactly that for rpm based distros. Unfortunately, for TTSynth on Ubuntu there's the problem that compat-libstdc++-296 (or 2.95) seems no longer available. Since ibmtts is quite proprietary, even though it's by far the most requested TTS engine out there, we don't have much control over updating its compile. -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: what happened to gnopernicus?
Hi, Don: Don Raikes writes: When I installed fedora core 6, I discovered that gnopernicus, gnome-speech and gok are all missing. What happened to these tools? They're all there, except that Gnopernicus is now replaced by Orca. I can't know, of course, what selections you made during your FC6 installation process that kept them from being installed, but you can easily install them using yum. Red Hat is keeping them quite current, in fact. My advice is to install orca from the Fedora development tree in order to track the latest developments. The downside of doing this is that you'll need to take care to retrieve updates by hand. Here's how to do that: yum --disablerepo='*' --enablerepo=development install orca For gok and gnome-speech, just do: yum install gok gnome-speech Here are the rpm listings from my FC6 installs: Name: orca Relocations: (not relocatable) Version : 2.17.2Vendor: Red Hat, Inc. Release : 1.fc7 Build Date: Tue 07 Nov 2006 03:14:49 PM EST Install Date: Wed 08 Nov 2006 10:28:54 PM EST Build Host: hs20-bc2-4.build.redhat.com Group : User Interface/Desktops Source RPM: orca-2.17.2-1.fc7.src.rpm Size: 4178596 License: LGPL Signature : (none) Packager: Red Hat, Inc. http://bugzilla.redhat.com/bugzilla URL : http://www.gnome.org/projects/orca/ Summary : Flexible, extensible, and powerful assistive technology Description : Orca is a flexible, extensible, and powerful assistive technology for people with visual impairments. Using various combinations of speech synthesis, braille, and magnification, Orca helps provide access to applications and toolkits that support the AT-SPI (e.g., the GNOME desktop). Name: gnome-speech Relocations: (not relocatable) Version : 0.4.6 Vendor: Red Hat, Inc. Release : 1.fc7 Build Date: Sun 05 Nov 2006 11:44:31 PM EST Install Date: Wed 15 Nov 2006 09:11:38 PM EST Build Host: hs20-bc2-3.build.redhat.com Group : Desktop/Accessibility Source RPM: gnome-speech-0.4.6-1.fc7.src.rpm Size: 73554License: LGPL Signature : (none) Packager: Red Hat, Inc. http://bugzilla.redhat.com/bugzilla URL : http://www.gnome.org/ Summary : GNOME Text to Speech Description : GNOME Speech Name: gok Relocations: (not relocatable) Version : 1.2.0 Vendor: Red Hat, Inc. Release : 1.fc6 Build Date: Fri 08 Sep 2006 01:03:34 PM EDT Install Date: Fri 27 Oct 2006 07:56:33 PM EDT Build Host: hs20-bc1-7.build.redhat.com Group : Desktop/Accessibility Source RPM: gok-1.2.0-1.fc6.src.rpm Size: 9669932 License: GPL Signature : DSA/SHA1, Tue 03 Oct 2006 09:51:32 PM EDT, Key ID b44269d04f2a6fd2Packager: Red Hat, Inc. http://bugzilla.redhat.com/bugzilla URL : http://www.gok.ca/ Summary : GNOME Onscreen Keyboard Description : The gok project aims to enable users to control their computer without having to rely on a standard keyboard or mouse, leveraging GNOME's built-in accessibility framework. Cheers, Don Raikes, Accessibility Specialist 4848 W. Rosebay S. Tucson, AZ 85742 Home office: (520) 579-9481 AIM: dnraikes ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca on laptops.
. The
reason is that I assume Orca is going to be something that the user runs
all the time to access their Desktop.
Attached is a patch to orca.py from GNOME CVS HEAD for anyone wants to
play around with this. You'll need to apply this patch (patch -p0
caplock.patch) and you'll need to add/edit the following line to your
~/.orca/user-settings.py (can get blown away) or your
~/.orca/orca-customizations.py (will not get blown away) file:
orca.settings.orcaModifierKeys = ['Caps_Lock']
Btw, you can also do the following if you want both Insert and Caps_Lock
as the Orca modifier key:
orca.settings.orcaModifierKeys = ['Caps_Lock', 'Insert', 'KP_Insert']
Let me know if this works for you. If it does, we can make it a
permanent part of Orca.
Will
On Thu, 2006-11-09 at 09:48 +, Bill Haneman wrote:
Makes sense, with the caveat that if we remap CapsLock to achieve this
(as we probably must, to avoid the latching behavior), then the end
user will no longer be able to use CapsLock in the normal way.
Probably that is not a significant issue for 99% of the users.
I agree with Will's point that we should be thinking user-centrically in
most of our discussion; however the point I made about remapping being
more intrusive as a technique still applies. The use of CapsLock is, as
Will pointed out in an earlier email, somewhat less clean and ideal
technically than using some other modifier key. This is because, unlike
the other keys, use of CapsLock is inherently modal (changes the X
keyboard state in a sticky way) unless the CapsLock key is re-mapped
to some other X keyboard symbol.
Bill
Janina Sajka wrote:
Bill Haneman writes:
Thanks Will. That clarifies things somewhat - we're using the term
modifier key differently. Maybe I'll contact you offlist for info
on
the internal details.
So does that basically mean this whole discussion of orca on laptops
is
moot, or at least addressed fully via orca.settings.orcaModifierKeys
(possibly with a UI for changing it easily) ?
Bill
I shouldn't think so. This discussion has already pointed out that
CapsLock is the established default modifier for JFW users on Windows
and for Speakup users on Linux. Furthermore, it is reasonable to expect
that no new application is likely to adopt CapsLock for it's own uses,
i.e. we run the least risk of conflict both today and tomorrow by
defaulting to CapsLock as the default Orca laptop modifier.
Of course, the fact that this is established practice and widely
expected by users both on Windows and Linux should really end this
discussion, from the user point of view. Choosing anything else will
certainly cause continuing confusion and displeasure among users, so
there'd need to be extremely powerful arguments to choose anything else.
I haven't heard arguments yet in this thread that strike me as
sufficiently convincing to look for some other modifier.
It's available, achievable and remappable, and it's what users expect.
What else do we need to put this one to bed?
Janina
Willie Walker wrote:
Hi All:
I don't think there's a need to map an existing X modifier to the Orca
modifier. Orca invents its own modifier internally and allows any key
to act as the Orca modifier. That's why Insert and KP_Insert can act
as
the Orca modifier key. As such, I'm not sure which modifier is an
important discussion to have.
Will
___
Orca-list mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/orca-list
Index: orca/src/orca/orca.py
===
RCS file: /cvs/gnome/orca/src/orca/orca.py,v
retrieving revision 1.165
diff -p -u -r1.165 orca.py
--- orca/src/orca/orca.py7 Nov 2006 19:19:01 - 1.165
+++ orca/src/orca/orca.py9 Nov 2006 14:44:10 -
@@ -857,6 +857,10 @@ def loadUserSettings(script=None, inputE
debug.println(debug.LEVEL_CONFIGURATION,
Magnification module has NOT been initialized.)
+for keyName in settings.orcaModifierKeys:
+if keyName == Caps_Lock:
+os.system('xmodmap -e clear Lock')
+
_showMainWindowGUI()
httpserver.init()
___
Orca-list mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/orca-list
___
Orca-list mailing list
[EMAIL
Re: Orca on laptops.
Bill Haneman writes: Thanks Will. That clarifies things somewhat - we're using the term modifier key differently. Maybe I'll contact you offlist for info on the internal details. So does that basically mean this whole discussion of orca on laptops is moot, or at least addressed fully via orca.settings.orcaModifierKeys (possibly with a UI for changing it easily) ? Bill I shouldn't think so. This discussion has already pointed out that CapsLock is the established default modifier for JFW users on Windows and for Speakup users on Linux. Furthermore, it is reasonable to expect that no new application is likely to adopt CapsLock for it's own uses, i.e. we run the least risk of conflict both today and tomorrow by defaulting to CapsLock as the default Orca laptop modifier. Of course, the fact that this is established practice and widely expected by users both on Windows and Linux should really end this discussion, from the user point of view. Choosing anything else will certainly cause continuing confusion and displeasure among users, so there'd need to be extremely powerful arguments to choose anything else. I haven't heard arguments yet in this thread that strike me as sufficiently convincing to look for some other modifier. It's available, achievable and remappable, and it's what users expect. What else do we need to put this one to bed? Janina Willie Walker wrote: Hi All: I don't think there's a need to map an existing X modifier to the Orca modifier. Orca invents its own modifier internally and allows any key to act as the Orca modifier. That's why Insert and KP_Insert can act as the Orca modifier key. As such, I'm not sure which modifier is an important discussion to have. Will ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca on laptops.
At the risk of beating on this to death ... Am I correct in the belief that we mean Insert and CapLocks interchangeably? If so, I agree. Insert is the long established default on full-sized keyboards. I don't believe this was at issue, in fact. CapLocks comes up only to facilitate laptop users where Insert is awkward, at best, and often plain impossible. Of course, once we have CapsLock, there's no reason to not use it as a modifier with a full-size keyboard, should a user wish. I suspect there is a point of divergence where a decision must be made, though. As I understand it, JFW uses Shift plus CapsLock to actually latch CapsLock. Speakup, on the other hand, uses Ctrl-CapsLock for this. I suggest the resolution we want is consistency, and I think we need to adopt practices already familiar in gnopernicus, orca, and indeed the Windows world. So, much as my Linux/Unix soul prefers Alt-Tab over Shift-Tab, I suspect the Shift-CapLocks should latch/unlatch caps. Janina Joe Lazzaro writes: I vote for employing Insert and CapsLock as modifiers. This will emulate what's used in some Windows screen readers, and users will be accustomed to it, which is a good thing. Joe Lazzaro -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rich Burridge Sent: Wednesday, November 08, 2006 9:27 PM To: Janina Sajka Cc: Bill Haneman; Willie Walker; 'Ubuntu Accessibility Mailing List'; 'Gnome Accessibility List'; 'Orca screen reader developers' Subject: Re: Orca on laptops. Hi Janina, Of course, the fact that this is established practice and widely expected by users both on Windows and Linux should really end this discussion, from the user point of view. Choosing anything else will certainly cause continuing confusion and displeasure among users, so there'd need to be extremely powerful arguments to choose anything else. I haven't heard arguments yet in this thread that strike me as sufficiently convincing to look for some other modifier. One of the arguments for Insert (or rather KP_Insert, the 0 on the numeric keypad), is that you can do chords (Insert-whatever) with one hand, whilst the other hand could remain on the braille display. I can quantify how significant that is to a blind user. Hopefully other members of this list can speakup (sorry) and tell us. It's available, achievable and remappable, and it's what users expect. What else do we need to put this one to bed? My feeling is that we just need to pick a default that most people want. If that's CapsLock to be compatible with JAWS and Speakup, then so be it. As it's configurable, other users can adjust accordingly. ___ Orca-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/orca-list -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
The Speakup Modified Fedora Distribution Returns
The Speakup Modified Fedora Distribution is back. Once again we invite you to use our images and installation guidance to install Fedora Core 6, also known as Zod, using your hardware speech synthesizer and the Speakup screen reader. Downloadable images and documentation are available at our new Internet address: http://SpeakupModified.Org You can also access the Speakup Modified Fedora files using ftp and rsync with commands such as: ftp://ftp.SpeakupModified.Org/speakupmodified/fedora/ rsync -l speakupmodified.org::speakupmodified The Speakup Modified Fedora provides: * installation media adapted expressly for those blind computer users who want to use the Speakup Linux screen reader to install a Fedora-style Linux on their computers. This means that the blind computer user will not require sighted assistance, and that the end result will be an installation that talks every time it is booted. * Other assistive technology including brltty, emacspeak,, and orca. * It's all there--in the installation images. * Fast and robust Internet connections on our new hosted servers, so * that your downloads can proceed at maximum speed In the very near future we will also provide: * A revised Installation HOWTO to guide you through the installation * process, including setup for Fedora's accessible graphical desktop. * A yum repository so you can update your Speakup Modified Fedora * distribution the easy way--overnight in your sleep, for instance. * Additional accessible applications such as Asterisk, LSR and elinks * with javascript support * A Help Wiki and mini HOWTOs on various Linux topics that you can use both to learn from and also to share your own expertise with others. The newly released Fedora Core 6 is the most accessible Fedora yet. We're pleased we can once again facilitate your installation of Fedora without sighted assistance. Enjoy! The Speakup Modified Team ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: ANNOUNCE: Linux Screen Reader 0.3.0
My apologies for givving out an incorrect URL for the LSR 0.3.0 rpms. The correct URL is: ftp://ftp.rednote.net/fedora/rednote/ The binaries are then in RPMS and the sources in SRPMS. Again, my apologies for this error and any confusion it may have caused. Janina Sajka writes: We now have rpm packages of LSR 0.3.0 built against Fedora Core 5 available at: ftp://ftp.rednote.net/fedora/speakupmodified As you would expect, the binaries are then under RPMS/ and the sources under SRPMS/. Enjoy! Janina Peter Parente writes: == * What is it ? == The Linux Screen Reader (LSR) project is an open source effort to develop an extensible assistive technology for the GNOME desktop environment. The goal of the project is to create a reusable development platform for building alternative and supplemental user interfaces in support of people with diverse disabilities. The primary use of the LSR platform is to give people with visual impairments access to the GNOME desktop and its business applications (e.g. Firefox, OpenOffice, Eclipse) using speech, Braille, and screen magnification. The extensions packaged with the LSR core are intended to meet this end. However, LSR's rich support for extensions can be used for a variety of other purposes such as supporting novel input and output devices, improving accessibility for users with other disabilities, enabling multi-modal access to the GNOME desktop, and so forth. == * What's changed ? == A demonstration of LSR 0.3.0 will be presented at the GNOME Accessibility Summit. A screencast of the demo will be posted on the LSR homepage shortly thereafter. The demo will showcase the latest screen reading features of LSR as well as two prototype interfaces for people with cognitive decline and reading disabilities. For users * The new settings dialog allows for configuration of settings defined by a particular device or script as well as the current user profile. For instance, a user can change their speech synthesizer without restarting LSR. * Settings are now persistent across sessions. More settings will be added in future versions. * New keyboard commands are now available such as reading accessible descriptions, reporting text attributes, routing focus and caret, etc. See the list of defined commands at * The LSR review keys now function on web pages in Firefox 3.0. The FirefoxPerk will grow new commands for rich document navigation in future releases. * The Perk chooser dialog allows users to manually load and unload scripts for the current application. This allows users to dynamically load/unload tool scripts at runtime, kind of like Emacs modes. * DECtalk is now supported through gnome-speech. * SpeechDispatcher is now supported. * A script to better support accessible login has been added. Instructions for configuring Fedora Core to start LSR at login are now available in the LSR FAQ. (http://live.gnome.org/LSR/FrequentlyAskedQuestions) For developers * The developer scripting API has grown a tremendous number of new convenience methods. See the epydoc on the LSR homepage for details. * Three developer monitors now exist in LSR for watching raw accessibility events from at-spi, execution of LSR scripts, and I/O streams to devices. * User configurable settings may now be defined by LSR scripts. The settings dialog automatically generates an accessible user interface for changing their values. * Developers can now add new dialogs and debugging monitors to LSR just as they can add scripts and input/output devices. They're all just extensions to LSR. * The command line interface for managing extensions is now simpler. * Extensions may now be added by the root user and made available system-wide, or added by an unprivileged user and available for his/her use only. * The spec is updated to support the building of relocatable RPMs. Translations * en_GB(David Lodge) * vi(Clytie Siddall) * zh_CN(Funda Wang) * pt_BR(Raphael Higino) * sv(Daniel Nylander) For full details, please see the ChangeLog at http://cvs.gnome.org/viewcvs/lsr/ChangeLog?rev=1.29. For an idea of where LSR is headed next, visit http://live.gnome.org/LSR/Timeline == * Where can I get it ? == Source code release and contributed packages: http://live.gnome.org/LSR#downloads For more information, visit the LSR home page: http://live.gnome.org/LSR ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina Sajka Phone: +1.202.595. Partner, Capital Accessibility LLC
Re: ANNOUNCE: Linux Screen Reader 0.3.0
We now have rpm packages of LSR 0.3.0 built against Fedora Core 5 available at: ftp://ftp.rednote.net/fedora/speakupmodified As you would expect, the binaries are then under RPMS/ and the sources under SRPMS/. Enjoy! Janina Peter Parente writes: == * What is it ? == The Linux Screen Reader (LSR) project is an open source effort to develop an extensible assistive technology for the GNOME desktop environment. The goal of the project is to create a reusable development platform for building alternative and supplemental user interfaces in support of people with diverse disabilities. The primary use of the LSR platform is to give people with visual impairments access to the GNOME desktop and its business applications (e.g. Firefox, OpenOffice, Eclipse) using speech, Braille, and screen magnification. The extensions packaged with the LSR core are intended to meet this end. However, LSR's rich support for extensions can be used for a variety of other purposes such as supporting novel input and output devices, improving accessibility for users with other disabilities, enabling multi-modal access to the GNOME desktop, and so forth. == * What's changed ? == A demonstration of LSR 0.3.0 will be presented at the GNOME Accessibility Summit. A screencast of the demo will be posted on the LSR homepage shortly thereafter. The demo will showcase the latest screen reading features of LSR as well as two prototype interfaces for people with cognitive decline and reading disabilities. For users * The new settings dialog allows for configuration of settings defined by a particular device or script as well as the current user profile. For instance, a user can change their speech synthesizer without restarting LSR. * Settings are now persistent across sessions. More settings will be added in future versions. * New keyboard commands are now available such as reading accessible descriptions, reporting text attributes, routing focus and caret, etc. See the list of defined commands at * The LSR review keys now function on web pages in Firefox 3.0. The FirefoxPerk will grow new commands for rich document navigation in future releases. * The Perk chooser dialog allows users to manually load and unload scripts for the current application. This allows users to dynamically load/unload tool scripts at runtime, kind of like Emacs modes. * DECtalk is now supported through gnome-speech. * SpeechDispatcher is now supported. * A script to better support accessible login has been added. Instructions for configuring Fedora Core to start LSR at login are now available in the LSR FAQ. (http://live.gnome.org/LSR/FrequentlyAskedQuestions) For developers * The developer scripting API has grown a tremendous number of new convenience methods. See the epydoc on the LSR homepage for details. * Three developer monitors now exist in LSR for watching raw accessibility events from at-spi, execution of LSR scripts, and I/O streams to devices. * User configurable settings may now be defined by LSR scripts. The settings dialog automatically generates an accessible user interface for changing their values. * Developers can now add new dialogs and debugging monitors to LSR just as they can add scripts and input/output devices. They're all just extensions to LSR. * The command line interface for managing extensions is now simpler. * Extensions may now be added by the root user and made available system-wide, or added by an unprivileged user and available for his/her use only. * The spec is updated to support the building of relocatable RPMs. Translations * en_GB(David Lodge) * vi(Clytie Siddall) * zh_CN(Funda Wang) * pt_BR(Raphael Higino) * sv(Daniel Nylander) For full details, please see the ChangeLog at http://cvs.gnome.org/viewcvs/lsr/ChangeLog?rev=1.29. For an idea of where LSR is headed next, visit http://live.gnome.org/LSR/Timeline == * Where can I get it ? == Source code release and contributed packages: http://live.gnome.org/LSR#downloads For more information, visit the LSR home page: http://live.gnome.org/LSR ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org
Re: Announcing Orca v2.17.0
: duplicate window titles are now spoken when navigating between them using Alt+Tab. * Fix for bug 350216: LAYERED_PANE is no longer in speech context. * Fix for bug 351797: make sure configuration GUI pops to top. * Fix for bug 347128: allow pan buttons to be used on braille display while in learn mode. * Fix for bug 347650: allow a script to determine if it is the active script or not (compare self to orca_state.activeScript). * For for bug 354983: From Rodrigo Moya [EMAIL PROTECTED] (THANKS!) to fill in dead code paths in brlmodule.c. * Fix for bug 354487: apostrophe no longer delimits a word boundary. * Fix for bug 354985: gedit script no longer generates a traceback due to a missing import line. * Fix for bug 342602: StarOffice Writer table cell speaking order fixed. * Fix for bug 351826: change orca shell script from sh to bash to allow it to better respond to kill -HUP signals. * Fix for bug 352866: add -q and --quit usage information * Fix for bug 353600: don't require the user to be root when doing a make distcheck. * New and updated translations (THANKS!): dz Dzongkha Pema Geyleg el GreekSimos Xenitellis es Spanish Francisco Javier F. Serrador et Estonian Priit Laes gl Galician Ignacio Casal Quinteiro th Thai Supranee Thirawatthanasuk and tr Turkish Deniz Kocak and Baris Cicek = * Where can I get it? = You can obtain Orca v2.17.0 in source code form at the following URL: http://ftp.gnome.org/pub/gnome/sources/orca/2.17/orca-2.17.0.tar.bz2 http://ftp.gnome.org/pub/gnome/sources/orca/2.17/orca-2.17.0.tar.gz From the Sun Microsystems, Inc., Accessibility Program Office, Willie Walker, Project Lead Mike Pedersen, User Interface Design Rich Burridge, Core Development and Scripting Lynn Monsanto, Core Development and Java Platform Support Michele Budris, Program Management ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.595. Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: getting orca included in gnome 2.16
Thanks, Kris, for getting at the real issue that I missed. I must indeed agree with you. I, for one, am glad that there are dozens of sopas at the store, and several airlines to fly across the Atlantic. I understand it's harder to support choice in distributions and desktops, but I believe it's essential so to do, if for no other reason than it makes us think harder to get the important things right. It's not important that we all use the same email client, for instance, but it is important that we can read email from anyone. I believe the latter is at risk when we allow ourselves the ease of the former. Janina Kris Van Hees writes: On Sat, Jun 10, 2006 at 08:01:00PM +0100, Henrik Nilsen Omma wrote: Janina Sajka wrote: Mike Pedersen writes: We have been informed, however, that there can be only one screen reader/magnifier in the GNOME desktop. That's a rather outrageous attitude. Who made that decision? Are they also prepared to have only one web browser? ONly one media player? ONly one word processor? Only one email client application? I think you may have misinterpreted this slightly. The idea is that there will only be one official screen reader in Gnome, as there indeed is only one email client (Evolution), one browser (Epiphany), one office suite (gnome office, using abiword and gnumeric). Distributions can, and do, change these defaults and users can install a whole range of options. Not to start a holy war, but a reasonable part of the audience that believes in an alternative to Microsoft Windows also supports the notion of *not* including various other applications and suites. While Gnome is surely not an OS, it seems rather weird (and potentially dangerous) to me to end up with a situation where Gnome has an official screen reader, an official mail client, etc... By including specific official applications and suites in Gnome, you're bound to get into a situation where a large group of people will end up simply sticking to the officially included applications and suites, either by choice (easier) or as mandated by an IT department that takes the we only run the officially included stuff approach (all too comon). And in the end... why not simply leave Gnome to be the desktop environment it is, and let users choose what they want? Why does there need to be one official choice, and optional alternatives? I can see where the general public falls for this, and how from a let's pretend the user is stupid perspective this can be considered user-friendly, but I would hope that we (as a special interest group) can express a genuine concern about this type of policy to the powers that be (and that make this type of policy). Kris ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.240.715.1272 Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
pdftk -- Making PDF Yet More Accessible
There's a new PDF tool reviewed at: http://www.linux.com/article.pl?sid=06/04/17/1943230 Among the features of pdftk is the ability to fill out PDF forms from the command line. The above article also references a GUI front end to pdftk. I have no notion whether the particular gui tool is also accessible, but the fact that one can devise a graphical front end certainly suggests that one might also be able to make an accessible front end for pdftk. This tool looks worthy to me, worthy of additional exploration because it performs functions otherwise not available on Linux/Unix platforms. -- Janina SajkaPhone: +1.240.715.1272 Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca 0.2.3
Tomas Cerha writes: Janina Sajka napsal(a): This will only be useful if if gui accessibility is still working. If the gui is broken so that orca isn't working for the use, no gui tool is going to help the user get it back. Hello, I believe the design of the Configuration infrastructure can be independent of the actual GUI. For example the solution proposed by Brailcom would allow to create a simple console-based or browser-based configuration frontend. In addition, the user still has the option of editing the configuration file, doesn't he? Yes, absolutely. My central point is that configuration is most useful if it can be performed apart from the environment being configured. I like the browser suggestion very much for just this reason. So, my complaint with Willie's original point focused on three words only, gui configuration tool. The problem is simple, if the gui isn't working for the user, no gui tool will help fix it. We need a tool outside the gui environment. PS: This is also an opportunity for our f/oss environment to provide greater accessibility than people have come to expect on platforms like Windows and Macintosh. I believe those two environments rely on gui configuration tools, so I am not surprised people would talk about wanting gui configuration tools. But, it's the wrong approach. Janina Best regards, Tomas. -- Brailcom, o.p.s. http://www.brailcom.org Free(b)soft project http://www.freebsoft.org Eurochance project http://eurochance.brailcom.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.240.715.1272 Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca 0.2.3
I have no quarrel with meeting the expectations of users who might migrate to Linux from some other OS, as long as that doesn't require us dumbing our environment down. But, I have every quarrel with allowing their expectations to define what is, and is not meaningful and possible on our environment. I think we have a golden opportunity to raise the bar for accessibility over the next year or two, and I'm pushing for that. I want to see us deliver more accessibility than has been seen before by users of any OS. Seems to me the browser based configuration tool which Tomas Cerha mentioned makes the most sense. Works across allenvironments--even remotely, if someone can log in. PS: Don't forget who the first users are, and who will be providing all that tech support to all those hordes of converts your email contemplates. If existing Linux users are not well served, how are new, inexperienced users going to be well served? We need to expand our horizons,not limit them to the confines of old, outworn prejudices. Thomas Ward writes: Janina Sajka wrote: I believe those two environments rely on gui configuration tools, so I am not surprised people would talk about wanting gui configuration tools. But, it's the wrong approach. Hello. I wouldn't go as far to say it is the wrong approach, but I do believe it should not be the only means of configuration. There will be those Windows converts who's major gripe with Linux and other gnu operating systems is there is not enough gui configuration. There are the console die-hards that absolutely want the power of the console. The only medium between the two extremes is to provide both methods of configuration. We must remember a console die-hard can't convert a gui die-hard to a console die-hard and the other way around. So providing both I feel is the best solution here. One last point Janina's point of view generally stems from the contention if the gui isn't properly configured for access then the console must be used. This is true. However, if the gui is working with accessibility then there is nothing saying the gui screen reader like Orca can't be used to do configurations in a gui environment, and gui tools can be used. -- Janina SajkaPhone: +1.240.715.1272 Partner, Capital Accessibility LLC http://CapitalAccessibility.Com Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada--Go to http://ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Orca 0.2.3
Willie Walker writes: == == * What's changed ? == == Orca 0.2.3 == * Many changes to the way settings are handled, including allowing them to be dynamically reloaded at run time. * Nascent support for configuration GUI (still needs work). This will only be useful if if gui accessibility is still working. If the gui is broken so that orca isn't working for the use, no gui tool is going to help the user get it back. Strongly suggest you build a console tool for orca setting first. Your initial group of users, your initial group of champions, are all console users with robust, reliable console accessibility at their fingertips. Put the tools where they can be utilized. Requiring a working gui so you can configure the gui is like telling a wheel chair user the courthouse is accessible once you get up that first flight of stairs. Janina ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: FC4, inaccessibility of core system utilities?
Perhaps so, Al. However, I would question the value of starting with apps such as you name, because the functionality these apps provide is fully accessible at the console. So, that reduces us to every application for a particular purpose needs to be accessible, which I don't believe is particularly defensible. In other words, we need to be able to perform the tasks, not use some particular app. To be spe;cific, let me take the three you've named: package manager Your console options include rpm, yum, and the old Redhat up2date. Both rpm and yum are fully accessible, imho. user manager You've got all the traditional tools, useradd, passwd, to say nothing of the ability to edit the relevant files directly (/etc/passwd, /etc/group, etc.). So, what's the problem? internet configuration wizard Here again, you have a plethera of tools that far exceed(I think) what the wizzard would do. In addition to tools like ifconfig and iptables, you've get a very accessible (imho) config tool via menu by typing setup at any console prompt. If we need to pick a battle, I couldn't support picking this one. Al Puzzuoli writes: Hello , while working with Gnome on FC4, I am noticing that a lot of system utilities still don't appear to have been ported to GTK2 and are therefore inaccessible. Some of The ones I have encountered, just to name a few include: package manager, , user manager, internet configuration wizard... The list goes on. My questions are: 1. Are most of the effected applications specific to the fedora distribution or just part of Gnome in general? 2. In either case as a concerned user, how can I help?I know that posting here is sort of like preaching to the quire, so are there other lists on which it would help to increase awareness by posting these concerns? Thanks in advance for any thoughts, --Al ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: FC4, inaccessibility of core system utilities?
Hi, Al: Al Puzzuoli writes: How can we claim an accessible desktop when simple tasks such as managing users and configuring network resources can't be accomplished accessibly Can't be accomplished accessibly? Don't you mean that you can't accomplish them with certain tools? That's not the same as can't accomplish accessibly. Of course package management, device configuration, user management, and all those sysadmin tasks are important. Indeed, they define a great and necessary portion of accessibility in any OS. However, it is not true, as you assert, that these tasks are inaccessible. In case you haven't noticed this yet, the f/oss environment tends to offer many tools for accomplishing the same tasks. If any particular tool happens to be inaccessible, therefore, it does not follow that accomplishing the task itself is inaccessible. That's fallacious and I must challenge you on such assertions. But, if you must have the graphical tools for these tasks, well the source is out there readily available to you and everyone else. Making them accessible is certainly a far lessor challenge than writing an accessible browser. So, have at it. PS: Who said we had an accessible desktop anyway? I don't believe that would be accurate. I believe it's a goal toward which we're making progress, not a fete accomplis. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: can't get multimedia working with any browser
You don't need to reboot to get back in control after a Gnopernicus crash. On Fedora -- Go to the cli and issue: telinit 3 To get back to the gui you then issue: telinit 5 Thomas Ward writes: Hi Jude, I can tell you that your problem is not unique, and it doesn't seam to be memory related. I have ran Fedora and Mandriva with systems of 512 MB or greater and Gnopernicus 0.9.12 and greater seam to high dive for no reason at all. An example I was opening evolution like I did several times that day, and suddenly gnopernicus bit the dust. No speech, no responce, and wouldn't even exit properly. I crashed out of x, logged back in, and gnopernicus says it can't load festival. I ended up rebooting the machine. Which I do about four times a day on average do to gnopernicus high diving and not coming back for one reason or another. To bad I can't use mozilla, Open Office, and other gui apps at the shell as I would happily stay there with speakup or something than put up gnopernicus crashing about 5 times aday. Anyway, I wouldn't recommend using Firefox as it simply doesn't work with gnopernicus. I am currently adding multimedia for Mandriva, and I am hoping to plug it in to Sun Mozilla. I'll be sure to let you know if I get something reasonable working in x. Hth. - Original Message - From: Jude DaShiell [EMAIL PROTECTED] To: gnome-accessibility-list@gnome.org Sent: Saturday, June 04, 2005 11:56 PM Subject: can't get multimedia working with any browser Having downloaded and installed mailcap-stuff.tar.gz I first tried listening to a realplayer stream using lynx. No go, display wasn't set. Okay no problem I figure I can go into xwindows and use gnopernicus and maybe firefox or epiphany. Maybe one of those browsers will work but hitting the f7 key to try to get some screen output seems on this system to actually be the crash gnopernicus immediately key. I could understand the desire of gnopernicus to do a high dive if all that was on this system was 128MB of ram which was the case earlier this week. However there's now 416MB of ram available in lower memory and this is happening. This is a fedora core 3 installation that has been modified for multimedia via the extra yum repositories. The network was opened with ifup ppp0 before startx ever ran. So what prerequisite configuration of gnome did I most likely neglect? ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.1 - Release Date: 6/3/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.1 - Release Date: 6/3/2005 ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org Janina SajkaPhone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: More issues with magnifier..
Hi, Christopher: I've noticed that no one has responded to your post, so I'm going to offer some thoughts. I don't know the proper resolution to your issue--which is why I haven't responded previously, but I do have a suggestion. I have nothing to suggest regarding your mouse. If you're able to log out with the lockups you're reporting, may I suggest opening a console and checking for process ids before logging back in? I would be willing to bet that there some pids that haven't been closed. I ran into exactly this behavior about a year ago which I did report here, though no one ever responded to my post on the subject. Here's my suggested sequence: log out Open a console, if you don't already have one. Do an: ps aux Look for Gnopernicus and bonobo related pids. When this happened to me it was quite obvious that there were listed processes that could be troublesome, such as a speech driver. Close them by hand with: kill -9 [process.id] Switch back to your graphical console and login to gnome hth. Janina Christopher Wagner writes: Hi folks! Thanks to your help, I've come a long way on getting the Gnome accessibility features to work for me in a work envrionment. My vision is decreasing rather severely due to rapidly forming cataracts. Naturally, due to this, I haven't really had the opportunity to plan this out more carefully. Now, with the accessibility features being an absolute neccessity for still performing my job functions, I am able to continue work. With that said, I've got a couple of issues I still haven't been able to resolve. :) The biggest for me now is with the magnifier intermittently freezing on me. It will still magnify, but it will stop following the mouse. It seems completely random, though it seems to happen more often when burning CDs or doing other resource intensive activities. The other issue I have is that occasionally a few items on my panel will lock up. Namely the workplace switcher, and my task buttons. They both lock at the same time. Getting the panel to reload properly usually requires a reboot as Gnome seems to think the panel is still running when I logout and login. This happens less often than the above problem, but I can find no reason or rhyme. This happens seemingly irrespective of resource usage. If these problems seem related to some other function of Gnome, and aren't neccessarily Accessibility related, please point me in the right direction. These issues may even be solved in the latest releases, but I'm sticking to the packages available with Debian testing. If updated packages are available in unstable, I may consider using them, but I don't want to compile from source unless absolutely necessary. :) All suggestions, advice, etc, will be gladly and thankfully listened to! :) Thanks again folks! - Christopher Wagner ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org If Linux can't solve your computing problem, you need a different problem. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: New user
Hi, Andrew: Long time no type, as I've been off the bcab list for awhile now. My summation for you is that you will get solid, robust accessibility on the Linux console, and reliable, but still rudimentary access via Gnome. Some of us are now using a few functions under Gnome regularly. I think all of us are also console users. No problem. This is Linux, and you can well afford to have both. Indeed, it's arguable you should be conversant with both console and gui. As to which distribution of Linux to adopt, my advice has long been to choose that for which you can best get assistance. The rest is personal preference. There are users here of multiple flavors of Linux, including Fedora, Debian, Slackware, and Gentoo primarily. As you may recall, I maintain an installation HOWTO which can be found at: http://www.linux-speakup.org/ftp/disks/fedora/HOWTO_INSTALL.html I think you'll find this HOWTO helpful, whichever distribution you ultimately select. PS: My personal advice would be Fedora, which I'm sure comes as no surprise. I have two reasons--you'll get a very full suite of software even before you know to go looking for it, and you'll get up to date drivers for all kinds of supported hardware--which is not to say that all hardware is supported on Linux, because that's not the case. However, the others are also sound distributions with their own strong points. Andrew Hodgson writes: Hi, Not sure whether this is the right place to ask this - but I am thinking of installing a Speakup modified Linux distribution with Gnome support. This will probably be Debian, but I am reluctant to use Woody on this moddern machine (AMD64 w/2gb ram). If I want to go down this road (either with or without Speakup support) using an external synth, what is the best option? I am fairly used to the command line but not really used the Linux desktop before. Any ideas? Thanks. Andrew. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -- Janina SajkaPhone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org If Linux can't solve your computing problem, you need a different problem. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Speakup Modified Available At CheapBytes
Dear Colleagues: The Speakup Modified Fedora Distribution is now available for purchase on CD ROM from Cheap Bytes at the following URL: http://cart.cheapbytes.com/cgi-bin/cart/0070011139.html If you've had difficulty downloading the installation images for our distribution, ior if you'd just rather not bother with downloading over 2 gigabytes of installation data, you now have the option to purchase it directly on media. We will shortly update our web site to provide this link there. -- Janina SajkaPhone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org If Linux can't solve your computing problem, you need a different problem. ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
