IBM®
Skip to main content
    Country/region [change]    Terms of use
 
 
 
    Home    Products    Services & solutions    Support & downloads    My account    

IBM Systems Journal
Accessibility   Volume 44, Number 3, 2005
Table of contents: HTMLPDF This article: HTMLPDF   Copyright info

Accessibility requirements for systems design to accommodate users with vision impairments - References

 by P. Brunet,
B. A. Feigenbaum,
K. Harris,
C. Laws,
R. Schwerdtfeger,
and L. Weiss
Cited references and notes

  1. OS/2 Version 1.0 was released in December 1987; IBM Screen Reader/2 Version 1.0 was made available in December 1992. Java Version 1.0 was available in January 1996, and the Java Accessibility API was available as part of the Java Foundation Classes, also known as JFC or Swing, in March 1998. GNOME 1.0 was available in March of 1999, and the GNOME Accessibility API was made available with GNOME 2.4 in September 2003.
  2. History of IBM Accessibility, IBM Accessibility Center, IBM Corporation, http://www.ibm.com/able/access_ibm/history.html.
  3. World Wide Web Consortium (W3C), http://www.w3.org.
  4. Web Accessibility Initiative (WAI), World Wide Web Consortium (W3C), http://www.w3.org/WAI/.
  5. Authoring Tool Accessibility Guidelines Working Group (AUWG), Web Accessibility Initiative, World Wide Web Consortium, http://www.w3c.org/WAI/AU/.
  6. Java Foundation Classes (JFC/Swing), Sun Microsystems, Inc., http://java.sun.com/products/jfc/.
  7. The Eclipse Platform Subproject, The Eclipse Foundation, http://www.eclipse.org/platform/index.php.
  8. B. A. Feigenbaum and M. A. Squillace, “IBM Reflexive User Interface Builder,” IBM alphaWorks (July 16, 2004), http://www.alphaworks.ibm.com/tech/rib.
  9. The Trace Research and Development Center at the University of Wisconsin maintains a list of accessible software guideline documents at http://trace.wisc.edu/world/computer_access/software/.
  10. Beyond ALT Text: Making the Web Easy to Use for Users with Disabilities: 75 Best Practices for Websites and Intranets, Based on Usability Studies with People Using Assistive Technology, Nielsen Norman Group Report, (2001), http://www.nngroup.com/reports/accessibility/.
  11. G. Vanderheiden, “Fundamental Principles and Priority Setting for Universal Usability,” Proceedings of the ACM 2000 Conference on Universal Usability, Arlington, VA, ACM Press, New York (2000), pp. 32–37.
  12. A. Savidis and C. Stephanidis, “Developing Dual User Interfaces for Integrating Blind and Sighted Users: The HOMER UIMS,” Proceedings of the ACM SIGCHI Conference on Human Factors in Computing Systems, Denver, CO, ACM Press, New York (1995), pp. 106–113.
  13. J. Goldthwaite, “Accessibility Standards for Operating Systems,” ACM SIGCAPH Newsletter 75, 2–3 (January 2003).
  14. L. Seeman, “The Semantic Web, Web Accessibility, and Device Independence,” Proceedings of the ACM International Cross-Disciplinary Workshop on Web Accessibility (2004), pp. 67–73.
  15. R. S. Schwerdtfeger, “Making the GUI Talk,” Byte Magazine (December 1991), ftp://ftp.software.ibm.com/sns/sr-os2/sr2doc/guitalk.txt.
  16. G. E. Krasner and S. T. Pope, “A Cookbook for Using the Model-View-Controller User Interface Paradigm in Smalltalk-80,” Journal of Object-Oriented Programming 1, No. 3, 26–49 (August 1988).
  17. B. Shneiderman, “Promoting Universal Usability with Multi-layer Interface Design,” Proceedings of the ACM Conference on Universal Usability (2003), pp. 1–8.
  18. ZoomText, Ai Squared, Inc., http://www.aisquared.com/.
  19. IBM Home Page Reader 3.04, IBM Accessibility Center, IBM Corporation, http://www.ibm.com/able/solution_offerings/hpr.html.
  20. WebBrowser Control Overviews and Tutorials, Microsoft Corporation, http://msdn.microsoft.com/workshop/browser/webbrowser/browser_control_ovw_entry.asp.
  21. MS-DOS (then known as PC-DOS) from Microsoft Corporation was introduced in August 1981.
  22. IBM Screen Reader (for DOS) was announced in 1987.
  23. Microsoft Accessibility, Microsoft Corporation, http://www.msdn.microsoft.com/library/en-us/dnanchor/html/accessibility.asp.
  24. Java Accessibility, Sun Microsystems, Inc., http://java.sun.com/j2se/1.4.2/docs/guide/access/index.html.
  25. GNOME Accessibility for Developers, The GNOME Project, http://developer.gnome.org/projects/gap/guide/gad/index.html.
  26. Disability Access to GNOME, The GNOME Project, http://developer.gnome.org/projects/gap/.
  27. Technical information for the Microsoft Longhorn project is available at http://msdn.microsoft.com/Longhorn/.
  28. Technical information for UI Automation can be found by searching or browsing the reference document at http://winfx.msdn.microsoft.com/.
  29. This description is taken from the World Wide Web Consortium's home page for semantic Web activity at http://www.w3.org/2001/sw/. For an introduction to RDF, refer to the “RDF Primer W3C Recommendation,” World Wide Web Consortium (February 2004), http://www.w3.org/TR/2004/REC-rdf-primer-20040210/.
  30. This specification is a work in progress by the W3C and not yet externally available.
  31. JAWS for Windows Overview, Freedom Scientific, Inc., http://www.freedomscientific.com/fs_products/software_jaws.asp.
  32. IBM Home Page Reader algorithms are described in the document “IBM Home Page Reader 3.04—Online Help for Developers,” IBM Corporation (January 2005), http://www-306.ibm.com/able/solution_offerings/hpr4devhelp.html.
  33. Scott Clark, “Java Talks the Talk with IBM's Self-Voicing Kit,” EarthWeb Developer News (January 1999), http://news.earthweb.com/dev-news/article.php/56261.
  34. R. S. Schwerdtfeger and P. D. Jenkins, “IBM's Self-Voicing Kit Technology for Java: IBM's Solution to Bring Cross-Platform Accessibility to Mainstream Computing,” California State University at Northridge Center on Disabilities 1999 Conference (CSUN 99) (March 1999), http://www.dinf.ne.jp/doc/english/Us_Eu/conf/csun_99/session0098.html.
  35. Section 508 of the Rehabilitation Act: Electronic and Information Technology Accessibility Standards, The Access Board (December 2000), http://www.access-board.gov/508.htm.
  36. User Agent Accessibility Guidelines 1.0 W3C Recommendation, World Wide Web Consortium (December 2002), http://www.w3.org/TR/2002/REC-UAAG10-20021217/.
  37. Web Guidelines References and Resources, IBM Accessibility Center, IBM Corporation, http://www.ibm.com/able/guidelines/web/webreferences.html.
  38. K. Harris, “Making Eclipse Accessible to People of all Abilities,” Presentation at EclipseCon 2004 (February 2004), http://www.eclipsecon.org/2004/EclipseCon_2004_TechnicalTrackPresentations/06_Harris.pdf.
  39. ParaSoft WebKing, http://www.parasoft.com/jsp/products/home.jsp?product=WebKing&itemId=105.
  40. J. J. Lazzaro, “Taking the Mystery Out of Microsoft Active Accessibility,” AccessWorld 1, No. 4, (July 2000), http://www.afb.org/afbpress/pub.asp?DocID=AW010404.
  41. D. Klementiev, “Software Driving Software: Active Accessibility-Compliant Apps Give Programmers New Tools to Manipulate Software,” MSDN Magazine (April 2000), http://msdn.microsoft.com/msdnmag/issues/0400/aaccess/default.aspx.
  42. Disk Operating System, free-definition, http://www.free-definition.com/disk-operating-system.html.
  43. P. Schroeder, “A Brief History of Microsoft and Accessibility,” AccessWorld 1, No. 4, (July 2000), http://www.afb.org/afbpress/pub.asp?DocID=AW010402.
  44. P. Corr, “Macintosh Utilities for Special Needs Users,” http://homepage.mac.com/corrp/macsupt/columns/specneeds.html.
  45. R. Bellinger, “Microsoft Grudgingly Given Credit for Features in Windows 95 for Disabled,” EE Times (March 22, 1995).
  46. D. Kendrick, “Inside Microsoft: An Accommodating Workplace for People Who Are Blind?” AccessWorld 1, No. 4, (July 2000), http://www.afb.org/afbpress/pub.asp?DocID=AW010406.
  47. Accessibility Aids May Not Work with Office Programs, Microsoft Corporation, http://support.microsoft.com/kb/q169975/.
  48. Active Accessibility 1.3 SDK, Microsoft Corp (April 2003), http://www.microsoft.com/downloads/details.aspx?FamilyId=4179742F-1F3D-4115-A8BA-2F7A6022B533&displaylang=en.
  49. “Microsoft Active Accessibility Version 1.2 is Now Available!” http://teddy.fcc.ro/articles/MSAA.html.
  50. Automating Word Using the Word Object Model, http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_wrcore/html/wroriAutomatingWordUsingWordObjectModel.asp.
  51. “Get Ready to Swing (1.0),” JavaWorld (March 1998), http://www.javaworld.com/javaworld/jw-03-1998/jw-03-swinggui-p2.html.
  52. R. S. Schwerdtfeger and P. D. Jenkins, “100% Pure Java: IBM's Focus to Develop Accessibility for the Next Generation,” California State University at Northridge Center on Disabilities 1998 Conference (CSUN 98) (March 1998), online proceedings, http://www.dinf.ne.jp/doc/english/Us_Eu/conf/csun_98/csun98_051.htm#_Toc412382694.
  53. R. S. Schwerdtfeger, IBM Guidelines for Writing Accessible Applications Using 100% Pure Java, IBM Accessibility Center, IBM Corporation (August 2000), http://www-306.ibm.com/able/guidelines/java/snsjavag.html.
  54. P. Korn, “JDK 1.2.2, JFC 1.1.1, and Access Bridge EA1 released!” JAVA-ACCESS accessibility interest mailing list archives (August 1999), http://archives.java.sun.com/cgi-bin/wa?A2=ind9908&L=java-access&F=&S=&P=69.
  55. Accessible Copy of the Microsoft Active Accessibility SDK Documentation, Microsoft Corporation (April 2003), http://www.microsoft.com/downloads/details.aspx?FamilyId=8BC82E65-DBEB-4BC4-9F27-8AC7DF6B7B77&displaylang=en.


    About IBM    Privacy    Contact