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."

34 of 319 comments (clear)

  1. So let's fix it. by Ritz_Just_Ritz · · Score: 5, Interesting

    I'm not an expert (as a matter of fact, I'm not even qualified to be called ignorant on the subject), but what can we do to make things better? Surely this is not an insurmountable problem and given the rather substantial savings for government institutions (ignoring the lobbying payola), you would think the people with the purse strings would have an interest in this answer as well.

    1. Re:So let's fix it. by StormReaver · · Score: 4, Insightful

      "...you would think the people with the purse strings would have an interest in this answer as well."

      You and many others are falling victim to Microsoft's red herrings. Open Source has absolutely nothing to do with OpenDocument. Here are some answers (yet again):

      1) OpenDocument is a format specification, not a program.

      2) Any program, Open Source or proprietary, can implement OpenDocument filters. That is all that is necessary to support OpenDocument.

      3) Microsoft is fighting OpenDocument by changing the subject. This is being done to maintain Microsoft's monopoly stranglehold on one of its two profitable rackets.

      4) If people think Microsoft Office has better accessibility than OO.o/StarOffice, then they can continue using Microsoft Office. All Microsoft, and any other proprietary company, has to do is write an I/O filter to work with the OpenDocument format.

      We need to keep our focus, and not allow ourselves to get diverted into senseless debates about irrelevancies.

    2. Re:So let's fix it. by flytopia · · Score: 3, Informative

      I think it's down to the fact that most 3rd party accessibility tools are written for Windows/MS Office. This is a result of Microsoft having the greatest market share, rather than any specific features that MS Office has over OpenOffice.

      Still, if the lack of accessibility tools is a barrier to increased market share, then it's down to the Open Source community to provide them. And this doesn't have to mean unpaid coders - these tools could come from Sun, Novell, IBM etc.

    3. Re:So let's fix it. by xtracto · · Score: 3, Informative

      Agree.

      Same thing happens with software documentation:

      Analysis, Requirements specifications document.
      Design: Design Specification document [with or without UML, DTDs, etc].
      Quality control/assurance: (Quality testing metrics documents).

      Nobody (at least not programmers) likes to spend their time doing that, which results in a lot of good Open Source projects (just look at sf.net) that have only the source code available. So, when/if someone wants to start helping (be it a programmer or a non programmer) they must dive into the source code, reverse engineer it and (to their better understanding) see how is the program working.

      When developing a propietary software for anyone, documentation is the one most important thing, and often the one that programmers hate to do. That is why System designers are better paid than programmers.

      In open-source world, nobody cares about documenting [and mantaining the domcumentation] of their software. My personal experience is with VirtualDimension multi-desktop software. I wanted to enhance the program with some ideas I had, but I hated that the only place to understand how it worket was the CVS repository C++ files. Although I know C++ (and I am good at it if-u-ask-me) it is the "logic" of the program what I wanted to find and, well, my time is worth more than what I needed to understand the inners of the program.

      The same happened with jabref. I would like to contribute to those projects with programming, but bah, at the end, all of them are just a mess.

      Returning to the accessibility issue. The only way accessibility could be handled is by creating a base framework (from the GTK, or QT or JSwing or any other GUI toolkits) that provides accessiblity features to the interfaces. This means that the application developers will not need to worry (too much) about accessibility because the "text control" will contain the features by default*(and this is the "most-most-important-issue"*. And, the programmer will just have to addere to a set of minimum accessibility rules (like using system defined colors and fonts [something, the great Mark's sysinternals process explorer doesn't do for example, as after I changed my font DPI to 144, the process list font is not changed and I also use background color as Black and font as white, but it is not adopted by this program)).

      * Talking on this "default state" of the features, it is the same story with accessibility as with security. For an example, I know that Java has some interfaces wich allow for accesibility properties (although I have not used them). It also has some classes for secure comunication. But these are not the DEFAULT classes which everyone uses.

      Iff Java had implemented security and accessibility in the common controls/classes used by everyone, of course it would be more work for the developers but it would help them to LEARN to implement those features.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
  2. Speaking of Accessibility by Lord+Byron+II · · Score: 5, Funny

    Light grey text on a white background with salmon-colored links. That's just great on the ol' eyes!

    1. Re:Speaking of Accessibility by Bogtha · · Score: 4, Informative

      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
  3. Accessibility isn't needed for everyone by alexwcovington · · Score: 5, Insightful

    and for the remainder of people, OpenOffice.org will work just as well under Windows for the folks that need the Accesibility tools, until Linux catches up (not long)

    --
    (It's never too late to join the Renaissance)
    1. Re:Accessibility isn't needed for everyone by Bert64 · · Score: 3, Interesting

      Surely opensource is a plus in this area..
      Those charities that push for and fund interoperability efforts could have a much more direct impact on opensource, instead of spending large amounts of money trying to convince vendors to implement accessibility features which may not directly meet their needs, they could actually hire coders to create these features exactly according to their specifications.

      Instead of this, these groups seem to be spending all their time and money lobbying.. Why not produce open source accessibility software that not only suits your requirements exactly, but also benefits other people too?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  4. Bigger command line text by doktorstop · · Score: 3, Insightful

    I can see it coming =) Seriously, I dont think that accessibility is the biggest obstacle, or the primary target. Inconsistancies in the GUI make it difficult for people to get used to Linux, even if they have no sight or hearing handicaps.

    --
    http://www.automatiq.se
    1. Re:Bigger command line text by Feyr · · Score: 3, Insightful

      i said it when it was first posted to technocrat, i'll say it again.

      accessibility doesn't have ANYTHING to do in a STORAGE FORMAT. this is purely a software issue, with lots of money involved.

      how much do you wanna bet these so called "accessibility experts" are getting paid to say they don't want an open document format? who do you think is paying them?

      and a sun accessibility expert? come on, this is the company that brought us JAVA, an accessibility nightmare in its own right.

  5. Not just OSS in Mass? by DaveCar · · Score: 3, Insightful

    In the Massachusetts case it doesn't just have to be OSS in use. Surely some office software vendor will provide support for OpenDocument AND accessibility.

    I mean there is more than one office software vendor isn't there?

    Yes, yes. I am new here ;)

    1. Re:Not just OSS in Mass? by NutscrapeSucks · · Score: 3, Informative

      Absolutely -- The cheapest and most obvious route to OpenDocument support for almost every organization is a translation filter for their existing MS Office apps.

      Since 3rd party filters are already in development, this whole scrum in Mass. is really pointless. Most agencies will probably just roll out the filter.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
  6. Then use closed source by mwvdlee · · Score: 3, Insightful

    MicroSofts' somewhat more accessible Office suite is free to implement the Open Document standard just like any and all other applications.

    You see, that's the beauty of it; any (specialized for a certain disability) application can implement the standard at no cost or risk besides the development itself.

    Personally, I'm waiting for a bunch of BSD-like licensed libraries that implement translation of Open Document from and to other common formats like HTML, plain text, LaTeX, PDF, etc so anybody can suffice with just a few lines of code to support the Open Document format.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  7. Re:on the other hand by BushCheney08 · · Score: 3, Funny

    on the other hand, open source means anyone (with the skills) can take matters in to their own hands...

    I don't have hands, you insensitive clod!

    --
    Be a real patriot: Question authority. Think for yourself. Formulate your own conclusions.
  8. Reading TFA... by meringuoid · · Score: 5, Informative
    ... it seems that the accessibility problems are not the fault of the open source programs or the Open Document Format, but the fault of the closed-source, proprietary Braille interpreters and screen readers which are incompatible.

    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.
  9. Marketshare by fireboy1919 · · Score: 3, Insightful

    These are highly specialized things. The reason there's not a lot of free software in this area is that there's just not a lot of demand for it at all, in either the Windows world, or the free one.

    I don't really see a problem, though. It seems reasonable to make an exception with open formats for those who need aid. We let seeing-eye dogs in where pets aren't allowed.

    And as far as the public face goes - dissemination of info to the public, that is - that should really be in 508 compliant HTML, shouldn't it? Which means no Word, PDF, openoffice, etc. anyway.

    --
    Mod me down and I will become more powerful than you can possibly imagine!
  10. The rights of the individual by Billosaur · · Score: 5, Informative

    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
  11. What really needs to be done by JWW · · Score: 4, Interesting

    What really needs to be done is for the accessibility lobby to put pressure on Microsoft to support Opendoc.

    Microsoft is using them. The one thing Microsoft can't have is an open format supported for Office documents. Office is the real monopoly, windows loses a lot of its lockin if it weren't for Office.

    Microsoft will fight this tooth and nail. What Mass. should do if the Opendoc inititave fails, is mandate that their provider of office software publically provide specifications for their file formats. If Microsoft refuses that, I think they should return to court on antitrust violations.

    I'm sick of Microsoft always getting away with playing dirty. And it is playing dirty to use people who have accessibility issues using a comptuer to maintain your monopoly.

  12. I'm not sure this is accurate by $RANDOMLUSER · · Score: 4, Interesting

    I've got a friend who has wet macular degeneration: he's slowly going blind, has been for years. He uses a 21-inch monitor, and every time he gets a new machine, I have to install his magnification software (sorry, the name escapes me). It costs several hundred dollars, and he's bought copies for NT 4, Win2K and XP through the years. He cussed for a solid ten minutes when I showed him KMagnifier, as it does everything his Windows magnifier does, and then some.

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
  13. Youth by troon · · Score: 3, Funny

    Getting any younger?

    Yes, I am.

    --
    Ydco co ,df C erb-y go. a Ekrpat t.fxrapev
  14. Sorry, but this makes my blood boil... by Noryungi · · Score: 5, Insightful

    [...] 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.

    How on earth can an open-source document format be a discrimination against the blind and/or handicapped?

    If it's a documented standard -- and it will be -- an open-source document format can actually be converted into other documented formats (ASCII text, ISO-8859-X text, CSV, RTF, HTML, etc, even sound waves through a vocal synthetizer) that are actually easier to use for blind users!!

    Compare and contrast this with the plight of handicapped people who are now using proprietary document formats, created by proprietary applications under proprietary operating systems... and who find out, the hard way, that their applications do not work anymore with their Braille readers under the newest version of the operating system. Or that they have to go through countless hoops to convert the proprietary document into another proprietary format, that they have no way to check for accuracy and/or problems. Or that can be endlessly confused by the changes that each version of ____________ [insert application name here] intoduces in its already confusing GUI.

    I worked for about a year and a half for a non-profit that was dedicated to improving the access of blind people to computer technology. Those were the days of DOS and BBS, a time many blind people remember as a true 'golden age', since most information was textual, and there was very little that could not be done with a simple Braille terminal emulator and/or speech synthetizer.

    Windows changed all that, for the worst. I knew people who used to be good programmers despite their handicaps who found themselves out of a job. Others that found themselves increasingly locked-out of the Internet revolution because the www was increasingly becoming graphical.

    And now, people attack Open Document on the basis that it creates discrimination against blind people? Come on, that is the most ridiculous argument I have heard in a long while. If anything, a truly universal, XML-based document format would be perfect for these users!

    In the worst possible case, I will volunteer to write converters to make sure these new documents can be exported into proprietary apps. And I am not joking: this was actually one of the things I did at the non-profit I mentioned above.

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
  15. Open source opportunity by jimand · · Score: 3, Insightful

    Now's the chance for open source advocates to show the power of open source. If enough volunteers step forward to resolve the accessibility issues in OpenOffice so that Massachusetts can go forward with their Open Document initiative then it will be a huge feather in the open source cap.

  16. I'd disagree by Peregr1n · · Score: 3, Insightful

    Having worked in accessibility for years I'd say that open source is the friend of accessibility. A document that can be easily read in any standards-compliant browser or application, or easily converted into accessible form (eg. speech), is most welcome.

    The main problem is documents which can only be opened in the particular application that generated them. Microsoft documents are an example of this; although as they're so popular, pretty much all accessibility companion-style programs sit on top of Word and change the style of delivery (style, size, clarity, to speech, etc) appropriately.

    So if everyone used open source, standards-compliant documents, there would be no need for the majority of accessibility programs. I think moving to open source document formats removes much of the accessibility problem at the source, rather than working round it, which is what most solutions do at the minute.

  17. Non Sequitor Argument? by rolfwind · · Score: 4, Insightful
    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


    What does one necessarily have to do with the other? Microsoft can put in the fileformat in their software just like OpenSource apps.
  18. Re:on the other hand by dyoung9090 · · Score: 3, Insightful

    And yet, they aren't taking the matters into their hands because it's not a problem they're dealing with, a bug they want to work-around or a nifty idea that would make thier life better. See, that's the thing about commercial products... they are, by their very nature, forced to consider what other people want or they don't exist. With the little home-brew jobbers, it's only going to get created if the author/authors feel they'll get something out of it and usually that's accomplishing some task they want done, not some task that some minority that they don't know somewhere may have a use for it.

  19. Give them large monitors by aphaenogaster · · Score: 4, Funny

    My grandfather started having eye problems around 90 so I bought him a used 21 inch ergo 1600 monitor. Set it to 800x600 and now he is a happy camper.

  20. Re:I can afford to ignore it. by Wudbaer · · Score: 3, Insightful

    ...until you happen to have that crippling accident or contract that nasty disease. I really hope neither will happen to you, but there are enough people that yesterday thought exactly like you and that today curse the city because of all the damned stairs they can't pass with their wheelchair.

  21. Yea, sounds great! by EraserMouseMan · · Score: 4, Interesting

    So here's what you want. You want highly-skilled developers to volunteer months of their time to write this free of charge. Then you'll turn around and charge MA $100/hr to implement OOo. Sounds wonderful. I'll get right on that. I love how all the Open Source junkies want developers to donate so they can charge big bucks to deploy the Open Source software.

    Everybody loves FOSS. How come there isn't an FOSC(Free Open Source Consulting) withing the OS movement? And don't talk about how you installed Red Hat for your grandma either. I'm talking about taking 3 months out of your personal time to help deploy a Linux solution for a mid-sized business and not charge them a dime. That's what the OSS developers do every day.

    1. Re:Yea, sounds great! by _Swank · · Score: 3, Insightful

      In fact, the politicians in Massachusetts are bright enough NOT to hire some programmers to develop whatever features are required. Governments are NOT IT shops and they don't usually have the expertise in either programming or managing programming projects to be able to do this in any way cost effectively. And it's not something they should try to get into - it's completely orthogonal to the business of governance. As such, it has nothing to do with being 'in the pockets' of anybody and all to do with 'that's not what we know how to do.'

  22. Re:on the other hand by antifoidulus · · Score: 4, Insightful

    Your comment is so vapid as to be worthless. Open source is just another software development/distribution model with it's own benefits and drawbacks. Nothing more, nothing less. People on here seem to think that by adding the word "open source" to something it will automagically be able to singlehandedly cure cancer, solve world hunger, and make Julian fries. It doesn't always work like that. Take your post for example:

    on the other hand, open source means anyone (with the skills) can take matters in to their own hands and address these issues to a higher standard than a commercial product, eventually.
    A claim so vague that it can't be verified or invalidated. WTF do you mean by "higher standard"? That seems to imply that there exists a single optimum solution to the problem that will make everyone happy. Well, if you have it I would like to hear it. Meanwhile, in the real world the "higher standards" dependend on both personal preference and problem domain. For example, is Linux at a "higher standard" than Windows? Depends on who you ask and in what context. Even in the open source world there are often competing(occaisionally conflicting) ideas on how to solve a particular problem, competition is good!

    Where as in a big profit motivated company may not want to spend time and money to go beyond covering the majority.
    Care to back this up? Or even explain how open source is really all that different? I have a lot of niche needs, and I find that open source doesn't cover them as often as it does. I use a propietary OS(Mac OS X) that covers a lot of my niche needs very well. I also use some other propietary software(in the realm of language learning) that is outside the majority, but it works rather well. There are open source alternatives, but they don't work as well for me personally. Does that mean they don't neccasarily work well for you? Of course not! Does the ideology put behind the product have any bearing on how well it functions? Again, not really. Thats not to say I don't use FOSS, on the contrary, I also use FOSS products that meet other demands that I have(I use emacs to write Ruby programs). So what was your point again?

    What is it with these vacuous fanboy comments on slashdot anyway?

  23. Obligatory monitor off reference by 192939495969798999 · · Score: 5, Informative

    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 |
  24. my 0.02$ by dogfull · · Score: 3, Insightful

    Can't really RTFA :-)

    Anyone with any visual impairments (like myself) can use ZoomText, or another comparable programm on windows, like they did with MS Office. No big difference, and not openoficce's job to fix.

    As for the blind.... I'm sure one could hack together a screen reader for ODT, at least? It's a bloody xml file, after all. Provided the screen reader/braille reader already works with windows, it should be trivial.

    What bothers me more personally is how IE systematically ignores the 'larger font sizé' option on a lot of webistes. I figure this is because of some use of css, but I didn't put too much effort in finding out what exactly causes the problem.

  25. re: 508 compliance is the right idea by shis-ka-bob · · Score: 4, Insightful
    I find is ironic that pro-Microsoft folks are touting handicap accessability. ASP and ASP.Net are notorious for generating remarkably bad HTML that is in no way compliant with 508 guidelines. As a quick and dirty test, open a web page in links (or any other text browser). If you can read it, it means that the 2 dimension 'web page' has been converted to a 1 dimensional 'text stream'. Braille terminals are able to represent these text streams quite successfully. Web sites built with some open source frameworks like Zope/Plone are almost automatically 508 compliant, but web applications developed with Visual Studio are rarely 508 Compliant. When you 'drag and drop' components onto a page, the relationship between the location and the order of the component in the 'text stream' is lost. So web development, as done by most developers using Visual Studio, results in pages that cannot easily be make 508 compliant.

    The Microsoft camp seems to be rather oportunistic in when they choose to extol the virtue of handicap-accessiblity

    --
    Think global, act loco
  26. Re:JAWS only works well with IE by R4modulator · · Score: 5, Informative

    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