DOCSLIB.ORG

Requirements for Web Developers and Web Commissioners in Ubiquitous

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Requirements for Web Developers and Web Commissioners in Ubiquitous Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development Deliverable 3.2 :: Public Keywords: web design and development, Web 2.0, accessibility, disabled web users, older web users Inclusive Future Internet Web Services Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development I2Web project (Grant no.: 257623) Table of Contents Glossary of abbreviations ........................................................................................................... 6 Executive Summary .................................................................................................................... 7 1 Introduction ...................................................................................................................... 12 1.1 Terminology ............................................................................................................. 13 2 Requirements for Web commissioners ............................................................................ 15 2.1 Introduction .............................................................................................................. 15 2.2 Previous work ........................................................................................................... 15 2.3 Method ..................................................................................................................... 17 2.3.1 Participants ........................................................................................................... 17 2.3.2 Interview schedule ............................................................................................... 18 2.3.3 Procedure ............................................................................................................. 18 2.4 Results ...................................................................................................................... 18 2.4.1 Range of organizations ......................................................................................... 18 2.4.2 The websites and web applications ..................................................................... 19 2.4.3 Organization of web design and development .................................................... 19 2.4.4 Website audiences ............................................................................................... 20 2.4.5 Policy on website accessibility ............................................................................. 20 2.4.6 Knowledge of and training in web accessibility and related concepts ................ 20 2.4.7 Quality processes for web accessibility ................................................................ 21 2.4.8 Quality processes for web usability ..................................................................... 21 2.5 Discussion and Conclusions ...................................................................................... 22 3 Requirements for web developers ................................................................................... 24 3.1 Introduction .............................................................................................................. 24 3.2 Previous work ........................................................................................................... 24 3.3 Survey of Web Developer Practices ......................................................................... 27 3.3.1 Method ................................................................................................................. 27 3.3.2 Results .................................................................................................................. 29 3.4 Contextual Inquiries with Web Developers ............................................................. 35 3.4.1 Method ................................................................................................................. 35 3.4.2 Results .................................................................................................................. 39 3.4.3 Discussion and Conclusions .................................................................................. 50 4 Requirements for Web accessibility experts .................................................................... 54 4.1 Introduction .............................................................................................................. 54 4.2 Method ..................................................................................................................... 54 Version 2.0 Page 2 of 92 © I2Web Consortium 2011 Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development I2Web project (Grant no.: 257623) 4.2.1 Participants ........................................................................................................... 54 4.2.2 Interview schedule ............................................................................................... 55 4.2.3 Procedure ............................................................................................................. 56 4.2.4 Data Analysis ........................................................................................................ 56 4.3 Results ...................................................................................................................... 56 4.3.1 Training and Experience ....................................................................................... 56 4.3.2 Participation in Guidelines/Standards Bodies ...................................................... 57 4.3.3 Tool Functionality ................................................................................................. 57 4.3.4 Completeness of accessibility tests ...................................................................... 60 4.3.5 Sampling Pages for Accessibility Testing .............................................................. 60 4.3.6 Tracking of Accessibility Tests and Problems ....................................................... 61 4.4 Common Accessibility Problems .............................................................................. 62 4.4.1 Reporting Accessibility Problems ......................................................................... 63 4.4.2 Maintenance of Accessibility ............................................................................... 64 4.5 Discussion and Conclusions ...................................................................................... 64 5 References ........................................................................................................................ 66 Appendix A: Interview schedule for website commissioners ................................................. 68 Appendix B: Survey of Web Developer Practices ..................................................................... 73 Appendix C: Contextual inquiry schedule on “Accessibility support for web developers” ..... 81 Appendix D: Web Accessibility Evaluator Interview Schedule ................................................. 90 Version 2.0 Page 3 of 92 © I2Web Consortium 2011 Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development I2Web project (Grant no.: 257623) List of Tables Table 2.1: Frequency of website features ................................................................................ 19 Table 2.2: Knowledge/Training in web technologies, accessibility and usability .................... 21 Table 3.1: Age distribution of respondents .............................................................................. 28 Table 3.2: Experience distribution of respondents .................................................................. 29 Table 3.3: Features for which the largest proportion of respondents prefer to use an IDE ... 32 Table 3.4: Features for which the largest proportion of respondents prefer to use some other application ................................................................................................................................ 33 Table 3.5: Features for which the largest proportion of respondents do not use .................. 33 Table 3.6: Technologies for which the largest proportion of respondents prefer to use an IDE .................................................................................................................................................. 33 Table 3.7: Technologies for which the largest proportion of respondents prefer to use a text editor ........................................................................................................................................ 33 Table 3.8: Technologies for which the largest proportion of respondents prefer to use some other application ...................................................................................................................... 34 Table 3.9: Technologies for which the largest proportion of respondents do not use ........... 34 Table 4.1: Age breakdown of interviewees .............................................................................. 54 Table 4.2: Functionality used in WATTs and AATTs ................................................................. 58 Version 2.0 Page 4 of 92 © I2Web Consortium 2011 Requirements for web developers and web commissioners in ubiquitous Web 2.0 design and development I2Web project (Grant no.: 257623) Contractual Date of Delivery to the EC: 30th April 2011 + 60 days
Load more

Recommended publications
  • Translators' Tool
    The Translator’s Tool Box A Computer Primer for Translators by Jost Zetzsche Version 9, December 2010 Copyright © 2010 International Writers’ Group, LLC. All rights reserved. This document, or any part thereof, may not be reproduced or transmitted electronically or by any other means without the prior written permission of International Writers’ Group, LLC. ABBYY FineReader and PDF Transformer are copyrighted by ABBYY Software House. Acrobat, Acrobat Reader, Dreamweaver, FrameMaker, HomeSite, InDesign, Illustrator, PageMaker, Photoshop, and RoboHelp are registered trademarks of Adobe Systems Inc. Acrocheck is copyrighted by acrolinx GmbH. Acronis True Image is a trademark of Acronis, Inc. Across is a trademark of Nero AG. AllChars is copyrighted by Jeroen Laarhoven. ApSIC Xbench and Comparator are copyrighted by ApSIC S.L. Araxis Merge is copyrighted by Araxis Ltd. ASAP Utilities is copyrighted by eGate Internet Solutions. Authoring Memory Tool is copyrighted by Sajan. Belarc Advisor is a trademark of Belarc, Inc. Catalyst and Publisher are trademarks of Alchemy Software Development Ltd. ClipMate is a trademark of Thornsoft Development. ColourProof, ColourTagger, and QA Solution are copyrighted by Yamagata Europe. Complete Word Count is copyrighted by Shauna Kelly. CopyFlow is a trademark of North Atlantic Publishing Systems, Inc. CrossCheck is copyrighted by Global Databases, Ltd. Déjà Vu is a trademark of ATRIL Language Engineering, S.L. Docucom PDF Driver is copyrighted by Zeon Corporation. dtSearch is a trademark of dtSearch Corp. EasyCleaner is a trademark of ToniArts. ExamDiff Pro is a trademark of Prestosoft. EmEditor is copyrighted by Emura Software inc. Error Spy is copyrighted by D.O.G. GmbH. FileHippo is copyrighted by FileHippo.com.
    [Show full text]
  • Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe
    Weblint: Just Another Perl Hack Neil Bowers1 Canon Research Centre Europe Abstract Weblint is a utility for checking the syntax and style of HTML pages. It was inspired by lint [15], which performs a similar function for C and C++ programmers. Weblint does not aspire to be a strict SGML validator, but to provide helpful comments for humans. The importance of quality assurance for web sites is introduced, and one particular area, validation of HTML, is described in more detail. The bulk of the paper is devoted to weblint: what it is, how it is used, and the design and implementation of the current development version. 1. Introduction The conclusion opens with a summary of the information and opinions given in this paper. A Web sites are becoming an increasingly critical part of selection of the lessons learned over the last four years how many companies do business. For many companies is given, followed by plans for the future, and related web sites are their business. It is therefore critical that ideas. owners of web sites perform regular testing and analysis, to ensure quality of service. 2. Web Site Quality Assurance There are many different checks and analyses which The following are some of the questions you should be you can run on a site. For example, how usable is your asking yourself if you have a web presence. I have site when accessed via a modem? An incomplete list of limited the list to those points which are relevant to similar analyses are given at the start of Section 2.
    [Show full text]
  • Fortran Resources 1
    Fortran Resources 1 Ian D Chivers Jane Sleightholme October 17, 2020 1The original basis for this document was Mike Metcalf’s Fortran Information File. The next input came from people on comp-fortran-90. Details of how to subscribe or browse this list can be found in this document. If you have any corrections, additions, suggestions etc to make please contact us and we will endeavor to include your comments in later versions. Thanks to all the people who have contributed. 2 Revision history The most recent version can be found at https://www.fortranplus.co.uk/fortran-information/ and the files section of the comp-fortran-90 list. https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=comp-fortran-90 • October 2020. Added an entry for Nvidia to the compiler section. Nvidia has integrated the PGI compiler suite into their NVIDIA HPC SDK product. Nvidia are also contributing to the LLVM Flang project. • September 2020. Added a computer arithmetic and IEEE formats section. • June 2020. Updated the compiler entry with details of standard conformance. • April 2020. Updated the Fortran Forum entry. Damian Rouson has taken over as editor. • April 2020. Added an entry for Hewlett Packard Enterprise in the compilers section • April 2020. Updated the compiler section to change the status of the Oracle compiler. • April 2020. Added an entry in the links section to the ACM publication Fortran Forum. • March 2020. Updated the Lorenzo entry in the history section. • December 2019. Updated the compiler section to add details of the latest re- lease (7.0) of the Nag compiler, which now supports coarrays and submodules.
    [Show full text]
  • Current Trends in Vector-Based Internet Mapping: a Technical Review
    Chapter 3 Current Trends in Vector-Based Internet Mapping: A Technical Review Christophe Lienert, Bernhard Jenny, Olaf Schnabel, and Lorenz Hurni Abstract Possibilities and limitations of Internet cartography software largely depend on the pace set by the software industry. The variety of commercial and non-commercial software caters for the needs of a continuously growing mapping community, including both professional and amateur cartographers. This chapter provides an overview of state-of-the-art technologies for vector-based Web- mapping as of the beginning of 2011. Both proprietary and open format technologies are discussed for vector data rendering in browsers, highlighting their advantages and disadvantages. The discussed technologies are Adobe Flash, Microsoft Silverlight, Scalable Vector Graphics (SVG), JavaFX, Canvas, and WebGL. The chapter also discusses client and server side frameworks which provide Application Programming Interfaces (APIs) for creating custom interactive maps, mainly by overlaying raster images with vector data. 3.1 Introduction Internet maps are the major form of spatial information delivery, as the Internet is today the primary medium for the transmission and dissemination of maps (Peterson 2008). For map authors, the maze of available techniques for creating and distributing Web maps is overwhelming, while authoring tools for Web-maps meeting the demands of high-quality cartography are difficult to find. Map authors may choose between GIS and graphics software products to create maps for the Internet, but these off-the-shelve maps oftentimes fall short of effectively convey- ing information. There are three main reasons for this shortcoming: (a) the design of these maps sometimes does not take into account the specific limitations of digital displays (Jenny et al., 2008); (b) the maps are often restricted in using standard C.
    [Show full text]
  • Rich Internet Applications
    Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight Master of Science Thesis in the Programme Software Engineering and Technology CARL-DAVID GRANBÄCK Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Göteborg, Sweden, October 2009 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight CARL-DAVID GRANBÄCK © CARL-DAVID GRANBÄCK, October 2009. Examiner: BJÖRN VON SYDOW Department of Computer Science and Engineering Chalmers University of Technology SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg, Sweden, October 2009 Abstract This Master's thesis report describes and compares the three Rich Internet Application !RIA" frameworks Adobe Flex, JavaFX and Microsoft Silverlight.
    [Show full text]
  • ANNI BOND 3101 Cinnamon Circle | Raleigh, NC 27610 (919) 758-6935 | [email protected]
    ANNI BOND 3101 Cinnamon Circle | Raleigh, NC 27610 (919) 758-6935 | [email protected] OBJECTIVE To write/edit technical documentation in the technology or gaming fields. PROFESSIONAL Troppus Software Corporation Superior, CO EXPERIENCE SKMS KB/CM Engineer, Engineering 2011 – Present Developed content for the premium tech support application, Symbi. Managed Sling Media knowledge base initiative where new Sling Media articles and article updates were implemented in our knowledge base for a Sling Media-branded version of our client; Spearheaded the development of the first internal style guide. Edited articles written by other content engineers for spelling, grammar, correctness, consistency, and in-house style guide adherence; Tested features, bugs, and fixes in the development tools. Tested DISH Network ViP722k, Hopper with Sling Adapter, and Joey DVRs. University of North Carolina at Charlotte Charlotte, NC Intern, Information Technology Services 2011 Authored a 60+ page manual with another student for the System Administration Management (SAM) tool, used to plan budgets and expenses in UNC Charlotte colleges; Authored a 30+ page manual for the reports section; Authored a quick reference guide for SAM; Edited a reference guide of commonly used account codes for SAM. UNC Charlotte Student Media Publications Charlotte, NC Copy Editor, The University Times 2009 – 2011 Was promoted to Asstistant Copy Editor in January 2010 and again to Copy Editor in August 2010. Edited articles written by other students for grammar, spelling, and Associated Press errors and applied the edits to digital copies; Edited housing and welcome guides produced by the paper three times a year; Wrote stories about events or ideas that impacted Charlotte.
    [Show full text]
  • Geany Tutorial
    How to use Geany Geany is essentially a text editor. To begin writing your program, you will need to create a new, blank file. Click on New. A new file called untitled will appear. You may start writing. As soon as you do, the option to save the file will be available. If the name of your file is in red, it means that it hasn’t been saved since the last change that is made. Click on the button called Save next to the New button. Save the file in a directory you had previously created before you launched Geany and name it main.cpp. All of the files you will write and submit to will be named specifically main.cpp. Once the .cpp has been specified, Geany will turn on its color coding feature for the C++ template. Next, we will set up our environment and then write a simple program that will print something to the screen Feel free to supply your own name in this small program Before we do anything with it, we will need to configure some options to make your life easier in this class The vertical line to the right marks the ! boundary of your code. You will need to respect this limit in that any line of code you write must not cross this line and therefore be properly, manually broken down to the next line. Your code will be printed out for The line is not where it should be, however, and grading, and if your code crosses the we will now correct it line, it will cause line-wrapping and some points will be deducted.
    [Show full text]
  • Fira Code: Monospaced Font with Programming Ligatures
    Personal Open source Business Explore Pricing Blog Support This repository Sign in Sign up tonsky / FiraCode Watch 282 Star 9,014 Fork 255 Code Issues 74 Pull requests 1 Projects 0 Wiki Pulse Graphs Monospaced font with programming ligatures 145 commits 1 branch 15 releases 32 contributors OFL-1.1 master New pull request Find file Clone or download lf- committed with tonsky Add mintty to the ligatures-unsupported list (#284) Latest commit d7dbc2d 16 days ago distr Version 1.203 (added `__`, closes #120) a month ago showcases Version 1.203 (added `__`, closes #120) a month ago .gitignore - Removed `!!!` `???` `;;;` `&&&` `|||` `=~` (closes #167) `~~~` `%%%` 3 months ago FiraCode.glyphs Version 1.203 (added `__`, closes #120) a month ago LICENSE version 0.6 a year ago README.md Add mintty to the ligatures-unsupported list (#284) 16 days ago gen_calt.clj Removed `/**` `**/` and disabled ligatures for `/*/` `*/*` sequences … 2 months ago release.sh removed Retina weight from webfonts 3 months ago README.md Fira Code: monospaced font with programming ligatures Problem Programmers use a lot of symbols, often encoded with several characters. For the human brain, sequences like -> , <= or := are single logical tokens, even if they take two or three characters on the screen. Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. Ideally, all programming languages should be designed with full-fledged Unicode symbols for operators, but that’s not the case yet. Solution Download v1.203 · How to install · News & updates Fira Code is an extension of the Fira Mono font containing a set of ligatures for common programming multi-character combinations.
    [Show full text]
  • Flex Resources*
    OpenStax-CNX module: m34542 1 Flex Resources* R.G. (Dick) Baldwin This work is produced by OpenStax-CNX and licensed under the Creative Commons Attribution License 3.0 Abstract The purpose of this document is to provide a list of links to online Flex and ActionScript resources to supplement the other lessons in the series. 1 Table of Contents • Preface (p. 1) • Resources (p. 1) • Miscellaneous (p. 3) 2 Preface This tutorial lesson is part of a series of lessons dedicated to programming using Adobe Flex. The purpose of this document is to provide a list of links to online Flex and ActionScript resources to supplement the other lessons in the series. note: The material in these lessons is based on Flex version 3 and Flex version 4. 3 Resources • Baldwin's Flex programming website 1 • Baldwin's ActionScript programming website 2 • Adobe Flex Home 3 • Download free open-source Adobe Flex 3.5 SDK 4 · Adobe Flex SDK Installation and Release Notes 5 · Application Deployment 6 • Download free open-source Adobe Flex 4 SDK 7 *Version 1.2: Jun 8, 2010 3:07 pm -0500 http://creativecommons.org/licenses/by/3.0/ 1http://www.dickbaldwin.com/tocFlex.htm 2http://www.dickbaldwin.com/tocActionScript.htm 3http://www.adobe.com/products/ex/?promoid=BPDEQ 4http://www.adobe.com/cfusion/entitlement/index.cfm?e=ex3sdk 5http://www.adobe.com/support/documentation/en/ex/3/releasenotes_ex3_sdk.html#installation 6http://livedocs.adobe.com/ex/3/html/help.html?content=Part3_deploy_1.html 7http://opensource.adobe.com/wiki/display/exsdk/Download+Flex+4 http://cnx.org/content/m34542/1.2/
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • These Web Design Tools Help with Access and Aesthetics
    These Web design tools help with access and aesthetics Company Product name Platform Notes Price Adobe Systems Inc. GoLive Windows, Mac Dynamic content Web design and site management package $499 San Jose, Calif. 800-833-6687 www.adobe.com Agile Compware Ltd. Agile Color Web Win95 up Shows how colors will appear in different browsers and monitors $10 Cambridge, U.K. www.agilie.com Apache Software Foundation PHP Linux, Mac General purpose server scripting language Free www.php.net Bare Bones Software Inc. BBEdit Mac Robust text-based Web page editor $119 Bedford, Mass. 781-687-0700 www.barebones.com Freecode HTP Windows, Unix Preprocessor Free www.freecode.com/ projects/htp iMatix Corp. HTMLpp MS-DOS, Preprocessor Free Brussels, Belgium Windows, www.imatix.com Unix Labyrinth Ppwizard MS-DOS, HTML preprocessor Free www.labyrinth.net.au/ Windows, BeOS, ~dbareis/ppwizard.htm Linux, OS/2 Macromedia Inc. HomeSite Windows Web site editor, with Dreamweaver $30 San Francisco 415-252-2000 Dreamweaver Fireworks Studio Windows, Mac High-end graphics and HTML editor $399 www.macromedia.com Macromedia Solutions Kit Windows 2 CD set includes design guides and templates Free 508 Accessibility Suite Windows, Mac Extensions for Dreamweaver Free Dreamweaver Accessibility Templates Windows, Mac Shows one way to reach 508 compliance Free Media Design in Progress Interaction Mac Web server companion helps automate updates; works with Mac, $795 Coronado, Calif. HTTP, WebServer 4D, Web-ten, Quid Pro Quo and WebStar 619-437-0664 interaction.in-progress.com Cascade Mac Cascading style sheet editor; lets you tailor sites for different visitors $69 Xpublish Mac For medium to large Web sites; uses CSS and XML $495 Sausage Software HotDog Professional Windows Editor supports HTML, CSS, ASP, PHP, VBScript, JavaScript $100 Southbank, Victoria, Australia 61-3-8696-6128 www.sausage.com/ Shadi-Soft Web Speak Windows Adds basic speech to Web pages $20 Nepean, Ontario 613-596-0048 www.shadisoft.com William F.
    [Show full text]
  • 1 Chapter -3 Designing Simple Website Using Kompozer
    RSCD Chapter -3 Designing Simple Website Using KompoZer ------------------------------------------------------------------------------------------- 1. ……………plays a very important role in a business now-a-days. a) Website b) webpage c) Web browser d) Web host 2. …………….is a collection of interlinked web pages for a specific purpose. a) Website b) webpage c) Web browser d) Web host 3. ………….defines what we want to achieve by developing a website. a)Objective b) Goal c) Planning d) Target 4. Once by knowing the reason for developing a website, you must decide …….of the website. a)Objective b) Goal c) Planning d) Target 5. ……….means for whom the website is to be developed. a)Objective b) Goal c) Planning d) Target audience 6. From the following which is important for content of a webpage? a) Text and graphics for website b) Content as per visitor’s requirements c) Too short or too long content d) All of these 7. Who provides trial version of the software for free download? a) Editor b) Vendor c) Visitor d) None 8. The visual diagram of the website is known as ……………… a) Site Map b) Image Map c) Site Editor d) Site Browser 9. The website should contain should be classified into ………….categories. a) General b) Detailed c) Simple d) Both a and b 10. What is the first step for planning a website? a) Homepage b) Target audience c) Objective and Goal d) Browser compatibility 11. The website must contain ………………….information. a) Complete b) relevant c) incomplete d) Both a and b 12. What is the key point of a website? a) Content b) Homepage c) Objective and Goal d) Browser Compatibility 13.
    [Show full text]