T. Joseph CARTER wrote:
And with your helpful assurance, the current inaccessible version of
OpenDocument is pushed into state mandates where it takes an Act of God or
an Act of State Government to get a new version of the standard (which
probably won't fix these kinds of problems anyway) to be adopted.
The CIO of Mass. has publicly stated that ODF will not be implemented
for disabled workers until there is a reasonable, accessible alternative.
Further, he has made good accessibility support a key point of the
contracts currently being bid for implementation.
On behalf of the blind, thanks a lot. At least with word documents we had
a chance of sorting these things out if someone bothered to set the
metadata on their images, and form entries just didn't exist.
I was under the impression that the screen readers and other tools
available for Office and kin were rather hackish and that a change in
the file formats generally made a mess of things until someone
reverse-engineered the changes.
Is this not the case?
Yeah, I know, this is open source--if I have a problem with it I need to
go and learn the codebase, figure out how to solve the problem, gather
support within the community for my proposed solution to it, write a
patch. and try to plead my case for it to be incorporated upstream. Then
I can try to get the state to use the new version. As if.
You could join the current working group for accessibility issues and
make your concerns known.
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office-accessibility
-ajb
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
