{"id":741,"date":"2007-10-22T04:11:00","date_gmt":"2007-10-22T04:11:00","guid":{"rendered":"https:\/\/pneumasolutions.com\/?p=741"},"modified":"2024-11-26T04:13:56","modified_gmt":"2024-11-26T04:13:56","slug":"the-problem-with-open-source-access-technology","status":"publish","type":"post","link":"https:\/\/pneumasolutions.com\/it\/the-problem-with-open-source-access-technology\/","title":{"rendered":"Il problema della tecnologia di accesso open source"},"content":{"rendered":"

I recently read an interesting blog post by Chris Hofstader<\/a>, which is in part inspired by Mike Calvo\u2019s recent article La crisi imminente<\/a>. He argued that open-source access technology is starting to gain traction and that open-source AT might be a viable solution to our industry\u2019s current problems. In response, I believe it\u2019s extremely unlikely that an open-source or non-profit project would match the usefulness and usability of commercial AT. In this post, I will try to explain why.<\/p>\n\n\n\n

Let\u2019s consider this statement from Chris\u2019s post:<\/p>\n\n\n\n

\n

\u201cIt would also be useful if Microsoft made Narrator open source, slapped on GPL and let the bazillion Windows hackers around the world take a crack at it. There are a ton of blind programmers who program for Windows who would enjoy the opportunity to hack away at a stable, albeit feature poor, screen reader.\u201d<\/p>\n<\/blockquote>\n\n\n\n

(end of quote)<\/p>\n\n\n\n

Does this strike anyone else as naive? Sure, there are a bazillion Windows programmers around the world, but how many of them would have any interest whatsoever in Narrator? Moreover, who would coordinate all of those contributions to produce something that\u2019s useful to non-geeks? NVDA seems to fit the description of \u201cstable, yet feature poor\u201d; it\u2019s not as feature poor as Narrator, but it\u2019s still feature poor in comparison to its commercial counterparts. So if a ton of blind programmers would enjoy hacking away at such a screen reader, then why doesn\u2019t NVDA even have all of the features of System Access 1.0?<\/p>\n\n\n\n

Before I attempt to answer that question, let me defend the assertion I just made, that NVDA doesn\u2019t have all of the features that System Access had at version 1.0. My intent is not to belittle the efforts of Michael Curran and the other NVDA developers. In fact, Serotek has contributed code to the NVDA project in the past. However, I believe that the open-source development model is not well-suited for developing a screen reader. I make the comparison between NVDA and System Access 1.0 for two reasons. First, as sole developer of System Access thus far, I know its history very well. Second, even we at Serotek considered System Access 1.0 feature poor; though we marketed its strengths aggressively, we knew the product needed more work in certain areas. Yet System Access 1.0 had a few important features that NVDA does not. It seems, then, that this is the best possible comparison I can make between an open-source AT project and a commercial one. So let\u2019s zoom in to a level of detail that has been missing from this discussion thus far, to compare NVDA and System Access 1.0 on a few points.<\/p>\n\n\n\n

First, System Access 1.0 had an off-screen model<\/a> (OSM). To be sure, the OSM was in its infancy at version 1.0; it needed much work for version 2.0. Still, the OSM was very useful in some situations. It enabled access to some menus which don\u2019t expose item names through MSAA, such as those in RealPlayer. It was able to detect highlighted text, such as in custom list views. It made owner-drawn status bars, such as the one in Skype, accessible. It helped us provide access to the spell checker in Word 2002. In short, an off-screen model is a very important feature that\u2019s missing in all of the current free screen readers for Windows. System Access 1.0 had one because we knew it was a must-have, and we realized that even a primitive OSM was appreciably better than no OSM.<\/p>\n\n\n\n

Second, System Access 1.0 provided automatic access to the Microsoft Word spell checker. I remember well the time that I spent making System Access work well with the spell checker in different versions of Word; the aforementioned Word 2002 was especially problematic. We knew that the spell checker is one of the most important features of Word and that any serious screen reader alternative for Windows needs to support Word well. In contrast, NVDA doesn\u2019t seem to support the spell checker at all. If you press F7 in a document with a misspelled word, you will eventually hear the content of the \u201cnot in dictionary\u201d edit box, after NVDA reads the rest of the dialog with a level of verbosity comparable to Narrator. However, as far as I know, NVDA cannot spell the misspelled word. This feature isn\u2019t nearly as difficult as the OSM, so why hasn\u2019t one of the blind programmers hacking away at NVDA attacked this feature yet?<\/p>\n\n\n\n

Third, System Access 1.0 generally presented information in a more intuitive, efficient way than NVDA does. I realize that this is the most subjective of the three features I\u2019ve mentioned, but I also believe it\u2019s more important than the other two. As I mentioned before, NVDA\u2019s verbosity is comparable to Narrator\u2019s. The result of such verbosity is that users must either listen through a lot of extraneous speech to hear what they want, or master the keyboard commands that are needed to obtain the desired information. Thus, System Access has always aimed to present relevant information automatically while not being too verbose. This is a delicate balancing act, but it\u2019s necessary for a product that aims to be useful to a large number of people.<\/p>\n\n\n\n

So why doesn\u2019t NVDA have these important features of System Access 1.0, which was developed in about three months and released in January 2005? Jamie Zawinski, one of the original programmers at Netscape, gives us a few clues in his rant \u201cResignation and Postmortem<\/a>.\u201d Among his list of common excuses for why the Mozilla project didn\u2019t even release a beta in its first year is this one:<\/p>\n\n\n\n

\n

\u201cPeople only really contribute when they get something out of it. When someone is first beginning to contribute, they especially need to see some kind of payback, some kind of positive reinforcement, right away.\u201d<\/p>\n<\/blockquote>\n\n\n\n

(end of quote)<\/p>\n\n\n\n

Unfortunately, many of the features that are most needed in a screen reader, especially a Windows screen reader, are not the kind that can be casually hacked together with an immediate payback to the contributor. Consider the off-screen model. It took me at least a week of full-time work to develop even the primitive OSM that shipped in System Access 1.0. Thus, after a large number of easily implemented features are done, it becomes much harder for casual contributors to help the project, and the features that remain undone are the hard but important ones.<\/p>\n\n\n\n

Elsewhere in his rant, Zawinski said:<\/p>\n\n\n\n

\n

\u201cThere exist counterexamples to this, but in general, great things are accomplished by small groups of people who are driven, who have unity of purpose. The more people involved, the slower and stupider their union is.\u201d<\/p>\n<\/blockquote>\n\n\n\n

(end of quote)<\/p>\n\n\n\n

Oddly, he wasn\u2019t talking about the Mozilla project here; he was talking about Netscape the company. Still, though he may not have realized it, I believe the same principle applies to open-source projects. What we need is not a large number of volunteers hacking away at an open-source screen reader; we need a small team of dedicated, motivated programmers. And to be sufficiently dedicated to the project, said programmers probably need to be paid to work on it full-time.<\/p>\n\n\n\n

We need to consider, then, who currently funds work on open-source AT, and what effect the source of the funding has on the outcome. The most obvious example is Sun. Based on the rate at which Sun\u2019s work on GNOME accessibility has moved forward over the past seven years, it\u2019s safe to say that Sun\u2019s GNOME accessibility team isn\u2019t sufficiently \u201cdriven,\u201d with \u201cunity of purpose,\u201d to use Zawinski\u2019s words. Considering that Sun is a large hardware and software company whose core business is not accessibility, it\u2019s safe to suppose that their chief motivation for funding work on GNOME accessibility is to be compliant with certain legislation, in order to increase sales to government agencies. Thus, those who make high-level decisions about accessibility probably don\u2019t care much about producing something that\u2019s actually useful to blind and low-vision people.<\/p>\n\n\n\n

Consider the history of screen reader development for the GNOME desktop. As Chris rightly noted, the Gnopernicus screen reader failed quite miserably. Yet as of mid-2003, Sun could claim that GNOME was accessible to blind users, albeit barely so. As far as I know, the situation didn\u2019t change substantially until mid-2004, when my good friend Marc Mulcahy, who worked for Sun on GNOME accessibility at the time, took the initiative to start developing Orca on his own. He had to get through much corporate red tape just to get Orca released. I\u2019ve seen evidence that there\u2019s still too much bureaucracy in the Sun GNOME accessibility team; refer to the Orca Documentation Series<\/a> to see what I mean. Perhaps bureaucracy is just another name for what Zawinski describes as a slow, stupid union of too many people. The history of Gnopernicus and Orca is an example of what happens when AT development is funded by a big corporation that has no incentive to deliver truly useful results. Incidentally, Marc left Sun in late 2004 to start working on what is now the LevelStar Icon PDA.<\/p>\n\n\n\n

Chris suggests that development of open-source AT could be coordinated by a foundation or consortium with support from corporations and governments around the world. But would the results be any better than what Sun has produced thus far? Would such an organization attract the right people, that is, great programmers who are driven to produce better AT that really improves people\u2019s lives? We must also wonder what kind of leadership such an organization would have. I suspect that especially if many large sponsors are involved, politics would get in the way, resulting in less than optimal leadership, which can be at least as harmful as bad or mediocre programmers.<\/p>\n\n\n\n

Another problem with the notion of no-cost AT as the norm is that it would take power away from blind and low-vision people as consumers. In a free market, where companies compete for the consumer\u2019s business, the consumer wins. If no-cost AT, open-source or otherwise, were the norm, then most blind and low-vision people would have no say in the development of the available products, because there would be no natural incentive for any particular company or organization to rise to the top. In this light, one might argue that even a temporary monopoly is better. Chris observes that FS and AI Squared have obtained virtual monopoly status in their markets. But they got there by developing great products. And why did they develop great products? To increase their sales during a period when the AT industry was fiercely competitive. Of course, now that they have monopoly status, these companies have apparently stopped innovating. But monopolies won\u2019t last; even empires fall. Perhaps the strongest motivation to develop an excellent product is the prospect of a temporary monopoly in an industry fueled by strong competition for the wallets of consumers. If this is so, then no-cost AT as the norm would be bad news indeed for blind and low-vision people, as it would kill the catalyst for innovation: competition for sales.<\/p>\n\n\n\n

Yet another problem with the notion of no-cost AT backed by a non-profit organization or government agency is that it perpetuates a sense of entitlement among blind and low-vision people. No, it\u2019s not our fault that we\u2019re blind or low-vision. But it\u2019s not society\u2019s fault either. We shouldn\u2019t depend on governments, philanthropists, or anyone else to solve our problems. They don\u2019t have our best interests at heart, anyway; only we do. Remember that by and large, politicians and philanthropists care most about what\u2019s in it for them, be it publicity, power, or an appeased conscience. There are exceptions, of course, but this is the rule. It stands to reason, then, that politicians and philanthropists wouldn\u2019t really care about providing technology that best meets our needs. No, it\u2019s up to us to buy and use technology, assistive or otherwise, that improves our lives.<\/p>\n\n\n\n

Mind you, I\u2019m by no means an advocate for the status quo. It\u2019s widely accepted that because most current AT products are so expensive, they\u2019re purchased mostly by government agencies. This, too, deprives blind and low-vision people of the power that normally belongs to consumers, and perpetuates a sense of entitlement, as discussed above. Furthermore, as Mike Calvo points out in La crisi imminente<\/a>, the community of blind and low-vision people at large is grossly underserved by current AT. Yes, FS and AI Squared dominate their markets, but these markets certainly don\u2019t represent blind and low-vision people at large. It\u2019s odd, then, that the most commonly cited reason for the high cost of AT is the small size of the market. If AT is developed for more than just a niche market, maybe competition will be effective again.<\/p>\n\n\n\n

The solution is neither high-cost AT that has a virtual monopoly on a small market, nor no-cost AT that isn\u2019t widely useful because it lacks the drive of competition for consumers. Rather, the solution is low-cost AT that competes for the business of a large and mostly untapped market. If this happens, then blind and low-vision people all over the world will ultimately win.<\/p>\n\n\n\n

<\/p>","protected":false},"excerpt":{"rendered":"

Di recente ho letto un interessante post sul blog di Chris Hofstader, che \u00e8 in parte ispirato al recente articolo di Mike Calvo The Coming...<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_convertkit_action_broadcast_export":false,"footnotes":""},"categories":[31,29],"tags":[361,105,136,362,185],"class_list":["post-741","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-sero","tag-chris-hofstader","tag-nvda","tag-open-source","tag-osm","tag-system-access"],"taxonomy_info":{"category":[{"value":31,"label":"Accessibility"},{"value":29,"label":"Serotek"}],"post_tag":[{"value":361,"label":"Chris Hofstader"},{"value":105,"label":"NVDA"},{"value":136,"label":"Open-source"},{"value":362,"label":"OSM"},{"value":185,"label":"System Access"}]},"featured_image_src_large":false,"author_info":{"display_name":"Pneuma Solutions Team","author_link":"https:\/\/pneumasolutions.com\/it\/author\/pneumafier\/"},"comment_info":0,"category_info":[{"term_id":31,"name":"Accessibility","slug":"accessibility","term_group":0,"term_taxonomy_id":31,"taxonomy":"category","description":"","parent":0,"count":50,"filter":"raw","cat_ID":31,"category_count":50,"category_description":"","cat_name":"Accessibility","category_nicename":"accessibility","category_parent":0},{"term_id":29,"name":"Serotek","slug":"sero","term_group":0,"term_taxonomy_id":29,"taxonomy":"category","description":"","parent":0,"count":99,"filter":"raw","cat_ID":29,"category_count":99,"category_description":"","cat_name":"Serotek","category_nicename":"sero","category_parent":0}],"tag_info":[{"term_id":361,"name":"Chris Hofstader","slug":"chris-hofstader","term_group":0,"term_taxonomy_id":361,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":105,"name":"NVDA","slug":"nvda","term_group":0,"term_taxonomy_id":105,"taxonomy":"post_tag","description":"","parent":0,"count":6,"filter":"raw"},{"term_id":136,"name":"Open-source","slug":"open-source","term_group":0,"term_taxonomy_id":136,"taxonomy":"post_tag","description":"","parent":0,"count":2,"filter":"raw"},{"term_id":362,"name":"OSM","slug":"osm","term_group":0,"term_taxonomy_id":362,"taxonomy":"post_tag","description":"","parent":0,"count":1,"filter":"raw"},{"term_id":185,"name":"System Access","slug":"system-access","term_group":0,"term_taxonomy_id":185,"taxonomy":"post_tag","description":"","parent":0,"count":30,"filter":"raw"}],"_links":{"self":[{"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/posts\/741","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/comments?post=741"}],"version-history":[{"count":1,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/posts\/741\/revisions"}],"predecessor-version":[{"id":742,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/posts\/741\/revisions\/742"}],"wp:attachment":[{"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/media?parent=741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/categories?post=741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pneumasolutions.com\/it\/wp-json\/wp\/v2\/tags?post=741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}