Eyetwoherbs wrote: > cannot even find how to shut it off.
">File >Exit" --- which is one of the things that JAWS 4.2 can read in OOo. [For non-JAWS users, this version is from circa 2001. The current version is 8.0.) >You have not made this very user friendly Nobody denies that OOo has a11y issues. In some areas, these are major issues. In this instance I think you are barking up the wrong tree. > with eye problems should have the same availability that others have. If you want to complain about the lack of support for Braille, Moon, or BlissSymbolics, then you have a legitimate concern. Likewise, if you want to complain about the lack of tools to translate to/from Braille, and/or Duxburry File Format, you have a legitimate concern. If you want to complain about the inability of OOo to print to a Braille Printer, you have a legitimate concern. To complain about things that are a result of defective screen reading software is not legitimate. To complain about things that are a function of a deliberate decision to design a user-hostile, anti-a11y operating system is not legitimate. [I'll also question the ethics of supporting an organization whose interests are antithetical to one's own.] > If you wish it to be used you need to get with the program For starters, the National Federation for the Blind needs to get with the program, and spend money developing software tools that blind people can use. The NFB would rather spend US$15,000 for a computer (hardware and software) for a blind person than budget US$200,000 for two programmers to work full time creating, or modifying existing FLOSS software so that it is more blind friendly. The real joke is that my Linux box is more accessible, then my house mates is, after installing the software that the NFB recommends. [Do you really want to use a keyboard from the NFB for Windows that says in the fine print "This product is not compatible with Windows"? (It worked fine with Linux.)] IIRC, the One Laptop Per Child project has got the cost of an a11y laptop to roughly US$200. Screen reader and standard keyboard. No Braille Monitor. No Perkins Keyboard. (For the rest of you the former adds roughly US$4,000 to the cost. A Perkins Keyboard adds roughly US$1,000 to the cost.) > and make it able for all to find the way out not hide it be hide areas > that are not viewable to people with dualities. A Braille Display Monitor should display the same things as a standard LCD or CRT monitor. If they don't, there is an issue with the design of the User Interface. Screen Readers will miss things that Braille Display Monitors pickup, because they look at the screen in a slightly different manner. Usually, a Braille Display Monitor will display the stuff on the floating screen, whereas the Screen Reader won't. For OOo, if the Screen Reader takes advantage of the Java Accessibility Bridge, then there are no hidden areas of the screen, using Linux. (I don't remember which --- if any Screen Readers for Windows do take advantage of the Java Accessibility Bridge. I wouldn't hold my breath waiting for Freedom Scientific to do so.) xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
