Slashdot Mirror
Open Source Accessibility
tbray writes "The strongest push-back against Massachusetts' effort to institute open, non-proprietary document formats has come from the accessibility community, who claim that Open-Source desktop software lags behind Windows; and thus that a transition to Open Document will amount to discrimination against the blind and those with other disabilities. This is serious stuff. Peter Korn, who's an Accessibility Architect at Sun, has written a massive piece that provides a general introduction to the subject, a discussion of how Open Source is doing on the the accessibility front (things could be worse, but they could be a lot better), and finally, a detailed look at the (interesting) history and (uncertain) future of these issues in Massachusetts. Anyone in Open Source who thinks they can ignore accessibility issues is probably wrong. Getting any younger? Eyes as good as they used to be? This is everybody's issue."
TFA actually has considerable praise for open source's accessibility in itself:
Another important question is the extent to which the Open Document file format itself supports or fails to support accessibility. This comes up for things like storing the alternate text tag for an image, or noting the relationships of labels with the objects they label in on-line forms. While a thorough examination of the file format specifically for these issues still needs to be done, much of ODF is based on standard web technologies like SMIL for audio and multimedia, and SVG for vector graphics, which have and continue to be vetted by the World Wide Web Accessibility Initiative processes. We also know that two of the existing applications that currently read/write ODF can export Tagged PDF files in support of PDF accessibility, and Adobe has already conducted some tests to verify that accessibility across that translation is preserved (and thus must exist in the original ODF file). Finally, at this very moment the OASIS Technical Committee that created ODF is looking into forming a specific subcommittee to examine ODF for just these accessibility issues and address any shortcomings found.
This is in stark contrast to proprietary file formats like those used by Microsoft Office. Those formats are totally opaque, with no peer review of accessibility issues possible. Thus we cannot objectively tell how well the Microsoft Office file format supports accessibility, or say whether it does a better or worse job than ODF.
Real Daleks don't climb stairs - they level the building.
Some were incensed at the American's with Disabilties Act (ADA) when it was passed, wondering why they had to go through all this trouble to accomodate a tiny fraction of the population. But the disabled population is not that small and it grows larger every year due to various factors most people don't think about or recognize.
Before getting back into computing, I spent 8 years in social services, working with the autistic and developmentally disabled. You don't realize what challenges there are to everyday living until you see how hard it is for anyone with any type of disability to do the simple tasks we "normals" take for granted.
Ultimately MA is going to have to decide whether it can afford to turn its back on a small slice of its populace or continue the process of inclusion. I'm hoping for the latter, since within the disabled spectrum, there are plenty of people still capable of working and being productive members of society.
Even if I lost the use of my legs, I could still program...
GetOuttaMySpace - The Anti-Social Network
Not to mention it's 10px Verdana. If you don't have Verdana installed on your system and another font is substituted, it looks about 2px smaller due to Verdana's larger than normal aspect ratio. Given that Mozilla's default is something like 15-16px and many people have to increase the size above the default, I think this isn't the best person to be preaching about accessibility.
Folks, if you have a website, even if it's just a weblog, the most effective thing you can do to increase accessibility is to read Dive Into Accessibility and apply the things you learn to your website.
Bogtha Bogtha Bogtha
Whenever an accessibility issue comes up, I have to remind everyone how it feels to operate a computer in accessibility mode. Turn on all the accessibility stuff you know about, then turn the monitor off and see how you do. We have blind people in our office that use computers with the monitor off -- until you've seen that in person, you can't understand how accessible computers /technology must be.
stuff |
I'm work for IBM as one of those 'accessibility experts' and am the module owner for accessibility in Firefox. IBM picked up the Firefox and Gecko accessibility work after AOL lost interest in anything Mozilla-related.
JAWS 7 in fact works with Firefox 1.5. Ask your friend to try that combination -- Firefox 1.5 RC 2 is avalable on mozilla.org. Your friend can also try Window-Eyes 5.5 with Firefox 1.5 -- it works great.
It took me since 2001 to get all of the APIs implemented that were required for Mozilla accessibility on Windows. We also had tons of keyboard, focus and UI issues to fix. Then there is the new stuff -- accessibility for JavaScript/DHTML/AJAX applications. Firefox 1.5 is the first browser to provide the ability for authors to make custom DHTML widgets accessible. See http://www.mozilla.org/access. So we're going beyond the status quo.
For any application with any kind of document viewer or editor application with its own engine, accessibility requires a lot of work in the code. After that it requires a great deal of cooperation from screen reader companies so that two complex systems interact correctly.
Aaron Leventhal
http://www.mozilla.org/access