Chad wrote: >Since JAWS is not written by MS.
Freedom Scientific is on record as stating: i) They will never support platforms other than Microsoft; ii) Then will never support programs that are not coded _and_ sold by Microsoft; Which means that they are effectively a microsoft subsidiary. > Where is this reader? XSLT filters are currently available. FLOSS Speech output code is available. All of the components of such a reader are currently available. It simply is a matter of picking them up, and putting them together. [I wouldn't be surprised to find both Python and perl libraries that contain all of the required components.] >And how does this reader help them create ODF documents and edit existing ODF files? a) The issue is not creating the documents, but being able to find the tools to create the documents. b) If the menu contains every option that the icons have, then the icons are irrelevant to a11y. >Does it read the buttons in OOo for them? Those buttons could be read with a screen reader _IF_ the OOo developers properly labelled them. Sorry, but graphic109, graphic 1119, graphic1202 does not constitute "proper labelling" in my book. > JAWS reevents itself with each edition of MS Office, because *that* is what > most people use. Freedom scientific adds those new features, to keep up with new microsoft products. The major reason JAWS has the market penetration it has, is because it is purchased by third parties for third parties. [The person who is buying it ignores both price and cost.] xan jonathon -- Does your Office Suite conform to ISO Standards?
