DOCSLIB.ORG

Techniques for User Agent Accessibility Guidelines

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Techniques for User Agent Accessibility Guidelines Techniques for User Agent Accessibility Guidelines W3C WD-WAI-USERAGENT-TECH-19980210 Techniques for User Agent Accessibility Guidelines W3C Working Draft 10-Feb-1999 This version: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech Latest version: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT/wai-useragent-tech Latest public version: http://www.w3.org/TR/WD-WAI-USERAGENT/wai-useragent-tech Previous version: http://www.w3.org/TR/1998/WD-WAI-USERAGENT-19981112 Latest "User Agent Accessibility Guidelines": http://www.w3.org/WAI/UA/WD-WAI-USERAGENT Latest public version of "User Agent Accessibility Guidelines": http://www.w3.org/TR/WD-WAI-USERAGENT Editors: Jon Gunderson <[email protected]> Ian Jacobs <[email protected]> Copyright W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This document describes techniques that user agent developers may use to satisfy the checkpoints listed in "User Agent Accessibility Guidelines." Techniques relate to the accessibility of user interfaces, content rendering, program interfaces, and accessibility features of languages such as HTML, CSS and SMIL. Like "User Agent Accessibility Guidelines", the current document emphasizes the accessibility of interoperability between two important classes of user agents - graphical desktop browsers and dependent assistive technologies (including screen readers, screen magnifiers, and voice input software). However, it is meant to be applicable to user agents in general, including text and voice browsers, and multimedia players. While "User Agent Accessibility Guidelines" has been designed to be a stable document of principles, the current document will continue to evolve as technologies change and user agent manufacturers discover more effective techniques for designing accessible user agents. This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative. 1 Techniques for User Agent Accessibility Guidelines Status of this document This is a W3C Working Draft for review by W3C Members and other interested parties. It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or Members of the WAI User Agent (UA) Working Group. Although the organization of this document has begun to stabilize, the Working Group has not yet filled in the details of all the techniques. This draft does not distinguish those techniques that mainstream user agents are expected to implement natively from those that may be satisfied by providing information through an interface. This document has been produced as part of the W3C WAI Activity and intends to improve user agent accessibility for all users. The goals of the WAI-UA Working Group are discussed in the WAI UA charter. A list of the current Working Group members is available. Available formats This document is available in the following formats: HTML: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech.html A plain text file: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech.txt, HTML as a gzip'ed tar file: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent.tgz, HTML as a zip file (this is a '.zip' file not an '.exe'): http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent.zip, A PostScript file: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech.ps, A PDF file: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech.pdf. In case of a discrepancy between the various formats of the specification, http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/wai-useragent-tech.html is considered the definitive version. Comments Please send comments about this document to the public mailing list: [email protected]. 2 Techniques for User Agent Accessibility Guidelines Table of Contents 1 Guidelines, Checkpoints, and Techniques . .4 2 The User Agent and the Operating System . .4 3 The User Agent and the Document . .5 3.1 Identification . .5 3.2 Rendering alternative representations of content . .6 3.3 Styles and formatting . .7 4 Functionality offered by the User Agent to allow the User to work with the Document . .8 4.1 Access to all functionality . .8 4.2 Selection and focus . .9 4.3 Navigation . .9 4.4 Searching . .9 4.5 Querying . 10. 4.6 Activation . 10. 5 The User Agent and the User . 10. 5.1 Accessible user interface . 10. 5.2 Visibility of accessibility features . 11. 5.3 Configuration . 11. 5.4 Notification of events and changes . 13. 6 The User Agent and Assistive Technologies . 13. 7 Support for accessibility features of certain languages . 14. 7.1 HTML . 14. 7.2 CSS . 14. 7.3 SMIL . 15. 7.4 MathML . 15. 8 Appendix: Accessibility features of some operating systems . 15. 8.1 Microsoft Windows 95, Windows 98, and Window NT 4.0 . 17. 8.2 Apple Macintosh Operating System . 17. 8.3 AccessX, X Keyboard Extension (XKB), and the X Window System 18. 8.4 DOS (Disk Operating System) . 18. 9 Acknowledgments . 18. 10 References . 19. 3 Techniques for User Agent Accessibility Guidelines 1 Guidelines, Checkpoints, and Techniques The guidelines documents have been organized to address readers seeking abstract principles of accessible user agent design and readers seeking concrete solutions. The guidelines documents define three terms for different levels of abstraction: Guideline A guideline is a general principle of accessible design. A guideline addresses the question "What accessibility issues should I be aware of?" Checkpoint A checkpoint is a specific way of satisfying one or more guidelines. While checkpoints describe verifiable actions that may be carried out by the user agent developer, implementation details are described elsewhere. A checkpoint answers the question "What should I do to improve accessibility?" Technique A technique is an implementation of one or more checkpoints in a given language (e.g., HTML, XML, CSS, DOM, ...). A technique answers the question "How do I do that in HTML or SMIL or CSS...?" The current document contains techniques, according to different interfaces between the user agent and the operating system, the document, the user, and other software. Note that each technique in this document is numbered according to its number in the guidelines document. 2 The User Agent and the Operating System 4.1.4 Follow operating system conventions for user interface design, user agent configuration (including configuration profiles), product installation and documentation, and accessibility flags and interfaces. [Priority 2] The operating system application programming interfaces (APIs) that support accessibility are designed to provide a bridge between the standard user interface supported by the operating system and alternative user interfaces developed by third-party assistive technology vendors to provide access to persons with disabilities. Applications supporting these APIs are therefore generally more compatible with third-party assistive technology. The WAI Working Group strongly recommends using and supporting APIs that improve accessibility and compatibility with 3rd party assistive technology. Third-party assistive technology can use the accessibility information provided by the APIs to provide an alternative user interface for various disabilities. The following is an informative list of currently public APIs that support accessibility: Microsoft Active Accessibility in Windows 95/NT versions. Information on active accessibility can be found at the Microsoft WWW site on Active Accessibility. Sun Microsystems Java Accessibility API in Java Code. Information on Java Accessibility API can be found at Java Accessibility Utilities. Many major operating systems have built-in accessibility features for improving the usability of the standard operating system by persons with disabilities. When designing software that runs above an underlying operating system, developers should ensure that the application: 4 Techniques for User Agent Accessibility Guidelines 1. Makes use of operating system level features. See the appendix of accessibility features [p. 15] for some comment operating systems. 2. Inherits operating system settings related to accessibility. Pertinent settings include font and color information as well as other pieces of information discussed in this document. [Ed. We Should put a more exhaustive list here.] 4.1.1 Ensure that the software may be installed in a device-independent manner for all supported input and output devices. [Priority 1] Ensure that software may be installed, when possible, according to the conventions of the operating system. 3 The User Agent and the Document 3.1 Identification In order for the user agent to satisfy many of the techniques in this document (related to rendering, notification, navigation, etc.), it must be able to identify certain types of information in addition to recognizing object types such as images, video, sound, and elements of the document language. Sources of alternative representations of information User agents must be able to recognize sources of alternative representations of content. In HTML For the IMG element: The "alt", "title", and "longdesc" attributes For the OBJECT element: The content of the element and the "title" attribute. For the APPLET element: The "alt" attribute and the content of the element. For the AREA element: The "alt" attribute. For the INPUT element: The "alt" attribute. For the ACRONYM and ABBR elements: The "title" attribute may be used for the acronym or abbreviation expansion. For the TABLE element, the "summary" attribute For frames, the NOFRAMES element and the "longdesc" attribute on FRAME and IFRAME. For scripts, the NOSCRIPT element. In SMIL The "alt", "title", "longdesc", and "abstract" attributes. To be completed.. Sources of blinking text and animation User agents that recognize the following sources of blinking text and animations must enable users to freeze that text.
Load more

Recommended publications
  • Engineering Accessible Web Applications
    Universidad Nacional de La Plata Facultad de Informática Thesis submitted in fulfillment of the requirements for the degree of Doctor (Ph.D.) in Informatics Science Engineering Accessible Web Applications. An Aspect-Oriented Approach Author: Mg. Adriana E. Martín Supervisor: Ph.D. Alejandra Cechich Co-Supervisor: Ph.D. Gustavo Rossi September 2011 ABSTRACT Building Accessible Web applications is nowadays a must. Every day more and more users with different abilities and/or temporally or permanent disabilities are accessing the Web, and many of them have special difficulties in reaching the desired information. However, the development of this kind of Web software is complicated for several reasons. Though some of them are technological, the majority are related with the need to compose different and, many times, unrelated design concerns which may be functional as in the case of most of the specific application’s requirements, or non- functional such as Accessibility itself. Even though, today there is a huge number of tools and proposals to help developers assess Accessibility of Web applications, looking from the designer perspective, there is no such a similar situation. It seems that creating accessible Web sites is more expensive and complicated than creating Web sites and then assessing/modifying them. Although this feeling may be largely true, the benefits of modelling Accessibility at early design stages outweigh the needs of a developer to implement that Accessibility. In this thesis, we present a novel approach to conceive, design and develop Accessible Web applications in an Aspect-Oriented manner. In order to reach our goal, we provide some modeling techniques that we specifically developed for handling the non- functional, generic and crosscutting characteristics of Accessibility as a quality factor concern.
    [Show full text]
  • [MS-HTML401]: Internet Explorer HTML 4.01 Standards Support
    [MS-HTML401]: Internet Explorer HTML 4.01 Standards Support Document Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • The Technical Specification for Content Development Is for General Information Purposes Only
    TECHNICAL SPECIFICATION FOR CONTENT DEVELOPMENT VERSION: 6.0 DATE: 22 DECEMBER, 2009 Commercial in Confidence © Curriculum Corporation, 2009 Technical Specification for Content Development Table of Contents 1 INTRODUCTION ............................................................................................................. 2 1.1 Purpose ........................................................................................................... 2 1.2 Obligations of The Le@rning Federation .................................................... 2 1.3 Monitoring and usage .................................................................................... 2 1.4 Conformance .................................................................................................. 2 1.5 Conventions used in this document ............................................................ 2 2 PRINCIPLES ................................................................................................................... 3 2.1 Accessibility ................................................................................................... 3 2.2 Useability ........................................................................................................ 3 2.3 Interoperability ............................................................................................... 3 2.4 Flexibility ......................................................................................................... 3 2.5 Durability ........................................................................................................
    [Show full text]
  • Introducing HTML5.Pdf
    ptg HTMLINTRODUCING 5 ptg BRUCE LAWSON REMY SHARP Introducing HTML5 Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2011 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Jeff Riley/Box Twelve Communications Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Doug Adrianson Proofreader: Darren Meiss Compositor: Danielle Foster Indexer: Joy Dean Lee Back cover author photo: Patrick H. Lauke Notice of Rights ptg All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Appendix a the Ten Commandments for Websites
    Appendix A The Ten Commandments for Websites Welcome to the appendixes! At this stage in your learning, you should have all the basic skills you require to build a high-quality website with insightful consideration given to aspects such as accessibility, search engine optimization, usability, and all the other concepts that web designers and developers think about on a daily basis. Hopefully with all the different elements covered in this book, you now have a solid understanding as to what goes into building a website (much more than code!). The main thing you should take from this book is that you don’t need to be an expert at everything but ensuring that you take the time to notice what’s out there and deciding what will best help your site are among the most important elements of the process. As you leave this book and go on to updating your website over time and perhaps learning new skills, always remember to be brave, take risks (through trial and error), and never feel that things are getting too hard. If you choose to learn skills that were only briefly mentioned in this book, like scripting, or to get involved in using content management systems and web software, go at a pace that you feel comfortable with. With that in mind, let’s go over the 10 most important messages I would personally recommend. After that, I’ll give you some useful resources like important websites for people learning to create for the Internet and handy software. Advice is something many professional designers and developers give out in spades after learning some harsh lessons from what their own bitter experiences.
    [Show full text]
  • Technical Specification Guide for Online Resources
    Technical specification guide for online resources Version 7.3 March 2012 Technical specification guide for online resources Disclaimer The material contained in the Technical specification guide for online resources is for general information purposes only. Any use of the Technical specification guide for online resources is at your own risk. To the extent permitted by law, Education Services Australia will not be liable for any loss or damage suffered as a result of any party relying upon the Technical specification guide for online resources. © Education Services Australia 2012 Version 7.3 Page 2 of 28 Technical specification guide for online resources Contents 1.0 Introduction ........................................................................................................................................................ 4 1.1 Purpose ......................................................................................................................................................... 5 1.2 Obligations of Education Services Australia .................................................................................................. 5 1.3 Development, monitoring and usage ............................................................................................................ 5 1.4 Associated standards .................................................................................................................................... 6 1.5 Conformance ...............................................................................................................................................
    [Show full text]
  • Introduction What Is Javascript?
    CS2361–Internet & Java 2.1 Introduction What is JavaScript? Discuss its features ¾ JavaScript is a client-side scripting language and is the defacto scripting language for most web-based application. ¾ It is used to enhance the functionality and appearance of Web pages by making it more dynamic, interactive and creating web pages on the fly. ¾ JavaScript is interpreted by the browser. ¾ Statements are terminated by a ; but is not required. ¾ JavaScript standard is defined by ECMA to which Netscape is fully compliant whereas IE complies with a modified version known as JScript. ¾ The <script> element introduces a client-side scripting language. ¾ It is generally placed within the <head> element, but can also be part of <body> o The type attribute specifies the MIME scripting language and its value is text/javascript for JavaScript. <html> <head> ... <script type="text/javascript"> <!-- Put your JavaScript code here // --> </script> </head> <body></body> </html> ¾ The script is executed either when page is loaded or when given event occurs. ¾ The script will not be executed if it is disabled in the browser environment. ¾ For browsers that do not understand javascript, the entire script code is enclosed within xhtml comment. ¾ Script can also be placed in a separate file and pointed by src attribute. ¾ JavaScript is an object-oriented language and has a set of pre-defined objects (document, window, form, etc) to access and manipulate XHTML elements. ¾ An object's attribute is used to set/read data, whereas a method provides service. ¾ Javascripthas
    [Show full text]
  • AN EXPLORATION INTO TWO SOLUTIONS to PROPAGATING WEB ACCESSIBILITY for BLIND COMPUTER USERS by Stephanie Rose Hackett B.S., Univ
    AN EXPLORATION INTO TWO SOLUTIONS TO PROPAGATING WEB ACCESSIBILITY FOR BLIND COMPUTER USERS by Stephanie Rose Hackett B.S., University of Pittsburgh, 2000 M.S., University of Pittsburgh, 2004 Submitted to the Graduate Faculty of School of Health and Rehabilitation Sciences in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Pittsburgh 2007 UNIVERSITY OF PITTSBURGH SCHOOL OF HEALTH AND REHABILITATION SCIENCES This dissertation was presented by Stephanie Rose Hackett It was defended on November 29, 2007 and approved by Ellen Cohn, Ph.D., CCC-SLP, Associate Professor, Communication Science and Disorders Valerie Monaco, Ph.D., MHCI, Assistant Professor, Biomedical Informatics, School of Medicine Valerie J.M. Watzlaf, Ph.D., RHIA, FAHIMA, Associate Professor, Health Information Management Dissertation Advisor: Bambang Parmanto, Ph.D., Associate Professor, Health Information Management ii Copyright © by Stephanie Hackett 2007 iii AN EXPLORATION INTO TWO SOLUTIONS TO PROPAGATING WEB ACCESSIBILITY FOR BLIND COMPUTER USERS Stephanie Rose Hackett, Ph.D. University of Pittsburgh, 2007 A model is presented depicting the driving forces (Web industry, consumers, U.S. federal government, and technology) promoting an accessible Web and potential solutions within those forces. This project examines two distinct solutions, lawsuits (a consumer-driven solution) and AcceSS 2.1 transcoder (a technology-driven solution) to provide more information on two under- researched methods that could have far-reaching impacts on Web accessibility for the blind. First, an evaluation of the intraclass correlation (ICC) between homepage Web Accessibility Barrier (WAB) scores and WAB scores of levels 1-3 found that the homepage is not sufficient to detect the accessibility of the website.
    [Show full text]
  • Extending Expression Web with Add-Ons
    APPENDIX Extending Expression Web with Add-Ons Any good web editor must be extensible, because the Web is constantly changing. This capability is one of the strongest assets of Expression Web; it means that third parties can add new features that are easy to use inside of Expression Web. You don’t have to wait for Microsoft to release a new version to get more features. I am talking not about code snippets, like the one we created in Chapter 2, but about fea- tures that make it easy to add e-commerce capabilities using PayPal buttons or a shopping cart, improve your search engine ranking using Google Sitemaps, or add Flash banners and interactivity without becoming a programmer or a search engine specialist. Some of these add-ons are commercial applications that charge a fee, and others are created by someone who sees a need and creates a free add-on. At the time of this writing, there were over a dozen add-ons available for download and more actively under develop- ment. A current list is available at http://foundationsofexpressionweb.com/exercises/ appendix. Add-ons are usually easy to install and use. Once you have found an extension for Expression Web that offers you the ability to extend what you can do, download the add-on, and follow the extension maker’s instructions on how to install it. Most add-ons will have an installer that creates either a toolbar or an entry in one of the menus. Adding PayPal Buttons The first add-on I will show you creates a menu item.
    [Show full text]
  • The Latest Web Developments', Paper Presented at IRISS 98 , Bristol, UK United Kingdom, 25/03/98 - 27/03/98
    Citation for published version: Kelly, B 1998, 'The Latest Web Developments', Paper presented at IRISS 98 , Bristol, UK United Kingdom, 25/03/98 - 27/03/98. Publication date: 1998 Document Version Early version, also known as pre-print Link to publication Publisher Rights CC BY University of Bath Alternative formats If you require this document in an alternative format, please contact: [email protected] General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 23. Sep. 2021 The Latest Web Developments Brian Kelly, UKOLN, University of Bath, Bath, UK [email protected] ABSTRACT This paper outlines some of the latest World Wide Web developments, in particular standards which are emerging from W3C, the World Wide Web Consortium. The paper gives an overview of the architectural components of the Web, summarise their deficiencies and describe how these deficiencies are being addressed. The paper should be of interest to people involved in developing applications and services on the Web and anyone who has a general interest in future developments of the Web. BACKGROUND The World Wide Web (often referred to as the web) is a distributed hypermedia system which is based on three key architectural components: 1.
    [Show full text]
  • Designing Beneath the Surface of the Web Sarah Horton Dartmouth College 6224 Baker/Berry Hanover, NH 03755 USA 603 646-1087 [email protected]
    Designing Beneath the Surface of the Web Sarah Horton Dartmouth College 6224 Baker/Berry Hanover, NH 03755 USA 603 646-1087 [email protected] ABSTRACT clarity influence how well software can read and interpret the At its most basic, the web allows for two modes of access: visual source code. Nonvisual web access can be improved by applying and non-visual. For the most part, our design attention is focused the following guidelines for source code design. on making decisions that affect the visual, or surface, layer — Shneiderman defines universal usability as an approach to design colors and type, screen dimensions, fixed or flexible layouts. that is focused on “enabling all citizens to succeed in using However, much of the power of the technology lies beneath the information and communication technologies to support their surface, in the underlying code of the page. There, in the unseen tasks” [18]. A focus on page code design improves the universal depths of the page code, we make decisions that influence how usability of web pages by addressing access challenges in a well, or poorly, our pages are read and interpreted by software. In variety of contexts. For instance, the small viewport on mobile this paper, we shift our attention beneath the surface of the web devices presents many of the same challenges as nonvisual access. and focus on design decisions that affect nonvisual access to web This paper concludes with a discussion of how these guidelines pages. can be applied to improve web access for mobile users. Categories and Subject Descriptors 2.
    [Show full text]
  • Introducing HTML5 Second Edition
    HTMLINTRODUCING SECOND 5EDITION BRUCE LAWSON REMY SHARP Introducing HTML5, Second Edition Bruce Lawson and Remy Sharp New Riders 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) Find us on the Web at: www.newriders.com To report errors, please send a note to [email protected] New Riders is an imprint of Peachpit, a division of Pearson Education Copyright © 2012 by Remy Sharp and Bruce Lawson Project Editor: Michael J. Nolan Development Editor: Margaret S. Anderson/Stellarvisions Technical Editors: Patrick H. Lauke (www.splintered.co.uk), Robert Nyman (www.robertnyman.com) Production Editor: Cory Borman Copyeditor: Gretchen Dykstra Proofreader: Jan Seymour Indexer: Joy Dean Lee Compositor: Danielle Foster Cover Designer: Aren Howell Straiger Cover photo: Patrick H. Lauke (splintered.co.uk) Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For informa- tion on getting permission for reprints and excerpts, contact permissions@ peachpit.com. Notice of Liability The information in this book is distributed on an “As Is” basis without war- ranty. While every precaution has been taken in the preparation of the book, neither the authors nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the com- puter software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]