DOCSLIB.ORG

A Glossary of Terms Web Accessibility: Web Standards and Regulatory Compliance

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Glossary of Terms Web Accessibility: Web Standards and Regulatory Compliance A GLOSSARY OF TERMS WEB ACCESSIBILITY: WEB STANDARDS AND REGULATORY COMPLIANCE A Accessibility Task Force (ATF) A subgroup of the Web Standards Project (WaSP) focusing on accessibility, assistive tech- nology, and standards support. ADA See Americans with Disabilities Act. Ajax A combination of technologies that allows bits of a web page to be refreshed from the server without refreshing the whole page, which gives the user a more responsive, seam- less experience. It is a good buzzword, but a lousy acronym for Asynchronous JavaScript and XML (because it doesn’t require XML). Ajax currently is most often seen in Google Maps, Google’s Gmail, and the like. Many accessibility problems have yet to be addressed. A similar result, without using JavaScript, may be achieved using Flash or even HTML frames. alt-text A generic term describing descriptive text attached to certain objects on a web page that can be read aloud by a screen reader, so that a person with a visual impairment can know the nature of such objects, too. Alt-text is therefore an accessible alternative to a poten- tially inaccessible item of content. For example, the object element may use text embed- ded within it as a fallback mechanism. The most common alternative text is found as an attribute of the <img> element, and it describes the function of an image, or is blank in the case of purely decorative images. It is evil and wrong to refer to this as an alt tag (there is no alt element in (X)HTML), and many hope that WCAG 3.0 will mandate the death penalty for such incorrect nomenclature. Americans with Disabilities Act (ADA) A U.S. law passed in 1990 that prohibits discrimination against people with disabilities. applet A Java program or application that provides interactivity not offered by (X)HTML and designed to be embedded in, and invoked from, a web page. In many cases, Flash has superseded applets as the means to achieve extra interactivity. assistive technology Equipment or software that assists people with disabilities in performing everyday activi- ties. Examples include screen readers and voice-input software. ATAG See Authoring Tools Accessibility Guidelines. ATF See Accessibility Task Force. 582 GLOSSARY OF TERMS Authoring Tools Accessibility Guidelines (ATAG) Published by the W3C in 2000 to assist authoring tool developers in “designing authoring tools that produce accessible Web content and to assist developers in creating an accessi- ble authoring interface” (www.w3.org/TR/ATAG10/). In other words, your blogging tool or CMS should not only produce accessible pages, but also be accessible itself so that users with disabilities can create content. B A baseline In WCAG 2.0, a set of technologies assumed to be supported by, and enabled in, user agents in order for web content to conform to WCAG 2.0. Some examples of entities that may set baselines include authors, companies, customers, and government entities. Bobby A free website accessibility assessment tool developed by CAST (www.cast.org/), and then acquired by Watchfire (www.watchfire.com/). The free version of Bobby was discontinued in April 2003. Bobby had some utility in checking for things like missing alt-text, but, unfortunately, it lulled site owners into a false sense of security, as they believed that “passing Bobby” guar- anteed accessibility. There are many other online “validators,” such as Cynthia Says and the WAVE. Gez Lemon has a salutary article about the usefulness of such programs at http:// juicystudio.com/article/invalid-content-accessibility-validators.php. browser The software on a computer that allows websites to be rendered so they can be displayed to users. There are two types of visual browsers. Internet Explorer, Firefox, Opera, Safari, and the like render all content including the latest technologies. Others, like Lynx, are text- only. But many other types of browsers exist, some of which produce voice output, such as IBM Home Page Reader. C Cascading Style Sheets (CSS) A means of applying styling/formatting to markup (for example, XML or HTML). This has many advantages over using HTML formatting tags, such as <b> and <font>. For a start, CSS formatting is more powerful and allows more flexibility. If you want to change a style, you need only change its definition in the style sheet, rather than changing every instance of it in the HTML. CSS has great uses for accessibility. For example, you can use an alter- native style sheet to make the text on a website bigger for the benefit of people with visual impairments. See Chapter 9 of this book for more details. CMS See content management system. 583 WEB ACCESSIBILITY: WEB STANDARDS AND REGULATORY COMPLIANCE content management system (CMS) A program that allows users to create and manage web pages and other content. CMSs are often browser-based. They can range from free blogging tools, such as WordPress, to expensive systems that can run a whole enterprise site, such as TeamSite or Vignette. They are generally template-driven and promise (with varying success) to turn user’s text-based input into HTML. Many spit out horribly inaccessible code, and most do not conform to ATAG and are therefore unable to be used by people with disabilities to produce sites. It’s always important to ask vendors about their conformance to ATAG before purchasing a CMS. CSS See Cascading Style Sheets. D DDA See Disability Discrimination Act. design for all See universal design. Disability Discrimination Act (DDA) A name shared by two laws passed in Australia (1992) and the United Kingdom (1995, extended 2005). They both prohibit discrimination against people with disabilities. D-LINK A link that takes the form of a capital D near an image. It provides a longer description of the image or its purpose than is feasible using the alt attribute. It’s basically a hack, because most browsers don’t cope with longdesc well. Document Object Model (DOM) A view of a document (HTML, XHTML, or XML) that can be parsed and manipulated to add new content, amend styles, and change behavior after a web page has loaded—generally via JavaScript, as this is built into most browsers. See Chapter 10 of this book for more details. Document Type Definition (DTD) A file that defines the relationships and constraints for elements and attributes used in the markup language in the form of a schema. For example, a DTD may define whether an attribute is required for a particular element. Effectively, it’s the grammatical rules for the language. DOM See Document Object Model. 584 GLOSSARY OF TERMS DTD See Document Type Definition. dyslexia A language-based learning disability that is often characterized by difficulties with under- standing written language and being more attuned to a graphical or an object-based learn- ing style. E A ECMAScript The standardized version of JavaScript (JScript in Internet Explorer) that can be used effec- tively to manipulate the DOM, validate forms, and control Ajax, or uselessly to produce effects such as pictures of unicorns following the mouse pointer. ActionScript (found in Adobe’s Flash) is also a flavor of ECMAScript (and is equally good with unicorns). Extensible Hypertext Markup Language (XHTML) Defined by the W3C as “a reformulation of the three HTML 4 document types as applica- tions of XML 1.0. It is intended to be used as a language for content that is both XML- conforming and, if some simple guidelines are followed, operates in HTML 4 conforming user agents” (www.w3.org/TR/xhtml1/#xhtml). XHTML is very much like HTML with a few extra rules. There are three main flavors. XHTML 1.0 Transitional allows many deprecated tags, and as the name suggests, was designed to help developers make the transition from HTML. XHTML 1.0 Frameset allows frames and therefore has attendant accessibility issues. XHTML 1.0 Strict is, well, strict (when com- pared with traditional HTML). The idea that XHTML is “better” than HTML is subject to ferocious (but rather futile) debate, as it is largely a matter of personal preference, understanding the difference, and using the right tools for the job. Extensible Markup Language (XML) A language specification from the W3C that allows users to develop their own markup lan- guages (often called vocabularies), and format their documents using style sheets to be presented on a browser if desired. XML has a very strict set of rules that must be adhered to, allowing a lot of control over document format. XML is most useful, however, as a com- pletely language/platform-agnostic data format. Extensible Stylesheet Language (XSL) A W3C specification that contains three parts: Extensible Stylesheet Language Transformations (XSLT) for changing the formatting and structure of markup according to a set of rules, Extensible Stylesheet Language Formatting Objects (XSL-FO) for applying a strong set of rules to a document to ensure reliable formatting when printed, and XPath to select the elements required by XSLT. 585 WEB ACCESSIBILITY: WEB STANDARDS AND REGULATORY COMPLIANCE F Firefox An open source browser available for all main operating systems, developed by the Mozilla Corporation. The good (but not perfect) standards support and availability of community- written extensions makes it the browser of choice for many web developers. Flash The name given to the product by Adobe (formerly Macromedia) that allows moving graphics to be displayed in a web page. It refers to the Flash Player, which plugs in to the browser, as well as (more generally) the program and effects. Flash can be made accessi- ble on Windows machines via MSAA, and some of the most widespread screen readers can access the content. Although Flash has gotten bad press from some accessibility advo- cates, it has proved very helpful in delivering accessible content to people with cognitive disabilities.
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]
  • 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]
  • Web Standards Facilitating Accessibility in a Digitally Inclusive South Africa – Perspectives from Developing the South African National Accessibility Portal
    Web standards facilitating accessibility in a digitally inclusive South Africa – Perspectives from developing the South African National Accessibility Portal L COETZEE*, I VIVIERS *Meraka Institute, CSIR, PO Box 395, Pretoria, 0001 Email: [email protected] 0 Abstract This paper presents limitations of technology, with specific reference to Web standards compliance, which impacted on meeting Many factors impact on the ability to create a accessibility requirements during the digitally inclusive society in a developing world development of the South African National context. These include lack of access to Accessibility Portal. These limitations introduce information and communication technology (ICT), barriers to information, thus impacting on the infrastructure, low literacy levels as well as low creation of a digitally inclusive society. ICT related skills. The lack of standards, or poor implementation of existing standards in The paper's layout is as follows. In Section 2 we technology, could also have a significant impact highlight the need for standards for the Web. on the pervasiveness and cost of developing Section 3 describes the most relevant and applications, thus creating more barriers in applicable standards with regard to the Web and society. This paper analyses the importance of specifically an accessible Web. Section 4 Web standards (especially those associated with presents a variety of tools that can be used to accessibility) in the creation of an inclusive measure the standards compliance of documents society using experiences gathered from the and websites. We introduce the South African development of the South African National National Accessibility Portal Initiative in Section Accessibility Portal. 5, with a focus on the South African National Accessibility Portal component (referred to as NAP) which forms the basis of our research.
    [Show full text]
  • What Is BS 8878?
    BS 8878:2010 - A Summary December 2010 Table of Contents Introduction ...................................................................................................................... 4 Background ..................................................................................................................... 4 What is BS 8878? ............................................................................................................ 4 BS 8878 and the law ....................................................................................................... 5 Who is BS 8878 for? ........................................................................................................ 6 Key concepts ................................................................................................................... 6 Web products ............................................................................................................... 6 Degree of user-experience ........................................................................................... 7 User personalized approach to accessibility ................................................................ 7 BS 8878 Code of practice and compliance .................................................................. 8 Structure of BS 8878 ....................................................................................................... 9 Clauses ........................................................................................................................ 9 Annexes
    [Show full text]
  • Jeremy Sydik — «Design Accessible Web Sites
    Thank you for taking part in this experiment. Andy and Dave Design Accessible Web Sites Thirty-Six Keys to Creating Content for All Audiences and Platforms Jeremy J. Sydik The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC. Quotation from “The Hobbit” by J. R. R. Tolkien. Copyright © 1937, 1966 by The J. R. R. Tolkien Copyright Trust. Reprinted by permission of The J. R. R. Tolkien Copyright Trust. Quotation from “Monty Python and the Holy Grail.” Copyright © 1975 by Python (Monty) Pictures Ltd. Reprinted by permission of Python (Monty) Pictures Ltd. Web Content Accessibility Guidelines 1.0 (Recommendation) http://www.w3.org/TR/WCAG10/ Copyright © 1999 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved Web Content Accessibility Guidelines 2.0 (Public Working Draft) http://www.w3.org/TR/WCAG20/ Copyright © 2007 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathemat- ics, Keio University). All Rights Reserved Cover image courtesy of Katherine A.W. Sydik Every precaution was taken in the preparation of this book. However, the publisher assumes no responsibility for errors or omissions, or for damages that may result from the use of information (including program listings) contained herein.
    [Show full text]
  • Museum Access & Interpretation with the Centre for Accessible
    Creating a Virtual Tour Design Guide for Museums with the Centre for Accessible Environments An Outline of Inclusive Recommendations for Virtual Tour Creation An Interactive Qualifying Project in partial fulfillment of the requirements of Worcester Polytechnic Institute submitted to: Professor Rick Brown Professor Scott Jiusto Submitted by: Cathryn Bedard Jason DuBois Scott Lehtinen Brian Loveland Project Center: London, United Kingdom Term: D06 Sponsoring Agency: The Centre for Accessible Environments Project Liaisons: Ms. Cassie Herschel-Shorland Mr. Paul Highman April 28th 2006 Executive Summary Museums in the United Kingdom are vital centers of historical, cultural and scientific learning that serve millions of visitors from the UK and around the world. Unfortunately, many of these museums are not fully accessible for all disabled people, due to physical, sensory, and intellectual barriers that can inhibit intended educational and inspirational experiences. In response to barriers at public facilities, the Disability Discrimination Act 1995 and 2005 were created to require public buildings to be accessible for disabled people. This includes overcoming access barriers that can hinder the quality of the experience for any visitors. New technologies, including virtual tours, offer alternative means for society to experience museums, and are often used as means to extend the museum experience to those who could not previously experience it due to access barriers. However, museums must be conscious of and avoid new barriers that can be created by these high-tech solutions. In addition, several smaller museums do not have the financial or personnel resources to implement changes to make the museum accessible for disabled people. The Centre for Accessible Environments (CAE), a nonprofit organization in London, assists organizations in finding access solutions for their buildings.
    [Show full text]
  • Guide to Good Practice in Commissioning Accessible Websites
    PUBLICLY AVAILABLE SPECIFICATION PAS 78:2006 Guide to good practice in commissioning accessible websites ICS 35.240.30 PAS 78:2006 This Publicly Available Specification comes into effect on 8 March 2006 Amendments issued since publication Amd. No. Date Comments © BSI 8 March 2006 ISBN 0 580 46567 5 PAS 78:2006 Contents Page Foreword ii Introduction 1 1Scope 5 2 Normative references 5 3 Terms and definitions 5 4 General principles 11 4.1 Development of an accessibility policy 11 4.2 Upholding W3C guidelines and specifications 11 4.2.1 General 11 4.2.2 Content formats 11 4.2.3 Authoring tools 11 4.3 Conformance checking 12 4.4 Involving disabled people in the requirements gathering and conceptual design process 12 4.5 Regular testing by disabled people 12 4.6 Additional accessibility provisions 12 5 How disabled people use websites 13 5.1 General 13 5.2 Operating systems 13 5.3 Access technology and other considerations for blind and partially sighted people 14 5.4 Access technology and other considerations for deaf and hard of hearing people 15 5.5 Access technology and other considerations for people with learning disabilities 15 5.6 Access technology and other considerations for people with cognitive impairments (eg dyslexia) 16 5.7 Access technology and other considerations for people with motor impairments 16 6 Defining the accessibility policy for the website 17 6.1 General 17 6.2 Content of the accessibility policy 17 6.3 Publicly available accessibility policy statement 19 6.4 Accessibility guidelines 19 © BSI 8 March 2006 i PAS
    [Show full text]
  • Making E-Communication Accessible Best Practice for Websites, Email and Electronic Documents
    Making E-communication Accessible Best practice for websites, email and electronic documents A supplement to the SAIF Standards for Disability Information and Advice Provision in Scotland Making E-communication Accessible A supplement to the SAIF Standards for Disability Information and Advice Provision in Scotland Written by Jim Byrne and Eva Bolander Published by the Scottish Consumer Council, Royal Exchange House, 100 Queen Street, Glasgow G1 3DN. ISBN 0-9551942-5-3 / 978-0-9551942-5-2 © Scottish Accessible Information Forum, 2006. First revised edition. You may photocopy all or part of this publication, but please acknowledge the source. First published 2002. SAIF Scottish Consumer Council Royal Exchange House 100 Queen Street Glasgow G1 3DN Tel: 0141 226 5261 Fax: 0141 221 0731 Minicom: 0141 226 8459 Email: [email protected] Website: www.saifscotland.org.uk This document is available on request: • in braille, • in large print, • on audio tape/CD, • in electronic format, • on the World Wide Web. Making E-communication Accessible 1 1 Foreword When SAIF published its Standards for Disability Information and Advice Provision in Scotland in 1999, the internet merited a few brief mentions as a possible method of delivering information and advice. The technological revolution that is the World Wide Web was receiving huge amounts of publicity but at that time it was making very little impact on the everyday lives of disabled people throughout Scotland. Three years later, when Making Websites Accessible was first written, it was unusual to come across an information and advice agency that was not planning, building or working hard to maintain a website in order to deliver some or all of its services.
    [Show full text]
  • How to Commission & Design Accessible Websites
    How to Commission & Design Accessible Websites For Voluntary and Community Organisations Produced by Copyright Statement All rights reserved. This publication is protected by copyright law. Material may be used or copied for personal use or for internal use within your organisation only. If you make unauthorised copies from these pages, the publisher could take you and your employer to court and claim legal damages. Apart from any fair dealing for the purposes of research or private study, or criticism or review, as permitted under the Copyright, Designs and Patents Act, 1988, this publication may only be reproduced, stored or transmitted, in any form or by any means, with the prior permission in writing of the publishers. Every effort has been made to make this publication as complete and accurate as possible, but no warranty of fitness is implied. AbilityNet does not represent or warrant that the information contained in this book is accurate, complete or up to date. Neither AbilityNet nor the ICT Hub shall have liability or responsibility to any persons or entity with respect to loss or damages arising from the information contained in this book. Copyright © 2006 AbilityNet 2 Contents Introduction .................................................................................................................................................. 4 Part one: An overview of web accessibility for the VCS .............................................................. 6 What is web accessibility? .................................................................................................................................................................
    [Show full text]
  • Learn to Love Accessibility, .Net Magazine, April 2007
    .net accessibility Whos responsible for accessibility? By Patrick Lauke In web accessibility, youll often hear emphasis being placed on the duty of web authors to create accessible content. However, this is only one part of the web accessibility equation. Right at the planning stage, clients and site owners should gain a basic understanding of what accessibility is, why its important for their project, and how to choose the right web authors/developers to do the job. An excellent starting point is the Publicly Available Specification (PAS) 78 Guide to Good Practice in Commissioning Accessible Websites, at tinyurl.com/yufg46, endorsed by the Disability Rights Commission (DRC). Web authors and developers need to be aware of potential accessibility issues when it comes to developing their content. The Web Content Accessibility Guidelines (WCAG) at www.w3.org/WAI/intro/wcag provide a solid Finally, there has to be an onus on users When using hierarchical navigation, you can either roll out or foundation for development and evaluation. themselves. They need to learn what user roll up the top levels, depending on how many options there are However, authors still need an actual agents are available to them, how to use them, understanding of the rationale underpinning and how to configure them to best suit their match, and I tend to use this format: Page name: the various checkpoints and current best particular needs. For example, if they require Site name > section name. This puts the important practices that not only satisfy the guidelines, larger text or particular colour combinations, information first, and the page name would be the but work in the real world (through user-testing they should strive to gain the knowledge to set same as the main heading.
    [Show full text]
  • Library Trends, V.55, No.4 Spring 2007
    Web Accessibility Peter Brophy and Jenny Craven Abstract The increasing provision of Web-based information resources has moved from a simple text interface to dynamic and interactive de- signs. While this move has provided people with a more creative and flexible experience, there are dangers that some people will be excluded because they cannot use standard methods of access. Research has shown that people with disabilities are most at risk of being excluded from access, and in particular people who are blind or visually impaired and who use assistive technologies such as screen readers. In a library environment, ensuring access for all is important because the method of delivery is predominantly Web-based and the development of e-book provision will provide increased opportuni- ties to access library services remotely. This article reviews some key issues relating to Web accessibility, identifying methods of access, principles of accessibility and usability, and how Web accessibility can be assessed. Studies show that despite a growing awareness of Web accessibility issues, people are still experiencing barriers to ac- cess. Research initiatives identified in this article, and the develop- ment of the W3C WAI WCAG version 2.0, show that the research momentum is being maintained, and together with specific library- oriented research this can only be positive for the development of the profession’s practice in this area. Introduction The accessibility of Web-based information can be improved in two principal ways: through the use of access technology and through adopt- ing good practice in interface design. Both are of equal importance: pro- vision of assistive equipment (adaptive, enabling, or access technology) LIBRARY TRENDS, Vol.
    [Show full text]
  • Metalib V.4.0 Customer Testing, Ex Libris Offices, Jerusalem, December 2006
    MetaLib v.4.0 customer testing, Ex Libris offices, Jerusalem, December 2006 Richard Cross eServices Development Officer Libraries and Learning Resources Nottingham Trent University January 2007 MetaLib v.4.0 | Customer testing, Ex Libris offices, Jerusalem | December 2006 | Richard Cross MetaLib v.4.0 customer testing, Ex Libris offices, Jerusalem, December 2006 1. Introduction and context 4 2. Test procedures 4 3. New functionality in MetaLib 4.0 7 /V (User interface) 4. Web accessibility compliance 9 5. /V GUI customisation options 10 6. Keyword search replacing phrase search default 11 7. Cluster and Facets 12 8. Quick Set ordering 12 9. Ejournal A-Z list and ejournals in My Space 13 /M (Management interface) 10. Institute_tab and other config settings 14 11. Statistics 14 12. New licence 14 13. Category management 15 14. Hints screen – new KB update data 15 System parameters and setting 15. Oracle 10 15 16. Proxy support 16 17. IP Loader utility 16 18. Back-up utility 16 19. Proxy support 16 20. Clear vir01 and statistics 16 21. New log reporting control 17 2 MetaLib v.4.0 | Customer testing, Ex Libris offices, Jerusalem | December 2006 | Richard Cross Upgrade methodology: MetaLib 3.13 to MetaLib 4.0 22. MetaLib Installation Kit (MIK) 18 23. Upgrade Express 19 24. Recommendations 24 Illustrations Figure 1: The Defects status life cycle used by Ex Libris for MetaLib 4.0 testing 6 Figure 2: Upgrade Express Utility MetaLib 3.13 to 4.00 Source menu 21 Figure 3: Upgrade Express Utility MetaLib 3.13 to 4.00 Target menu 21 Figure 4: Customised /V GUI in MetaLib 4.0, post-Upgrade Express installation 22 3 MetaLib v.4.0 | Customer testing, Ex Libris offices, Jerusalem | December 2006 | Richard Cross MetaLib v.4.0 customer testing, Ex Libris offices, Jerusalem, December 2006 1.
    [Show full text]