DOCSLIB.ORG

Assessment of Web Accessibility and Technical Specifications Conformance of Web Sites from Four EU Member States

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Assessment of Web Accessibility and Technical Specifications Conformance of Web Sites from Four EU Member States Assessment of Web Accessibility and Technical Specifications Conformance of Web Sites from Four EU Member States Carmen Marincu, BEng Submitted for qualification of: PhD Supervisor: Dr. Barry McMullin School of Electronic Engineering Dublin City University Dublin, Ireland I hereby certify that this material, which I now submit for assessment on the programme of study leading to the award of PhD is entirely my own work and has not been taken from the work of others save and to the extent that such work has been cited and acknowledged within the text of my work. Signed: ID No: 50162292 UfrftiHaU Date: 16/01/2006 Contents 1 Introduction 1 1.1 Web accessibility.................................................................................. 1 1.2 Web accessibility in the E U .................................................................. 2 1.3 Thesis overview ...................................................................................... 2 2 Background Information 6 2.1 Chapter Overview ................................................................................... 6 2.2 The World Wide W eb ............................................................................ 7 2.3 The Web and People with Disab ilities................................................ 12 2.3.1 B lindness................................................................................... 15 2.3.2 Visual im p airm en t.................................................................. 20 2.3.3 Mobility impairments ............................................................ 23 2.3.4 Deafness and hard of hearing.................................................. 24 2.3.5 Cognitive and neurological disability .................................. 25 2.3.6 Web Accessibility ................................................................... 28 2.4 W3C’s Web Content Accessibility Guidelines 1 .0 .......................... 34 2.4.1 O verview ................................................................................... 34 2.4.2 WCAG—The Future (WCAG 2.0)......................................... 37 2.5 Web Accessibility P o lic ie s ................................................................... 39 2.6 Chapter Sum m ary................................................................................... 46 1 3 Web Accessibility Survey 47 3.1 Chapter Overview ................................................................................. 47 3.2 The survey objectives........................................................................... 48 3.2.1 Evaluation of web accessibility levels on samples of web s ite s ............................................................................................ 48 3.2.2 Implementation of automated web accessibility surveying system ...................................................................................... 50 3.3 Related w o r k ........................................................................................ 51 3.4 Chapter Summary................................................................................. 60 4 Methodology 61 4.1 Chapter Overview .................................................................................. 61 4.2 Sampling methodology........................................................................ 63 4.2.1 Subjective sampling methodology of the Irish web space . 64 4.2.2 Automated random sampling methodology of the Irish, UK, German and French web spaces.................................... 67 4.3 Mirroring tool........................................................................................ 76 4.4 WCAG conformance evaluation to o l ................................................. 79 4.5 HTML technical conformance evaluation to o l ................................. 85 4.6 The automated surveying system ........................................................ 96 4.6.1 Implementation of data gathering s t a g e .............................. 96 4.6.1.1 Gathering overall process information ............. 96 4.6.1.2 Gathering mirroring process information .... 101 4.6.1.3 Gathering WCAG 1.0 conformance investiga­ tion information 103 4.6.1.4 Gathering HTML technical conformance inves­ tigation information ................................................. 106 4.6.2 Implementation of data reporting stage ................................. 108 2 4.6.2.1 Reporting web content mirroring process infor­ mation ........................................................................ 110 4.6.2.2 Reporting WCAG 1.0 conformance investiga­ tion information............................................. I l l 4.6.2.3 Reporting HTML technical conformance inves­ tigation information 112 4.7 Chapter Summary......................................................................................114 5 Web accessibility guidelines and HTML technical conformance tests 115 5.1 Chapter Overview ...................................................................................... 115 5.2 Bobby Priority 1 diagnostics...................................................................116 5.2.1 g9: Provide alternative text for all im a g e s ..............................116 5.2.2 g240: Provide alternative text for all image map hot-spots (A R E A s)..................................................................................... 120 5.2.3 glO: Provide alternative text for all image-type buttons in f o r m s .........................................................................................123 5.2.4 g39: Give each frame a t i t l e ....................................................124 5.2.5 g38: Each FRAME must reference an HTML file 126 5.2.6 g21: Provide alternative text for each A PPLET .................... 127 5.2.7 g20: Provide alternative text for each O B JEC T .................... 128 5.3 Bobby Priority 2 diagnostics...................................................................129 5.3.1 g 104: Use relative sizing and positioning (percent values) rather than absolute (pixels).....................................................129 5.3.2 g271: Use a public text identifier in a DOCTYPE statement 130 5.3.3 g265: Do not use the same link phrase more than once when the links point to different U R Ls.................................... 131 5.3.4 g269: Make sure event handlers do not require use of a m ouse............................................................................................133 3 5.3.5 g41: Explicitly associate form controls and their labels with the LABEL elem ent...........................................................133 5.3.6 g34: Create link phrases that make sense when read out of co n tex t.................................................................................. 134 5.3.7 g2: Nest headings properly........................................................135 5.3.8 g273: Include a document T IT L E .......................................... 135 5.3.9 g37: Provide a NOFRAMES section when using FRAMES 136 5.3.10 g5: Avoid scrolling text created with the MARQUEE ele­ ment ............................................................................................136 5.3.11 g4: Avoid blinking text created with the BLINK element . 137 5.3.12 g254: Do not cause a page to redirect to a new URL . 138 5.3.13 g33: Do not cause a page to refresh automatically 138 5.4 OpenSP diagnostics..................................................................................139 5.4.1 Missing or unusable DOCTYPE declaration..........................141 5.4.2 Undefined attribute (OpenSP diagnostic ID 108) ................ 141 5.4.3 Element not allowed by the document type (OpenSP di­ agnostic ID 6 4 ) ........................................................................... 142 5.4.4 Required attribute not specified (OpenSP diagnostic ID 127) 143 5.4.5 End tag for element not opened (OpenSP diagnostic ID 79) 143 5.4.6 Missing required end tag (OpenSP diagnostic ID 68) . 144 5.4.7 Non SGML character number (OpenSP diagnostic ID 139) 144 5.4.8 General entity not defined and no default entity (OpenSP diagnostic ID 2 5 ) ........................................................................ 145 5.4.9 Attribute value not allowed (OpenSP diagnostic ID 131) . 146 5.4.10 End tag for element not finished (OpenSP diagnostic ID 73) 146 5.4.11 Attribute value must be literal (OpenSP diagnostic ID 82) 146 5.5 Chapter O verview..................................................................................... 147 4 6 Analysis of web accessibility evaluation results of Irish, UK, French and German web samples - December 2004 148 6.1 Chapter Overview ......................................................................................148 6.2 Analysis of web content mirroring process results........................... 151 6.3 Analysis of WCAG 1.0 conformance investigation results................. 155 6.3.1 Key r e s u lts ................................................................................... 155 6.3.2 Bobby completion data ............................................................... 156 6.3.3 Bobby Priority 1 diagnostics......................................................157 6.3.4 Bobby Priority 2 diagnostics......................................................162 6.4 Analysis of HTML technical conformance investigation results . 168 6.4.1 Key r e s u lts ................................................................................... 168 6.4.2 OpenSP completion d ata ............................................................ 168
Load more

Recommended publications
  • 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]
  • 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]
  • Michael T. Nygard — «Release It! Design and Deploy Production-Ready Software
    What readers are saying about Release It! Agile development emphasizes delivering production-ready code every iteration. This book finally lays out exactly what this really means for critical systems today. You have a winner here. Tom Poppendieck Poppendieck.LLC It’s brilliant. Absolutely awesome. This book would’ve saved [Really Big Company] hundreds of thousands, if not millions, of dollars in a recent release. Jared Richardson Agile Artisans, Inc. Beware! This excellent package of experience, insights, and patterns has the potential to highlight all the mistakes you didn’t know you have already made. Rejoice! Michael gives you recipes of how you redeem yourself right now. An invaluable addition to your Pragmatic bookshelf. Arun Batchu Enterprise Architect, netrii LLC Release It! Design and Deploy Production-Ready Software Michael T. Nygard 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. 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. Our Pragmatic courses, workshops, and other products can help you and your team create better software and have more fun.
    [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]
  • The Irregular Musings of Lou Montulli: the Reasoning Behind Web Cookies
    1/25/2018 The irregular musings of Lou Montulli: The reasoning behind Web Cookies The irregular musings of Lou Montulli Early web guy, engineer and entrepreneur TUESDAY, MAY 14, 2013 BLOG ARCHIVE ► 2015 (1) The reasoning behind Web Cookies ► 2014 (2) I get a fair number of questions about cookies from ▼ 2013 (15) individuals and the press. I thought I would try and ► June (5) explain some of the motivation and history behind Web ▼ May (10) cookies as well as some of the design behind them. Value based home music recording Feel free to post more questions and I will try and expand this article with more details. Wow, Flickr is giving away 1TB of storage for pers... See my recent post on 3rd party cookies as well! It's the end of <blink>! Why blocking 3rd party cookies could be a bad thin... Google "Play All" music service initial Motivation review HTTP is the networking language behind your browser. HTTP, or Hyper Text The reasoning behind Web Cookies Transport Protocol, was designed and introduced as part of the WWW project that started with Tim Berners­Lee at CERN and was expanded upon by several universities, A short history of the "about:" URL corporations and private individuals. The WWW and HTTP are open standards which The origins of the <blink> tag are published and given into the public trust in order to foster interoperability and to I'm trying out blogger create products that can become ubiquitous. Fine cabinetry meets not so modern gaming One of the problems faced in the early years of the web was how to create websites that had "memory" for individual users.
    [Show full text]
  • A Taxonomy of Hyperlink Hiding Techniques
    A Taxonomy of Hyperlink Hiding Techniques Guang-Gang Geng1, Xiu-Tao Yang2, Wei Wang1, and Chi-Jie Meng1 1 China Internet Network Information Center, Computer Network Information Center, Chinese Academy of Sciences, Beijing, China, 100180 {gengguanggang,wangwei,mengchijie}@cnnic.cn 2 Beijing Institute of Electronic System Engineering, Beijing, China, 100854 xiutaoyang [email protected] Abstract. Hidden links are designed solely for search engines rather than visitors. To get high search engine rankings, link hiding techniques are usually used for the profitability of underground economies, such as illicit game servers, false medical services, illegal gambling, and less attractive high-profit industry. This paper investigates hyperlink hiding techniques on the Web, and gives a detailed taxonomy. We believe the taxonomy can help develop appropriate countermeasures. Statistical experimental results on real Web data indicate that link hiding techniques are very prevalent. We also tried to explore the attitude of Google towards link hiding spam by analyzing the PageRank values of relative links. The results show that more should be done to punish the hidden link spam. Keywords: Web spam, link hiding, hidden spam, spam detection 1 Introduction Most Web surfers depend on search engines to locate information on the Web. Link analysis algorithms [1], such as PageRank [2] and HITS [3], are usually used for Search engines ranking. Link analysis algorithms assume that every link represents a vote of support, in the sense that if there is a link from page x to page y and these two pages are authored by different people, then the author of page x is recommending page y.
    [Show full text]
  • Internet Programming Chapter Name: Markup Language UNIT 1 MARKUP LANGUAGE
    Course Code: SIT1302 Course Name: Internet Programming Chapter Name: Markup Language UNIT 1 MARKUP LANGUAGE UNIT 1: Introduction to HTML - Structure of HTML, HTML elements - Mark up tags for inserting URL, Images, Tables, Frames - Form and its controls - Image maps - Client and Server Side – CSS – Inline – Internal and External - Multimedia components - Audio and Video - Dynamic HTML. 1.1 Introduction to HTML 1.1.1 Brief History of HTML In the late 1980's , A physicist, Tim Berners-Lee who was a contractor at CERN, proposed a system for CERN researchers. In 1989, he wrote a memo proposing an internet based hypertext system. Tim Berners-Lee is known as father of HTML. The first available description of HTML was a document called "HTML Tags" proposed by Tim in late 1991. 1.1.2 Features of HTML 1) It is a very easy and simple language. It can be easily understood and modified. 2) It is very easy to make effective presentation with HTML because it has a lot of formatting tags. 3) It is a markup language so it provides a flexible way to design web pages along with the text. 4) It facilitates programmers to add link on the web pages (by html anchor tag) , so it enhances the interest of browsing of the user. 5) It is platform-independent because it can be displayed on any platform like Windows, Linux and Macintosh etc. 6) It facilitates the programmer to add Graphics, Videos, and Sound to the web pages which makes it more attractive and interactive. ➢ HTML stands for Hyper Text Markup Language.
    [Show full text]