This is a summary of a SIG session at CHI 99 on "Universal Web Access: Delivering Services to Everyone" attempting to make simultaneous progress on multiple dimensions of diversity: Multilingual/International/Multicultural, Handicapped/Disabled, Gender, Age, Economics, etc. Wednesday, May 19, 1999 2:30-4:00pm
At OCLC I work on the FirstSearch service user interface, in part on increasing the potential markets by offering French and Spanish versions, improved support for accessibility, additional functionality while maintaining support for low-end machines and legacy browsers. To accomplish this level of adaptability, we have developed some techniques for (1) separately specifying the functionality, the language strings, and the display format, and (2) setting parameters (e.g., dimensions, fonts, tables vs. lists) based on browser version, availability of JavaScript, screen size, etc. Web pages are dynamically constructed based on function, data, and user options. The user interface architecture evolved over time, with several periods of reworking sub-optimal choices. Even when organized, there is a large cognitive overhead to developers to separate form, function, and language.To learn about techniques for increasing adaptability, I've found it useful to explore features on volunteer-run services such as (1) The HCI Bibliography site and search service and (2) a CGI script for presenting accessible versions of a variety of usability questionnaires in multiple languages. Some details are available in notes from a BuckCHI Presentation on Universal Access .
It is sometimes difficult to motivate companies to work toward universal access, if they perceive the beneficiaries as a small and relatively invisible minority. Many people in the disability access communities have advocated the notion of "electronic curbcuts." Electronic curbcuts work like physical curbcuts: They are innovations that improve access for people with disabilities, but that also benefit huge numbers of other people (the temporarily able bodied, or TABs). I will describe some simple electronic curbcuts and their extended benefits (e.g., closed captioning). I will then propose a strategy that many of us can follow, to show companies how improving accessibility for people with disabilities can also lead to products and services with greater flexibility, increased functionality, and expanded markets.
While the rest of the presenters are tending to focus on issues surrounding getting people to the technology, I am concerned about what happens next: Just because someone has the computer or has access to the internet does not mean they understand how to use it. How can we identify what our users are bringing with them to this new environment? As developers, how can we work with that information to provide ramps to the new environment that they understand? My present work is focusing on how to make online courses accessible to those who are not familiar with the web.
Internationalization is really an issue of whether to pursue a product strategy of tailored (localized) products, or homogeneous (single-version) products. This is an ongoing, fundamental issue in marketing and manufacturing of all products, but it is not discussed as such in software design circles. Instead, there is a focus on poorly localized products that contain awkward cultural "signs". Also critical are the motivations of marketers and their cost/benefit analyses for decisions.