<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Usability of a Mobile Application for Teaching Braille to People with Visual Disabilities</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Edison</forename><surname>Amézquita-Soto</surname></persName>
							<email>edison.amezquita@ucsm.edu.pe</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">Universidad Católica de Santa María</orgName>
								<orgName type="institution" key="instit2">Urb. San José s</orgName>
								<address>
									<addrLine>n Umacollo</addrLine>
									<postCode>04000</postCode>
									<settlement>Arequipa</settlement>
									<country>Perú</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Diego</forename><surname>Mendoza-Polanco</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">Universidad Católica de Santa María</orgName>
								<orgName type="institution" key="instit2">Urb. San José s</orgName>
								<address>
									<addrLine>n Umacollo</addrLine>
									<postCode>04000</postCode>
									<settlement>Arequipa</settlement>
									<country>Perú</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Joseph</forename><surname>Ordoñez-Arratia</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">Universidad Católica de Santa María</orgName>
								<orgName type="institution" key="instit2">Urb. San José s</orgName>
								<address>
									<addrLine>n Umacollo</addrLine>
									<postCode>04000</postCode>
									<settlement>Arequipa</settlement>
									<country>Perú</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Nicoll</forename><surname>Soto-Sana</surname></persName>
							<email>nicoll.soto@ucsm.edu.pe</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">Universidad Católica de Santa María</orgName>
								<orgName type="institution" key="instit2">Urb. San José s</orgName>
								<address>
									<addrLine>n Umacollo</addrLine>
									<postCode>04000</postCode>
									<settlement>Arequipa</settlement>
									<country>Perú</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">José</forename><surname>Sulla-Torres</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">Universidad Católica de Santa María</orgName>
								<orgName type="institution" key="instit2">Urb. San José s</orgName>
								<address>
									<addrLine>n Umacollo</addrLine>
									<postCode>04000</postCode>
									<settlement>Arequipa</settlement>
									<country>Perú</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Usability of a Mobile Application for Teaching Braille to People with Visual Disabilities</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">6A4BA6026B4A64B411F3A02B833EBFEF</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T20:15+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Mobile application</term>
					<term>teaching</term>
					<term>visual disability</term>
					<term>braille</term>
					<term>usability1</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Today, where information and communication play a central role, it is essential to ensure that visually impaired people can develop their skills in the Braille system. This gives them a powerful tool to access knowledge, communicate knowledge, communicate efficiently, and participate actively in daily life. This paper documents the development of the mobile application called Vide, which is focused on teaching the tactile Braille reading and writing system to visually impaired people, using the agile framework Scrum, having the requirements specification, design, and construction as part of the development cycle. For the validation, the proposed "System Usability Scale" tool was used to validate the purpose of knowing the appreciation in terms of usability that the selected users that the selected users have in the interaction with the application. In the application, a similar percentage of user satisfaction is evidenced. Satisfaction.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Today, where information and communication play a central role, it is essential to ensure that visually impaired people have access to the tools they need to develop their skills and participate fully in daily life. One of these tools is the Braille system, which enables visually impaired people to access knowledge and communicate efficiently.</p><p>Globally, statistics reveal a significant gap in access to Braille. According to the World Health Organization (WHO) <ref type="bibr" target="#b0">[1]</ref>, at least 2.2 billion people globally have near or distance vision problems. In at least one billion of them, visual impairment could have been avoided or has not yet been addressed. However, only a small percentage of these people have braille skills, which limits their ability to read, write, and communicate independently.</p><p>In the context of Latin America, the figures also reflect this problem. According to the World Blind Union, the region has one of the lowest Braille literacy rates, which hinders access to education and information for people with visual impairment <ref type="bibr" target="#b1">[2]</ref>.</p><p>In the specific case of Peru, data from the National Institute of Statistics and Informatics (INEI) indicate that 801 thousand people are permanently limited in their vision, even when wearing glasses. Of this total, 52.6% are in urban areas and 44.8% in rural areas <ref type="bibr">[3]</ref>. However, previous studies reveal an urgent need to promote the learning and teaching of Braille in the country.</p><p>The Braille alphabet is a tactile representation of alphabetic and numeric symbols that uses dots so that people with visual impairments can recognize it to enable them to read, write, and communicate. Despite the importance of braille for people with visual impairment, few studies explore technology to facilitate braille literacy. Some of this work is for using Braille with mobile applications to support literacy skills in <ref type="bibr" target="#b2">[4]</ref>  <ref type="bibr" target="#b3">[5]</ref>.</p><p>In this paper, this issue is addressed from the perspective of the development of the mobile application and its usability, which focuses on teaching Braille to people with visual impairment. It is expected to foster independence and inclusion of people with visual impairment, empowering them to develop their skills and communicate effectively in an increasingly digital society <ref type="bibr" target="#b4">[6]</ref>.</p><p>The mobile application will be implemented in Android Studio Flamingo 2022.2.1, which aims to facilitate the learning of Braille language to people with visual impairment. This tool allows users to learn interactively and practically, using their mobile device as a teaching platform. The application has a simple and intuitive interface designed so users can learn Braille autonomously and progressively. The program has exercises and activities so that the user can practice reading and writing this language and a feedback system that will allow them to know their progress.</p><p>The application is designed to be accessible and adaptable to the needs of each user. For example, voice and sound options can be configured so that the user receives verbal instructions and auditory feedback. In addition, it has a virtual braille feature that allows users to practice without needing a specialized device.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>The following are the papers most closely related to the topic of study. The article by Hoskin et al. <ref type="bibr" target="#b5">[7]</ref> indicates that evaluations of the impact of the use of assistive devices in the academic setting of children and youth who are blind or visually impaired are needed. This systematic review evaluated the effectiveness of technology in supporting braille literacy education for children and youth.</p><p>Jones <ref type="bibr" target="#b6">[8]</ref> designs effective and refreshable Braille displays, which describe the technical and design challenges faced by developers of refreshable Braille displays, which are mechanical devices that communicate Braille characters on a raised dot matrix that visually impaired users can read.</p><p>Anderson's paper <ref type="bibr" target="#b7">[9]</ref> looks at the world's first cell phone with a Braille display, developed by an Indian company called Kriyate. Here, he describes the functionalities and features of the phone, including a 6-dot Braille display, a camera for taking pictures, and a messaging application that allows users to send and receive messages in Braille.</p><p>On the other hand, Wagh et al., in their paper "E-Braille-a self-learning Braille device" <ref type="bibr" target="#b8">[10]</ref>, describes the development of a stand-alone Braille learning device for visually impaired people, which consists of a Braille matrix that is updated by the user's input of text, and speech recognition software that guides the user in creating new Braille characters. The solution is designed in such a way as to optimize the cost and speed of operation of the device.</p><p>In the article by Zeinullin and Hersh <ref type="bibr" target="#b9">[11]</ref>, they explain how visual impairment can create barriers to accessing information in a visual format and how assistive technology has been developed to solve this problem. A system has been made that includes pre-labeled tactile graphics, an interactive web-based labeling tool, and a mobile application that provides audio descriptions for the graphics. The purpose of the application is to enable visually impaired people to obtain information without visual aids. A study was conducted to evaluate the system, which included a structured interview, quantitative measurements, and a post-experimental session to gather feedback. The study results showed that the proposed mobile application allows users to explore graphics more efficiently. Finally, there is the article "Game-Based Literacy for blind people," which explains a prototype that was designed to teach the Braille alphabet to blind people with a video game technique; this includes an extra module that can be connected via Bluetooth to the application, the system generates a set of letters and emits a sound of the letter to through the speakers of the telephone and the module displays the letter, so that the student can identify it. Kausar et al. <ref type="bibr" target="#b10">[12]</ref> present a novel automatic Braille character recognition approach. The designed method works in two main stages. In the first stage, image alignment and enhancement are performed using various image preprocessing techniques. In the second stage, character recognition is performed using a lightweight convolutional neural network (CNN). The proposed model shows 95.2% and 98.3% prediction accuracy, respectively. The reported testing time of the model is approximately 0.01 seconds for English images and 0.03 seconds for DSBI Braille images. The Backend as a Service (BaaS) provides a database in the cloud to store and manage information related to the application's users. This includes their progress in Braille exercises <ref type="bibr" target="#b11">[13]</ref>, configuration preferences, and other relevant data. Choosing a BaaS with scalability ensures that the application can handle growth in the number of users and the amount of data stored without compromising performance. Firebase BaaS <ref type="bibr" target="#b12">[14]</ref> provides authentication and user management services, allowing users to register, log in, and maintain personalized profiles. This ensures the security of user information and facilitates data synchronization across different devices. In addition, BaaS provides functionalities such as access permission management and password recovery, simplifying the implementation of these critical features in the mobile application.</p><p>Lutfun, Sulaiman, and Jaafar <ref type="bibr" target="#b13">[15]</ref> present an educational software based on the Android platform for visually impaired students. They designed the software to give users vibration and audio feedback in response to their inputs. The developed interfaces were evaluated by six advanced students, three experts, and three teachers through questionnaires and by 30 visually impaired people after using the software. Overall, the results showed that all respondents rated the software higher than 4.30 out of 5 on all usability criteria (efficiency, learnability, memorability, error, and satisfaction).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Materials and Methods</head><p>For the development of the mobile application based on the Braille language for blind people called VIDE, it has been decided to use the agile methodology Scrum <ref type="bibr" target="#b14">[16]</ref>.</p><p>The Scrum methodology is suitable for complex and dynamic projects, where the customer and the development team work together to adapt to changes in requirements and the environment. In addition, Scrum focuses on the incremental delivery of functional software, which allows the team to obtain early feedback from the customer and adjust the project accordingly. This is shown in Figure <ref type="figure" target="#fig_0">1</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Project planning</head><p>In this phase, the project's objectives are aligned, trying to focus on what we want to achieve and not to reach other goals. The team was set up to establish the project's main objective and identify the application's requirements and key features. The Product Backlog, a prioritized list of items we need to develop, has been created. A multidisciplinary team that includes developers, designers, and accessibility experts. We have the Scrum Master, who will guide us through the process, and a Product Owner, who will represent us and the users' needs and manage the Product Backlog.</p><p>The main functionality of the system is to provide a mobile Braille learning application designed for Android devices. The application allows people with visual impairment to learn and practice Braille language in an interactive and accessible way through their mobile devices.</p><p>The objectives of developing the Braille learning application are as follows:</p><p>1. Facilitate access to Braille language learning for the visually impaired, providing an interactive and practical tool on their mobile devices.</p><p>2. Provide a simple and intuitive interface that allows users to learn autonomously and progressively, adapting to different skill levels. 3. To offer exercises and activities that allow users to practice reading and writing in Braille, strengthening their skills in this language. 4. Implement a feedback system that allows users to monitor their progress and receive immediate feedback to correct errors and improve their learning. 5. Comply with accessibility standards to ensure the application is accessible and usable for the visually impaired. 6. Promote inclusion and equal opportunities by providing a tool that facilitates the learning and mastery of Braille. The Braille learning system users are people with or without visual impairment who wish to learn and practice the Braille language using the mobile application. The report is aimed primarily at users with little or no prior experience using Braille and looking for an accessible and effective tool to acquire Braille skills.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Sprint Planning</head><p>In each sprint, defined as two weeks, they meet to plan, select the highest priority items from the Product Backlog to be addressed during the Sprint, and set a specific goal to be achieved.</p><p>Next, in Table <ref type="table" target="#tab_0">1</ref>, the navigability requirements are presented. These allow a comfortable and ergonomic experience for the user who, due to the visual impairment they may have, the application should have an intuitive and easy-to-use navigability. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Requirement Stakeholders High/Essential</head><p>The Usability Requirements focus on the objective of the application and the purpose for which it is being carried out, as shown in Table <ref type="table" target="#tab_1">2</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">Development of Sprints</head><p>We focus on developing the selected features during each of the Sprints. The work is divided into smaller tasks and assigned to team members. Daily Scrum meetings discuss progress, challenges, and upcoming tasks, maintaining constant and collaborative communication.</p><p>It is essential to highlight that the system has been designed with the specific needs and characteristics of visually impaired users. It provides an intuitive interface, accessibility options, and adaptability to different levels of ability in Braille learning. The goal is to provide an inclusive and satisfactory user experience for all users involved in the Braille learning process.</p><p>As for the application's design, the Figma tool <ref type="bibr" target="#b15">[17]</ref> was used to create the mockups. First, the ideal color palette was sought, considering the need for contrasting colors so people with limited visibility could recognize them. The colors green and yellow were chosen, so the logo was designed with those colors and the letter "V" in Braille as the main image.</p><p>Next, the login interface was designed to allow the user to log in or register, considering the distinctive colors and the large font size, as shown in Figure <ref type="figure" target="#fig_1">2</ref>. After that, the main menu briefly explains the application, showing three buttons that log out, practice and learn. Each contains different functionalities, and the last two buttons show the various learning modules. Once this was done, the screens of each module were designed, and both had the option of accessing letters, numbers, and grammar signs. Fig. <ref type="figure" target="#fig_5">4</ref> shows the practice interface containing an additional word button, which would be the main difference between the two buttons: Finally, the keyboard screen was designed, which has a horizontal orientation for greater comfort with the user; 6 buttons are displayed representing each space in the regular braille grid, and centrally, the letter, number, sign, or word that the user must learn or practice-having as functionality the positioning of the fingers. And the other button, guide, is the quick mentoring of the alphabet, shown in Figure   The functionality of the Braille Alphabet Quick Guide button is shown in Figure <ref type="figure" target="#fig_6">5</ref>. Data persistence was performed by saving each user registered in the non-relational Firestore database <ref type="bibr" target="#b17">[19]</ref>. For this, a new project was created in Firebase, connected to the application through Android Studio tools.</p><p>Figure <ref type="figure" target="#fig_7">6</ref> shows that registered users are stored in the Firestore database, including the email, ID, last name, and password fields. 7.  Once a user is registered, they can access the application through the Login interface. The necessary changes were also applied to these interfaces to verify the registered credentials correctly. Likewise, the Firebase Authentication tool <ref type="bibr" target="#b18">[20]</ref> was used so that users can authenticate through their registered e-mails and any Google accounts.</p><p>Figure <ref type="figure" target="#fig_9">8</ref> shows the list of users with credentials registered in the application's database. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.4.">Sprint Review</head><p>A review meeting is held at the end of each sprint. The completed work is shown to the Product Owner and relevant stakeholders. We collect their feedback to improve our product and development process continuously.</p><p>During this period, the development team has focused on implementing new functionalities and making improvements based on the feedback received. Below, we highlight the key points that have been addressed:</p><p>• Feedback and Improvements:</p><p>-Improvements have been made to the feedback system to provide users with more detailed and valuable comments on errors made in the exercises, helping them to correct their Braille reading and writing skills.</p><p>-We adjusted the user interface to improve the usability and overall accessibility of the application based on user feedback and suggestions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Integration of additional tools:</head><p>-A quick guide to full Braille characters has been added, allowing users to look up and obtain definitions of Braille terms. A set of practical examples of Braille use in everyday situations has also been implemented, helping users to apply their knowledge in real-life contexts.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.5.">Sprint Retrospective</head><p>After the review meeting, time is taken to reflect internally on Sprint's performance. We identify what worked well, what we can improve, and how to optimize our work process. We learn from our past experiences and apply improvements in future Sprints.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Results</head><p>This section shows the results obtained; for this, a Usability questionnaire called "System Usability Scale" (SUS) <ref type="bibr" target="#b19">[21]</ref> was used to test the level of ease of use of the software. Usability is a technique for testing or measuring software applications that is viewed from five aspects: learnability, efficiency, memorability, errors, and satisfaction.</p><p>As shown in Figure <ref type="figure" target="#fig_10">10</ref> and Figure <ref type="figure" target="#fig_11">11</ref>, a similar percentage of user satisfaction is evident as items in disagreement.  With this feedback, we plan to improve, add more exercises, and implement an excellent database of activities and words.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusions</head><p>The development of the VIDE mobile application using the agile Scrum methodology has been highly successful. Implementing this methodology has allowed us to achieve outstanding results in terms of accessibility and effectiveness so that visually impaired people can learn the Braille language effectively.</p><p>The application has been designed and developed considering the specific needs of visually impaired users. Thanks to this, we have created an inclusive learning experience, providing users with the necessary tools and resources to master the Braille language.</p><p>Collaboration and effective communication among team members have been critical elements in the success of this project. Constant and open interaction has allowed for efficient problemsolving, knowledge sharing, and a clear focus on the project's success. In addition, the involvement of stakeholders and users has been fundamental to obtaining early feedback and ensuring that the application meets their expectations and needs.</p><p>Frequent iterations and early feedback have been critical elements in our agile approach. These practices have allowed us to make constant adjustments and improvements throughout the development of the application. As a result, we have been able to adapt the application according to emerging needs and ensure that it meets the required quality standards.</p><p>In future work, expanding the number of exercises and implementing the database of activities and words is recommended.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Scrum Methodology [16].</figDesc><graphic coords="3,101.00,500.29,392.25,153.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Login initial and Menu Interface</figDesc><graphic coords="6,131.75,72.00,143.65,261.17" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Practice and learning interface</figDesc><graphic coords="6,180.13,399.23,234.85,239.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head></head><label></label><figDesc>.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head></head><label></label><figDesc>4.    </figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Keyboard Interface</figDesc><graphic coords="7,149.75,72.00,295.50,120.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Functionality of the "Guide" button For the development of the application, a new project was created in Android Studio [18] Flamingo 2022.2.1Data persistence was performed by saving each user registered in the non-relational Firestore database<ref type="bibr" target="#b17">[19]</ref>. For this, a new project was created in Firebase, connected to the application through Android Studio tools.Figure6shows that registered users are stored in the Firestore database, including the email, ID, last name, and password fields. 7.</figDesc><graphic coords="7,174.88,246.58,245.80,99.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Database in FirestoreUser registration is done through the application interfaces, to which modifications were applied to send the content of each input to the database.</figDesc><graphic coords="7,106.25,476.04,382.40,143.24" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Figure 7 :</head><label>7</label><figDesc>Figure 7: User registration interface</figDesc><graphic coords="8,255.00,72.00,120.45,207.45" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_9"><head>Figure 8 :</head><label>8</label><figDesc>Figure 8: View of authenticated users Access and verification of credentials is done through the login interface in the application.</figDesc><graphic coords="8,104.00,382.62,386.95,179.98" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_10"><head>Figure 10 :</head><label>10</label><figDesc>Figure 10: First part of the results</figDesc><graphic coords="9,86.20,372.32,437.99,183.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_11"><head>Figure 11 :</head><label>11</label><figDesc>Figure 11: Second part of the results</figDesc><graphic coords="10,86.20,72.00,431.88,174.20" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 Navigability Requirements</head><label>1</label><figDesc></figDesc><table><row><cell>Requisition Number</cell><cell>Name of request</cell><cell>Description</cell><cell>Type</cell><cell>Source of the request</cell><cell>Priority of the requirement</cell></row><row><cell></cell><cell></cell><cell>The size of the</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell>Large</cell><cell>buttons should cover</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-1.1</cell><cell>button</cell><cell>a large area of the</cell><cell cols="2">Requirement Stakeholders</cell><cell>High/Essential</cell></row><row><cell></cell><cell>size</cell><cell>screen for user</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>comfort.</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>When entering the</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-1.2</cell><cell>Voice assistant between menus</cell><cell>application and navigating between menus, it should display a tutorial guided by a voice</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>assistant.</cell><cell></cell><cell></cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2</head><label>2</label><figDesc></figDesc><table><row><cell cols="2">Usability Requirements</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Requirement number</cell><cell>Name of request</cell><cell>Description</cell><cell>Type</cell><cell>Source of the request</cell><cell>Priority of the requirement</cell></row><row><cell></cell><cell></cell><cell>Log in and register</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-2.1</cell><cell>User authenticati on</cell><cell>for progress, subsequent and storage of information,</cell><cell>Requirement</cell><cell>Operational Environment</cell><cell>Medium/desired</cell></row><row><cell></cell><cell></cell><cell>feedback.</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-2.2</cell><cell>Learning section</cell><cell>Section where the user can learn the language.</cell><cell>Requirement</cell><cell>Operational Environment</cell><cell>High/Essential</cell></row><row><cell></cell><cell></cell><cell>Section where the</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-2.3</cell><cell>Practice Section</cell><cell>user can test and strengthen the knowledge acquired</cell><cell>Requirement</cell><cell>Operational Environment</cell><cell>High/Essential</cell></row><row><cell></cell><cell></cell><cell>in the language.</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>Users should be</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>able to monitor</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-2.4</cell><cell>Progress Statistics</cell><cell>their learning and see its evolution</cell><cell>Requirement</cell><cell>Operational Environment</cell><cell>High/Essential</cell></row><row><cell></cell><cell></cell><cell>over time using</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>progress statistics.</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>It should provide</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>immediate</cell><cell></cell><cell></cell><cell></cell></row><row><cell>RF-2.5</cell><cell>Immediate feedback</cell><cell>feedback to help users correct errors</cell><cell>Requirement</cell><cell>Operational Environment</cell><cell>High/Essential</cell></row><row><cell></cell><cell></cell><cell>and improve their</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell>learning.</cell><cell></cell><cell></cell><cell></cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>We thank the Universidad Católica de Santa María for its support in the development of the paper.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Blindness and vision impairment</title>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">H O</forename><surname>Who</surname></persName>
		</author>
		<ptr target="https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment" />
	</analytic>
	<monogr>
		<title level="m">Blindness and vision impairment</title>
				<imprint>
			<date type="published" when="2023-09-30">2023. Sep. 30, 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">World Blind Union</title>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">B U</forename><surname>Wbu</surname></persName>
		</author>
		<ptr target="https://worldblindunion.org/es/" />
		<imprint>
			<date type="published" when="2023-09-30">2023. Sep. 30, 2023</date>
			<publisher>World Blind Union</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Reflections on the Design, Development, and Implementation of a Braille Mobile App</title>
		<author>
			<persName><forename type="first">C</forename><surname>Kamei-Hannan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Assist. Technol. Outcomes Benefits</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Braille Based Mobile Communication for Deaf and Blind People</title>
		<author>
			<persName><forename type="first">T</forename><surname>Barathkumar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Saran</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Sujitha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Vikash</surname></persName>
		</author>
		<idno type="DOI">10.1109/ICACCS57279.2023.10112705</idno>
	</analytic>
	<monogr>
		<title level="m">2023 9th International Conference on Advanced Computing and Communication Systems</title>
				<meeting><address><addrLine>ICACCS</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2023">2023. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Gesture Recognition Algorithm for Visually Blind Touch Interaction Optimization Using Crow Search Method</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">M</forename><surname>Aslam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Samreen</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2020.3006443</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Effectiveness of technology for braille literacy education for children: a systematic review</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">R</forename><surname>Hoskin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">K</forename><surname>Coyne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>White</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">C D</forename><surname>Dobri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">C</forename><surname>Davies</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">D</forename><surname>Pinder</surname></persName>
		</author>
		<idno type="DOI">10.1080/17483107.2022.2070676</idno>
	</analytic>
	<monogr>
		<title level="j">Disability and Rehabilitation: Assistive Technology</title>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Designing effective refreshable Braille displays</title>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">A</forename><surname>Jones</surname></persName>
		</author>
		<idno type="DOI">10.1109/mc.2016.12</idno>
	</analytic>
	<monogr>
		<title level="j">Computer (Long. Beach. Calif)</title>
		<imprint>
			<biblScope unit="volume">49</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Inside the world&apos;s first braille cellphone [Resources_First Look</title>
		<author>
			<persName><forename type="first">M</forename><surname>Anderson</surname></persName>
		</author>
		<idno type="DOI">10.1109/mspec.2013.6545116</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Spectr</title>
		<imprint>
			<biblScope unit="volume">50</biblScope>
			<biblScope unit="issue">7</biblScope>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">E-Braille-a self-learning Braille device</title>
		<author>
			<persName><forename type="first">P</forename><surname>Wagh</surname></persName>
		</author>
		<idno type="DOI">10.1109/NCC.2016.7561162</idno>
	</analytic>
	<monogr>
		<title level="m">2016 22nd National Conference on Communication</title>
				<meeting><address><addrLine>NCC</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2016">2016. 2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Tactile Audio Responsive Intelligent System</title>
		<author>
			<persName><forename type="first">M</forename><surname>Zeinullin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hersh</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2022.3223099</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Deep Learning Strategy for Braille Character Recognition</title>
		<author>
			<persName><forename type="first">T</forename><surname>Kausar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Manzoor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kausar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Lu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wasif</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">Adnan</forename><surname>Ashraf</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACCESS.2021.3138240</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Access</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Application of Educational Support Through Disruptive Technology in Deaf Student Learning</title>
		<author>
			<persName><forename type="first">L</forename><surname>Borges</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">F</forename><surname>De Moraes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>De</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Speroni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">P A</forename><surname>Correa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">A</forename><surname>Silva</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-031-14859-0_30</idno>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">A Review on Firebase (Backend as A Service) for Mobile Application Development</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">R</forename><surname>Saraf</surname></persName>
		</author>
		<idno type="DOI">10.22214/ijraset.2022.39958</idno>
	</analytic>
	<monogr>
		<title level="j">Int. J. Res. Appl. Sci. Eng. Technol</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Bangla Braille learning application&apos; in smartphones for visually impaired students in Bangladesh</title>
		<author>
			<persName><forename type="first">L</forename><surname>Nahar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Sulaiman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Jaafar</surname></persName>
		</author>
		<idno type="DOI">10.1080/10494820.2019.1619588</idno>
	</analytic>
	<monogr>
		<title level="j">Interact. Learn. Environ</title>
		<imprint>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="issue">5</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">SCRUM Development Process</title>
		<author>
			<persName><forename type="first">K</forename><surname>Schwaber</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-1-4471-0947-1_11</idno>
	</analytic>
	<monogr>
		<title level="m">Business Object Design and Implementation</title>
				<imprint>
			<date type="published" when="1997">1997</date>
			<biblScope unit="page" from="117" to="134" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Alcaraz</surname></persName>
		</author>
		<title level="m">Guía de uso de Figma Aplicaciones y Dispositivos móviles</title>
				<meeting><address><addrLine>Univ. Barcelona</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Android Studio</title>
		<author>
			<persName><forename type="first">T</forename><surname>Hagos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hagos</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-1-4842-3156-2_2</idno>
	</analytic>
	<monogr>
		<title level="j">Learn Android Studio</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Cloud computing: Google Firebase firestore optimization analysis</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">B</forename><surname>Semma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ali</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Saerozi</surname></persName>
		</author>
		<author>
			<persName><surname>Mansur</surname></persName>
		</author>
		<author>
			<persName><surname>Kusrini</surname></persName>
		</author>
		<idno type="DOI">10.11591/ijeecs.v29.i3.pp1719-1728</idno>
	</analytic>
	<monogr>
		<title level="j">Indones. J. Electr. Eng. Comput. Sci</title>
		<imprint>
			<biblScope unit="volume">29</biblScope>
			<biblScope unit="issue">3</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">Firebase Authentication</title>
		<imprint>
			<date type="published" when="2023">2023</date>
			<publisher>Firebase</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">SYSTEM USABILITY SCALE VS HEURISTIC EVALUATION: A REVIEW</title>
		<author>
			<persName><forename type="first">U</forename><surname>Ependi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">B</forename><surname>Kurniawan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Panjaitan</surname></persName>
		</author>
		<idno type="DOI">10.24176/simet.v10i1.2725</idno>
	</analytic>
	<monogr>
		<title level="j">Simetris J. Tek. Mesin, Elektro dan Ilmu Komput</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
