[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: usability issues with JavaScript (fwd)
- Subject: RE: usability issues with JavaScript (fwd)
- From: Kelly Pierce <kelly@ripco.com>
- Date: Sat, 5 Feb 2000 21:47:21 -0600 (CST)
On Thu, 27 Jan 2000, Barrett, Don wrote: > Good question. Can we really tell folks they can't use Javascript, > especially when most Windows screen readers handle it okay. At what point > can we say that Windows is accessible enough so that we can't demand that > pages be all character-based and work with Lynx or other character-only > browsers. I am not taking sides, but merely raising the questions. Don, You raise a larger issue: when do we decide access in a given area has been achieved to a degree that while it is not optimal it is usable and generally considered "accessible." What is missing in your analysis is consideration of cost. Switching to Windows from dos or even buying an updated version of a Windows screen reader is not free. It can cost hundreds of dollars and easily approaches and sometimes exceeds a thousand dollars or more. Accessibility is one part of the legacy issue, cost is another. With three-quarters of blind persons unemployed, upgrade costs from legacy software are part of the access equation for many. Not everyone can afford the latest and greatest that will enable them to enjoy maximum accessibility. kelly
- Prev by Date: FW: EU moves on accessibiliy
- Next by Date: 61% of users could not buy (fwd)
- Previous by thread: RE: usability issues with JavaScript (fwd)
- Next by thread: Re: usability issues with JavaScript (fwd)
- Index(es):