<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMU</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Mhealth Uhealth</journal-id>
      <journal-title>JMIR mHealth and uHealth</journal-title>
      <issn pub-type="epub">2291-5222</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v7i10e14198</article-id>
      <article-id pub-id-type="pmid">31670695</article-id>
      <article-id pub-id-type="doi">10.2196/14198</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Quality of Deaf and Hard-of-Hearing Mobile Apps: Evaluation Using the Mobile App Rating Scale (MARS) With Additional Criteria From a Content Expert</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Wolfe</surname>
            <given-names>Rosalee</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Dewey</surname>
            <given-names>Rebecca</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Romero</surname>
            <given-names>Ryan Lee</given-names>
          </name>
          <degrees>BPH</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>College of Public Health and Health Professions</institution>
            <institution>University of Florida</institution>
            <addr-line>1225 Center Drive</addr-line>
            <addr-line>Gainesville, FL</addr-line>
            <country>United States</country>
            <phone>1 (352) 273 6060</phone>
            <email>ryan.romero1000@ufl.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6938-7627</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Kates</surname>
            <given-names>Frederick</given-names>
          </name>
          <degrees>PhD, MBA</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-8859-7507</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Hart</surname>
            <given-names>Mark</given-names>
          </name>
          <degrees>EdD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5253-5873</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Ojeda</surname>
            <given-names>Amanda</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5059-0008</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Meirom</surname>
            <given-names>Itai</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-1042-2744</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Hardy</surname>
            <given-names>Stephen</given-names>
          </name>
          <degrees>MEd</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0625-6050</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>College of Public Health and Health Professions</institution>
        <institution>University of Florida</institution>
        <addr-line>Gainesville, FL</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Ryan Lee Romero <email>ryan.romero1000@ufl.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>10</month>
        <year>2019</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>30</day>
        <month>10</month>
        <year>2019</year>
      </pub-date>
      <volume>7</volume>
      <issue>10</issue>
      <elocation-id>e14198</elocation-id>
      <history>
        <date date-type="received">
          <day>29</day>
          <month>3</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>15</day>
          <month>6</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>7</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>18</day>
          <month>8</month>
          <year>2019</year>
        </date>
      </history>
      <copyright-statement>©Ryan Lee Romero, Frederick Kates, Mark Hart, Amanda Ojeda, Itai Meirom, Stephen Hardy. Originally published in JMIR Mhealth and Uhealth (http://mhealth.jmir.org), 30.10.2019.</copyright-statement>
      <copyright-year>2019</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR mhealth and uhealth, is properly cited. The complete bibliographic information, a link to the original publication on http://mhealth.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://mhealth.jmir.org/2019/10/e14198/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The spread of technology and dissemination of knowledge across the World Wide Web has prompted the development of apps for American Sign Language (ASL) translation, interpretation, and syntax recognition. There is limited literature regarding the quality, effectiveness, and appropriateness of mobile health (mHealth) apps for the deaf and hard-of-hearing (DHOH) that pose to aid the DHOH in their everyday communication and activities. Other than the star-rating system with minimal comments regarding quality, the evaluation metrics used to rate mobile apps are commonly subjective.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to evaluate the quality and effectiveness of DHOH apps using a standardized scale. In addition, it also aimed to identify content-specific criteria to improve the evaluation process by using a content expert, and to use the content expert to more accurately evaluate apps and features supporting the DHOH.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>A list of potential apps for evaluation was generated after a preliminary screening for apps related to the DHOH. Inclusion and exclusion criteria were developed to refine the master list of apps. The study modified a standardized rating scale with additional content-specific criteria applicable to the DHOH population for app evaluation. This was accomplished by including a DHOH content expert in the design of content-specific criteria.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The results indicate a clear distinction in Mobile App Rating Scale (MARS) scores among apps within the study’s three app categories: ASL translators (highest score=3.72), speech-to-text (highest score=3.6), and hard-of-hearing assistants (highest score=3.90). Of the 217 apps obtained from the search criteria, 21 apps met the inclusion and exclusion criteria. Furthermore, the limited consideration for measures specific to the target population along with a high app turnover rate suggests opportunities for improved app effectiveness and evaluation.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>As more mHealth apps enter the market for the DHOH population, more criteria-based evaluation is needed to ensure the safety and appropriateness of the apps for the intended users. Evaluation of population-specific mHealth apps can benefit from content-specific measurement criteria developed by a content expert in the field.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>eHealth</kwd>
        <kwd>mobile health</kwd>
        <kwd>mHealth</kwd>
        <kwd>mobile app</kwd>
        <kwd>hearing</kwd>
        <kwd>deaf persons</kwd>
        <kwd>sign language</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>The continuous growth of mobile phone technology opens new opportunities for mobile health (mHealth) apps. The improved computing capability, increased memory, and the open operating systems of smartphones support mHealth app development and help shape the future of health care [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. In 2018, there were approximately 205.4 billion mobile apps downloaded worldwide, with a forecasted growth to 258.2 billion by 2022 [<xref ref-type="bibr" rid="ref3">3</xref>]. This emerging technology can create a more inclusive and accessible environment for the deaf and hard-of-hearing (DHOH) population, representing more than 7 million Americans or over 2% of the US population [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. New mHealth apps leveraging the internet can help to reduce barriers for individuals with disabilities, which is a crucial component of the Americans with Disabilities Act [<xref ref-type="bibr" rid="ref6">6</xref>]. Disability and health inclusion strategies include identifying and eliminating communication barriers for people with hearing impairments [<xref ref-type="bibr" rid="ref7">7</xref>]. Universal accessibility of apps that can increase the multidirectional communication between DHOH persons and those who are not is essential for social inclusion [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
        <p>Although there are mHealth apps available to the DHOH population, there is minimal information regarding the quality, features, effectiveness, and maintenance of these apps. Information regarding the status of DHOH apps should be expanded; this information will give consumers valuable knowledge relevant to choosing an app. In addition, information on specific user needs could assist developers in recognizing features desired by the population that have not been fulfilled with the present mobile apps. Relying on star ratings and reviews may be insufficient for app developers and analysts because of the volume of ratings and the usefulness of the information [<xref ref-type="bibr" rid="ref9">9</xref>]. To evaluate and rank apps relevant to the DHOH in a quantitative manner, a standardized scale is needed, such as the Mobile App Rating Scale (MARS) by Stoyanov et al [<xref ref-type="bibr" rid="ref10">10</xref>]. The MARS is an evaluation system divided into 5 core sections that can accommodate a wide variety of mHealth apps.</p>
        <p>The deaf population can be divided into groups based on different criteria such as the degree of hearing loss, language preference, educational experience, and integration in the Deaf community or the hearing population [<xref ref-type="bibr" rid="ref11">11</xref>]. Throughout, the study will use DHOH to indicate the DHOH population in the United States. Within this population, there is a distinction to be made between persons identifying as Deaf (uppercase D) and deaf (lowercase D). Those who identify as Deaf are actively engaged in a common Deaf culture and the identity behind the culture and prefer to use American Sign Language (ASL) or use only ASL [<xref ref-type="bibr" rid="ref12">12</xref>]. Persons identifying as deaf or hard-of-hearing may comprise those who have postlingual hearing loss, prefer to use English over ASL, or choose to associate with the hearing culture [<xref ref-type="bibr" rid="ref13">13</xref>]. Owing to the unique characteristics of the DHOH population in the United States and the complexity of the ASL [<xref ref-type="bibr" rid="ref14">14</xref>], there is no commonly used written system for ASL; Web-based text is needed for updating content or simple user queries [<xref ref-type="bibr" rid="ref15">15</xref>]. In the United States, more than 500,000 individuals use sign language as their primary mode of communication [<xref ref-type="bibr" rid="ref16">16</xref>]. ASL interpreters are commonly employed to resolve communication barriers between the DHOH and others [<xref ref-type="bibr" rid="ref17">17</xref>]. The Bureau of Labor Statistics projects 18% growth for the industry from 2016 to 2026, which is much faster than the average for all occupations. The United States is expected to add 12,100 new positions by 2026 [<xref ref-type="bibr" rid="ref18">18</xref>]. However, it can take years to become fluent in ASL [<xref ref-type="bibr" rid="ref19">19</xref>], and in many areas of the country, there is a shortage of sign language interpreters [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Although signing interpreters are a staple of interpersonal communication for the DHOH community, mobile apps can also bolster interpersonal communication in numerous ways [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Objective</title>
        <p>The aim of this study was to modify a standardized scale to evaluate and rank apps designed for the DHOH. The study sought the use of a content expert to develop content-specific criteria that would gauge the presence of features relevant to the target population.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Search and Selection Criteria</title>
        <p>An initial screening of the DHOH apps was conducted in May 2018 across 2 mobile app stores: Apple’s App Store and the Google Play Store (for Android platform). The initial search criteria sought apps aimed toward assisting the DHOH community in the United States.</p>
        <p>The following search terms were used: “deaf,” “deaf application,” “deaf hearing,” “hard of hearing,” “sign language translator,” “sign language,” “sign language applications,” “ASL translator,” ASL sign language,” “sign language dictionary,” “sign language keyboard,” “text to speech,” “hearing assistant,” “hearing aid,” “deaf text to speech,” “deaf translator,” and “ASL assistant.”</p>
        <p>A list of potential apps to review was generated after a preliminary screening was done based on the app description in the stores and supporting screenshots to establish relevance and initial inclusion. In-store reviews and star ratings were not considered to prevent rater bias. The study was IRB201802567 exempt.</p>
      </sec>
      <sec>
        <title>Inclusion Criteria of Apps and Processes</title>
        <p>To best select a list of apps, inclusion and exclusion criteria were developed for the master list of apps with the goals of the study in mind, which were (1) to determine the objective quality of hard-of-hearing apps on the mobile market and (2) to gauge the affinity of these apps to integrate the hard-of-hearing population into the national community via the elimination of a social barrier. As the 2 main resource pools for target apps were the Apple’s App Store and the Google Play Store, only apps from these 2 repositories were considered.</p>
        <sec>
          <title>Initial Apps Excluded From the Study</title>
          <p>Apps from both stores (n=217) underwent an initial filtering to obtain a diverse spread of apps related to the DHOH community based on the search criteria. Apps not directly related to the DHOH were not considered further, which include apps related to music or musical instruction (n=39); apps related to sound or pitch detection (n=9); apps related to handwriting or signatures (n=16); games or apps intended for gaming purposes (n=37); apps not otherwise related to the DHOH, or contained keywords related to DHOH (such as apps with “sound,” “hearing,” “hard to hear,” or other hearing-related keywords within the app title) but did not include DHOH features (n=48); and apps using a sign language other than ASL (eg, British Sign Language or French Sign Language; n=4; see <xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Inclusion and exclusion criteria flowchart. ASL: American Sign Language; DHOH: deaf and hard-of-hearing; MARS: Mobile App Rating Scale.</p>
            </caption>
            <graphic xlink:href="mhealth_v7i10e14198_fig1.png" alt-version="no" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Considered Apps Excluded From the Study</title>
          <p>After the initial filtering, apps were screened for compatibility with the 3 categories of the study (ASL translators, speech-to-text, and hearing assistants; n=64). Apps having a primary focus other than the aid of the DHOH population were excluded in this step. Apps designed for children (n=10), religious purposes (n=2), or mental health topics (n=2) were not considered for inclusion criteria screening (see <xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
        </sec>
        <sec>
          <title>Final Apps Excluded From the Study</title>
          <p>Remaining apps (n=50) were then assessed against the inclusion and exclusion criteria. Apps meeting 4 final exclusion criteria were not considered for evaluation with the MARS: apps including assistive features relevant to other special populations (apps with assistive features intended for other populations were excluded to standardize the scoring of the study’s content-specific measures; n=11); apps requiring external devices or a subscription for function (n=6); apps in beta test, or having features such as <italic>coming soon</italic> or otherwise incomplete (n=8); and apps representing an older version of an app being considered (n=4; see <xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
          <p>The use of mHealth apps typically falls under the definition of assistive technology (AT), which can be a piece of equipment, software program, or product used to increase, maintain, or improve the functional capabilities of persons with disabilities [<xref ref-type="bibr" rid="ref23">23</xref>]. Therefore, the study includes a content expert (SH) to evaluate the MARS criteria and to create criteria to better match particular assistive apps to specific needs. Owing to the complexity of evaluating ASL apps, particularly for a person who has no hearing difficulties or ASL experience, it was evident that a content expert was needed.</p>
        </sec>
      </sec>
      <sec>
        <title>Apps</title>
        <p>The development of a multicategory master list of apps allowed for an independent evaluation of each category of apps with the MARS scale and developed content-specific measures (see <xref rid="figure2" ref-type="fig">Figure 2</xref>).</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Master list of apps. ASL: American Sign Language.</p>
          </caption>
          <graphic xlink:href="mhealth_v7i10e14198_fig2.png" alt-version="no" position="float" xlink:type="simple"/>
        </fig>
        <sec>
          <title>American Sign Language Translators</title>
          <p>Apps providing translational functionality to and from ASL were considered in this section. Statistically, “congenital hearing loss affects two to three infants per 1,000 live births” [<xref ref-type="bibr" rid="ref24">24</xref>]. As ASL is the main component of communication for many Deaf persons in the United States [<xref ref-type="bibr" rid="ref25">25</xref>], in addition to the unique accessibility needs of Deaf persons regarding communication [<xref ref-type="bibr" rid="ref11">11</xref>], it was appropriate to allocate an entire section of study to this app category. ASL is unique from verbal language as it provides a mode of communication based on symbols and visual cues [<xref ref-type="bibr" rid="ref25">25</xref>]. In addition, those who are prelingually deafened (and who typically associate with the Deaf culture) are more reliant on ASL-based communication than verbal or written English [<xref ref-type="bibr" rid="ref26">26</xref>]. Apps that serve to translate sign language to and from words, whether it be by visual interpretation or ASL dictionary function, were sorted into this category.</p>
        </sec>
        <sec>
          <title>Speech-to-Text</title>
          <p>Threaded speech-to-text apps are also helping individuals with hearing loss to take part in conversations with family and groups of people. The best hard-of-hearing lip-readers can understand approximately 30% of a dialogue [<xref ref-type="bibr" rid="ref27">27</xref>]. With threaded speech-to-text apps, the accuracy of conversation increases to around 80% to 90% [<xref ref-type="bibr" rid="ref28">28</xref>]. Speech-to-text allows for a more conversational-speed communication between the hard-of-hearing and others. In the current app market, there are a substantial number of these apps competing to be used, yet many are not geared toward the hard-of-hearing population. Although this category of apps poses great benefit to those who were postlingually deafened or are hard of hearing, speech-to-text translators may not be particularly useful toward individuals who were prelingually deafened, stemming from a lower level of English usage and comprehension [<xref ref-type="bibr" rid="ref29">29</xref>].</p>
        </sec>
        <sec>
          <title>Hearing Assistants</title>
          <p>The study’s third category included apps that sought to improve user communication and interaction in everyday life. This section was created to give the study the opportunity to analyze apps that did not fit into the other 2 categories yet provided some feature that positively affected a DHOH person’s ability to communicate. A content expert was used to determine whether or not an app provided some benefit to a DHOH person in social function or public navigation.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Collection and the Mobile App Rating Scale</title>
        <p>Decision was made to use a reliable and flexible app quality rating scale designed by expert research panelists to assess the quality of mHealth apps via multiple descriptive factors [<xref ref-type="bibr" rid="ref10">10</xref>]. The MARS was developed to satisfy the need for a reliable and objective scale that could rate the degree to which mHealth apps satisfy the defined quality criteria [<xref ref-type="bibr" rid="ref10">10</xref>]. The study used the 4 MARS classifications, plus an additional <italic>content-specific</italic> section: engagement, functionality, aesthetics, and information quality. The subjective quality section of the MARS was substituted for the custom-designed content-specific measures section to better gauge app quality and appropriateness. With the inclusion of the study’s 4 custom-designed criteria, apps were evaluated on 23 metrics. All the metrics were quantified by assigning integer values: 1=poor, 2=fair, 3=acceptable, 4=good, and 5=excellent.</p>
        <p>The mobile apps using the MARS were analyzed by 3 members of the research team (RR, IM, and AO), designated as <italic>raters</italic>. Each rater underwent 2 training sessions to correctly attribute scores from the MARS to the apps. These training sessions were supplemented by a video developed by the MARS creators to aid in the rater training and calibration [<xref ref-type="bibr" rid="ref30">30</xref>]. The MARS training video is a reference created by the authors of the MARS to explain the purpose of the scale, the app characteristics that each subsection of the scale measures, and the guidelines for evaluating each subsection. The video describes the relative quality of each app characteristic that is appropriate for each score (poor-excellent), along with examples of quality features. Furthermore, the MARS training video acted as a knowledge base during the construction of content-specific measures and generated ideas as to how content-specific criteria may be scored. These ideas aided the refinement of the content-specific questions after development with the content expert. The 3 raters are members of the College of Public Health who are involved in hard-of-hearing research. The raters were all trained with knowledge from the content expert to give a shared and equal understanding of the needs and characteristics of the DHOH population. A total of 3 control apps were used to determine the intraclass correlation coefficients among raters based on Shrout and Fleiss’ guidelines [<xref ref-type="bibr" rid="ref31">31</xref>]. A test similar to Fleiss’ kappa, the Krippendorff alpha, was used to test for interrater agreement [<xref ref-type="bibr" rid="ref32">32</xref>]. An alpha of .91 was obtained. All issues regarding agreeability were discussed among team members and reevaluated for appropriate concurrence.</p>
      </sec>
      <sec>
        <title>Use of a Content Expert and “Content-Specific” Measures</title>
        <p>Content experts can be useful when determining the relevance of a proposed study to a specific population or subject [<xref ref-type="bibr" rid="ref33">33</xref>]. Specifically, the study revolves around the needs, desires, and attributes of the DHOH population. The study’s content expert (SH) is a professor of ASL who himself is deaf. The Deaf culture is a broad network of beliefs, values, and rules for behaviors that are incorporated into the lives of many with hearing difficulties [<xref ref-type="bibr" rid="ref12">12</xref>]. The use of a content expert allowed the study design to consider the needs and desires of this population as related to mobile app features so that valid and meaningful metrics could be designed to test for the presence of such features.</p>
        <p>An additional scoring section, the content-specific section, was tailored with a content expert (SH) for hearing-specific apps following the MARS authors’ interest in criteria applicable to specific populations [<xref ref-type="bibr" rid="ref10">10</xref>]. This section included 4 subfactors: signing space, distractions, assistive features, and societal integration potential. To help create the content-specific classifications and improve validity, a content expert with experience in teaching ASL and ASL linguistics and Deaf studies was added to the study. After the initial review of apps, concerns were discussed with the content expert to further refine the criteria. All the category factors were quantified by assigning integer values: 1=poor, 2=fair, 3=acceptable, 4=good, and 5=excellent.</p>
        <sec>
          <title>Signing Space</title>
          <p>Evaluating the signing space is an important measurement criterion as this area gauges the digital interpreter’s use of sign language. In sign language, the signing space encompasses the distinctive locations surrounding the signer [<xref ref-type="bibr" rid="ref34">34</xref>], particularly the space in front of the signer extending from the waist to the forehead [<xref ref-type="bibr" rid="ref35">35</xref>]. The content expert emphasized that signing in apps should be in a consistent space and easy to follow. The content expert developed several questions with measurable criteria to assist the evaluators in scoring apps: Does the signing stay within approximately 12 inches of the body’s center mass? Does the reader have to concentrate on entirely different areas when facial expressions are used? Is the signing too fast or too slow?</p>
        </sec>
        <sec>
          <title>Distractions</title>
          <p>Distraction evaluation includes any attribute or behavior by the app or interpreter that may be distracting to the reader. These include distracting clothing (with patterns or multiple colors), bright nail polish or jewelry, and extraneous events occurring in the background or the background color [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. Furthermore, signers should consider the contrast between their skin complexion and their clothing and the background to focus the attention around the hands [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
        </sec>
        <sec>
          <title>Assistive Features</title>
          <p>The initial purpose of hard-of-hearing apps and translators is to allow those with hearing difficulties to achieve social function similar to those who are not hard of hearing. One way the apps can achieve this is by integrating the assistive features within their menus and the graphical user interfaces (GUIs). These assistive features can be (but are not limited to) enlarged buttons and text, a magnifier function, closed captioning on app dialogue, and slow scrolling text of a large font style.</p>
        </sec>
        <sec>
          <title>Societal Integration</title>
          <p>One desirable function of apps that seek to assist the DHOH and similar populations would be to provide functions that further aid in the user’s inclusion and experience in society. The nature of certain apps may lead them to have a higher affinity for this criterion, but overall, this section can be rated by reviewing the potential for a particular app to integrate a DHOH person into society (via social outings, dating, or simply acting as an aid in public).</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>App Turnover</title>
        <p>One outcome not expected was the high level of <italic>app turnover</italic> noted in the ASL translator section. For the study’s purposes, <italic>app turnover</italic> has been defined as an app being added to the master list of apps for evaluation but later being wholly inaccessible or unusable because of its removal from software repositories, extremely poor design, or abandonment by the developer. A total of 5 of the 7 apps were lost to app turnover: ASL Provider, APEX VRI, Interpret Live, Fluency Mobile, and ASL Coach. Although the study was left with a reasonable distribution of apps to evaluate, it should be noted that the high level of app turnover serves as a general reflection of the state of hard-of-hearing apps.</p>
      </sec>
      <sec>
        <title>Scoring for American Sign Language Translators</title>
        <p>Upon completion of scoring for the ASL translator apps, the consensus among the 3 evaluators was that this category of apps had quality apps, yet it was subject to a large amount of <italic>app turnover</italic>, as previously discussed. Of the 7 ASL translator apps selected for evaluation, only 2 were accessible or even discoverable in either app repositories. The best app rated in the category was Signily (3.72/5), with the second best being The ASL App (3.642/5). Both apps had acceptable to good general attributes and acceptable content-specific qualities (see <xref ref-type="table" rid="table1">Table 1</xref>).</p>
      </sec>
      <sec>
        <title>Scoring for Speech-to-Text</title>
        <p>Of the 6 apps tested in the speech-to-text category, all 6 apps were still accessible at the end of the scoring period. The best app in the category was Text to Speech! by Gwyn Durbridge (3.595/5), followed by Speak4Me–Text to Speech (3.584/5) and Smart Record: Audio Recorder (3.48/5). This category of apps had the lowest average score for all 4 general attribute categories, and the lowest average score in the content-specific measures section (see <xref ref-type="table" rid="table1">Table 1</xref>). However, because these apps were not explicitly designed for the DHOH population, they should only be faulted if drastic improvements toward the target population’s needs would be easily achievable.</p>
      </sec>
      <sec>
        <title>Scoring for Hearing Assistants</title>
        <p>Of the 8 apps tested in the hearing assistant category, all 8 apps were still accessible at the end of the scoring period. The best app in the hearing assistant category was ListenClear (3.90/5), followed by Petralex Hearing Aid (3.89/5) and Sound Alert (3.73). Of the 3 categories evaluated, consensus was reached that this particular category boasted the most consistent level of engagement across apps (see <xref ref-type="table" rid="table1">Table 1</xref>). In addition, the average functionality score was the highest in this category. Although the quality of the general attributes of these apps is either acceptable or good, several of the apps had only fair or poor scores for the content-specific measures (see <xref ref-type="table" rid="table1">Table 1</xref>). There was a notable variance among raters in the content-specific section while evaluating the app <italic>ListenClear</italic>. Although the ListenClear app has an exceptional GUI, assistive features, and minimal distractions, it would be desirable for this app to have increased societal integration features considering how it is marketed to the DHOH population (as a hearing assistant).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Mobile App Rating Scale app quality ratings.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="290"/>
            <col width="120"/>
            <col width="120"/>
            <col width="110"/>
            <col width="150"/>
            <col width="180"/>
            <thead>
              <tr valign="bottom">
                <td colspan="2">Mobile health app ranking</td>
                <td>Engagement</td>
                <td>Functionality</td>
                <td>Aesthetics</td>
                <td>Information quality</td>
                <td>Content-specific criteria<sup>a</sup></td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="7">
                  <bold>ASL<sup>b</sup></bold>
                  <bold>translators</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Signily</td>
                <td>3.8</td>
                <td>3.8</td>
                <td>3.2</td>
                <td>3.8</td>
                <td>3.9</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The ASL App</td>
                <td>3.0</td>
                <td>4.4</td>
                <td>3.9</td>
                <td>3.8</td>
                <td>3.0</td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>DHOH<sup>c</sup></bold>
                  <bold>assistants</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>ListenClear</td>
                <td>4.1</td>
                <td>4.3</td>
                <td>4.7</td>
                <td>4.0</td>
                <td>2.5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Petralex Hearing Aid</td>
                <td>3.9</td>
                <td>4.3</td>
                <td>3.9</td>
                <td>3.9</td>
                <td>3.4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Sound Alert</td>
                <td>3.8</td>
                <td>4.3</td>
                <td>4.1</td>
                <td>3.5</td>
                <td>3.0</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>BeWarned–App for DHOH</td>
                <td>4.2</td>
                <td>4.1</td>
                <td>3.7</td>
                <td>3.6</td>
                <td>3.1</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Visual Hearing Aid</td>
                <td>3.3</td>
                <td>4.1</td>
                <td>3.2</td>
                <td>3.6</td>
                <td>2.0</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>eyeHear</td>
                <td>2.7</td>
                <td>3.8</td>
                <td>3.0</td>
                <td>3.1</td>
                <td>2.2</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Live Caption</td>
                <td>2.8</td>
                <td>3.8</td>
                <td>2.6</td>
                <td>2.9</td>
                <td>2.4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Earfy</td>
                <td>2.9</td>
                <td>3.3</td>
                <td>2.0</td>
                <td>2.4</td>
                <td>1.8</td>
              </tr>
              <tr valign="top">
                <td colspan="7">
                  <bold>Speech-to-text</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Text to Speech!</td>
                <td>3.9</td>
                <td>3.8</td>
                <td>3.6</td>
                <td>3.5</td>
                <td>3.2</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Speak4Me–Text to Speech</td>
                <td>3.9</td>
                <td>4.1</td>
                <td>3.4</td>
                <td>3.4</td>
                <td>3.0</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Smart Record: Audio Recorder</td>
                <td>3.1</td>
                <td>3.8</td>
                <td>4.1</td>
                <td>4.4</td>
                <td>1.0</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Transcribe–Speech to Text</td>
                <td>3.1</td>
                <td>3.3</td>
                <td>3.4</td>
                <td>3.2</td>
                <td>2.1</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>TextToSpeech (Iconic Solutions, LLC)</td>
                <td>2.6</td>
                <td>2.8</td>
                <td>2.7</td>
                <td>2.4</td>
                <td>1.5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Text to Speech for iMessage</td>
                <td>1.9</td>
                <td>1.7</td>
                <td>1.9</td>
                <td>2.1</td>
                <td>1.3</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Content-specific criteria are based on the interest in an <italic>app-specific</italic> section by the original Mobile App Rating Scale authors to evaluate apps for specific populations.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>ASL: American Sign Language.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>DHOH: deaf and hard-of-hearing.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>The State of Hard-of-Hearing Assistance Technology</title>
        <p>There is both a need and demand for continuing development of Android and iOS app support for the DHOH. This study’s findings agree with previous findings that app developers prefer Android and iOS for their projects [<xref ref-type="bibr" rid="ref38">38</xref>]. Of the 217 apps from the search criteria, 50 apps were assessed against the inclusion and exclusion criteria for the study. Given the relatively low yield of candidate apps from the App Store and Google Play Store, it is thought necessary for more development of apps targeted toward the DHOH population. A refinement of the master list of apps to 21 apps based on the inclusion and exclusion criteria was thought sufficient to mitigate any anomalies in the study. When it came time to evaluate the apps, however, it was observed that 5 of the 7 hard-of-hearing assistants had become unavailable or had otherwise disappeared from the app stores. This suggests a high rate of app turnover in the subject field, which may contribute to the limited availability of quality DHOH apps. It may be inferred that DHOH apps are experiencing high turnover rates, consistent with the current AT turnover rates as high as 75% to 80% [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. It seems apparent that although these apps may have been designed by skilled developers, features that may be basic necessities to some persons in the DHOH population are being overlooked or poorly implemented. Furthermore, the relative lack of high-level features, such as an app’s ability to act as a social advocate for the user, underlines the state of the DHOH apps: available, but limited in scope.</p>
      </sec>
      <sec>
        <title>The Value of Hard-of-Hearing Assistance Technology</title>
        <p>One of the tenets of the study was to determine the quality of the available DHOH apps so that it may be inferred on their value to DHOH persons. Given the current state of mobile assistance technology for the intended population, it is reasonable to say that these apps provide augmentation to a deaf or hard-of-hearing person’s ability to navigate in public, interact both publicly and with family, and be connected to other deaf persons through the availability of features that facilitate interpersonal interaction. It is notable, however, that there should be more research into other purposes for these apps. For example, there may be a useful purpose for these kinds of apps in both domestic and emergency scenarios such as hurricanes or severe storms. Indeed, the development of emergency AT could help to reduce the disproportionately high level of morbidity among the DHOH during natural disasters [<xref ref-type="bibr" rid="ref41">41</xref>]. Mobile apps or devices could have a preprogrammed functionality that assists DHOH persons in an emergency, although this warrants further research.</p>
      </sec>
      <sec>
        <title>Use of a Content Expert to Evaluate Mobile Apps</title>
        <p>One measure seeking to validate the study’s design and metrics was the consultation of a content expert (SH) who could act as a representative of the DHOH community with the intent of gauging the quality and applicability of DHOH apps. As a deaf individual, he was able to advocate for the needs of the target population from a position of membership; the study gained insight into the needs of the population along with reasonable knowledge to design content-specific measures included in the MARS. This proved invaluable in guiding the direction of the study to focus not only on the features of the apps that would be representative of a quality app but also on those that could augment the interpersonal and social capability of the user.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The study leverages the MARS, which is considered a valid and reliable scale for evaluating mHealth apps. The study introduces a novel MARS modification to create content-specific criteria using a content expert to address the needs of intended end users who will use the apps. One of the limitations of this review was that the search was limited to US app stores. This limitation might have restricted the results and the quality of the apps for the DHOH, particularly if other countries are further ahead in the development of DHOH apps. Only DHOH apps that are publicly available were included, which could have excluded apps developed by a specific health care network that focuses on the DHOH population. A relatively small sample of apps was included in the study. The entire pool of apps for the DHOH was not large to begin with, which may be representative of the DHOH population being a smaller segment of the entire population. There was a high rate of DHOH app turnover, which might be due to the information quality, or that the app is not meeting the needs of the DHOH population<bold>.</bold></p>
      </sec>
      <sec>
        <title>Future Research</title>
        <p>The authors of this study suggest continuing research into the use of the modified MARS scale with content-specific (app-specific) criteria developed with content experts to evaluate mHealth apps for different populations. Further research into the use of content experts while designing a study, and their effect on the validity of subject-specific content will elucidate more information about the potential benefits of using content experts to design content-specific metrics. Additional research is needed for both mHealth apps and DHOH apps to establish additional criteria to measure information quality in terms of patient safety and privacy. Being able to measure the risk of patient safety is a growing concern as some mHealth apps do not follow evidence-based guidelines, or the app developers have little or no medical training [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. Other research opportunities would be to design some app evaluation criteria that can aggregate different types of apps with some beneficial DHOH features (not directly intended for DHOH users). For example, in this study, the initial search terms identified apps such as audio analyzers and sound detectors, which were excluded as they did not have DHOH features. However, 1 sound detection app, eezySoundDetector, recognized the potential to assist the DHOH by providing flashing lights or vibrating alarms for a fire or a crying child. There were other types of apps that were excluded for only having minimal DHOH features, yet these might make a difference for the DHOH in a predominantly hearing world. Developing an evaluation tool that can aggregate a wider variety of apps with different assistive features could be a significant contribution to the development of mHealth apps. In addition, adding a qualitative component to studies that survey user preferences and feedback on the usability of specific mHealth apps has shown to be effective. A preliminary study of a sound detection algorithm that used a training and feedback survey from the DHOH got firsthand insights about detection preferences, such as running water in the home or a printer in the work environment, which improve app usability [<xref ref-type="bibr" rid="ref44">44</xref>]. Finally, this study can be expanded with a follow-up review on the highest ranked DHOH apps to access effectiveness and tangible gains identified by the users, as well as to measure the DHOH app turnover.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The MARS remains a high-fidelity tool for app evaluation. The study emphasizes the value of including a content expert early in the mHealth app development process as well as the evaluation process to improve effectiveness and to assist in making criteria-based recommendations to end users. The focus on mHealth apps for the DHOH population illustrates the importance of including a related content expert. For someone who has a hearing difficulty, it can be both reassuring and empowering to see mHealth app developers, evaluators, and providers, who recommend these products, value the understanding of the needs of the intended users. This can be particularly true for an individual with hearing difficulties who struggles with his or her identity in a world set in an overwhelmingly hearing context.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">ASL</term>
          <def>
            <p>American Sign Language</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AT</term>
          <def>
            <p>assistive technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DHOH</term>
          <def>
            <p>deaf and hard-of-hearing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">GUI</term>
          <def>
            <p>graphical user interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">MARS</term>
          <def>
            <p>Mobile App Rating Scale</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sapci</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sapci</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Digital continuous healthcare and disruptive medical technologies: m-Health and telemedicine skills training for data-driven healthcare</article-title>
          <source>J Telemed Telecare</source>
          <year>2018</year>
          <month>08</month>
          <day>22</day>
          <fpage>1357633X18793293</fpage>
          <pub-id pub-id-type="doi">10.1177/1357633X18793293</pub-id>
          <pub-id pub-id-type="medline">30134779</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Terry</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Medical apps for smartphones</article-title>
          <source>Telemed J E Health</source>
          <year>2010</year>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>17</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1089/tmj.2010.9999</pub-id>
          <pub-id pub-id-type="medline">20070172</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <source>Statista</source>
          <access-date>2019-02-23</access-date>
          <comment>Number of Mobile App Downloads Worldwide From 2016 to 2018<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.statista.com/statistics/271644/worldwide-free-and-paid-mobile-app-store-downloads/">https://www.statista.com/statistics/271644/worldwide-free-and-paid-mobile-app-store-downloads/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <source>Census</source>
          <access-date>2018-12-12</access-date>
          <comment>Americans With Disabilities: 2010<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.census.gov/library/publications/2012/demo/p70-131.html">https://www.census.gov/library/publications/2012/demo/p70-131.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carroll</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Courtney-Long</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Stevens</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Sloan</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Lullo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Visser</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Fox</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Armour</surname>
              <given-names>BS</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>VA</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>DR</given-names>
            </name>
            <name name-style="western">
              <surname>Dorn</surname>
              <given-names>JM</given-names>
            </name>
            <collab>Centers for Disease Control and Prevention (CDC)</collab>
          </person-group>
          <article-title>Vital signs: disability and physical activity--United States, 2009-2012</article-title>
          <source>MMWR Morb Mortal Wkly Rep</source>
          <year>2014</year>
          <month>05</month>
          <day>9</day>
          <volume>63</volume>
          <issue>18</issue>
          <fpage>407</fpage>
          <lpage>13</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/mmwr/preview/mmwrhtml/mm6318a5.htm"/>
          </comment>
          <pub-id pub-id-type="medline">24807240</pub-id>
          <pub-id pub-id-type="pii">mm6318a5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5779402</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="web">
          <source>Americans with Disabilities Act</source>
          <access-date>2019-02-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ada.gov/">https://www.ada.gov/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="web">
          <source>Centers for Disease Control and Prevention</source>
          <access-date>2018-12-12</access-date>
          <comment>Disability and Health Inclusion Strategies<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/ncbddd/disabilityandhealth/disability-strategies.html">https://www.cdc.gov/ncbddd/disabilityandhealth/disability-strategies.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jaeger</surname>
              <given-names>PT</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Developing online community accessibility guidelines for persons with disabilities and older adults</article-title>
          <source>J Disabil Policy Stud</source>
          <year>2008</year>
          <month>10</month>
          <day>17</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>55</fpage>
          <lpage>63</lpage>
          <pub-id pub-id-type="doi">10.1177/1044207308325997</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Maalej</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kurtanović</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Nabil</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Stanik</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>On the automatic classification of app reviews</article-title>
          <source>Requir Eng</source>
          <year>2016</year>
          <volume>21</volume>
          <issue>3</issue>
          <fpage>311</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1007/s00766-016-0251-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stoyanov</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Hides</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Kavanagh</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Zelenko</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Tjondronegoro</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Mani</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile app rating scale: a new tool for assessing the quality of health mobile apps</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2015</year>
          <month>03</month>
          <day>11</day>
          <volume>3</volume>
          <issue>1</issue>
          <fpage>e27</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2015/1/e27/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mhealth.3422</pub-id>
          <pub-id pub-id-type="medline">25760773</pub-id>
          <pub-id pub-id-type="pii">v3i1e27</pub-id>
          <pub-id pub-id-type="pmcid">PMC4376132</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reagan</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Toward an 'archeology of deafness': Etic and Emic constructions of identity in conflict</article-title>
          <source>J Lang Identity Educ</source>
          <year>2002</year>
          <month>01</month>
          <day>2</day>
          <volume>1</volume>
          <issue>1</issue>
          <fpage>41</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1207/S15327701JLIE0101_4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Deafness as culture: a psychosocial perspective</article-title>
          <source>Disabil Stud Q</source>
          <year>2002</year>
          <month>04</month>
          <day>15</day>
          <volume>22</volume>
          <issue>2</issue>
          <pub-id pub-id-type="doi">10.18061/dsq.v22i2.344</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <source>National Association of the Deaf</source>
          <access-date>2019-07-06</access-date>
          <comment>Community and Culture – Frequently Asked Questions<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nad.org/resources/american-sign-language/community-and-culture-frequently-asked-questions/">https://www.nad.org/resources/american-sign-language/community-and-culture-frequently-asked-questions/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morgan</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>On language acquisition in speech and sign: development of combinatorial structure in both modalities</article-title>
          <source>Front Psychol</source>
          <year>2014</year>
          <volume>5</volume>
          <fpage>1217</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.3389/fpsyg.2014.01217"/>
          </comment>
          <pub-id pub-id-type="doi">10.3389/fpsyg.2014.01217</pub-id>
          <pub-id pub-id-type="medline">25426085</pub-id>
          <pub-id pub-id-type="pmcid">PMC4227467</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kacorri</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Huenerfauth</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ebling</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Menzies</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Willard</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Regression analysis of demographic and technology-experience factors influencing acceptance of sign language animation</article-title>
          <source>ACM Trans Access Comput</source>
          <year>2017</year>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>33</lpage>
          <pub-id pub-id-type="doi">10.1145/3046787</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Bachleda</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Karchmer</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>How many people use ASL in the United States? Why estimates need updating</article-title>
          <source>Sign Lang Stud</source>
          <year>2006</year>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>306</fpage>
          <lpage>35</lpage>
          <pub-id pub-id-type="doi">10.1353/sls.2006.0019</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McKee</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Winters</surname>
              <given-names>PC</given-names>
            </name>
            <name name-style="western">
              <surname>Sen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Zazove</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Fiscella</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Emergency department utilization among deaf American sign language users</article-title>
          <source>Disabil Health J</source>
          <year>2015</year>
          <month>10</month>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>573</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/26166160"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.dhjo.2015.05.004</pub-id>
          <pub-id pub-id-type="medline">26166160</pub-id>
          <pub-id pub-id-type="pii">S1936-6574(15)00084-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC4570852</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <source>Bureau of Labor and Statistics</source>
          <access-date>2019-02-23</access-date>
          <comment>Interpreters and Translators-Job Outlook<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.bls.gov/ooh/media-and-communication/interpreters-and-translators.htm#tab-6">https://www.bls.gov/ooh/media-and-communication/interpreters-and-translators.htm#tab-6</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <source>HandSpeak</source>
          <access-date>2019-02-23</access-date>
          <comment>How Long Does It Take to Learn ASL?<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.handspeak.com/learn/index.php?id=61">https://www.handspeak.com/learn/index.php?id=61</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <source>National Association of the Deaf</source>
          <access-date>2019-02-23</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nad.org/">https://www.nad.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pang</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>How does time spent on WeChat bolster subjective well-being through social integration and social capital?</article-title>
          <source>Telemat Inform</source>
          <year>2018</year>
          <month>12</month>
          <volume>35</volume>
          <issue>8</issue>
          <fpage>2147</fpage>
          <lpage>56</lpage>
          <pub-id pub-id-type="doi">10.1016/j.tele.2018.07.015</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile phones and the good life: Examining the relationships among mobile use, social capital and subjective well-being</article-title>
          <source>New Media Soc</source>
          <year>2015</year>
          <volume>17</volume>
          <issue>1</issue>
          <fpage>96</fpage>
          <lpage>113</lpage>
          <pub-id pub-id-type="doi">10.1177/1461444813516836</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <source>Assistive Technology Industry Association</source>
          <access-date>2018-05-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.atia.org/">https://www.atia.org/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gaffney</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Eichwald</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Grosse</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mason</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Identifying infants with hearing loss-United States, 1999-2007</article-title>
          <source>Morb Mortal Wkly Rep</source>
          <year>2010</year>
          <volume>59</volume>
          <issue>8</issue>
          <fpage>220</fpage>
          <lpage>3</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.cdc.gov/mmwr/preview/mmwrhtml/mm5908a2.htm"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <source>The National Institute on Deafness and Other Communication Disorders</source>
          <year>2015</year>
          <access-date>2019-02-23</access-date>
          <comment>American Sign Language<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nidcd.nih.gov/health/american-sign-language">https://www.nidcd.nih.gov/health/american-sign-language</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dickson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Magowan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Magowan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Meeting deaf patients' communication needs</article-title>
          <source>Nurs Times</source>
          <year>2014</year>
          <volume>110</volume>
          <issue>49</issue>
          <fpage>12</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="medline">26016132</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gannon</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The deaf community and sexuality education</article-title>
          <source>Sex Disabil</source>
          <year>1998</year>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>283</fpage>
          <lpage>93</lpage>
          <pub-id pub-id-type="doi">10.1023/A:1023067828478</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Wahid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Habib</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Implementation of Bangla Speech Recognition in Voice Input Speech Output (VISO) Calculator</article-title>
          <source>Proceedings of the 2018 International Conference on Bangla Speech and Language Processing</source>
          <year>2018</year>
          <conf-name>ICBSLP'18</conf-name>
          <conf-date>September 21-22, 2018</conf-date>
          <conf-loc>Sylhet, Bangladesh</conf-loc>
          <pub-id pub-id-type="doi">10.1109/icbslp.2018.8554773</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Strong</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Prinz</surname>
              <given-names>PM</given-names>
            </name>
          </person-group>
          <article-title>A study of the relationship between American sign language and English literacy</article-title>
          <source>J Deaf Stud Deaf Educ</source>
          <year>1997</year>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>46</lpage>
          <pub-id pub-id-type="doi">10.1093/oxfordjournals.deafed.a014308</pub-id>
          <pub-id pub-id-type="medline">15579834</pub-id>
          <pub-id pub-id-type="pii">2/1/37</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <source>YouTube</source>
          <year>2018</year>
          <access-date>2018-04-26</access-date>
          <comment>MARS training video<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.youtube.com/watch?v=25vBwJQIOcE">https://www.youtube.com/watch?v=25vBwJQIOcE</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shrout</surname>
              <given-names>PE</given-names>
            </name>
            <name name-style="western">
              <surname>Fleiss</surname>
              <given-names>JL</given-names>
            </name>
          </person-group>
          <article-title>Intraclass correlations: uses in assessing rater reliability</article-title>
          <source>Psychol Bull</source>
          <year>1979</year>
          <month>03</month>
          <volume>86</volume>
          <issue>2</issue>
          <fpage>420</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1037//0033-2909.86.2.420</pub-id>
          <pub-id pub-id-type="medline">18839484</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Krippendorff</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <source>University of Pennsylvania ScholarlyCommons</source>
          <year>2011</year>
          <access-date>2019-10-01</access-date>
          <comment>Computing Krippendorff 's Alpha-Reliability<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://repository.upenn.edu/cgi/viewcontent.cgi?article=1043&#38;context=asc_papers">https://repository.upenn.edu/cgi/viewcontent.cgi?article=1043&#38;context=asc_papers</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Polit</surname>
              <given-names>DF</given-names>
            </name>
            <name name-style="western">
              <surname>Beck</surname>
              <given-names>CT</given-names>
            </name>
          </person-group>
          <article-title>The content validity index: are you sure you know what's being reported? Critique and recommendations</article-title>
          <source>Res Nurs Health</source>
          <year>2006</year>
          <month>10</month>
          <volume>29</volume>
          <issue>5</issue>
          <fpage>489</fpage>
          <lpage>97</lpage>
          <pub-id pub-id-type="doi">10.1002/nur.20147</pub-id>
          <pub-id pub-id-type="medline">16977646</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liddell</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Grammar, Gesture, And Meaning In American Sign Language</source>
          <year>2003</year>
          <publisher-loc>Cambridge</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Emmorey</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Damasio</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>McCullough</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Grabowski</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Ponto</surname>
              <given-names>LL</given-names>
            </name>
            <name name-style="western">
              <surname>Hichwa</surname>
              <given-names>RD</given-names>
            </name>
            <name name-style="western">
              <surname>Bellugi</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Neural systems underlying spatial language in American Sign Language</article-title>
          <source>Neuroimage</source>
          <year>2002</year>
          <month>10</month>
          <volume>17</volume>
          <issue>2</issue>
          <fpage>812</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1006/nimg.2002.1187</pub-id>
          <pub-id pub-id-type="medline">12377156</pub-id>
          <pub-id pub-id-type="pii">S1053811902911870</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sunjoto</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Unwin</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>UCL Discovery</source>
          <year>2017</year>
          <access-date>2019-10-01</access-date>
          <comment>Traffic signage conspicuity<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://discovery.ucl.ac.uk/1570053/1/Unwin_LJ%20July_Aug%20p30-35%20new-ilovepdf-compressed.pdf">http://discovery.ucl.ac.uk/1570053/1/Unwin_LJ%20July_Aug%20p30-35%20new-ilovepdf-compressed.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pisharady</surname>
              <given-names>PK</given-names>
            </name>
            <name name-style="western">
              <surname>Vadakkepat</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Loh</surname>
              <given-names>AP</given-names>
            </name>
          </person-group>
          <article-title>Attention based detection and recognition of hand postures against complex backgrounds</article-title>
          <source>Int J Comput Vis</source>
          <year>2013</year>
          <volume>101</volume>
          <issue>3</issue>
          <fpage>403</fpage>
          <lpage>19</lpage>
          <pub-id pub-id-type="doi">10.1007/s11263-012-0560-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martínez-Pérez</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>de la Torre-Díez</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>López-Coronado</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Mobile health applications for the most prevalent conditions by the World Health Organization: review and analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2013</year>
          <month>06</month>
          <day>14</day>
          <volume>15</volume>
          <issue>6</issue>
          <fpage>e120</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2013/6/e120/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.2600</pub-id>
          <pub-id pub-id-type="medline">23770578</pub-id>
          <pub-id pub-id-type="pii">v15i6e120</pub-id>
          <pub-id pub-id-type="pmcid">PMC3713954</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sharpe</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <source>CORE</source>
          <year>2010</year>
          <access-date>2019-10-01</access-date>
          <comment>Assistive Technology Attrition: Identifying Why Teachers Abandon Assistive Technologies<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://core.ac.uk/download/pdf/51097930.pdf">https://core.ac.uk/download/pdf/51097930.pdf</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Verza</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Carvalho</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Battaglia</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Uccelli</surname>
              <given-names>MM</given-names>
            </name>
          </person-group>
          <article-title>An interdisciplinary approach to evaluating the need for assistive technology reduces equipment abandonment</article-title>
          <source>Mult Scler</source>
          <year>2006</year>
          <month>02</month>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>88</fpage>
          <lpage>93</lpage>
          <pub-id pub-id-type="doi">10.1191/1352458506ms1233oa</pub-id>
          <pub-id pub-id-type="medline">16459724</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kamau</surname>
              <given-names>PW</given-names>
            </name>
            <name name-style="western">
              <surname>Ivey</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Griese</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Qari</surname>
              <given-names>SH</given-names>
            </name>
          </person-group>
          <article-title>Preparedness training programs for working with deaf and hard of hearing communities and older adults: lessons learned from key informants and literature assessments</article-title>
          <source>Disaster Med Public Health Prep</source>
          <year>2018</year>
          <month>10</month>
          <volume>12</volume>
          <issue>5</issue>
          <fpage>606</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1017/dmp.2017.117</pub-id>
          <pub-id pub-id-type="medline">29041996</pub-id>
          <pub-id pub-id-type="pii">S1935789317001173</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ferrero</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Morrell</surname>
              <given-names>DS</given-names>
            </name>
            <name name-style="western">
              <surname>Burkhart</surname>
              <given-names>CN</given-names>
            </name>
          </person-group>
          <article-title>Skin scan: a demonstration of the need for FDA regulation of medical apps on iPhone</article-title>
          <source>J Am Acad Dermatol</source>
          <year>2013</year>
          <month>03</month>
          <volume>68</volume>
          <issue>3</issue>
          <fpage>515</fpage>
          <lpage>6</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jaad.2012.10.045</pub-id>
          <pub-id pub-id-type="medline">23394920</pub-id>
          <pub-id pub-id-type="pii">S0190-9622(12)01181-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Huckvale</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morrison</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Car</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Apps for asthma self-management: a systematic assessment of content and tools</article-title>
          <source>BMC Med</source>
          <year>2012</year>
          <month>11</month>
          <day>22</day>
          <volume>10</volume>
          <fpage>144</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedicine.biomedcentral.com/articles/10.1186/1741-7015-10-144"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1741-7015-10-144</pub-id>
          <pub-id pub-id-type="medline">23171675</pub-id>
          <pub-id pub-id-type="pii">1741-7015-10-144</pub-id>
          <pub-id pub-id-type="pmcid">PMC3523082</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bragg</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Huynh</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ladner</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>A Personalizable Mobile Sound Detector App Design for Deaf and Hard-of-Hearing Users</article-title>
          <source>Proceedings of the 18th International ACM SIGACCESS Conference on Computers and Accessibility</source>
          <year>2016</year>
          <conf-name>ASSETS'16</conf-name>
          <conf-date>October 23-26, 2016</conf-date>
          <conf-loc>Reno, Nevada, USA</conf-loc>
          <fpage>3</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1145/2982142.2982171</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
