DOCSLIB.ORG

AN OPEN SOURCE SCREEN READER for BLIND and VISUALLY IMPAIRED PEOPLE Experiences and Thoughts

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AN OPEN SOURCE SCREEN READER for BLIND and VISUALLY IMPAIRED PEOPLE Experiences and Thoughts AN OPEN SOURCE SCREEN READER FOR BLIND AND VISUALLY IMPAIRED PEOPLE Experiences and Thoughts Martina Weicht, Frank Zenker, Ilvio Bruder and Andreas Heuer IT Science Center Ruegen gGmbH, Circus 14, 18581 Putbus/Ruegen, Germany Keywords: Open source software development, Community, eHealth, Screen reader. Abstract: Developing open source software offers great potential for sustainable software evolution and for software product distribution, holding particular advantages in financial, psychological, security, and other aspects. However, lots of effort and fortunate circumstances are needed to enforce them. This paper will take a look at open source software development and its success factors using the example of the SUE screen reader project. This project deals with supporting blind and visually impaired users on Linux by providing alternative access to the graphical user interface. The development of SUE is an interesting example of FLOSS development in the eHealth area. We will introduce SUE and provide an overview of our open source development experiences discussing a special factor in the success of open source development: communities. 1 INTRODUCTION ment in SUE along with its success factors and chal- lenges, we will introduce the SUE project in section Open source software development provides an inter- 2 and provide an overview of our open source devel- esting way for sustainable software evolution and for opment experiences in section 3. In section 4 we will distributing software products. It offers advantages in discuss a special factor in the success of open source various aspects such as in economy (efficient produc- development: communities. Section 5 summarizes tion of software based on available resources, better and discusses our experiences. market position among competitors with similar, but non-free products, shorter time to market thanks to code reuse), in security (quick identification of po- 2 THE OPEN SOURCE SCREEN tential security problems and their correction), and in READER SUE personal psychology (peer recognition, engagement into a rewarding task) – just to name a few. For a more The project SUE: Screenreader & Usability Exten- detailed discussion cf. (Working group on Libre Soft- sions2 has been funded by the German Federal Min- ware, 2000). However, to enforce these aspects lots istry for Labor and Social Affairs for a period of 3 of effort and also fortunate circumstances are needed. years (2007 – 2009). Its goal was to support blind and This paper will take a look at open source software visually impaired computer users on Linux using the development and its success factors using the example most important applications: desktop environment in- of the SUE screen reader project. This project deals teraction, e-mail and text processing, spreadsheet cal- with supporting blind and visually impaired users on culation and a basic web browser support. Linux by providing alternative access to the graphical Development for SUE is based on the former user interface. The development of SUE is an interest- 3 1 Linux Screen Reader (LSR) project . LSR was meant ing example of FLOSS development in general and to be a “reusable development platform for building in the health care area in particular. alternative and supplemental user interfaces in sup- In order to describe open source software develop- port of people with diverse disabilities” (Parente and 1Free/Libre Open Source Software; free/libre/open 2http://sue.sourceforge.net/ in terms of source code access and reuse 3http://live.gnome.org/LSR 525 Weicht M., Zenker F., Bruder I. and Heuer A. (2010). AN OPEN SOURCE SCREEN READER FOR BLIND AND VISUALLY IMPAIRED PEOPLE - Experiences and Thoughts. In Proceedings of the Third International Conference on Health Informatics, pages 525-531 DOI: 10.5220/0002787905250531 Copyright c SciTePress HEALTHINF 2010 - International Conference on Health Informatics Clippingdale, 2006). Its development was funded by 3 REQUIREMENTS FOR A IBM until a change in their accessibility support strat- SUCCESSFUL OPEN SOURCE egy (Parente, 2007b) led to the LSR project going dor- mant after one last release of version 0.5.3. PROJECT Looking carefully into the LSR project and all the There are quite a few information sources available on work that had been done up to then, the decision was criterias for a successful open source project. Some of made to base screen reader development within SUE them provide rather practical guidelines such as “Use upon the LSR project – made possible by generous a version control system” or “Get free hosing for your licensing of LSR. project”6. Others describe more abstract success fac- For the SUE project, building upon LSR meant tors like pursuing a clear goal, maintaining focus on that we did not have to start from scratch. The LSR the project’s mission, or choosing a business model7. code base was carefully laid out as a sustainable, ex- With our background in software development, we tensible architecture for assistive applications and al- have chosen four main success criteria and will apply lowed us to continue its development both along our them to the screen reader project. ideas and a retrospect document provided by the LSR project lead (Parente, 2007a). Most of its architecture 3.1 Resources in Terms of Time, is still recognizable in SUE, especially the strategy of Knowledge, and Money abstracting dependencies which was even improved in SUE. The code has been adapted to a more recent When the SUE project started, resources seemed version of the used accessibility interface and restruc- plenty. The project was laid out for four full-time de- tured for better handling. Some of the actual screen velopers over a period of three years. None of them reading functionality was only implemented in very had any experience in either open source software de- basic ways in LSR, such as Braille support, which we velopment (though all have been using open source integrated into a holistic output concept for all out- software before) or screen reader software, but had put capabilities in SUE: Braille, speech, and magni- different levels of experience in software development fication. These are represented by both virtual and in general (on Windows and Linux) and in project physical devices: a Braille display and a Braille moni- management. In order to gain insight into both of the tor, magnification, and speech output (text-to-speech). new fields, a community of open source / accessibil- Application support – both for the requested applica- ity / screen reader experts was brought together in a tions and a few small other ones – had to be updated workshop. and extended in some parts and newly created in oth- ers. 3.2 A Clear Goal and a Goal-pursuing Today, SUE’s base called AccessEngine is this en- visioned platform for assistive applications and the Strategy screen reader SUE is the first of them; others are cer- tainly possible. In general, the AccessEngine pro- After the workshop, the project team retreated to eval- vides an event-based information processing to any uating and interpreting this gathering, unifying its re- input and output devices connected to it. It takes care sults with their project description while going into of all data and device management tasks including re- further research where necessary, into requirements ceiving information from the accessibility interface analysis and project specification. This behavior has (AT-SPI, part of Gnome Accessibility project4) and been criticized by the above-mentioned community as delivering it to the proper recipients. they did not feel involved into the decision-making process. They expected a more bazaar-like project or- Both the AccessEngine and SUE are published 5 ganization (many contributors loosely organized via under BSD license , so anyone may either support our the Internet) whereas the project team – coming from work, develop their own open source screen reader closed source software development – adopted the based on SUE or develop another open source assis- cathedral style (code developed by small group and tive application based on the AccessEngine. One idea released to the public) (Raymond, 1999). This ap- may be to integrate it into an AAL scenario by turning proach seemed natural to the project team as they the TV into an easy-to-use in-home information basis were funded by the Ministry as opposed to the group with speech output and sound icons. 6http://www.wikihow.com/Have-a-Successful-Open- Source-Project 4http://projects.gnome.org/accessibility/ 7http://beradrian.wordpress.com/2009/05/12/success- 5http://www.opensource.org/licenses/bsd-license.php in-open-source/ 526 AN OPEN SOURCE SCREEN READER FOR BLIND AND VISUALLY IMPAIRED PEOPLE - Experiences and Thoughts of volunteers spending their free time on open source titude of tools for open source software development: projects. Unfortunately, this misconception signif- web hosting, forums, blogs, mailing lists, trackers for icantly harmed the parties’ trust into one another, bugs, feature requests, and patches, code control sys- which for the remainder of the project did not recover. tems like SVN, Bazaar, Git, a file release system, Meanwhile with respect to their project descrip- project, content and task management tools, a wiki tion the development team made decisions for their and more. SourceForge.net is well-established among development, defined a road map and milestones for OSS developers and only requires one registration for their work and dove into screen reader development all activities within one or more projects. All infor- preparing first releases. When in doubt, the project mation at SourceForge.net is provided in English in description was used as a reference. At different order not to limit ourselves to German contributions, stages during the project it differed from the com- but to find as many users as possible. munity’s opinion. However, it was decided to rely upon the official project description while at the same 3.4 Sustainability time respecting the community’s interests and wishes as much as possible.
Load more

Recommended publications
  • Accessible Cell Phones
    September, 2014 Accessible Cell Phones It can be challenging for individuals with vision loss to find a cell phone that addresses preferences for functionality and accessibility. Some prefer a simple, easy-to-use cell phone that isn’t expensive or complicated while others prefer their phone have a variety of applications. It is important to match needs and capabilities to a cell phone with the features and applications needed by the user. In regard to the accessibility of the cell phone, options to consider are: • access to the status of your phone, such as time, date, signal and battery strength; • options to access and manage your contacts; • type of keypad or touch screen features • screen reader and magnification options (built in or by installation of additional screen-access software); • quality of the display (options for font enlargement and backlighting adjustment). Due to the ever-changing technology in regard to cell phones, new models frequently come on the market. A wide variety of features on today’s cell phones allow them to be used as web browsers, for email, multimedia messaging and much more. Section 255 of the Communications Act, as amended by the Telecommunications Act of 1996, requires that cell phone manufacturers and service providers do all that is “readily achievable” to make each product or service accessible. iPhone The iPhone is an Apple product. The VoiceOver screen reader is a standard feature of the phone. Utilizing a touch screen, a virtual keyboard and voice control called SIRI the iPhone can do email, web browsing, and text messaging, as well as function as a telephone.
    [Show full text]
  • ABC's of Ios: a Voiceover Manual for Toddlers and Beyond!
    . ABC’s of iOS: A VoiceOver Manual for Toddlers and Beyond! A collaboration between Diane Brauner Educational Assistive Technology Consultant COMS and CNIB Foundation. Copyright © 2018 CNIB. All rights reserved, including the right to reproduce this manual or portions thereof in any form whatsoever without permission. For information, contact [email protected]. Diane Brauner Diane is an educational accessibility consultant collaborating with various educational groups and app developers. She splits her time between managing the Perkins eLearning website, Paths to Technology, presenting workshops on a national level and working on accessibility-related projects. Diane’s personal mission is to support developers and educators in creating and teaching accessible educational tools which enable students with visual impairments to flourish in the 21st century classroom. Diane has 25+ years as a Certified Orientation and Mobility Specialist (COMS), working primarily with preschool and school-age students. She also holds a Bachelor of Science in Rehabilitation and Elementary Education with certificates in Deaf and Severely Hard of Hearing and Visual Impairments. CNIB Celebrating 100 years in 2018, the CNIB Foundation is a non-profit organization driven to change what it is to be blind today. We work with the sight loss community in a number of ways, providing programs and powerful advocacy that empower people impacted by blindness to live their dreams and tear down barriers to inclusion. Through community consultations and in our day to
    [Show full text]
  • VPAT™ for Apple Ipad Pro (12.9-Inch)
    VPAT™ for Apple iPad Pro (12.9-inch) The following Voluntary Product Accessibility information refers to the Apple iPad Pro (12.9-inch) running iOS 9 or later. For more information on the accessibility features of the iPad Pro and to learn more about iPad Pro features, visit http://www.apple.com/ipad- pro and http://www.apple.com/accessibility iPad Pro (12.9-inch) referred to as iPad Pro below. VPAT™ Voluntary Product Accessibility Template Summary Table Criteria Supporting Features Remarks and Explanations Section 1194.21 Software Applications and Operating Systems Not applicable Section 1194.22 Web-based Internet Information and Applications Not applicable Does not apply—accessibility features consistent Section 1194.23 Telecommunications Products Please refer to the attached VPAT with standards nonetheless noted below. Section 1194.24 Video and Multi-media Products Not applicable Does not apply—accessibility features consistent Section 1194.25 Self-Contained, Closed Products Please refer to the attached VPAT with standards nonetheless noted below. Section 1194.26 Desktop and Portable Computers Not applicable Section 1194.31 Functional Performance Criteria Please refer to the attached VPAT Section 1194.41 Information, Documentation and Support Please refer to the attached VPAT iPad Pro (12.9-inch) VPAT (10.2015) Page 1 of 9 Section 1194.23 Telecommunications products – Detail Criteria Supporting Features Remarks and Explanations (a) Telecommunications products or systems which Not applicable provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use.
    [Show full text]
  • Adriane-Manual – Wikibooks
    Adriane-Manual – Wikibooks Adriane-Manual Notes to this wikibook Target group: Users of the ADRIANE (http://knopper.net/knoppix-adriane /)-Systems as well as people who want to install the system, configure or provide training to. Learning: The user should be enabled, to use the system independently and without sighted assistance and to work productively with the installed programs and services. This book is a "reference book" for a user in which he takes aid to individual tasks. The technician will get instructions for the installation and configuration of the system, so that he can configure it to meet the needs of the user. Trainers should be enabled to understand easily and to explain the system to users so that they can learn how to use it in a short time without help. Contact: Klaus Knopper Are Co authors currently wanted? Yes, in prior consultation with the contact person to coordinate the writing of individual chapters, please. Guidelines for co authors: see above. A clear distinction would be desirable between 'technical part' and 'User part'. Topic description The user part of the book deals with the use of programs that are included with Adriane, as well as the operation of the screen reader. The technical part explains the installation and configuration of Adriane, especially the connection of Braille lines, set-up of internet access, configuration of the mail program etc. Inhaltsverzeichnis 1 Introduction 2 Working with Adriane 2.1 Start and help 2.2 Individual menu system 2.3 Voice output functions 2.4 Programs in Adriane 2.4.1
    [Show full text]
  • Vizlens: a Robust and Interactive Screen Reader for Interfaces in The
    VizLens: A Robust and Interactive Screen Reader for Interfaces in the Real World Anhong Guo1, Xiang ‘Anthony’ Chen1, Haoran Qi2, Samuel White1, Suman Ghosh1, Chieko Asakawa3, Jeffrey P. Bigham1 1Human-Computer Interaction Institute, 2Mechanical Engineering Department, 3Robotics Institute Carnegie Mellon University, 5000 Forbes Ave, Pittsburgh, PA 15213 fanhongg, xiangche, chiekoa, jbighamg @cs.cmu.edu, fhaoranq, samw, sumangg @andrew.cmu.edu ABSTRACT INTRODUCTION The world is full of physical interfaces that are inaccessible The world is full of inaccessible physical interfaces. Mi­ to blind people, from microwaves and information kiosks to crowaves, toasters and coffee machines help us prepare food; thermostats and checkout terminals. Blind people cannot in­ printers, fax machines, and copiers help us work; and check­ dependently use such devices without at least first learning out terminals, public kiosks, and remote controls help us live their layout, and usually only after labeling them with sighted our lives. Despite their importance, few are self-voicing or assistance. We introduce VizLens —an accessible mobile ap­ have tactile labels. As a result, blind people cannot easily use plication and supporting backend that can robustly and inter­ them. Generally, blind people rely on sighted assistance ei­ actively help blind people use nearly any interface they en­ ther to use the interface or to label it with tactile markings. counter. VizLens users capture a photo of an inaccessible Tactile markings often cannot be added to interfaces on pub­ interface and send it to multiple crowd workers, who work lic devices, such as those in an office kitchenette or check­ in parallel to quickly label and describe elements of the inter­ out kiosk at the grocery store, and static labels cannot make face to make subsequent computer vision easier.
    [Show full text]
  • VERSE: Bridging Screen Readers and Voice Assistants for Enhanced
    VERSE: Bridging Screen Readers and Voice Assistants for Enhanced Eyes-Free Web Search Alexandra Vtyurina∗ Adam Fourney Meredith Ringel Morris University of Waterloo Microsoft Research Microsoft Research Waterloo, Ontario, Canada Redmond, WA, USA Redmond, WA, USA [email protected] [email protected] [email protected] Leah Findlater Ryen W. White University of Washington Microsoft Research Seattle, WA, USA Redmond, WA, USA [email protected] [email protected] ABSTRACT INTRODUCTION People with visual impairments often rely on screen readers People with visual impairments are often early adopters of when interacting with computer systems. Increasingly, these audio-based interfaces, with screen readers being a prime individuals also make extensive use of voice-based virtual example. Screen readers work by transforming the visual assistants (VAs). We conducted a survey of 53 people who are content in a graphical user interface into audio by vocalizing legally blind to identify the strengths and weaknesses of both on-screen text. To this end, they are an important accessibility technologies, and the unmet opportunities at their intersection. tool for blind computer users – so much so that every major We learned that virtual assistants are convenient and accessible, operating system includes screen reader functionality (e.g., but lack the ability to deeply engage with content (e.g., read VoiceOver1, TalkBack2, Narrator3), and there is a strong mar- beyond the frst few sentences of an article), and the ability ket for third-party offerings (e.g., JAWS4, NVDA5). Despite to get a quick overview of the landscape (e.g., list alternative their importance, screen readers have many limitations.
    [Show full text]
  • Turning Voiceover on with Siri 1
    Texas School for the Blind and Visually Impaired Outreach Programs www.tsbvi.edu | 512.454.8631 | 1100 W. 45th St. | Austin, TX 78756 Coffee Hour - August 27, 2020 VoiceOver Basics on iOS Presented by Carrie Farraje Introduction: Question: What is VoiceOver? Answer: VoiceOver is a screen reader software that is built into iOS devices such as iPads or iPhones that gives audio description of the screen that people with vision navigate with their eyes. Note: There are multiple ways and gestures to access an iOS device with VoiceOver Important Terms • iOS device: iPad, iPhone, Apple Watch • home button: newer devices do not have a Home button • settings: location of iOS setup and customization • orientation: landscape or portrait • app: application • app icons: small picture that represents an app • page: apps are in rows and columns on a page • gestures: touches that create actions • focus: what has the attention of VoiceOver • page adjuster: to navigate to different pages • dock: area on bottom of screen customized with commonly used apps • status bar: where features such as time, date, battery are located • control center: direct access to customizable settings 1 Turning VoiceOver on in Settings 1. Go to the Settings icon 2. Go to General 3. Go to Accessibility 4. Go to VoiceOver and, tap it on 5. Press Home button to go back to the home screen Turning VoiceOver on with Accessibility Shortcut 1. Go to the Settings icon 2. Go to Accessibility 3. Go to Accessibility Shortcut (at the bottom of the screen) 4. Tap VoiceOver on 5. Turn VoiceOver on by pressing the Home button or the top side button(on newer devices) three times.
    [Show full text]
  • Slide Rule: Making Mobile Touch Screens Accessible to Blind People Using Multi-Touch Interaction Techniques Shaun K
    Slide Rule: Making Mobile Touch Screens Accessible to Blind People Using Multi-Touch Interaction Techniques Shaun K. Kane,1 Jeffrey P. Bigham2 and Jacob O. Wobbrock1 1 2 The Information School Computer Science & Engineering DUB Group DUB Group University of Washington University of Washington Seattle, WA 98195 USA Seattle, WA 98195 USA {skane, wobbrock}@u.washington.edu [email protected] ABSTRACT Recent advances in touch screen technology have increased the prevalence of touch screens and have prompted a wave of new touch screen-based devices. However, touch screens are still largely inaccessible to blind users, who must adopt error-prone compensatory strategies to use them or find accessible alternatives. This inaccessibility is due to interaction techniques that require the user to visually locate objects on the screen. To address this problem, we introduce Slide Rule, a set of audio- based multi-touch interaction techniques that enable blind users to access touch screen applications. We describe the design of Slide Rule, our interaction techniques, and a user study in which 10 blind people used Slide Rule and a button-based Pocket PC screen reader. Results show that Slide Rule was significantly faster than Figure 1. Participant using Slide Rule on a multi-touch the button-based system, and was preferred by 7 of 10 users. smartphone. Slide Rule uses audio output only and does not However, users made more errors when using Slide Rule than display information on the screen. when using the more familiar button-based system. different interfaces on the same surface, such as a scrollable list, a Categories and Subject Descriptors: QWERTY keyboard, or a telephone keypad.
    [Show full text]
  • Darkreader: Bridging the Gap Between Perception and Reality Of
    DarkReader: Bridging the Gap Between Perception and Reality of Power Consumption in Smartphones for Blind Users Jian Xu∗ Syed Masum Billah* Roy Shilkrot Stony Brook University Stony Brook University Stony Brook University Stony Brook, USA Stony Brook, USA Stony Brook, USA [email protected] [email protected] [email protected] Aruna Balasubramanian Stony Brook University Stony Brook, USA [email protected] ABSTRACT This paper presents a user study with 10 blind participants to understand their perception of power consumption in smart- phones. We found that a widely used power saving mechanism for smartphones–pressing the power button to put the smart- phone to sleep–has a serious usability issue for blind screen reader users. Among other findings, our study also unearthed several usage patterns and misconceptions of blind users that contribute to excessive battery drainage. Informed by the first user study, this paper proposes DarkReader, a screen reader developed in Android that bridges users’ perception of power consumption to reality. DarkReader darkens the screen by truly turning it off, but allows users to interact with their smart- phones. A second user study with 10 blind participants shows that participants perceived no difference in completion times in performing routine tasks using DarkReader and default screen reader. Yet DarkReader saves 24% to 52% power depending Figure 1. A blind user is interacting with his smartphone using a (A) on tasks and screen brightness. standard screen reader (e.g., TalkBack in Android), and (B) DarkReader. Unlike TalkBack, DarkReader keeps the screen off to save power. Author Keywords Vision impairment, blind; screen readers, TalkBack, Android, iOS; low-power, battery, screen, brightness; privacy, curtain INTRODUCTION mode, shoulder-surfing.
    [Show full text]
  • Creating Word Documents Which Are Accessible for Screen Readers
    Creating Word Documents which are Accessible for Screen Readers Create Properly Formatted Titles and Paragraph Headings It is important to create uniform headings in your document so that a screen reader can navigate the document and the reader can understand how the document is structured. When you create a heading in a document, such as a title or a paragraph heading, it is not enough simply to bold the text or increase the font size. A screen reader cannot “see” the bold letters. Always use the “Style” tool in Microsoft Word. The Style tool enables you to create consistent headings so that an individual can follow how your document is organized. Instructions for Word 2007 and above on PCs • Select your heading text. • Using the Style tool at the top of the menu bar, click on the appropriate style (e.g., Heading 1, Heading 2, etc.). The document title should be marked as Heading 1. Major topic headings should be Heading 2. Subtopic headings should be Heading 3. Sub-subtopics should be Heading 4, and so on. Do not skip heading levels. Instructions for Macs • The Style menu can be found in the Formatting palette. Create Properly Formatted Lists • If you need to create a list in a document, use the appropriate button (e.g., bullets and numbering) on Word’s formatting toolbar. Avoid making lists with just dashes or asterisks; otherwise a screen reader may not be able to read the list in the proper order. A properly formatted list would look like the ones below: • Apples • Bananas • Oranges Or 1.
    [Show full text]
  • Community Notebook
    Community Notebook Free Software Projects Projects on the Move Accessibility for computer users with disabilities is one of the noblest goals for Linux and open source software. Vinux, Orca, and Gnome lead the way in Linux accessibility. By Carla Schroder ccessibility of any kind for people with disabilities has a long history of neglect and opposition. The US Rehabilitation Act of 1973 prohibited fed- eral agencies from discriminating on the basis of disability (Sections 501, A503, 504, 508) [1]. Passing a law is one thing; enforcing it is another, and it took years of activism to make any progress. In the 1980s, the Reagan Adminis- tration targeted Section 504 (addressing civil rights for people with disabilities) for de- Lisa Young, 123RF regulation because it was too “burdensome.” Once again advocates organized, and after two years of intensive effort, they succeeded in preserving Section 504. However, years more of Supreme Court fights, legislative battles, and public education efforts had to be won. The culmination of that work was the Americans with Disabilities Act (ADA) of 1990, which addresses some of the basic aspects of everyday life: employ- ment, public accommodations, telecommunications, and government agencies. This law still leaves an awful lot of gaps. Designing for accessibility is more than just bolting on a few aids as an afterthought – it’s a matter of architecture, of design- ing for everyone from the ground up. Accessibility covers a lot of ground, including: • Impaired vision to complete blindness • Impaired hearing to complete deafness • Color blindness • Difficulty or inability to type or use a mouse • Cognitive, learning, or reading problems • Low stamina, difficulty sitting up Talking computers have existed in science fiction for decades, but the world isn’t much closer to having them than it was 10 years ago.
    [Show full text]
  • Exploring User Interface Improvements for Software Developers Who Are Blind
    Exploring User Interface Improvements for Software Developers who are Blind Guarionex Salivia* Flint Million Minnesota State University-Mankato Minnesota State University-Mankato Megan Bening Minnesota State University-Mankato Abstract: Software developers who are blind and interact with the computer non-visually face unique challenges with information retrieval. We explore the use of speech and Braille combined with software to provide an improved interface to aid with challenges associated with information retrieval. We motivate our design on common tasks performed by students in a software development course using a Microprocessor without Interlocked Pipeline Stages (MIPS) architecture simulation tool. We test our interface via a single-subject longitudinal study, and we measure and show improvement in both the user’s performance and the user experience. Keywords: Accessibility; Blindness; Visual Impairments; Braille; Screen reader technology; Software development *Corresponding Author, Guarionex Salivia [email protected] Submitted October, 2019 Accepted February 4, 2020 Published online July 23, 2020 1 Vol. 23, No. 1 - 2020; Journal of Science Education for Students with Disabilities 1. INTRODUCTION problem, because these interfaces provide information contextually via visual cues, People who are blind face unique challenges as which are clearly not specifically designed for software developers. Screen reading individuals who are blind and may not work technology is often unable to adequately with existing accessibility tools such as screen represent the complex and dynamic nature of readers. Therefore, those who are blind or modern application interfaces often used for visually impaired often find IDEs to be software development. Complex interfaces challenging to work with, and in many make the task of information seeking and situations completely unusable even with the retrieval particularly challenging to developers use of screen reading technology (Lazar, Allen, who are blind.
    [Show full text]