Software Tools for Blind and Visually Impaired in GNOME2 Œaccessibilty in GNOME2 Œ

Total Page:16

File Type:pdf, Size:1020Kb

Software Tools for Blind and Visually Impaired in GNOME2 Œaccessibilty in GNOME2 Œ Anale. Seria Informatic. Vol. III fasc. I Annals. Computer Science Series. 3rd Tome 1st Fasc. Software tools for blind and visually impaired in GNOME2 œAccessibilty in GNOME2 œ Dr. Victoria Iordan, Associate Professor University of the W est, Timisoara, Romania REZUMAT. Aceast lucrare are drept scop prezentarea İi analizarea posibilit$ilor ca o persoan cu handicap vizual s utilizeze calculatorul folosind desktopul GNOME. Ín prima parte lucrarea prezint no$iunea de accesibilitate (—Accessibility“) în general İi identific solu$ii existente pentru a da sens no$iunii de accesibilitate referitor la persoanele cu deficien$e vizuale, fcându-se analiza desktopului GNOME İi a suportului pe care acesta îl ofer pentru accesibilitate. Partea a doua este dedicat analizei unicului screen reader pentru GNOME (cel pu$in pân în momentul de fa$): Gnopernicus. Acesta este parte a GAP (Gnome Accessibility Project), managementul proiectului fiind realizat de Sun Microsystems în colaborare cu BAUM Retec AG dar implementarea efectiv realizându-se în România, de ctre BAUM Engineering S.R.L. Este analizat modul în care este posibil s i se ofere utilizatorului un feedback auditiv (comunicarea cu diferite mecanisme TTS œ Text To Speech) İi de asemenea modul în care se poate oferi un feedback Braille (cum se pot accepta mai multe tipuri de dispozitive Braille, mai multe tabele braille). 1. W hat Accessibility means? Accessibility is about enabling people with disabilities to participate in substantial life activities that include work and the use of services, products, and information. Everybody must be sure that PC technology can be tremendously empowering. A significant portion of the growth in the U.S. economy during the 1990s can be directly attributed to productivity improvements 39 Anale. Seria Informatic. Vol. III fasc. I Annals. Computer Science Series. 3rd Tome 1st Fasc. brought on by PC technology. W ith each new generation of PCs, new applications are enabled that offer more benefits. As PCs become more powerful, they improve most people‘s lives in more ways every day. The PC technology can be particularly empowering for people who are blind or visually impaired. In an increasingly information-driven economy, the potential benefit of personal computers on employment for blind and visually impaired people is dramatic. The unemployment rate for blind and severely visually impaired people in the U.S. is currently over 70%. The PCs, paired with accessibility technology, have allowed the disabled users to effectively overcome their visual disabilities, and to live and work with able-bodied people in ways that would have otherwise been impossible. By opening up new opportunities to hold mainstream jobs œ good jobs that make full use of a person‘s mental talents and abilities œ PCs can bring blind and visually impaired people out of a world of dependence and isolation and into one of full productivity and participation. Indeed, PCs have promised to be the most important tool for empowerment of blind and visually impaired people since the invention of Braille or the magnifying glass. History of the Development of Blind and Low-Vision AT The history of accessibility technology for blind and visually impaired users is one of rapid innovation and continual adaptation. In the early days of computers, accessibility for blind users was not terribly difficult. A standard 80x24 text screen used by DOS and other text-only operating systems could be reliably translated into refreshable Braille or speech (using special hardware connected to a serial port). These were very exciting days for blind people. Using the new technologies, they could stand practically level with other sighted colleagues. Then came W indows… W indows 3.0 and 3.1 didn‘t work with the traditional DOS screen readers. The visual interface was fundamentally more complex, as well as the underlying operating system technologies. Unfortunately, W indows 3.1 did not come with any support for accessibility utilities. Screen reader companies had to re-invent their products, using much more complex methods for gathering and interpreting information about what was happening on the screen. It took a while for screen reader companies to develop these utilities, and in the interim a number of blind people lost their jobs as their employers switched to W indows. As adoption of W indows accelerated and the introduction of W indows 95 (another major architectural revision of the operating system) loomed, blind people saw that they could once again lose jobs by the thousands. To remedy the situation, people within the Massachusetts Commission for the Blind, the 40 Anale. Seria Informatic. Vol. III fasc. I Annals. Computer Science Series. 3rd Tome 1st Fasc. Massachusetts Assistive Technology Partnership (MATP), the National Council on Disability, and the National Federation of the blind lobbied Microsoft to fix the problem by making windows accessible. Specifically, they asked for standard —hooks“ in the operating system that would support the creation of robust and reliable accessibility utilities. Their requests were generally rebuffed. W hen these methods failed, the advocates began to lobby state governments to get them to boycott Microsoft products until adequate accessibility technologies could be developed. That got Microsoft‘s attention. Microsoft‘s response to the commitment to provide —hooks“ in the operating system for use by accessibility utilities was the creation of the MSAA interfaces to facilitate direct communication between the applications and utilities. Initially it was hoped that this technology would solve the problem of making application accessible. Unfortunately, it took several years to complete the first version of MSAA, relatively few applications outside of Microsoft use it, and prospects for widespread adoption are not good. No corresponding standard lower-level hooks have been provided to implement reliable support for legacy and non-compliant applications (which grow geometrically in number every year). So the current situation is one of mixed progress and a similarly mixed outlook toward the future. W hile the overall reliability of screen readers for W indows has increased in the last 5 years, they are still plagued by technical problems. The W indows operating system has increased support for accessibility, but it also introduces significant new problems with each major update. But what about Linux? There are some solutions to allow people with visual disabilities to use it? The answer is YES: visually impaired people are able to use GNOME desktop (there are many signals that KDE will be also accessible in the near future) by using Gnopernicus as a screen reader and magnifier. How Screen Readers W ork œ Overview Screen readers are special utility programs that run concurrently with other regular programs to figure out what is on the screen, interpret it, and then interact with the blind or visually impaired user through text-to- speech or refreshable Braille. Screen readers use two primary methods to gather information about what is on the screen: a) directly communication with the applications that are running. This is preferred, but requires additional work on the part of the application vendor 41 Anale. Seria Informatic. Vol. III fasc. I Annals. Computer Science Series. 3rd Tome 1st Fasc. b) —hooks“ in the operating system that are used to intercept low- level operations, such as text output, to deduce what is going on. These and other sources of information are combined in real time to construct an alternate view of the world, frequently called an —off-screen model“ (OSM). Since utility programs do not have eyes to observe the output to the screen, they take a more sophisticated approach. The observation of normal output to the screen involves collecting (directly or indirectly) information from multiple sources within the system during normal program operation. Considered abstractly, some information is collected at a higher level (closer to the user) and some information is collected at a lower level (closer to the hardware). An example of a highest-level operation would be direct communication between the screen reader and a running application. In this instance the screen reader might ask, —W hat is under the mouse cursor?“ or —W hat text is in this rectangle on screen?“ This kind of direct communication represents the ideal situation, because the application has the opportunity to provide information about what is happening on screen that is sufficiently detailed and complete such that the screen reader can provide an adequate translation for the user. In the less ideal (though more common) situations, if the application does not provide a direct method for querying what is happening on the screen, the alternative fallback strategy for the screen reader is to infer, using lower-level information, what is happening. For example, all word processors generally send blocks of text to the screen using APIs provided by the operating system. By intercepting calls to the text-display APIs, the screen reader can see where most of the text is on the screen, and can then try to infer what is actually going on. This is a simplified example. Screen readers frequently rely on several types of intercepted information when making inferences about what is happening on the screen because each source of information is incomplete. The process of intercepting API calls in the system is called —hooking“. Historically there have been two primary methods of hooking calls in the operating system. —Hooking high“ means hooking the APIs that the operating system provides for use by applications. —Hooking low“ means hooking the display driver interfaces (DDIs), a step closer to the hardware (video card). The logic that must be used for interpretation and translation of the available high-level and low-level information is frequently very specific to individual applications. This means that the screen reader must effectively be tuned to work with each new application most effectively.
Recommended publications
  • Annual Report in This Report
    GNOME FOUNDATION 2018–2019 ANNUAL REPORT IN THIS REPORT 3 Letter from the GNOME Foundation 4 About GNOME 5 Releases 6 Accessibility 6 GNOME Moves to Discourse 7 GitLab Statistics and Activity 8 Hackfests CREDITS 9 Conferences Thank you to everyone involved in the making of this report! We appreciate the authors, editors, and organizers that helped highlight 10 Finances at a Glance all the great work GNOME accomplished in the 2018‑2019 fiscal year. Gaurav Agrawal, Matthias Clasen, Emmanuele Bassi, Molly de Blanc, 12 Outreach Sebastian Dröge, Caroline Henriksen, Juanjo Marin, Neil McGovern, Bartłomiej Piotrowski, Kristi Progri, Oliver Propst, Andrea Veri, 13 Friends of GNOME Britt Yazel, and Rosanna Yuen. 2 2019 was an exciting year for us! We increased the Foundation‘s staff with three new employees—a GTK+ core developer, a Program LETTER FROM Coordinator, and a Strategic Initiatives Manager—expanded our efforts with new projects, and continued making great soware. We had three wildly successful conferences, several hackfests, and a number of newcomer events geared towards helping new contributors get THE GNOME involved in GNOME. We sponsored three amazing Outreachy interns and mentored nine students through Google Summer of Code. There were numerous technical successes: updates to GTK, two new releases of the desktop environment, and numerous infrastructure improvements, including both hardware and soware upgrades. We introduced an Inclusion and Diversity team in order to make the FOUNDATION GNOME community a more welcoming place. We announced the GNOME Community Engagement Challenge. We had speakers and booths at conferences in Asia, Europe, North America, and South America.
    [Show full text]
  • 50 Are Gnome and KDE Equal? KNOW-HOW 50
    KNOW-HOW Ask Klaus! ASK KLAUS! and even with its very reduced features, linking of KDE or Gnome programs is it has always been sufficient for me. more likely fail because of this modular There were quarrels between develop- structure than for any other reason.) ers and users about KDE being “non- This can get you into some problems. Klaus Knopper is the creator of free” in the old days, because of the qt li- If you use KDE regularly, and you want Knoppix and co-founder of the cense (for the library KDE is based on); to install a single Gnome program such that it was more memory-consuming as Gnopernicus, you end up installing LinuxTag expo. He currently than Gnome; or that its graphics were the entire Gnome software suite because poorer. None of these are genuine prob- you won’t be able to to get the program works as a teacher, program- lems today, and I don’t know if the ru- to run otherwise. In very bad cases, mer, and consultant. If you have mors about graphics and memory con- Gnome dependencies try to deinstall sumption ever were true, or whether parts of KDE (or vice versa) because of a configuration problem, or if they were just part of the creative com- conflicting services that are present in petition between different groups and both (a very rare case, though). you just want to learn more philosophies. OK, I cheated a little in this example. about how Linux works, send Nowadays, Gnome consumes the Gnopernicus is more like a suite of pl- same amount of system resources as ugins and addons for Gnome than like a your questions to: KDE (if not more), performance bench- standalone application.
    [Show full text]
  • Guile-GNOME: Atk Version 2.16.2, Updated 9 December 2011
    Guile-GNOME: Atk version 2.16.2, updated 9 December 2011 Bill Haneman Marc Mulcahy Padraig O'Briain This manual is for (gnome atk) (version 2.16.2, updated 9 December 2011) Copyright 2001-2007 Bill Haneman, Marc Mulcahy, Padraig O'Briain Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation. i Short Contents 1 Overview :::::::::::::::::::::::::::::::::::::::::::: 1 2 AtkAction ::::::::::::::::::::::::::::::::::::::::::: 2 3 AtkComponent ::::::::::::::::::::::::::::::::::::::: 4 4 AtkDocument :::::::::::::::::::::::::::::::::::::::: 8 5 AtkEditableText ::::::::::::::::::::::::::::::::::::: 10 6 AtkGObjectAccessible :::::::::::::::::::::::::::::::: 12 7 AtkHyperlinkImpl :::::::::::::::::::::::::::::::::::: 13 8 AtkHyperlink ::::::::::::::::::::::::::::::::::::::: 14 9 AtkHypertext ::::::::::::::::::::::::::::::::::::::: 17 10 AtkImage::::::::::::::::::::::::::::::::::::::::::: 18 11 AtkNoOpObjectFactory ::::::::::::::::::::::::::::::: 20 12 AtkNoOpObject ::::::::::::::::::::::::::::::::::::: 21 13 AtkObjectFactory :::::::::::::::::::::::::::::::::::: 22 14 AtkObject :::::::::::::::::::::::::::::::::::::::::: 23 15 AtkRegistry ::::::::::::::::::::::::::::::::::::::::: 29 16 AtkRelationSet :::::::::::::::::::::::::::::::::::::: 31 17 AtkRelation::::::::::::::::::::::::::::::::::::::::: 33 18 AtkSelection :::::::::::::::::::::::::::::::::::::::: 35 19 AtkStateSet :::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • WIKI on ACCESSIBILITY Completion Report March 2010
    WIKI ON ACCESSIBILITY Completion report March 2010 By Nirmita Narasimhan Programme Manager Centre for Internet and Society Project Title: Wiki on “Accessibility, Disability and the Internet in India” Page | 1 REPORT Accessibility wiki: accessibility.cis-india.org The wiki project was envisaged and funded by the National Internet Exchange of India (www.nixi.in) and has been executed by the Centre for Internet and Society (www.cis-india.org), Bangalore. Project Start date: May 2009 End date: February 2010. Background India has a large percentage of disabled persons in its population— estimated to be over seven per cent as per the Census of 2001. Even this figure is believed to be a gross under representation of the total number of disabled persons residing in this large and diverse country. Taken in figures, this amounts to roughly 70-100 million persons with disabilities in the territory of India. Out of this number, a mere two per cent residing in urban areas have access to information and assistive technologies which enable them to function in society and enhance their performance. There are several reasons for this, one of them being that there is a deplorable lack of awareness which exists on the kinds of disabilities and about ways in which one can provide information and services to disabled persons. Parents, teachers, government authorities and society at large are all equally unaware about the options which exist in technology today to enable persons with disabilities to carry on independent and productive lives. Barring a few exceptions, India is still trapped in an era where a white cane and a Braille slate symbolises the future for blind people, while the world has progressed to newer forms of enabling technology such as screen readers, daisy players, the Kindle and so on.
    [Show full text]
  • A Game Engine for the Blind
    Bachelor in Computer Science and Engineering 2016/2017 Bachelor Thesis Designing User Experiences: a Game Engine for the Blind Álvaro Cáceres Muñoz Tutor/s: Teresa Onorati Thesis defense date: July 3rd, 2017 This work is subject to the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International Public License. Abstract Video games experience an ever-increasing interest by society since their incep- tion on the 70’s. This form of computer entertainment may let the player have a great time with family and friends, or it may as well provide immersion into a story full of details and emotional content. Prior to the end user playing a video game, a huge effort is performed in lots of disciplines: screenwriting, scenery design, graphical design, programming, opti- mization or marketing are but a few examples. This work is done by game studios, where teams of professionals from different backgrounds join forces in the inception of the video game. From the perspective of Human-Computer Interaction, which studies how people interact with computers to complete tasks [9], a game developer can be regarded as a user whose task is to create the logic of a video game using a computer. One of the main foundations of HCI1. is that an in-depth understanding of the user’s needs and preferences is vital for creating a usable piece of technology. This point is important as a single piece of technology (in this case, the set of tools used by a game developer) may – and should have been designed to – be used on the same team by users with different knowledge, abilities and capabilities.
    [Show full text]
  • Open Source Used in Tesla Series Switches 2.5.0.X 2.5.0.X
    Open Source Used In 250, 350, 350X, and 550X Series Switches 2.5.0.x Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-190526882 Open Source Used In 250, 350, 350X, and 550X Series Switches 2.5.0.x 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-190526882 En ce qui a trait au logiciel gratuit ou à exploitation libre figurant dans ce document, si vous avez des questions ou souhaitez recevoir une copie du code source, auquel vous avez droit en vertu des licences gratuites ou d'exploitation libre applicables (telles que licences GNU Lesser/General Public), veuillez communiquer avec nous à l'adresse external- [email protected]. Dans vos demandes, veuillez inclure le numéro de référence 78EE117C99-190526882 Contents 1.1 Angular Bootstrap 0.12.0 1.1.1 Available under license 1.2 Angular UI Sortable 1.1.1 1.2.1 Available under license 1.3 angular-chart.js 0.7.2 1.3.1 Available under license 1.4 Angular-dashboard-frmework 0.8.0 1.4.1
    [Show full text]
  • New Gnome 2.16 Desktop? NEW GNOME
    REVIEWS Gnome 2.16 What’s new in the new Gnome 2.16 desktop? NEW GNOME The changes in Gnome 2.16 are more than cosmetic: the current release sees a leaner and faster version of the desktop. BY CHRISTIAN MEYER ust six months ago, when Gtk#. The libraries makes it easier for Although Metacity, the original Gnome Gnome 2.14 reached the mirror developers who prefer not to use C to window manager, does not support all Jservers, the Gnome developers enter the world of Gnome. Gnome bind- the effects I just referred to, it will still proved they can set milestones without ings are available for C++, C#, and perform well with the new 3D X servers. sacrificing usability. Programs such as Python. The features are not enabled by default, the Deskbar applet demonstrate the but enabling them will give you a first power of Gnome’s underpinnings, pro- 3D Desktop impression of the capabilities you can viding an attractive GUI that is both effi- In last couple of years, much time and expect with the new X server extensions. cient and remarkably uncluttered. money has gone into investigating new You don’t even need to terminate the The latest 2.16 version adds a variety GUI concepts. One of the results is the current session (that is, log off and back of new features, and there have been Looking Glass project [1] by Sun Micro- on) to disable the effects. major improvements with respect to per- systems, which gives users the ability to formance and memory consumption.
    [Show full text]
  • Pulse Connect Secure 8.2R5 Attributions
    Pulse Connect Secure 8.2R5 Attributions Revision Date 08/18/16 © 2016 by Pulse Secure, LLC. All rights reserved 1 Pulse Connect Secure 8.2R3 Attributions Pulse Secure, LLC 2700 Zanker Road, Suite 200 San Jose, CA 95134 http://www.pulsesecure.net © 2016 by Pulse Secure, LLC. All rights reserved Pulse Secure and the Pulse Secure logo are trademarks of Pulse Secure, LLC in the United States. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Pulse Secure, LLC assumes no responsibility for any inaccuracies in this document. Pulse Secure, LLC reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Pulse Policy Secure Enterprise Guest Access Solution Configuration Guide The information in this document is current as of the date on the title page. END USER LICENSE AGREEMENT The Pulse Secure product that is the subject of this technical documentation consists of (or is intended for use with) Pulse Secure software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at http://www.pulsesecure.net/support/eula. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. © 2016 by Pulse Secure, LLC. All rights reserved 2 Pulse Connect Secure 8.2R5 Attributions Table of Contents This document contains information on the following products or licenses: Table of Contents .....................................................................................................................................
    [Show full text]
  • GNOME 3 Application Development Beginner's Guide
    GNOME 3 Application Development Beginner's Guide Step-by-step practical guide to get to grips with GNOME application development Mohammad Anwari BIRMINGHAM - MUMBAI GNOME 3 Application Development Beginner's Guide Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: February 2013 Production Reference: 1080213 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-942-7 www.packtpub.com Cover Image by Duraid Fatouhi ([email protected]) Credits Author Project Coordinator Mohammad Anwari Abhishek Kori Reviewers Proofreader Dhi Aurrahman Mario Cecere Joaquim Rocha Indexer Acquisition Editor Tejal Soni Mary Jasmine Graphics Lead Technical Editor Aditi Gajjar Ankita Shashi Production Coordinator Technical Editors Aparna Bhagat Charmaine Pereira Cover Work Dominic Pereira Aparna Bhagat Copy Editors Laxmi Subramanian Aditya Nair Alfida Paiva Ruta Waghmare Insiya Morbiwala About the Author Mohammad Anwari is a software hacker from Indonesia with more than 13 years of experience in software development.
    [Show full text]
  • Pdfswqokdvt2o.Pdf
    GNOME 3 Application Development Beginner's Guide Step-by-step practical guide to get to grips with GNOME application development Mohammad Anwari BIRMINGHAM - MUMBAI GNOME 3 Application Development Beginner's Guide Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: February 2013 Production Reference: 1080213 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-942-7 www.packtpub.com Cover Image by Duraid Fatouhi ([email protected]) Credits Author Project Coordinator Mohammad Anwari Abhishek Kori Reviewers Proofreader Dhi Aurrahman Mario Cecere Joaquim Rocha Indexer Acquisition Editor Tejal Soni Mary Jasmine Graphics Lead Technical Editor Aditi Gajjar Ankita Shashi Production Coordinator Technical Editors Aparna Bhagat Charmaine Pereira Cover Work Dominic Pereira Aparna Bhagat Copy Editors Laxmi Subramanian Aditya Nair Alfida Paiva Ruta Waghmare Insiya Morbiwala About the Author Mohammad Anwari is a software hacker from Indonesia with more than 13 years of experience in software development.
    [Show full text]
  • 2 ODF Application Accessibility
    Open Document Format v1.1 Accessibility Guidelines Version 1.0 Committee Specification 01 1 May 2008 Specification URIs: This Version: http://docs.oasis-open.org/office/office- accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.odt [Authoritative] http://docs.oasis-open.org/office/office- accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.pdf http://docs.oasis-open.org/office/office- accessibility/v1.0/cs01/ODF_Accessibility_Guidelines-v1.0.html Previous Version: http://docs.oasis-open.org/office/office- accessibility/v1.0/cd02/ODF_Accessibility_Guidelines-v1.0.odt http://docs.oasis-open.org/office/office- accessibility/v1.0/cd02/ODF_Accessibility_Guidelines-v1.0.pdf http://docs.oasis-open.org/office/office- accessibility/v1.0/cd02/ODF_Accessibility_Guidelines-v1.0.html Latest Version: http://docs.oasis-open.org/office/office-accessibility/v1.0/ODF_Accessibility_Guidelines- v1.0.odt http://docs.oasis-open.org/office/office-accessibility/v1.0/ODF_Accessibility_Guidelines- v1.0.pdf http://docs.oasis-open.org/office/office-accessibility/v1.0/ODF_Accessibility_Guidelines- v1.0.html Technical Committee: OASIS Open Document Format for Office Applications (OpenDocument) Technical Committee Co-chairs: Peter Korn, Sun Microsystems, Inc. Rich Schwerdtfeger, IBM ODF_Accessibility_Guidelines-v1.0.odt 1 May 2008 Copyright © OASIS Open 2006 - 2008. All Rights Reserved. Page 1 of 54 Editors: Peter Korn, Sun Microsystems, Inc. Rich Schwerdtfeger, IBM Related Work: These guidelines apply to the OASIS OpenDocument v1.1 specification, which can be found at: http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1.odt Abstract: This document is a guide for Office Applications, that support version 1.1 of the OpenDocument format, to promote and preserve accessible ODF documents.
    [Show full text]
  • Multi-Lingual Screen Reader and Processing of Font-Data in Indian Languages Submitted by A
    MULTI-LINGUAL SCREEN READER AND PROCESSING OF FONT-DATA IN INDIAN LANGUAGES A THESIS submitted by A. ANAND AROKIA RAJ for the award of the degree of Master of Science (by Research) in Computer Science & Engineering LANGUAGE TECHNOLOGIES RESEARCH CENTER INTERNATIONAL INSTITUTE OF INFORMATION TECHNOLOGY HYDERABAD - 500 032, INDIA February 2008 Dedication I dedicate this work to my loving parents ANTONI MUTHU RAYAR and MUTHU MARY who are always behind my growth. i THESIS CERTIFICATE This is to certify that the thesis entitled Multi-Lingual Screen Reader and Processing of Font-Data in Indian Languages submitted by A. Anand Arokia Raj to the International Institute of Information Technology, Hyderabad for the award of the degree of Master of Science (by Research) in Computer Science & Engineering is a bonafide record of research work carried out by him under our supervision. The contents of this thesis, in full or in parts, have not been submitted to any other Institute or University for the award of any degree or diploma. Hyderabad - 500 032 (Mr. S. Kishore Prahallad) Date: ACKNOWLEDGMENTS I thank my adviser Mr.Kishore Prahallad for his guidance during my thesis work. Because of him now I am turned into not only a researcher but also a developer. I thank Prof.Rajeev Sangal and Dr.Vasudeva Varma for their valuable advices and inputs for improving the screen reading software. I am also thankful to my speech lab friends and other IIIT friends who helped me in many ways. They were with me when I needed a help and when I needed a relaxation.
    [Show full text]