<?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">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</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">v25i1e43917</article-id>
      <article-id pub-id-type="pmid">37140967</article-id>
      <article-id pub-id-type="doi">10.2196/43917</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>Personal Health Data Tracking by Blind and Low-Vision People: Survey Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Choi</surname>
            <given-names>Woohyeok</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Jerome</surname>
            <given-names>Gerald</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Veldandi</surname>
            <given-names>Hareesh</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Jarrett G W</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-6783-8129</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Kyungyeon</given-names>
          </name>
          <degrees>BSE</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-8966-6209</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Lee</surname>
            <given-names>Bongshin</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4217-627X</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Choi</surname>
            <given-names>Soyoung</given-names>
          </name>
          <degrees>RN, PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0998-3352</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Seo</surname>
            <given-names>JooYoung</given-names>
          </name>
          <degrees>MEd, PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4064-6012</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Choe</surname>
            <given-names>Eun Kyoung</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>College of Information Studies</institution>
            <institution>University of Maryland</institution>
            <addr-line>Hornbake Building, 2117F</addr-line>
            <addr-line>4130 Campus Drive</addr-line>
            <addr-line>College Park, MD, 20742</addr-line>
            <country>United States</country>
            <phone>1 3014051085</phone>
            <email>choe@umd.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5038-8320</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>College of Information Studies</institution>
        <institution>University of Maryland</institution>
        <addr-line>College Park, MD</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Computer Science</institution>
        <institution>University of Maryland</institution>
        <addr-line>College Park, MD</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Microsoft Research</institution>
        <addr-line>Redmond, WA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Kinesiology and Community Health</institution>
        <institution>University of Illinois at Urbana-Champaign</institution>
        <addr-line>Urbana, IL</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>School of Information Sciences</institution>
        <institution>University of Illinois at Urbana-Champaign</institution>
        <addr-line>Champaign, IL</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Eun Kyoung Choe <email>choe@umd.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>4</day>
        <month>5</month>
        <year>2023</year>
      </pub-date>
      <volume>25</volume>
      <elocation-id>e43917</elocation-id>
      <history>
        <date date-type="received">
          <day>29</day>
          <month>10</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>3</day>
          <month>1</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>25</day>
          <month>2</month>
          <year>2023</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>3</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Jarrett G W Lee, Kyungyeon Lee, Bongshin Lee, Soyoung Choi, JooYoung Seo, Eun Kyoung Choe. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 04.05.2023.</copyright-statement>
      <copyright-year>2023</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 the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2023/1/e43917" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Personal health technologies, including wearable tracking devices and mobile apps, have great potential to equip the general population with the ability to monitor and manage their health. However, being designed for sighted people, much of their functionality is largely inaccessible to the blind and low-vision (BLV) population, threatening the equitable access to personal health data (PHD) and health care services.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to understand why and how BLV people collect and use their PHD and the obstacles they face in doing so. Such knowledge can inform accessibility researchers and technology companies of the unique self-tracking needs and accessibility challenges that BLV people experience.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We conducted a web-based and phone survey with 156 BLV people. We reported on quantitative and qualitative findings regarding their PHD tracking practices, needs, accessibility barriers, and work-arounds.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>BLV respondents had strong desires and needs to track PHD, and many of them were already tracking their data despite many hurdles. Popular tracking items (ie, exercise, weight, sleep, and food) and the reasons for tracking were similar to those of sighted people. BLV people, however, face many accessibility challenges throughout all phases of self-tracking, from identifying tracking tools to reviewing data. The main barriers our respondents experienced included suboptimal tracking experiences and insufficient benefits against the extended burden for BLV people.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>We reported the findings that contribute to an in-depth understanding of BLV people’s motivations for PHD tracking, tracking practices, challenges, and work-arounds. Our findings suggest that various accessibility challenges hinder BLV individuals from effectively gaining the benefits of self-tracking technologies. On the basis of the findings, we discussed design opportunities and research areas to focus on making PHD tracking technologies accessible for all, including BLV people.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>personal health data</kwd>
        <kwd>self-tracking</kwd>
        <kwd>blind and low vision</kwd>
        <kwd>survey</kwd>
        <kwd>consumer health information</kwd>
        <kwd>mobile phone</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Over the last decade, technologies for individuals to track personal health data (PHD; eg, exercise, sleep, diet, blood pressure, and blood glucose) have become increasingly popular. The number of mobile health (mHealth) and fitness apps has increased, reaching &#62;350,000 in 2021 [<xref ref-type="bibr" rid="ref1">1</xref>]. Approximately 1 in 5 Americans are currently using fitness trackers including smartwatches, and a similar number of Americans are using health and fitness apps on mobile devices [<xref ref-type="bibr" rid="ref2">2</xref>]. People with or without health problems use these technologies to manage their health and well-being. Many studies have shown the benefits of personal health technologies in monitoring health status, managing chronic diseases, and maintaining healthy lifestyles [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>However, these technologies are often designed for sighted people using graphical user interfaces (GUIs) and providing vision-dependent feedback to aid in data collection and reflection. For example, commercial food and nutrition tracking apps (eg, MyFitnessPal and Love It!) use vision-oriented designs to capture data (eg, photo journaling and barcode scanning) that are not designed with blind and low-vision (BLV) people in mind. These apps often provide feedback through data visualizations (eg, bar, line, and pie charts) without providing adequate text descriptions. In addition, many extra features and advertisements of the app put an additional burden on blind people who cannot easily navigate or ignore them.</p>
      <p>As such, personal health tracking technologies remain largely inaccessible to the BLV population, providing limited self-tracking experience [<xref ref-type="bibr" rid="ref8">8</xref>]. Therefore, it is imperative for accessibility researchers and designers to understand the first-hand self-tracking experiences and identify unique self-tracking needs and accessibility challenges of BLV people. Recent studies have started looking into accessibility barriers of mHealth apps, but they either casted a wide net covering all types of disabilities instead of focusing on BLV [<xref ref-type="bibr" rid="ref9">9</xref>-<xref ref-type="bibr" rid="ref11">11</xref>] or examined accessibility issues of only a few selected mHealth apps [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>], limiting the generalizability of the findings.</p>
      <p>This study aims to fill this gap by gaining an in-depth understanding of why and how BLV people collect and use their PHD and the obstacles they face. We reported the results from a web-based and phone survey we conducted to understand BLV people’s current practices and lived experiences of tracking and using their PHD. We also discussed the implications for designing and developing personal health technologies that are accessible to BLV people. Throughout this paper, we use the identity-first language (ie, BLV people) instead of person-first language (ie, people who are blind or have low vision [LV]) because both our community partner, National Federation of the Blind, and the blind author of this paper view blindness as identity rather than any negative characteristic that defines one or one’s future.</p>
      <p>Health disparities emerge from health system disparities and socioeconomic factors that create differential access to resources [<xref ref-type="bibr" rid="ref14">14</xref>]. It is now generally accepted that health and health care are strongly influenced by race, ethnicity, socioeconomic status, age, sex, residence, and social networks [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Although the relationship between digital technologies and health is nonlinear and complex, digital health ecosystems can deepen the existing health disparities between people with and without disabilities [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
      <p>Although many digital technologies, including wearable tracking devices and mobile apps, have great potential to equip the general population with the ability to monitor and manage their health [<xref ref-type="bibr" rid="ref18">18</xref>], they could also threaten the equitable access to PHD and health care services among people with disabilities [<xref ref-type="bibr" rid="ref19">19</xref>]. In other words, the inaccessible designs and poor usability of digital technologies that were originally designed to support individuals’ health care may widen the existing health disparity gap in our society [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      <p>People with disabilities often seem to be marginalized from the benefits of digital health technologies. Jones et al [<xref ref-type="bibr" rid="ref10">10</xref>] conducted a survey with people with all types of disabilities about their experiences of using personal health apps. They found that people with disabilities have strong needs and desires to use mHealth apps (ie, 40% of current users) but face many challenges including difficulty locating suitable apps and accessibility problems.</p>
      <p>In studies specifically targeting BLV people, researchers investigated the accessibility of personal health apps [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Although sighted people use personal health technologies to stay healthy, the available options and benefits from those technologies are limited for BLV people [<xref ref-type="bibr" rid="ref21">21</xref>]. It is especially challenging for BLV people to learn how to use highly visually oriented technologies compared with those with other types of disabilities [<xref ref-type="bibr" rid="ref22">22</xref>]. Milne et al [<xref ref-type="bibr" rid="ref8">8</xref>] assessed the accessibility of 9 mHealth apps (5 blood glucometer apps and 4 blood pressure apps) and found that none of them met the basic accessibility guidelines. Kim [<xref ref-type="bibr" rid="ref12">12</xref>] checked the level of accessibility of the 5 most commonly used self-care apps using the Web Content Accessibility Guidelines 2.0 mobile accessibility checklists [<xref ref-type="bibr" rid="ref12">12</xref>]. For each of the Web Content Accessibility Guidelines accessibility principles, they identified several issues, including information overload, no access to GUIs, and incomplete (or missing) description about user interface components.</p>
      <p>Although previous works point to high-level accessibility pitfalls of mHealth technologies, we still lack an understanding of the in-depth accessibility challenges BLV people have faced in adopting and using mHealth technologies. To fill this gap, we investigated BLV people’s experience of tracking and using their PHD through a comprehensive web-based and phone survey.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>We conducted a web-based survey on Qualtrics [<xref ref-type="bibr" rid="ref23">23</xref>] to understand BLV people’s current practices and lived experiences of tracking and using their PHD. We ensured that our survey was accessible to screen readers (eg, JAWS, NVDA, and VoiceOver), the main assistive technology tools for BLV people that narrate digital content as synthesized speech.</p>
      </sec>
      <sec>
        <title>Survey Design</title>
        <p>We started the survey with questions about basic background information, such as the vision history and status, list of devices they owned, self-reported health conditions, and the level of interest in their own health. Before asking questions about PHD, we defined the term “Personal Health Data” as health-related data that people can track about themselves outside the clinic [<xref ref-type="bibr" rid="ref7">7</xref>] and provided examples, such as exercise (eg, step count and miles run), sleep, diet, heart rate, weight, and blood pressure data. As we wanted to ask different sets of questions based on people’s experience with PHD tracking, we asked a question to categorize respondents into 1 of the 3 groups: current tracker (CT), past tracker (PT), and no experience (NE).</p>
        <p>Our main survey asked about four aspects of PHD tracking experience: (1) types of data, (2) tracking methods and tools, (3) reasons for tracking (or not), and (4) barriers to tracking. For the data types and tracking methods and tools, we asked respondents to select items from a comprehensive list and let them also specify any missing items using the “Others” option. We used open-ended questions to elicit the reasons for tracking (or not) and barriers to tracking. <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> presents the key questions for each aspect; we have slightly rephrased some of the questions for different groups based on the respondents’ answers to prior questions. A full list of questions can be found in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <boxed-text id="box1" position="float">
          <title>Key questions asked in our survey.</title>
          <p>
            <bold>Types of personal health data</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>What types of personal health data do you currently (or did you formerly) track? (Check all that apply)</p>
            </list-item>
            <list-item>
              <p>In addition to what you have been tracking, what other personal health data do you want to track, if any? (Check all that apply)</p>
            </list-item>
          </list>
          <p>
            <bold>Tracking methods and tools</bold>
          </p>
          <p>
            <italic>For current tracker (and past tracker)</italic>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>How do (did) you track your personal health data, if any? (Check all that apply)</p>
            </list-item>
            <list-item>
              <p>
                <italic>If smartphone apps or wearable devices are selected</italic>
              </p>
              <list>
                <list-item>
                  <p>What smartphone apps (or wearable devices) have you used to track which of your data?</p>
                </list-item>
                <list-item>
                  <p>How was your experience?</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>How did you access the data you tracked? (eg, screen reader, smartphone’s text to speech, or ask for help)? Did you have any accessibility challenges when accessing your data?</p>
            </list-item>
          </list>
          <p>
            <italic>For no experience</italic>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>If you wanted to track your health data, what would your preferred method be? (Check all that apply)</p>
            </list-item>
          </list>
          <p>
            <bold>Reasons for tracking (or not)</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Why are you tracking your personal health data?</p>
            </list-item>
            <list-item>
              <p>Why did you stop tracking your personal health data?</p>
            </list-item>
            <list-item>
              <p>Could you explain why you do not want to collect your personal health data?</p>
            </list-item>
          </list>
          <p>
            <bold>Barriers to tracking</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Please describe any barriers or challenges you faced when tracking your personal health data.</p>
            </list-item>
          </list>
        </boxed-text>
      </sec>
      <sec>
        <title>Respondents’ Recruitment</title>
        <p>We recruited people who were interested in PHD and met the following inclusion criteria: people who were (1) blind or LV (ie, those with mild to severe distance vision impairment); (2) aged at least 18 years; and (3) able to participate in the survey via a computer, mobile device, or phone. We provided an option to take the survey over the phone, in which case a researcher read out the questions and recorded responses. We recruited respondents via the National Federation of the Blind’s mailing list, researchers’ personal network, and web-based BLV communities on Facebook. The survey was available on the web during April and May 2022. As it was created in English, the survey was accessible to those who spoke English.</p>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>We initially had a total of 203 (198 via the web and 5 via phone) survey responses. Of the 184 completed responses, we excluded 2 (1.1%) that were submitted from the same IP address. On further inspection of the quality of the responses, we noticed a suspicious data entry pattern. A total of 26 responses repeated the same answer (“No,” “n,” or “I don’t really want to say”) for several open-ended optional questions, with most having the same set of answers across several response IDs. As it is highly unlikely that different individuals submit the same answers for multiple open-ended questions that are optional, we excluded these from our data set, resulting in a total of 156 responses.</p>
        <p>We used open coding to analyze qualitative data from open-ended survey responses. Through several rounds of iterative refinements, we generated 71 codes that captured representative ideas in the data. We then used affinity diagramming to categorize similar codes and drew higher-level themes over several refinements. For quantitative data, such as demographics, PHD type, and data capturing methods, we characterized the data using descriptive statistics.</p>
      </sec>
      <sec>
        <title>Ethics Approval</title>
        <p>Our survey study was reviewed and approved by the University of Maryland, College Park’s Institutional Review Board under #1854542. We maintained the confidentiality of our respondents by using a security-accredited survey provider, deidentifying survey results during our analysis phase and in our reporting, and solely using password-protected servers and workstations for data storage.</p>
        <p>To motivate participation, we used raffles, offering a US $50 Amazon gift card to 2 respondents and a US $20 Amazon gift card to 10 respondents. Before individuals took our survey, they were informed of our study’s procedures, potential risks and benefits, and their individual rights as participants and were given the opportunity to opt-out.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Respondents’ Demographics and Tracking Background</title>
        <p><xref ref-type="table" rid="table1">Table 1</xref> summarizes the demographic characteristics of 156 respondents. Nearly an equal number of respondents who self-identified as totally blind (TB; 79/156, 50.6%) or LV (77/156, 49.4%) participated in our survey. Approximately two-thirds of them were CT (102/156, 65.4%), 19.2% (30/156) were PT, and 15.4% (24/156) had NE tracking PHD. More than half of the respondents were visually impaired since birth (83/156, 53.2%), and approximately one-third became visually impaired after birth and had been visually impaired for at least 10 years (51/156, 32.7%). Most respondents (151/156, 96.8%) rated their health condition as fair or better. Respondents varied in age, with 22.4% (35/156) aged 35 to 44 years and 21.2% (33/156) aged 55 to 64 years; 68.6% (107/156) were female, 29.5% (46/156) were male, and 1.9% (3/156) were nonbinary. More than two-thirds of the respondents were White (107/156, 68.6%), 10.9% (17/156) were Asian, and 5.8% (9/156) were Black or African American. In terms of education, 59.6% (93/156) of the respondents had a bachelor’s degree or higher.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>The demographic and technology ownership information of the 156 respondents.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="350"/>
            <col width="200"/>
            <col width="190"/>
            <col width="230"/>
            <thead>
              <tr valign="top">
                <td colspan="2">
                  <break/>
                </td>
                <td>Totally blind (n=79), n (%)</td>
                <td>Low vision (n=77), n (%)</td>
                <td>Combined (N=156), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Tracking status</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Current tracker</td>
                <td>54 (35)</td>
                <td>48 (31)</td>
                <td>102 (65.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Past tracker</td>
                <td>15 (10)</td>
                <td>15 (10)</td>
                <td>30 (19.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>No experience</td>
                <td>10 (6)</td>
                <td>14 (9)</td>
                <td>24 (15.4)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Vision history</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Since birth</td>
                <td>45 (29)</td>
                <td>38 (24)</td>
                <td>83 (53.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>10 years or longer (but not since birth)</td>
                <td>27 (17)</td>
                <td>24 (15)</td>
                <td>51 (32.7)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>5 years or longer and less than 10 years</td>
                <td>4 (3)</td>
                <td>8 (5)</td>
                <td>12 (7.7)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>1 year or longer and less than 5 years</td>
                <td>2 (1)</td>
                <td>6 (4)</td>
                <td>8 (5.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Less than 1 year</td>
                <td>1 (1)</td>
                <td>0 (0)</td>
                <td>1 (0.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Prefer not to say</td>
                <td>0 (0)</td>
                <td>1 (1)</td>
                <td>1 (0.6)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Health status</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Very poor</td>
                <td>1 (1)</td>
                <td>1 (1)</td>
                <td>2 (1.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Poor</td>
                <td>1 (1)</td>
                <td>2 (1)</td>
                <td>3 (1.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Fair</td>
                <td>23 (15)</td>
                <td>23 (15)</td>
                <td>46 (29.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Good</td>
                <td>35 (22)</td>
                <td>33 (21)</td>
                <td>68 (43.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Very good</td>
                <td>19 (12)</td>
                <td>18 (12)</td>
                <td>37 (23.7)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Age (years)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>18-24</td>
                <td>5 (3)</td>
                <td>5 (3)</td>
                <td>10 (6.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>25-34</td>
                <td>13 (8)</td>
                <td>14 (9)</td>
                <td>27 (17.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>35-44</td>
                <td>19 (12)</td>
                <td>16 (10)</td>
                <td>35 (22.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>45-54</td>
                <td>12 (8)</td>
                <td>15 (10)</td>
                <td>27 (17.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>55-64</td>
                <td>14 (9)</td>
                <td>19 (12)</td>
                <td>33 (21.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>≥65</td>
                <td>15 (10)</td>
                <td>7 (4)</td>
                <td>22 (14.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Prefer not to say</td>
                <td>1 (1)</td>
                <td>1 (1)</td>
                <td>2 (1.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Gender</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Male</td>
                <td>16 (10)</td>
                <td>30 (19)</td>
                <td>46 (29.5)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Female</td>
                <td>62 (40)</td>
                <td>45 (29)</td>
                <td>107 (68.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Nonbinary or third gender</td>
                <td>1 (1)</td>
                <td>2 (1)</td>
                <td>3 (1.9)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Ethnicity</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>White</td>
                <td>52 (33)</td>
                <td>55 (35)</td>
                <td>107 (68.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Asian</td>
                <td>12 (8)</td>
                <td>5 (3)</td>
                <td>17 (10.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Black or African American</td>
                <td>5 (3)</td>
                <td>4 (3)</td>
                <td>9 (5.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>American Indian or Alaska Native</td>
                <td>3 (2)</td>
                <td>2 (1)</td>
                <td>5 (3.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Native Hawaiian or other Pacific Islander</td>
                <td>0 (0)</td>
                <td>1 (1)</td>
                <td>1 (0.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Other</td>
                <td>6 (4)</td>
                <td>9 (6)</td>
                <td>15 (9.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Prefer not to say</td>
                <td>1 (1)</td>
                <td>1 (1)</td>
                <td>2 (1.3)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Education</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Less than a high school diploma</td>
                <td>1 (1)</td>
                <td>0 (0)</td>
                <td>1 (0.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>High school degree or equivalent</td>
                <td>7 (4)</td>
                <td>8 (5)</td>
                <td>15 (9.6)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Some college, no degree</td>
                <td>18 (12)</td>
                <td>15 (10)</td>
                <td>33 (21.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Associate degree</td>
                <td>6 (4)</td>
                <td>8 (5)</td>
                <td>14 (9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bachelor’s degree</td>
                <td>19 (12)</td>
                <td>17 (11)</td>
                <td>36 (23.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Master’s degree</td>
                <td>25 (16)</td>
                <td>22 (14)</td>
                <td>47 (30.1)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Professional degree</td>
                <td>1 (1)</td>
                <td>2 (1)</td>
                <td>3 (1.9)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Doctorate</td>
                <td>2 (1)</td>
                <td>5 (3)</td>
                <td>7 (4.5)</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Technology owned</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Laptop or desktop</td>
                <td>78 (50)</td>
                <td>73 (47)</td>
                <td>151 (96.8)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Smartphone</td>
                <td>73 (47)</td>
                <td>74 (47)</td>
                <td>147 (94.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Smartwatch or fitness band</td>
                <td>37 (24)</td>
                <td>32 (21)</td>
                <td>69 (44.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bodyfat or weight scale</td>
                <td>36 (23)</td>
                <td>33 (21)</td>
                <td>69 (44.2)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Tablet</td>
                <td>24 (15)</td>
                <td>42 (27)</td>
                <td>66 (42.3)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Medical device</td>
                <td>32 (21)</td>
                <td>31 (20)</td>
                <td>63 (40.4)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Other</td>
                <td>7 (4)</td>
                <td>8 (5)</td>
                <td>15 (9.6)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Tracking Items and Data Collection Tools</title>
        <p>Exercise (115/132, 87.1%) and weight (101/132, 76.5%) were the 2 most popular items the CT and PT respondents reported tracking (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Other highly ranked items were sleep (63/132, 47.7%), heart rate (61/132, 46.2%), food (60/132, 45.5%), water (58/132, 43.9%), and blood pressure (55/132, 41.7%). On average, CT respondents tracked 5.8 (SD 2.9; range 1-14) items, and PT respondents tracked 4.7 (SD 2.6; range 1-11) items. In responding to the question “What other PHD do you want to track?,” the CT and PT respondents commonly mentioned stress (36/132, 27.3%), cholesterol (31/132, 23.5%), blood pressure (30/132, 22.7%), and mood (29/132, 22%). We noted that 27.3% (36/132) of respondents selected “None (I don’t have anything else I want to track),” which is tied with “stress” for the most selected. Refer to <xref rid="figure2" ref-type="fig">Figure 2</xref> for further details.</p>
        <p>For 24 NE respondents, we asked what type of PHD they wanted to track. The top 5 items were weight (17/24, 71%), stress (16/24, 67%), exercise (15/24, 63%), food intake (15/24, 63%), and water intake (15/24, 63%; <xref rid="figure3" ref-type="fig">Figure 3</xref>). NE respondents wanted to track 7.3 (SD 4.2) items on average, demonstrating high interest in tracking PHD.</p>
        <p><xref rid="figure4" ref-type="fig">Figure 4</xref> shows the tracking methods for the CT and PT respondents. A majority of participants used smartphone apps (90/132, 68.2%), with the most frequently mentioned apps being Apple Health (n=45), Fitbit (n=15), and MyFitnessPal (n=15). However, few respondents also mentioned Weight Watchers (n=4); Google Fit (n=3); and Strava (n=3), an outdoor cycling app. Approximately half of the CT and PT respondents reported using wearable devices (68/132, 51.5%); Apple Watch was the most popular device (n=41), followed by Fitbit (n=22). Among the CT who used some sort of technology for tracking (n=87), 59 (68%; 34 very satisfied and 25 somewhat satisfied) respondents reported that they were satisfied with the current technology (<xref rid="figure5" ref-type="fig">Figure 5</xref>).</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>What personal health data current and past tracker respondents (n=132) have been tracking or have tracked.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e43917_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>What personal health data current and past tracker respondents (n=132) want to track that they are not currently tracking or have not tracked.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e43917_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>What personal health data no experience (no tracking experience) respondents (n=24) want to track.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e43917_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Tracking methods that current and past tracker respondents (n=132) used.</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e43917_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure5" position="float">
          <label>Figure 5</label>
          <caption>
            <p>A waffle chart of current tracker respondents (n=87) reporting their satisfaction level toward personal health tracking technology. A cross symbol (+) indicates a totally blind respondent, and color represents a satisfaction level: very satisfied (n=34), somewhat satisfied (n=25), neutral (n=7), somewhat dissatisfied (n=20), and very dissatisfied (n=1).</p>
          </caption>
          <graphic xlink:href="jmir_v25i1e43917_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>BLV’s Desire and Needs for Tracking</title>
        <p>Our survey with BLV individuals shows that there is not only substantial interest but also important needs for tracking PHD by the respondents (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>). Unless otherwise noted, the total sample size for this section was 156 respondents.</p>
        <p>A total of 33 respondents perceived tracking as an important tool for preventative health. Of this group, 23 described tracking as a means of maintaining their current state, whether sustaining a healthy status or preventing deterioration into a health problem. Awareness of the medical issues in their family’s history and aging were also listed as reasons why tracking was needed.</p>
        <p>A means to improve oneself was another desired benefit for trackers. For some, improving one’s health was noted as a step to external goals, such as enabling new activities like aerial arts. General health improvement was a tracking reason for 24 respondents, with weight loss being the most mentioned. Some shared additional benefits of tracking, which helped them toward better health, such as being coached with “<italic>information to figure out how [to] effectively manage my health</italic>.” Tracking systems also provided welcomed encouragement that helped respondents remain on their health journey. For example, 1 respondent whose data led to a sustained effort said the following (as a respondent’s anonymized ID, we used the last 4 letters from the identifier the survey system automatically creates. We used “CT” to denote participants who are “current trackers” and “TB” to denote those who are “totally blind”):</p>
        <disp-quote>
          <p>I find that by keeping track of steps, hours standing, heart rate [and] these other issues I can encourage myself to remain active. I can encourage myself to keep on that eating plan or that exercise plan that will help me get to a healthier lifestyle. Seeing the small changes and seeing the trends of how I am improving helps to motivate me to keep going and to start pushing myself to do better.</p>
          <attrib>i6fh, CT and TB</attrib>
        </disp-quote>
        <p>A total of 50 respondents wished to use tracking as a means to learn about themselves, whether simply because of curiosity, or to view what progress was made in their activity. Of this group, the majority (34/50, 68%) found tracking to be an important diagnostic tool for their health, keeping track of various measurements and being made aware of any outlying incidents. Several respondents also valued the averages provided in the tracking systems for measurement comparison.</p>
        <p>A group of 22 respondents expanded their analysis and wished to use tracking data for outcome analysis to examine how different actions affected their health. This ranged from inspecting the correlations of activity toward health to the effectiveness of their medications and treatments. One respondent shared how tracking was used to validate the proper use of medical equipment:</p>
        <disp-quote>
          <p>With sleep apnea, I need to make sure my mask seal is correct and my number of episodes per hour are below a certain level to gauge whether the treatment is working as it should.</p>
          <attrib>pu8s, CT and TB</attrib>
        </disp-quote>
        <boxed-text id="box2" position="float">
          <title>A summary of blind and low-vision respondents’ motivation and needs to track personal health data (PHD).</title>
          <p>
            <bold>Tool for preventative health</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>To sustain healthy status</p>
            </list-item>
            <list-item>
              <p>To prevent health deterioration</p>
            </list-item>
            <list-item>
              <p>To be aware of family- or aging-related issues</p>
            </list-item>
          </list>
          <p>
            <bold>A means to improve oneself</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Enabling general health improvement, especially weight loss</p>
            </list-item>
            <list-item>
              <p>Activity as a step toward external goals, for example, losing weight so that one can try new activities</p>
            </list-item>
            <list-item>
              <p>Learning from system-provided health coaching</p>
            </list-item>
            <list-item>
              <p>Being inspired by encouragement given by system</p>
            </list-item>
          </list>
          <p>
            <bold>Way to learn about themselves</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Diagnostic tool for health, for example, blood sugar monitoring</p>
            </list-item>
            <list-item>
              <p>Allowing a comparison of PHD with system’s global averages</p>
            </list-item>
            <list-item>
              <p>Tracking personal health activity progress</p>
            </list-item>
            <list-item>
              <p>Mere curiosity</p>
            </list-item>
          </list>
          <p>
            <bold>Outcome analysis</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Inspecting correlations of actions toward health</p>
            </list-item>
            <list-item>
              <p>Measuring the effectiveness of medications and treatments</p>
            </list-item>
            <list-item>
              <p>Using systems as a historical record keeper</p>
            </list-item>
          </list>
          <p>
            <bold>With and for others</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Enabling social activities, for example, step count challenges</p>
            </list-item>
            <list-item>
              <p>Remaining healthy to continue caring for others</p>
            </list-item>
            <list-item>
              <p>Maintaining health to lessen the need for others’ aid</p>
            </list-item>
          </list>
        </boxed-text>
        <p>A total of 13 respondents mentioned the additional use of tracking systems as a historical record keeper as a reason for tracking. Of the 13 respondents, 2 saw this historical data as a means of sharing information with their doctors.</p>
        <p>Different aspects of using tracking data with others were mentioned, such as social activities, including step count challenges. A total of 3 respondents tracked PHD to benefit others, striving to remain healthy to continue caring for family or clients in their lives, or merely to lessen the need for others’ aid.</p>
      </sec>
      <sec>
        <title>Barriers to Tracking</title>
        <sec>
          <title>Overview</title>
          <p>In this section, we report a wide range of barriers experienced by BLV respondents in tracking PHD (<xref ref-type="boxed-text" rid="box3">Textbox 3</xref>). Unless otherwise noted, the total sample size for this section is 132 CT and PT respondents.</p>
          <boxed-text id="box3" position="float">
            <title>Summary of the barriers experienced by blind and low-vision (BLV) respondents in tracking personal health data.</title>
            <p>
              <bold>Knowing it could be better</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Blocked from initiating tracking</p>
                <list>
                  <list-item>
                    <p>No accessible options for tracking certain activities</p>
                  </list-item>
                  <list-item>
                    <p>Visual roadblocks prevent users from initiating tracking, for example, inaccessible device pairing codes</p>
                  </list-item>
                  <list-item>
                    <p>Lacking information on accessibility of available apps and devices</p>
                  </list-item>
                  <list-item>
                    <p>Accessible equipment can be unaffordable for the population</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Adaptation tools not supported by systems</p>
                <list>
                  <list-item>
                    <p>Incompatibility with tools, for example, screen reader and braille output</p>
                  </list-item>
                  <list-item>
                    <p>Lack of visibility options, for example, magnification or contrast</p>
                  </list-item>
                  <list-item>
                    <p>Misapplied aid, for example, screen reader compatible but giving incorrect label for button</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Missing out on features because of disability</p>
                <list>
                  <list-item>
                    <p>Limited from features on devices because of lack of accessibility, for example, screens on wearables</p>
                  </list-item>
                  <list-item>
                    <p>Inaccessibility when graphs are used to portray data in apps</p>
                  </list-item>
                  <list-item>
                    <p>Specific app features not enabled with accessibility</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Information delay</p>
                <list>
                  <list-item>
                    <p>Waiting for data to be transferred to accessible app</p>
                  </list-item>
                  <list-item>
                    <p>Waiting for aid of others in reading data</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Negative awareness of sighted users’ experiences</p>
                <list>
                  <list-item>
                    <p>Measuring time expenditure against sighted users’ efforts</p>
                  </list-item>
                  <list-item>
                    <p>Jealousy in how others benefit from features inaccessible to them</p>
                  </list-item>
                  <list-item>
                    <p>Comparison of prior experience to current use with declined vision</p>
                  </list-item>
                  <list-item>
                    <p>Recognizing accessibility deterioration, for example, losing accessibility functions with new updates</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Perceived low valuation in tracking</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Tracking can be burdensome for BLV users</p>
                <list>
                  <list-item>
                    <p>Increased time consumption in entering data and using app</p>
                  </list-item>
                  <list-item>
                    <p>Needing to involve others to complete tracking procedure</p>
                  </list-item>
                  <list-item>
                    <p>Data comprehension requiring in-memory manipulation</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Data are not seen as trustworthy</p>
                <list>
                  <list-item>
                    <p>Observing discrepancies between devices</p>
                  </list-item>
                  <list-item>
                    <p>Noticing incomplete data about known activities</p>
                  </list-item>
                  <list-item>
                    <p>Incompatibility of trackers with ailments, for example, cerebral palsy affecting step count</p>
                  </list-item>
                  <list-item>
                    <p>Not finding discrete data points as representative of true health</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Data elicits negative emotions</p>
                <list>
                  <list-item>
                    <p>Data becoming too overwhelming</p>
                  </list-item>
                  <list-item>
                    <p>Privacy concerns</p>
                  </list-item>
                  <list-item>
                    <p>Lucidity of recorded behavior is upsetting, for example, realization in food tracking</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>General disinterest in tracking</p>
                <list>
                  <list-item>
                    <p>Tracking follows activity—fading when user’s interest in activity fades</p>
                  </list-item>
                  <list-item>
                    <p>Tracking only seen as an assignment, ending when directive is completed</p>
                  </list-item>
                  <list-item>
                    <p>Data not providing insight or usefulness</p>
                  </list-item>
                </list>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>Knowing It Could Be Better</title>
          <p>Respondents not only noted their suboptimal tracking experiences but also the specific ways in which the situations could be better. This led to frustration and occasional discontinuance of tracking.</p>
          <p>Some attempts in tracking were simply blocked at the start. A total of 15 respondents did not have accessible options in trackers, especially for blood glucose and blood pressure monitoring. Tracking procedures requiring vision, such as reading caloric information from food packaging, were not tenable.</p>
          <p>Even in tracking systems that attempt accessibility, 4 BLV respondents ran into roadblocks preventing them from getting started, with several mentioning the initial pairing procedure requiring a sighted user to read a code on the device. Some physical design choices were hurdles to continued use, such as difficult battery replacement doors or blood test strips relying solely on visual indicators for application.</p>
          <p>In some cases, the landscape of available trackers and apps was frustratingly uncharted for the respondents. For example, 1 respondent journeyed through the many pitfalls of attempting to buy an accessible tracker:</p>
          <disp-quote>
            <p>Biggest issue is I did not know if an app was going to be accessible until I download it. In the description it does not say whether or not VoiceOver [Apple’s built-in screen reader] is friendly with the app...But sometimes you don’t know if it will work until it is paired to the device which means you have to purchase the device. Then when you try and go and purchase a device especially if you’re doing it online, you don’t know to get the device whether or not it is accessible.</p>
            <attrib>i6fh, CT and TB</attrib>
          </disp-quote>
          <p>Finally, although accessible trackers may be known and available, 9 noted their usual increased costs and inability to afford them. One respondent divulged the relationship between their disability and income and how it affected their device ownership:</p>
          <disp-quote>
            <p>Talking devices are a lot more expensive than non-talking ones. Being low income as a totally blind person, I really have to try hard to get those devices.</p>
            <attrib>45jg, CT and TB</attrib>
          </disp-quote>
          <p>Among the respondents who could begin tracking, 49 reported the lack of support for their adaptation tools in the paired apps, with the majority (31/49, 63%) specifically referring to compatibility with screen readers. Some shared incidents of misapplied aid, such as a screen reader identifying a button but using an incorrect label or reading fields in an illogical order. A total of 8 LV respondents mentioned problems with the visibility in apps, wishing for magnification and contrast options, and another LV respondent wanted better braille support.</p>
          <p>Two respondents shared different problems with the exercise apps. One LV respondent, who used a magnifier, liked the written descriptions and visual demos via their television but found difficulty during the actual exercise routines when missing verbal cues about new text instructions. Another TB respondent found themselves blocked because of the difficulties in understanding the verbal explanations of the exercises.</p>
          <p>Respondents shared the sense of missing out on features that sighted users could use. A total of 19 respondents noted how they were only able to use a subsegment of their tracking systems, such as tracking devices that use inaccessible screens or advanced statistics not available from the accessible portions of the app. In addition, 15 respondents mentioned the frequent use of inaccessible graphs and their ineffectiveness for BLV users.</p>
          <p>The immediacy of PHD is sometimes a luxury that is unavailable to BLV users. Some respondents use the aid of others to work around the inaccessible areas of their tracking systems, but when helpers are not available, feedback is delayed. Others experience similar information delays owing to the need to wait until the data are transferred to the accessible portion of the system. One respondent shared annoyance in waiting to read their data:</p>
          <disp-quote>
            <p>I had to sync my Fitbit with the Fitbit app in order to access my stats. This was very frustrating as sighted people can just look at their Fitbits to tell how many steps they have done.</p>
            <attrib>7cqb, CT and TB</attrib>
          </disp-quote>
          <p>This knowledge of abled users’ easier experiences in tracking led to varied negative emotions among the respondents. One respondent noted their frustration in the PHD manual entry, in part by measuring themselves against how long a sighted person would take. Another mentioned being jealous of their husband’s enhanced gym experience, as her PHD was locked behind inaccessible screen-based equipment:</p>
          <disp-quote>
            <p>I do not recognize it when I am gradually improving by going faster or working harder like my husband does. He says things like “I did my 2 mile run faster today” I have no idea how far I ran...I have no idea if I’m doing better or worse today than yesterday or last week or last month so my motivation is waning.</p>
            <attrib>aeym, CT and TB</attrib>
          </disp-quote>
          <p>At times, the evidence of a better experience came from the respondent’s own history: 1 respondent shared the need to change how they accessed their system because of worsening vision. However, 8 respondents pointed out a deterioration in the accessibility of features in their tracking system, losing access to functionality they previously used.</p>
        </sec>
        <sec>
          <title>Perceived Low Valuation in Tracking</title>
          <p>Some respondents were disinterested in PhD tracking because the benefits did not provide enough value compared to the effort required. Although some reasons may be shared with sighted individuals, in many instances, this valuation was because of their systems’ incompatibility with their situation.</p>
          <p>For 10 respondents, this value equation was affected by the extended burden of tracking for BLV users. At times, the data provided by tracking added an additional burden of being reliant solely on memory when reviewing data, perhaps only being presented via the screen reader. Others noted the added time consumption in entering data into apps or simply using the apps in general. The need to involve others in tracking data that required sight was another unwanted burden, as it reduced some respondents’ feelings of independence.</p>
          <p>Some respondents shared how the collected PHD from their tracking devices were not trustworthy. Awareness of discrepancies between parallel trackers and devices, incomplete data about known activities, and incompatibility of trackers with ailments such as cerebral palsy were all mentioned as barriers to tracking PHD.</p>
          <p>Even if the collected PHD were accurate, the data itself could elicit unfavorable reactions in users. Three respondents found the incoming data too overwhelming, such as 1 CT and TB user who found most notifications as unimportant and resigned to ignore them all because of the difficulty of reading notifications. Moreover, 2 respondents shared concerns with privacy, including a PT and LV respondent who disliked when others were able to read their “personal info” whenever they needed assistance with their Fitbit. For a few respondents, the lucidity of their recorded behavior proved stressful or upsetting; 1 PT and TB respondent preferred “<italic>not wanting to know any bad news</italic>.”</p>
          <p>In some PT cases, the tracking experience was not of interest. Three PT respondents merely saw their tracking efforts as an assigned task from others, which once ended meant that they could discontinue further use. In addition, 5 respondents found tracking to be a subtask of their health activity, and when their commitment to the activity dropped, the lack of tracking followed. Moreover, 5 PT respondents found no interest in what they captured (eg, data levels that remained constant throughout), and so their efforts of data entry did not provide enough value for continuance.</p>
        </sec>
      </sec>
      <sec>
        <title>Work-Arounds to Access Inaccessible Data</title>
        <p>Some tracking systems aid BLV trackers in adapting to their disability. A majority of respondents (67/132, 50.8%) relied on a screen reader (either on a smartphone or computer) to access the tracked data (<xref ref-type="table" rid="table2">Table 2</xref>). They augmented inaccessible devices with their smartphones, which provided an accessible screen reader for transferred data, and others relied on the added haptic feedback to alert them to various reminders and alerts. When buttons were mislabeled and screen readers were not helpful, BLV respondents learned by trial and error to memorize the functionalities of the mislabeled buttons.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>How current tracker and past tracker respondents (n=132) access the tracked data based on an optional response question.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="310"/>
            <col width="230"/>
            <col width="210"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Current tracker (n=69), n (%)</td>
                <td>Past tracker (n=63), n (%)</td>
                <td>Combined (n=132), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Screen reader</td>
                <td>38 (29)</td>
                <td>29 (22)</td>
                <td>67 (50.8)</td>
              </tr>
              <tr valign="top">
                <td>Braille display</td>
                <td>0 (0)</td>
                <td>1 (1)</td>
                <td>1 (0.8)</td>
              </tr>
              <tr valign="top">
                <td>Magnification or residual vision</td>
                <td>0 (0)</td>
                <td>8 (6)</td>
                <td>8 (6.1)</td>
              </tr>
              <tr valign="top">
                <td>Assistance from others</td>
                <td>3 (2)</td>
                <td>4 (3)</td>
                <td>7 (5.3)</td>
              </tr>
              <tr valign="top">
                <td>No response</td>
                <td>28 (21)</td>
                <td>21 (16)</td>
                <td>49 (37.1)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>Tracking systems also provided other types of organizational help, such as one user who appreciated how they were able to “<italic>funnel as much as possible into my Apple Health app as the primary hub</italic>,” and another who liked the ability to favorite specific health statistics to add to their feed.</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of the Key Findings and Implications</title>
        <p>Self-tracking has been extensively studied in the health informatics community [<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref29">29</xref>], but the experience of BLV people was rarely represented. We contributed to an understanding of BLV people’s personal health tracking motivation, practices, needs, and challenges. Our survey showed that BLV respondents have strong desires and needs to track their PHD, and many of them are already tracking their data despite many hurdles. Popular tracking items—exercise, weight, sleep, and food—and the reasons for tracking reported in this study were similar to those of sighted people [<xref ref-type="bibr" rid="ref3">3</xref>]. However, BLV people experienced diverse accessibility challenges in tracking and accessing data, failing to effectively benefit from self-tracking technologies.</p>
        <p>Challenges persist throughout the different phases of self-tracking, starting from identifying accessible tools to difficulty in tracking and reviewing data. The main barriers our respondents experienced included suboptimal tracking experiences and insufficient benefits against the extended burden for BLV people. Some of these accessibility challenges were unique to BLV users, making already burdensome self-tracking even more challenging. For example, a common challenge faced by sighted users was to identify a personal tracking app that would help them meet their goals. To address this problem, sighted users would try out multiple apps before they settle on a tool of their choice—a process called “trialing” [<xref ref-type="bibr" rid="ref30">30</xref>]. Such an approach is unlikely to be viable for BLV people because it requires considerable efforts to check whether a tool is accessible before they can assess the tool’s efficacy.</p>
      </sec>
      <sec>
        <title>Accessibility Exists on a Spectrum</title>
        <p>A recurring theme we identified in the data was whether a technology is accessible is not all black and white, but it exists on a spectrum (refer to the themes under “Knowing It Could Be Better” in <xref ref-type="boxed-text" rid="box3">Textbox 3</xref>). Even if BLV users spot an accessible technology, it is unclear to what extent the technology is accessible: tracking might be possible, but there may be an information delay in accessing the tracked data; data may be accessible only from an app but not from a wearable device, or the feedback (eg, a chart) may not be accessible at all. Contrary to our expectations and to the reported barriers from the open-ended survey responses, most current BLV trackers (59/87, 68%) were satisfied with the personal health technologies that they are using. Of the 34 highly satisfied respondents, 10 (30%) answered the questions specifically for their current setup, that is, they did not consider systems with barriers that had already been pruned from their setup. However, for others, perhaps the contrasting result indicates that despite many accessibility challenges BLV users experience, some people could have successfully used work-arounds to meet their tracking goals or might have been satisfied with subpar experience because they had low expectations to begin with. Further research is warranted to examine the gap between the high level of satisfaction and the accessibility challenges reported and to what extent the currently supported self-tracking features are being used and what key accessibility challenges have high impact on user satisfaction had they been addressed.</p>
        <p>Similarly, the relationship between barriers to tracking and people’s current tracking status may prove to be another avenue of research worth investigating further. Although a large majority of NE respondents (22/24, 92%) expressed interest in collecting PHD, additional studies are needed to find more details on the barriers that limit these individuals from beginning to track and possible solutions to overcome them. Although our survey found similar barriers reported by PT and CT members, future work is needed to fully investigate why some persevere when confronted with barriers and others discontinue. It is conceivable that a decreased level of importance assigned to one’s health or circumstantial disadvantages that intensify some barriers are the reasons that contribute to discontinuation, but this inquiry would benefit from studies that allow for more depth beyond this initial survey.</p>
      </sec>
      <sec>
        <title>Limitations and Future Work</title>
        <p>Our participants appeared to be technologically savvy, as there were 94.2% (147/156) of smartphone users compared with the US average of 85%, and 96.8% (151/156) laptop or desktop device owners compared with the US average of 77% [<xref ref-type="bibr" rid="ref31">31</xref>]. Moreover, 44.2% (69/156) of our survey respondents reported that they currently own wearable devices, which is much higher than the US average of 21% [<xref ref-type="bibr" rid="ref2">2</xref>]. Although not generalizable to all BLV people, this shows our respondents’ high interest in personal health tracking. The challenges we reported regarding PHD tracking still hold because the lived experience of interacting with personal health technologies can come from those who had or have been using the technologies. Furthermore, fewer tech-savvy groups will likely experience the identified accessibility challenges if they were to engage in self-tracking.</p>
        <p>However, our findings also indicate that a large variability exists among BLV individuals. Further studies are warranted to understand how general BLV individuals engage in personal health tracking while not conflating the 2 groups—TB and LV people—as their vision capabilities (eg, whether one has residual vision vs not) and respective solutions (eg, GUI based and screen reader based) could be different [<xref ref-type="bibr" rid="ref32">32</xref>]. Furthermore, we need to devise ways to help BLV individuals with less technical proficiency onboard with self-tracking, such as identifying appropriate tools that meet their individual tracking goals.</p>
        <p>We collected data through a web-based and phone survey to recruit more respondents more easily. To ensure the data quality, we carefully inspected the quality of responses and excluded 28 suspicious responses—2 with duplicate IP addresses and 26 with a suspicious pattern. However, as we did not observe or interact with the respondents, the inherent concern about the data quality of web-based surveys remains.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>On the basis of our survey of 156 BLV users’ PHD tracking experiences, we reported quantitative and qualitative findings that contribute to an in-depth understanding of their motivations, tracking practices, challenges, and work-arounds. These findings shed light on design opportunities and areas to focus on making PHD technologies more accessible to BLV individuals. We strongly encourage technology companies and health researchers to invest their efforts in making PHD technologies accessible to BLV people, as a step toward ensuring equitable access to health data for all.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>The web-based version of the survey we distributed.</p>
        <media xlink:href="jmir_v25i1e43917_app1.docx" xlink:title="DOCX File , 32 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Codebook from the qualitative data analysis.</p>
        <media xlink:href="jmir_v25i1e43917_app2.pdf" xlink:title="PDF File  (Adobe PDF File), 46 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BLV</term>
          <def>
            <p>blind and low-vision</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CT</term>
          <def>
            <p>current tracker</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">GUI</term>
          <def>
            <p>graphical user interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">LV</term>
          <def>
            <p>low vision</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">mHealth</term>
          <def>
            <p>mobile health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">NE</term>
          <def>
            <p>no experience</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">PHD</term>
          <def>
            <p>personal health data</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">PT</term>
          <def>
            <p>past tracker</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">TB</term>
          <def>
            <p>totally blind</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors would like to thank their survey respondents for sharing their experiences and thoughts. This research was partially supported by the National Science Foundation under Award 1753452.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The data sets generated during this study are not available according to our institutional review board protocol and consent form, but the study protocol (questionnaire) and analyses of the qualitative data are available in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendices 1</xref> and <xref ref-type="supplementary-material" rid="app2">2</xref>.</p>
      </sec>
    </notes>
    <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="web">
          <article-title>Digital health trends 2021: innovation, evidence, regulation, and adoption</article-title>
          <source>IQVIA Institute for Human Data Science</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iqvia.com/insights/the-iqvia-institute/reports/digital-health-trends-2021">https://www.iqvia.com/insights/the-iqvia-institute/reports/digital-health-trends-2021</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vogles</surname>
              <given-names>EA</given-names>
            </name>
          </person-group>
          <article-title>About one-in-five Americans use a smart watch or fitness tracker</article-title>
          <source>Pew Research Center</source>
          <year>2020</year>
          <month>1</month>
          <day>9</day>
          <access-date>2022-10-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/fact-tank/2020/01/09/about-one-in-five-americans-use-a-smart-watch-or-fitness-tracker">https://www.pewresearch.org/fact-tank/2020/01/09/about-one-in-five-americans-use-a-smart-watch-or-fitness-tracker</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Choe</surname>
              <given-names>EK</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kientz</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Understanding quantified-selfers' practices in collecting and exploring personal data</article-title>
          <source>Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</source>
          <year>2014</year>
          <conf-name>CHI '14: CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>Apr 26-May 1, 2014</conf-date>
          <conf-loc>Toronto Ontario Canada</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2556288.2557372</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Cook</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Bales</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Zia</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Munson</surname>
              <given-names>SA</given-names>
            </name>
          </person-group>
          <article-title>More than telemonitoring: health provider use and nonuse of life-log data in irritable bowel syndrome and weight management</article-title>
          <source>J Med Internet Res</source>
          <year>2015</year>
          <month>08</month>
          <day>21</day>
          <volume>17</volume>
          <issue>8</issue>
          <fpage>e203</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2015/8/e203/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4364</pub-id>
          <pub-id pub-id-type="medline">26297627</pub-id>
          <pub-id pub-id-type="pii">v17i8e203</pub-id>
          <pub-id pub-id-type="pmcid">PMC4642406</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Heo</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ji</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Prescribing 10,000 steps like aspirin: designing a novel interface for data-driven medical consultations</article-title>
          <source>Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems</source>
          <year>2017</year>
          <conf-name>CHI '17: CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 6 - 11, 2017</conf-date>
          <conf-loc>Denver Colorado USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/3025453.3025570</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>West</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Giordano</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Van Kleek</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Shadbolt</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>The quantified patient in the doctor's office: challenges and opportunities</article-title>
          <source>Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems</source>
          <year>2016</year>
          <conf-name>CHI'16: CHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>May 7 - 12, 2016</conf-date>
          <conf-loc>San Jose California USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/2858036.2858445</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Colgan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Choe</surname>
              <given-names>EK</given-names>
            </name>
          </person-group>
          <article-title>Sharing patient-generated data in clinical practices: an interview study</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2016</year>
          <volume>2016</volume>
          <fpage>1303</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28269928"/>
          </comment>
          <pub-id pub-id-type="medline">28269928</pub-id>
          <pub-id pub-id-type="pmcid">PMC5333267</pub-id>
        </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>Milne</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bennett</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Ladner</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>The accessibility of mobile health sensors for blind users</article-title>
          <source>J Technol Pers Disabil</source>
          <year>2014</year>
          <volume>2</volume>
          <fpage>75</fpage>
        </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>Deruyter</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Mobile health apps and needs of people with disabilities: a national survey</article-title>
          <source>J Technol Pers Disabil</source>
          <year>2018</year>
          <volume>6</volume>
          <fpage>61</fpage>
        </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>Jones</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Deruyter</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Mobile healthcare and people with disabilities: current state and future needs</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2018</year>
          <month>03</month>
          <day>14</day>
          <volume>15</volume>
          <issue>3</issue>
          <fpage>515</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph15030515"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph15030515</pub-id>
          <pub-id pub-id-type="medline">29538292</pub-id>
          <pub-id pub-id-type="pii">ijerph15030515</pub-id>
          <pub-id pub-id-type="pmcid">PMC5877060</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lippincot</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>DeRuyter</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Survey of user needs: mobile apps for mHealth and people with disabilities</article-title>
          <source>Computers Helping People with Special Needs</source>
          <year>2020</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </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>Kim</surname>
              <given-names>HN</given-names>
            </name>
          </person-group>
          <article-title>Mobile health technology accessible to people with visual impairments</article-title>
          <source>J Technol Pers Disabil</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>35</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://scholarworks.csun.edu/bitstream/handle/10211.3/210387/02_Mobile%20Health%20Technology%20Accessible%20to%20People%20with%20Visual%20Impairments.pdf?sequence=1"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Radcliffe</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Lippincott</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>A pilot evaluation of mHealth app accessibility for three top-rated weight management apps by people with disabilities</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2021</year>
          <month>04</month>
          <day>01</day>
          <volume>18</volume>
          <issue>7</issue>
          <fpage>3669</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph18073669"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph18073669</pub-id>
          <pub-id pub-id-type="medline">33915917</pub-id>
          <pub-id pub-id-type="pii">ijerph18073669</pub-id>
          <pub-id pub-id-type="pmcid">PMC8036471</pub-id>
        </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>Iezzoni</surname>
              <given-names>LI</given-names>
            </name>
          </person-group>
          <article-title>Eliminating health and health care disparities among the growing population of people with disabilities</article-title>
          <source>Health Aff (Millwood)</source>
          <year>2011</year>
          <month>10</month>
          <volume>30</volume>
          <issue>10</issue>
          <fpage>1947</fpage>
          <lpage>54</lpage>
          <pub-id pub-id-type="doi">10.1377/hlthaff.2011.0613</pub-id>
          <pub-id pub-id-type="medline">21976339</pub-id>
          <pub-id pub-id-type="pii">30/10/1947</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>Magesh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>John</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>WT</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Mattingly-App</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jain</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>EY</given-names>
            </name>
            <name name-style="western">
              <surname>Ongkeko</surname>
              <given-names>WM</given-names>
            </name>
          </person-group>
          <article-title>Disparities in COVID-19 outcomes by race, ethnicity, and socioeconomic status: a systematic-review and meta-analysis</article-title>
          <source>JAMA Netw Open</source>
          <year>2021</year>
          <month>11</month>
          <day>01</day>
          <volume>4</volume>
          <issue>11</issue>
          <fpage>e2134147</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34762110"/>
          </comment>
          <pub-id pub-id-type="doi">10.1001/jamanetworkopen.2021.34147</pub-id>
          <pub-id pub-id-type="medline">34762110</pub-id>
          <pub-id pub-id-type="pii">2785980</pub-id>
          <pub-id pub-id-type="pmcid">PMC8586903</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>Shavers</surname>
              <given-names>VL</given-names>
            </name>
          </person-group>
          <article-title>Measurement of socioeconomic status in health disparities research</article-title>
          <source>J Natl Med Assoc</source>
          <year>2007</year>
          <month>09</month>
          <volume>99</volume>
          <issue>9</issue>
          <fpage>1013</fpage>
          <lpage>23</lpage>
          <pub-id pub-id-type="medline">17913111</pub-id>
          <pub-id pub-id-type="pmcid">PMC2575866</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>Scheerder</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Deursen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Dijk</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Determinants of internet skills, uses and outcomes. A systematic review of the second- and third-level digital divide</article-title>
          <source>Telematic Informatic</source>
          <year>2017</year>
          <month>12</month>
          <volume>34</volume>
          <issue>8</issue>
          <fpage>1607</fpage>
          <lpage>24</lpage>
          <pub-id pub-id-type="doi">10.1016/j.tele.2017.07.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>von Huben</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Howell</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Howard</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Carrello</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Norris</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Health technology assessment for digital technologies that manage chronic disease: a systematic review</article-title>
          <source>Int J Technol Assess Health Care</source>
          <year>2021</year>
          <month>05</month>
          <day>26</day>
          <volume>37</volume>
          <issue>1</issue>
          <fpage>e66</fpage>
          <pub-id pub-id-type="doi">10.1017/S0266462321000362</pub-id>
          <pub-id pub-id-type="medline">34034851</pub-id>
          <pub-id pub-id-type="pii">S0266462321000362</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>van Kessel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Hrzic</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>O'Nuallain</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Weir</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Wong</surname>
              <given-names>BL</given-names>
            </name>
            <name name-style="western">
              <surname>Anderson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baron-Cohen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Mossialos</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Digital health paradox: international policy perspectives to address increased health inequalities for people living with disabilities</article-title>
          <source>J Med Internet Res</source>
          <year>2022</year>
          <month>02</month>
          <day>22</day>
          <volume>24</volume>
          <issue>2</issue>
          <fpage>e33819</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2022/2/e33819/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/33819</pub-id>
          <pub-id pub-id-type="medline">35191848</pub-id>
          <pub-id pub-id-type="pii">v24i2e33819</pub-id>
          <pub-id pub-id-type="pmcid">PMC8905475</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Veinot</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Mitchell</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Ancker</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Good intentions are not enough: how informatics interventions can worsen inequality</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>08</month>
          <day>01</day>
          <volume>25</volume>
          <issue>8</issue>
          <fpage>1080</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29788380"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy052</pub-id>
          <pub-id pub-id-type="medline">29788380</pub-id>
          <pub-id pub-id-type="pii">4996916</pub-id>
          <pub-id pub-id-type="pmcid">PMC7646885</pub-id>
        </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>Thompson</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Morris</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Jones</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>DeRuyter</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Use of mHealth technologies by people with vision impairment</article-title>
          <source>J Technol Pers Disabil</source>
          <year>2019</year>
          <volume>7</volume>
          <fpage>35</fpage>
        </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>Madrigal-Cadavid</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Amariles</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pino-Marín</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Granados</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Giraldo</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Design and development of a mobile app of drug information for people with visual impairment</article-title>
          <source>Res Social Adm Pharm</source>
          <year>2020</year>
          <month>01</month>
          <volume>16</volume>
          <issue>1</issue>
          <fpage>62</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.1016/j.sapharm.2019.02.013</pub-id>
          <pub-id pub-id-type="medline">30853509</pub-id>
          <pub-id pub-id-type="pii">S1551-7411(19)30131-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <source>Qualtrics</source>
          <access-date>2023-04-13</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.qualtrics.com/">https://www.qualtrics.com/</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>Bietz</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Bloss</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Calvert</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Godino</surname>
              <given-names>JG</given-names>
            </name>
            <name name-style="western">
              <surname>Gregory</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Claffey</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Sheehan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Patrick</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Opportunities and challenges in the use of personal health data for health research</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>04</month>
          <volume>23</volume>
          <issue>e1</issue>
          <fpage>e42</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26335984"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv118</pub-id>
          <pub-id pub-id-type="medline">26335984</pub-id>
          <pub-id pub-id-type="pii">ocv118</pub-id>
          <pub-id pub-id-type="pmcid">PMC4954630</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Choe</surname>
              <given-names>EK</given-names>
            </name>
          </person-group>
          <article-title>Investigating data accessibility of personal health apps</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2019</year>
          <month>05</month>
          <day>01</day>
          <volume>26</volume>
          <issue>5</issue>
          <fpage>412</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30861531"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocz003</pub-id>
          <pub-id pub-id-type="medline">30861531</pub-id>
          <pub-id pub-id-type="pii">5376662</pub-id>
          <pub-id pub-id-type="pmcid">PMC6433179</pub-id>
        </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>Murnane</surname>
              <given-names>EL</given-names>
            </name>
            <name name-style="western">
              <surname>Cosley</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Guha</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Frank</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Gay</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Matthews</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Self-monitoring practices, attitudes, and needs of individuals with bipolar disorder: implications for the design of technologies to manage mental health</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2016</year>
          <month>05</month>
          <volume>23</volume>
          <issue>3</issue>
          <fpage>477</fpage>
          <lpage>84</lpage>
          <pub-id pub-id-type="doi">10.1093/jamia/ocv165</pub-id>
          <pub-id pub-id-type="medline">26911822</pub-id>
          <pub-id pub-id-type="pii">ocv165</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>Shaw</surname>
              <given-names>RJ</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Barnes</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hatch</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Crowley</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Vorderstrasse</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Vaughn</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Diane</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Lewinski</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stevenson</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Steinberg</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Self-monitoring diabetes with multiple mobile health devices</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <volume>27</volume>
          <issue>5</issue>
          <fpage>667</fpage>
          <lpage>76</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/32134447"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocaa007</pub-id>
          <pub-id pub-id-type="medline">32134447</pub-id>
          <pub-id pub-id-type="pii">5782084</pub-id>
          <pub-id pub-id-type="pmcid">PMC7309229</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Qu</surname>
              <given-names>X</given-names>
            </name>
          </person-group>
          <article-title>Presenting self-monitoring test results for consumers: the effects of graphical formats and age</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2018</year>
          <month>08</month>
          <day>01</day>
          <volume>25</volume>
          <issue>8</issue>
          <fpage>1036</fpage>
          <lpage>46</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/29762686"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocy046</pub-id>
          <pub-id pub-id-type="medline">29762686</pub-id>
          <pub-id pub-id-type="pii">4995316</pub-id>
          <pub-id pub-id-type="pmcid">PMC7646882</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>Turner-McGrievy</surname>
              <given-names>GM</given-names>
            </name>
            <name name-style="western">
              <surname>Beets</surname>
              <given-names>MW</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Kaczynski</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Barr-Anderson</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Tate</surname>
              <given-names>DF</given-names>
            </name>
          </person-group>
          <article-title>Comparison of traditional versus mobile app self-monitoring of physical activity and dietary intake among overweight adults participating in an mHealth weight loss program</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>05</month>
          <day>01</day>
          <volume>20</volume>
          <issue>3</issue>
          <fpage>513</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/23429637"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-001510</pub-id>
          <pub-id pub-id-type="medline">23429637</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-001510</pub-id>
          <pub-id pub-id-type="pmcid">PMC3628067</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Schroeder</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Epstein</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <article-title>Understanding and supporting self-tracking app selection</article-title>
          <source>Proc ACM Interact Mobile Wearable Ubiquitous Technologies</source>
          <year>2021</year>
          <month>12</month>
          <day>30</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>1</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1145/3494980</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>Mobile Fact Sheet</article-title>
          <source>Pew Research Center</source>
          <year>2021</year>
          <month>4</month>
          <day>7</day>
          <access-date>2022-10-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewresearch.org/internet/fact-sheet/mobile">https://www.pewresearch.org/internet/fact-sheet/mobile</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>NW</given-names>
            </name>
            <name name-style="western">
              <surname>Joyner</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Riegelhuth</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Accessible visualization: design space, opportunities, and challenges</article-title>
          <source>Comput Graphics Forum</source>
          <year>2021</year>
          <month>06</month>
          <day>29</day>
          <volume>40</volume>
          <issue>3</issue>
          <fpage>173</fpage>
          <lpage>88</lpage>
          <pub-id pub-id-type="doi">10.1111/cgf.14298</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
