<?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 Human Factors</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Hum Factors</journal-id>
      <journal-title>JMIR Human Factors</journal-title>
      <issn pub-type="epub">2292-9495</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">v8i3e26532</article-id>
      <article-id pub-id-type="pmid">34406123</article-id>
      <article-id pub-id-type="doi">10.2196/26532</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>Usability of a Co-designed eHealth Prototype for Caregivers: Combination Study of Three Frameworks</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Kushniruk</surname>
            <given-names>Andre</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Khan</surname>
            <given-names>Alsa</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Pimentel</surname>
            <given-names>Juan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Tremblay</surname>
            <given-names>Melanie</given-names>
          </name>
          <degrees>MA</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <address>
            <institution>Department of Teaching and Learning Studies</institution>
            <institution>Université Laval</institution>
            <addr-line>2325 Rue de l'Université</addr-line>
            <addr-line>Québec, QC, G1V 0A6</addr-line>
            <country>Canada</country>
            <phone>1 (418) 656 2131</phone>
            <email>melanie.tremblay.50@ulaval.ca</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2176-5902</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Latulippe</surname>
            <given-names>Karine</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff01" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7998-6498</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Guay</surname>
            <given-names>Manon</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff02" ref-type="aff">2</xref>
          <xref rid="aff03" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2219-9327</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Provencher</surname>
            <given-names>Véronique</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff02" ref-type="aff">2</xref>
          <xref rid="aff03" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8211-7135</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Giguère</surname>
            <given-names>Anick</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff04" ref-type="aff">4</xref>
          <xref rid="aff05" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9928-7395</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Poulin</surname>
            <given-names>Valérie</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff06" ref-type="aff">6</xref>
          <xref rid="aff07" ref-type="aff">7</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-7376-5256</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Dubé</surname>
            <given-names>Véronique</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff08" ref-type="aff">8</xref>
          <xref rid="aff09" ref-type="aff">9</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0602-0390</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Giroux</surname>
            <given-names>Dominique</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff04" ref-type="aff">4</xref>
          <xref rid="aff10" ref-type="aff">10</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3264-5319</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff01">
        <label>1</label>
        <institution>Department of Teaching and Learning Studies</institution>
        <institution>Université Laval</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff02">
        <label>2</label>
        <institution>School of Rehabilitation</institution>
        <institution>Université de Sherbrooke</institution>
        <addr-line>Sherbrooke, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff03">
        <label>3</label>
        <institution>Center of Research on Aging</institution>
        <institution>Centre intégré universitaire de santé et de services sociaux de l’Estrie</institution>
        <institution>Centre hospitalier universitaire de Sherbrooke</institution>
        <addr-line>Sherbrooke, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff04">
        <label>4</label>
        <institution>Center of Excellence on Aging Quebec</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff05">
        <label>5</label>
        <institution>Department of Family Medicine and Emergency Medicine</institution>
        <institution>Université Laval</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff06">
        <label>6</label>
        <institution>Université du Québec in Trois-Rivières</institution>
        <addr-line>Trois-Rivières, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff07">
        <label>7</label>
        <institution>Interdisciplinary Center for Research in Rehabilitation and Social Integration</institution>
        <institution>Université Laval</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff08">
        <label>8</label>
        <institution>Research Centre of the University Hospital of Montreal</institution>
        <addr-line>Montreal, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff09">
        <label>9</label>
        <institution>School of Social Work and Criminology</institution>
        <institution>Université Laval</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <aff id="aff10">
        <label>10</label>
        <institution>Department of Rehabilitation</institution>
        <institution>Université Laval</institution>
        <addr-line>Québec, QC</addr-line>
        <country>Canada</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Melanie Tremblay <email>melanie.tremblay.50@ulaval.ca</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Jul-Sep</season>
        <year>2021</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>18</day>
        <month>8</month>
        <year>2021</year>
      </pub-date>
      <volume>8</volume>
      <issue>3</issue>
      <elocation-id>e26532</elocation-id>
      <history>
        <date date-type="received">
          <day>16</day>
          <month>12</month>
          <year>2020</year>
        </date>
        <date date-type="rev-request">
          <day>17</day>
          <month>1</month>
          <year>2021</year>
        </date>
        <date date-type="rev-recd">
          <day>6</day>
          <month>3</month>
          <year>2021</year>
        </date>
        <date date-type="accepted">
          <day>28</day>
          <month>3</month>
          <year>2021</year>
        </date>
      </history>
      <copyright-statement>©Melanie Tremblay, Karine Latulippe, Manon Guay, Véronique Provencher, Anick Giguère, Valérie Poulin, Véronique Dubé, Dominique Giroux. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 18.08.2021.</copyright-statement>
      <copyright-year>2021</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Human Factors, is properly cited. The complete bibliographic information, a link to the original publication on https://humanfactors.jmir.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://humanfactors.jmir.org/2021/3/e26532" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Co-design (or the participation of users) has shown great potential in the eHealth domain, demonstrating positive results. Nevertheless, the co-design approach cannot guarantee the usability of the system designed, and usability assessment is a complex analysis to perform, as evaluation criteria will differ depending on the usability framework (or set of criteria) used. ISO (International Organization for Standardization) on usability (ISO 9241-210), Nielsen heuristic, and Garrett element of user experience inform different yet complementary aspects of usability.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to assess the usability and user experience of a co-design prototype by combining 3 complementary frameworks.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>To help caregivers provide care for functionally impaired older people, an eHealth tool was co-designed with caregivers, health and social service professionals, and community workers assisting caregivers. The prototype was a website that aims to support the help-seeking process for caregivers (finding resources) and allow service providers to advertise their services (offering resources). We chose an exploratory study method to assess usability in terms of each objective. The first step was to assess users’ first impressions of the website. The second was a task scenario with a think-aloud protocol. The final step was a semistructured interview. All steps were performed individually (with a moderator) in a single session. The data were analyzed using 3 frameworks.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A total of 10 participants were recruited, 5 for each objective of the website. We were able to identify several usability problems, most of which were located in the <italic>information design</italic> and <italic>interface design</italic> dimensions (Garrett framework). Problems in both dimensions were mainly coded as <italic>effectiveness</italic> and <italic>efficiency</italic> (ISO framework) and <italic>error prevention</italic> and <italic>match between the system</italic> <italic>and the real world</italic> (Nielsen heuristic).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Our study provided a novel contribution about usability analysis by combining the 3 different models to classify the problems found. This combination provided a holistic understanding of the usability improvements needed. It can also be used to analyze other eHealth products.</p>
        </sec>
        <sec sec-type="registered-report">
          <title>International Registered Report Identifier (IRRID)</title>
          <p>RR2-10.2196/11634</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>usability evaluation</kwd>
        <kwd>co-design</kwd>
        <kwd>research methods</kwd>
        <kwd>caregivers</kwd>
        <kwd>service providers</kwd>
        <kwd>product objectives</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>eHealth is becoming increasingly important to support people in taking care of their own health and that of their loved ones. In 2019, more than 90% of Canadians had access to the internet and 50% reported having access to at least one web-based health service [<xref ref-type="bibr" rid="ref1">1</xref>]. The COVID-19 pandemic has amplified its use. eHealth is notably one of the solutions that can support caregivers in the daily tasks required to care for an older person at home [<xref ref-type="bibr" rid="ref2">2</xref>]. Guay et al [<xref ref-type="bibr" rid="ref3">3</xref>] suggest that internet-based interventions can have positive effects on the psychological well-being of caregivers of older persons<italic>.</italic> Irani et al [<xref ref-type="bibr" rid="ref4">4</xref>] reported that people with chronic diseases and their caregivers were satisfied with the use of the technology. However, some faced technical challenges, whereas others were concerned about the technology’s lack of a personalized approach. Moreover, caregivers of functionally dependent older persons are often older themselves. In 2012, in Québec (Canada), 41% of caregivers were aged over 55 years [<xref ref-type="bibr" rid="ref5">5</xref>]. A digital divide related to age and education [<xref ref-type="bibr" rid="ref6">6</xref>], which are both determining factors of internet use [<xref ref-type="bibr" rid="ref7">7</xref>], still remains. Concerns can, therefore, be raised about the acceptability of eHealth solutions within this group of users, as many factors influence older people’s acceptance of technology, such as privacy implications and usability factors [<xref ref-type="bibr" rid="ref8">8</xref>].</p>
        <p>In response to this issue, there is a growing interest in the co-design approach [<xref ref-type="bibr" rid="ref9">9</xref>]. In this approach, researchers, designers, and participants are cocreating with users, who are considered experts of their experience and play a large role in knowledge development, idea generation, and concept development [<xref ref-type="bibr" rid="ref10">10</xref>]. Authors have reported that the participation of different actors in a co-design project allowed a better understanding of each other’s perspective and reality [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. As co-designers, caregivers and older adults can share their concerns and expectations about the technology in a democratic process, which might increase the fit between their needs and the system developed. However, the co-design approach cannot guarantee the usability and user experience (UX) of the designed system.</p>
      </sec>
      <sec>
        <title>Usability and UX Evaluation</title>
        <sec>
          <title>Usability Definition</title>
          <p>Usability is the “functional relationships between people and the products and systems they use” [<xref ref-type="bibr" rid="ref12">12</xref>]. It is also defined as the “extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use” [<xref ref-type="bibr" rid="ref13">13</xref>]. Users do not want a difficult or uncomfortable experience in their interaction with the system, but usability requires more than just the users’ desire for it [<xref ref-type="bibr" rid="ref14">14</xref>]. To achieve usability of the system, we need to evaluate it and adjust the design to address the problems found. Usability assessment is a complex analysis to perform, as evaluation criteria will differ depending on the usability framework (or set of criteria) used.</p>
        </sec>
        <sec>
          <title>The International Organization for Standardization Framework</title>
          <p>The ISO (International Organization for Standardization) usability framework (ISO 9241-210) is a framework accepted worldwide [<xref ref-type="bibr" rid="ref13">13</xref>] to assess usability in general. The criteria of this framework are all part of the ISO’s definition of usability: <italic>effectiveness</italic>, <italic>efficiency</italic>, <italic>satisfaction,</italic> and <italic>context of use</italic>. The <italic>specified users,</italic> <italic>specified goals</italic>, and <italic>context of use</italic> are a combination of the situated aspects of the interaction with the system: who are the users, what do they want to achieve with the system, and in which context (at home or at work, on their phone or on their computer, etc)? All these factors need to be considered when assessing the usability of a system. <italic>Effectiveness</italic> is the <italic>accuracy and completeness with which users achieve specified goals</italic>. Are users able to achieve the task? <italic>Efficiency</italic> refers to the <italic>resources used in relation to the results achieved</italic>. How long and how easy was it to accomplish the task? <italic>Satisfaction</italic> is defined as the “extent to which the user’s physical, cognitive and emotional responses that result from the use of a system, product or service meet the user’s needs and expectations” [<xref ref-type="bibr" rid="ref13">13</xref>]. Did users appreciate their interaction with the system while performing the task?</p>
          <p>This framework allows a general picture of usability but cannot provide specific insights into what is needed to achieve better results. How can we fix a problem related to effectiveness? The Nielsen heuristic framework (1995) provides more details on what the system should do to meet the ISO criteria.</p>
        </sec>
        <sec>
          <title>The Nielsen 10 Usability Heuristics Framework</title>
          <p>Heuristics describe an approach to problem solving whereby people will rely on a limited number of principles to reduce the complexity of a task by <italic>predicting values to simpler judgmental operations</italic> [<xref ref-type="bibr" rid="ref15">15</xref>]. Heuristics are helpful in predicting the reaction of users interacting with a system. The Nielsen framework (1995) listed 10 heuristics to consider while assessing or trying to achieve usability:</p>
          <list list-type="order">
            <list-item>
              <p><italic>Visibility of system status:</italic> “The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time.”</p>
            </list-item>
            <list-item>
              <p><italic>Match between the system and the real world:</italic> “The design should speak the user’s language. Use words, phrases, and concepts familiar to the user, rather than internal jargon. Follow real-world conventions, making information appear in a natural and logical order.”</p>
            </list-item>
            <list-item>
              <p><italic>User control and freedom:</italic> “Users often perform actions by mistake. They need a clearly marked ‘emergency exit’ to leave the unwanted action without having to go through an extended process.”</p>
            </list-item>
            <list-item>
              <p><italic>Consistency and standards:</italic> “Users should not have to wonder whether different words, situations, or actions mean the same thing. [Words, situations, and actions should] follow platform and industry conventions.”</p>
            </list-item>
            <list-item>
              <p><italic>Error prevention:</italic> “Good error messages are important, but the best designs carefully prevent problems from occurring in the first place. Either eliminate error-prone conditions or check for them, and present users with a confirmation option before they commit to the action.”</p>
            </list-item>
            <list-item>
              <p><italic>Recognition rather than recall:</italic> “Minimize the user’s memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.”</p>
            </list-item>
            <list-item>
              <p><italic>Flexibility and efficiency of use:</italic> “Shortcuts, hidden from novice users, may speed up the interaction for the expert user, such that the design can cater to both inexperienced and experienced users. [The system should] allow users to tailor frequent actions.”</p>
            </list-item>
            <list-item>
              <p><italic>Esthetic and minimalist design:</italic> “Interfaces should not contain information which is irrelevant or rarely needed. Every extra unit of information in an interface competes with the relevant units of information and diminishes their relative visibility.”</p>
            </list-item>
            <list-item>
              <p><italic>Help users recognize, diagnose, and recover from errors:</italic> “Error messages should be expressed in plain language (no error codes), precisely indicate the problem, and constructively suggest a solution.”</p>
            </list-item>
            <list-item>
              <p><italic>Help and documentation:</italic> “It’s best if the system doesn’t need any additional explanation. However, it may be necessary to provide documentation to help users understand how to complete their tasks [<xref ref-type="bibr" rid="ref16">16</xref>].”</p>
            </list-item>
          </list>
          <p>Refer to the NNGroup website [<xref ref-type="bibr" rid="ref16">16</xref>] for a detailed description, with examples of each heuristic. These heuristics are guidelines for achieving <italic>effectiveness, efficiency,</italic> and <italic>satisfaction</italic>. They focus on the task goals. However, users’ goals are not always task oriented (do-goals) [<xref ref-type="bibr" rid="ref17">17</xref>]. Other goals, such as be-goals, will affect their experience with technology [<xref ref-type="bibr" rid="ref18">18</xref>]. Users are not just users. They are also human beings with feelings. The UX shifts the focus from the product to feelings while users interact with the technology [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        </sec>
        <sec>
          <title>Garrett Framework: The Elements of UX</title>
          <p>The elements of UX framework [<xref ref-type="bibr" rid="ref20">20</xref>] proposes 5 dimensions to describe UX design: strategy, scope, structure, skeleton, and surface. Each dimension has distinctive elements (<xref ref-type="boxed-text" rid="box1">Textbox 1</xref>).</p>
          <p>Each framework provides a different understanding of how a product can get closer to what users really want. These frameworks inform different yet complementary aspects of usability and UX.</p>
          <boxed-text id="box1" position="float">
            <title>The elements of user experience and their description.</title>
            <p>
              <bold>Dimension, Elements, and Description</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Strategy</p>
                <list>
                  <list-item>
                    <p>Product objectives: what are the business goals or other specific goals the product is aiming for?</p>
                  </list-item>
                  <list-item>
                    <p>User needs: who are the target users and what do they want?</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Scope</p>
                <list>
                  <list-item>
                    <p>Functional specifications: what functionalities are required to address user needs and product objectives?</p>
                  </list-item>
                  <list-item>
                    <p>Content requirements: what content is required to address user needs and product objectives?</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Structure</p>
                <list>
                  <list-item>
                    <p>Interaction design: how does the system behave in response to the users’ actions?</p>
                  </list-item>
                  <list-item>
                    <p>Information architecture: what is the structural arrangement and distribution of information throughout the system?</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Skeleton</p>
                <list>
                  <list-item>
                    <p>Information design: how is the information presented to facilitate understanding?</p>
                  </list-item>
                  <list-item>
                    <p>Interface design: how are the interface elements organized on the page to enable users to interact with the system?</p>
                  </list-item>
                  <list-item>
                    <p>Navigation design: what elements allow the user to access the different sections of the information architecture?</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Surface</p>
                <list>
                  <list-item>
                    <p>Sensory design: what sensory (vision, touch, etc) experience is created by the product?</p>
                  </list-item>
                </list>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
      <sec>
        <title>Objective</title>
        <p>The objective of this study is to assess the usability and UX of an early version co-designed prototype to support the help-seeking process of caregivers of functionally dependent older persons. Trying to gather as much information as possible on potential improvements, we want to explore the contribution of the 3 frameworks presented: the ISO [<xref ref-type="bibr" rid="ref13">13</xref>], Nielsen usability heuristics [<xref ref-type="bibr" rid="ref16">16</xref>], and Garrett elements of UX [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Context of the Study</title>
        <p>On the basis of the potential value of the co-design approach in the eHealth domain, we first co-designed an eHealth prototype to support the help-seeking process of caregivers of functionally dependent older persons (<xref rid="figure1" ref-type="fig">Figure 1</xref>). The co-design phase of the study (phase 2) included 8 co-design sessions and 3 advisory committee meetings held in 11 of the 16 administrative regions of the province of Québec from May 2017 to June 2018.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Context of the study. Ac: advisory committee session; CoD: co-design session.</p>
          </caption>
          <graphic xlink:href="humanfactors_v8i3e26532_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The research project protocol of the entire study can be found in the paper by Latulippe et al [<xref ref-type="bibr" rid="ref21">21</xref>], and results on user needs, requirements, and overall process and design decisions are presented in 3 papers [<xref ref-type="bibr" rid="ref22">22</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]. A total of 74 co-designers were recruited, including 30 caregivers, 26 community workers, and 18 health professionals. Advisory committee meetings were held in plenary and co-design sessions were held in both plenary and subgroup workshops and included different types of activities depending on the objectives of the session.</p>
        <p>The eHealth prototype developed was a website with 2 main objectives: helping caregivers to find resources (with a search tool and a questionnaire to help identify the needs) and allowing service providers to offer their services. The prototype is currently hosted on a private server.</p>
      </sec>
      <sec>
        <title>Explorative Usability and UX Assessment</title>
        <p>We chose an exploratory study method to assess usability, as the prototype was in its first version [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. Changes were made to phase 3 of the initial protocol to gather more appropriate knowledge about usability and UX, considering the state of the prototype [<xref ref-type="bibr" rid="ref21">21</xref>]. These changes include the addition of users’ first impressions, the accuracy of the methods used to perform the think-aloud method, and the use of a semistructured interview rather than a standardized questionnaire.</p>
      </sec>
      <sec>
        <title>Recruitment</title>
        <p>Participant recruitment included recruiting for the 2 objectives of the website (offering and finding resources for caregivers). Two researchers (KL and MC) completed the recruitment and data collection. All participants were recruited from a single region of Québec for feasibility reasons. The first inclusion criterion was potential users of the website. We contacted service providers via telephone and email. Service providers helped to recruit caregivers within their organization. One inclusion criterion for service providers was to provide services to caregivers of functionally dependent older persons. One inclusion criterion for caregivers was to provide assistance on a regular basis (at least once a week) to a person aged 65 years or older. Participating in phase 2 (co-design of the tool) was not an inclusion criterion for recruitment in the usability study (phase 3), but it was also not an exclusion criterion. As the objective of this study was exploratory and we were testing with an early version of the prototype, we targeted 10 users, including service providers and caregivers. We wanted an equal representation of participants for each objective of the website. Faulkner [<xref ref-type="bibr" rid="ref27">27</xref>] revealed that the average percentage of problem areas found in 100 trials of 5 users found 85% (38/45), ranging from 55% (25/45) to nearly 100% (45/45), whereas groups of 10 found 95% (43/45) of the problems.</p>
      </sec>
      <sec>
        <title>Data Collection</title>
        <sec>
          <title>Global Process</title>
          <p>As the prototype was in the early stages of development, the database did not contain any resources except the <italic>test</italic> resource entered by researchers during the programming of the prototype. Thus, we completed data collection in 2 parts through individual user testing, including 3 steps each (<xref rid="figure2" ref-type="fig">Figure 2</xref>). For the first part, we evaluated usability and UX for the <italic>offering resources</italic> objective. Participants contributed to adding some resources in the database in which caregivers would eventually search. For the second part, we evaluated usability and UX for the <italic>finding resources</italic> objective with caregivers. We collected data in French, the main language used in Québec.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Study methodology.</p>
            </caption>
            <graphic xlink:href="humanfactors_v8i3e26532_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
          <p>We completed the 3 steps of each part in a single session of 30-45 minutes with each participant. All sessions were videotaped. We conducted tests at the workplace for service providers and at home (or in a community center) for caregivers. Moderators used either a portable PC with a webcam and the Open Broadcast Studio (The OBS Project) [<xref ref-type="bibr" rid="ref28">28</xref>] or the participant’s own computer, a camera or an iPad, and an audio recorder. Open Broadcast Studio is a free open-source software that allows the recording of multiple sources of data simultaneously. The webcam captures the participants’ reaction. The integrated audio captor records participants’ verbalization, and the desktop or browser windows are captured as another source.</p>
        </sec>
        <sec>
          <title>Step 1: Users’ First Impressions</title>
          <p>We used the 5-second test (5ST) to gather the first impression of users. This involved a display of the home page for 5 seconds, followed by questions [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. The 5ST technique was used to gather information about general eye-catching attributes of the home page and provided general first impressions. After the 5 second display, we asked participant, “Can you tell me what you remember seeing?” To collect more detailed information about the perception of the utility for each user subgroup, we added a second display of the home page without a time limit. Participants were then asked to express their perceived usefulness, “As a [caregiver or service provider], what do you think you could do with this website?”</p>
        </sec>
        <sec>
          <title>Step 2: Task Scenarios</title>
          <p>The second step included task scenarios [<xref ref-type="bibr" rid="ref25">25</xref>] with a coaching think-aloud protocol [<xref ref-type="bibr" rid="ref31">31</xref>]. The task scenarios represented several tasks that the user would typically perform with this website and put them in context [<xref ref-type="bibr" rid="ref25">25</xref>]. Scenarios differed depending on the targeted subgroup. Each scenario included a practice task to familiarize participants with the think-aloud protocol, followed by 5 assessed tasks. We selected the tasks based on what each subgroup of users would typically want to do with the website and on specific interactions that the research team wanted to assess (<xref ref-type="boxed-text" rid="box2">Textbox 2</xref>). In accordance with the <italic>coaching think-aloud</italic> protocol, moderators worked with participants during task performance. When the participant stopped talking during the task, the moderator repeated the instruction, <italic>keep thinking aloud, please</italic>. When a participant struggled with a task, the moderator provided some guidance.</p>
          <boxed-text id="box2" position="float">
            <title>Task scenarios and related questions.</title>
            <p>
              <bold>Part 1: Offering Resources</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Find resources</p>
                <list>
                  <list-item>
                    <p>“You want to find resources for a caregiver you interact with. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Create a profile</p>
                <list>
                  <list-item>
                    <p>“You want to create a profile for your organization. How would you proceed? Please create a complete profile.”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Add an activity</p>
                <list>
                  <list-item>
                    <p>“You want to add an activity offered by your organization. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Add a document</p>
                <list>
                  <list-item>
                    <p>“You want to add an information document presenting details of your organization’s services. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
            </list>
            <p>
              <bold>Part 2: Finding Resources</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Identifying their own needs</p>
                <list>
                  <list-item>
                    <p>“You are tired and you need help but you do not know exactly what you are looking for. What would you do?”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Finding a resource in their region</p>
                <list>
                  <list-item>
                    <p>“You want to find a support group in your region. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Adding a search result to their favorites</p>
                <list>
                  <list-item>
                    <p>“You want to keep the name of an organization to go back to it more quickly. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Finding a document</p>
                <list>
                  <list-item>
                    <p>“You want a document suggesting strategies for bathing assistance. How would you proceed?”</p>
                  </list-item>
                </list>
              </list-item>
            </list>
          </boxed-text>
        </sec>
        <sec>
          <title>Step 3: Semistructured Interview</title>
          <p>We created an interview guide based on validated usability questionnaires [<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref35">35</xref>]. We created our own interview guide because validated questionnaires have limited applicability and are not suited to all systems [<xref ref-type="bibr" rid="ref36">36</xref>]. We also wanted to address the specific objectives of the usability evaluation and UX of our prototype, such as problems faced during task performance [<xref ref-type="bibr" rid="ref25">25</xref>]. We included 8 questions, with probing questions adapted to our designed prototype in the interview guide to answer more specifically to our study objectives (<xref ref-type="boxed-text" rid="box3">Textbox 3</xref>).</p>
          <boxed-text id="box3" position="float">
            <title>Questions for the semistructured interview.</title>
            <p>
              <bold>Questions</bold>
            </p>
            <list list-type="order">
              <list-item>
                <p>“When you were [task], I noticed [negative attitude, discomfort, difficulties, time to perform tasks]. Can you tell me why you had [negative attitude, discomfort, difficulties, time to perform tasks]?”</p>
              </list-item>
              <list-item>
                <p>“Is the website easy to use?”</p>
                <p><italic>Probing question:</italic> “What seems complicated to you?”</p>
              </list-item>
              <list-item>
                <p>“Is the organization of the website logical and optimal?”</p>
                <p><italic>Probing question:</italic> “What is inconsistent in the website’s organization?”</p>
              </list-item>
              <list-item>
                <p>“Did you find information easily?”</p>
                <p><italic>Probing question:</italic> “Which information did you not find easily?”</p>
              </list-item>
              <list-item>
                <p>“When navigating on the website, is it easy to know where you are?”</p>
                <p><italic>Probing question:</italic> “When were you not able to know where you were?”</p>
              </list-item>
              <list-item>
                <p>“Generally speaking, are you satisfied with this website?”</p>
              </list-item>
              <list-item>
                <p>“Do you feel comfortable using this website?”</p>
              </list-item>
              <list-item>
                <p>“Would you like to use this website for your tasks?”</p>
              </list-item>
            </list>
          </boxed-text>
          <p>To collect sociodemographic data, participants were asked questions about their age, profession, education level, and profession. We also asked 3 multiple-choice questions to assess participants’ perceptions of their technology profiles (<xref ref-type="boxed-text" rid="box4">Textbox 4</xref>).</p>
          <boxed-text id="box4" position="float">
            <title>Sociodemographic data collection.</title>
            <p>
              <bold>Multiple-Choice Questions and Their Answer Choices</bold>
            </p>
            <list list-type="bullet">
              <list-item>
                <p>Frequency of internet use</p>
                <list>
                  <list-item>
                    <p>Several times a day</p>
                  </list-item>
                  <list-item>
                    <p>Several times a week</p>
                  </list-item>
                  <list-item>
                    <p>About once a week</p>
                  </list-item>
                  <list-item>
                    <p>About once a month</p>
                  </list-item>
                  <list-item>
                    <p>Never</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Ability to find information on the internet</p>
                <list>
                  <list-item>
                    <p>Always</p>
                  </list-item>
                  <list-item>
                    <p>Most of the time</p>
                  </list-item>
                  <list-item>
                    <p>Occasionally</p>
                  </list-item>
                  <list-item>
                    <p>Rarely</p>
                  </list-item>
                </list>
              </list-item>
              <list-item>
                <p>Comfort level with technology in general</p>
                <list>
                  <list-item>
                    <p>Rate from 1 to 10 (1 being very uncomfortable and 10 being very comfortable)</p>
                  </list-item>
                </list>
              </list-item>
            </list>
          </boxed-text>
        </sec>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>One researcher (corresponding author) performed the data analysis. We conducted qualitative data analysis in Microsoft Excel using the video recordings of each session. For the first (user impression) and third (semistructured interviews) steps, we conducted an inductive thematic analysis [<xref ref-type="bibr" rid="ref37">37</xref>]. All participant verbalizations (answers) were transcribed, and some answers were translated by the author for publication purposes. We numbered each answer and collected a list of 5 data items for each (<xref ref-type="boxed-text" rid="box5">Textbox 5</xref>). We used the filter functionality to group and analyze the data.</p>
        <p>For the second step (task scenarios), we conducted a deductive analysis [<xref ref-type="bibr" rid="ref37">37</xref>] based on each criterion of the 3 frameworks [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. We entered participant observations and verbalizations for each task. We numbered each problem found during the tasks and registered details for 12 items, each being a column in the Microsoft Excel spreadsheet. <xref ref-type="boxed-text" rid="box5">Textbox 5</xref> presents a list of the items collected for each step.</p>
        <p>For step 2, we first coded each problem according to one criterion of each framework. We then combined the coding for all frameworks using the pivot table functionality. We selected the Garrett [<xref ref-type="bibr" rid="ref20">20</xref>] criteria to organize the identified heuristic [<xref ref-type="bibr" rid="ref16">16</xref>] of each problem in the rows field and crossed them with ISO categories [<xref ref-type="bibr" rid="ref13">13</xref>] in the columns field in the Microsoft Excel spreadsheet.</p>
        <p>The study received ethical approval from the <italic>Comité d’éthique de la recherche sectoriel santé des populations et première ligne</italic> (2016-2017-10 MP). Informed consent was obtained from each participant, who also received a nominal compensation of Can $20 (US $16.45).</p>
        <boxed-text id="box5" position="float">
          <title>List of data items collected.</title>
          <p>
            <bold>Items Collected at Each Step</bold>
          </p>
          <list list-type="bullet">
            <list-item>
              <p>Step 1 (first impression) and step 3 (semistructured interview)</p>
              <list>
                <list-item>
                  <p>Data input number</p>
                </list-item>
                <list-item>
                  <p>Participant ID</p>
                </list-item>
                <list-item>
                  <p>Participant category (service provider or caregiver)</p>
                </list-item>
                <list-item>
                  <p>Source of data (question)</p>
                </list-item>
                <list-item>
                  <p>Data (transcript)</p>
                </list-item>
              </list>
            </list-item>
            <list-item>
              <p>Step 2 (task scenarios)</p>
              <list>
                <list-item>
                  <p>Data input number</p>
                </list-item>
                <list-item>
                  <p>Participant ID</p>
                </list-item>
                <list-item>
                  <p>Participant category (service provider or caregiver)</p>
                </list-item>
                <list-item>
                  <p>Source of data (observation, verbalization, or both)</p>
                </list-item>
                <list-item>
                  <p>Data (transcript or description of observation)</p>
                </list-item>
                <list-item>
                  <p>Problem identified</p>
                </list-item>
                <list-item>
                  <p>Task</p>
                </list-item>
                <list-item>
                  <p>Source of error</p>
                </list-item>
                <list-item>
                  <p>Potential solution</p>
                </list-item>
                <list-item>
                  <p>International Organization for Standardization category</p>
                </list-item>
                <list-item>
                  <p>Heuristic category</p>
                </list-item>
                <list-item>
                  <p>Garrett category</p>
                </list-item>
              </list>
            </list-item>
          </list>
        </boxed-text>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Participants’ Demographics</title>
        <p>We recruited a total of 10 participants: 4 caregivers and 6 service providers. We conducted 5 user tests for each phase (part 1: offering resources and part 2: finding resources; <xref ref-type="table" rid="table1">Table 1</xref>). One service provider participated as if she were a caregiver (phase 2). She represented what could happen in a real-context setting: a service provider helping a caregiver.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Participants’ sociodemographic data (N=10).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="470"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td colspan="2">Sociodemographic items</td>
                <td>Offering resources (n=5)</td>
                <td>Finding resources (n=5)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="4">
                  <bold>Gender, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Women</td>
                <td>3 (60)</td>
                <td>4 (80)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Men</td>
                <td>2 (40)</td>
                <td>1 (20)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Age (years), mean (SD; range)</td>
                <td>53.4 (13.4; 42-75)</td>
                <td>71.2 (7.8; 58-78)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Education level, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>College</td>
                <td>2 (40)</td>
                <td>N/A<sup>a</sup></td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Bachelor’s degree</td>
                <td>1 (20)</td>
                <td>4 (80)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Master’s degree</td>
                <td>1 (20)</td>
                <td>N/A</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Doctorate</td>
                <td>1 (20)</td>
                <td>1 (20)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Frequency of internet use, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Several times a day</td>
                <td>1 (20)</td>
                <td>1 (20)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Several times a week</td>
                <td>3 (60)</td>
                <td>4 (80)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>About once a week</td>
                <td>1 (20)</td>
                <td>0 (0)</td>
              </tr>
              <tr valign="top">
                <td colspan="4">
                  <bold>Capacity to find information on the internet, n (%)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Always</td>
                <td>1 (20)</td>
                <td>2 (40)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Most of the time</td>
                <td>4 (80)</td>
                <td>3 (60)</td>
              </tr>
              <tr valign="top">
                <td colspan="2">Comfort level with technology in general from 1 to 10, mean (SD; range)</td>
                <td>7.9 (1.02; 6-9)</td>
                <td>7 (0.70; 6-8)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>N/A: not applicable.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Step 1: Users’ First Impressions</title>
        <p><xref ref-type="table" rid="table2">Table 2</xref> presents the results (emerging categories) for the 5ST of the home page. Elements most commonly identified by participants were located in the top-right section of the page (n=10).</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Participants’ first impressions of the home page (5-second test; n=10).</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="440"/>
            <col width="0"/>
            <col width="250"/>
            <col width="0"/>
            <col width="280"/>
            <thead>
              <tr valign="top">
                <td colspan="3">Interface section</td>
                <td colspan="2">Caregivers mentions (n=5), n (%)</td>
                <td>Service providers mentions (n=5), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="6">
                  <bold>Header (9 mentions)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The phone number of the helpline for caregivers</td>
                <td colspan="2">1 (20)</td>
                <td colspan="2">3 (60)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The name of the website</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (20)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The log-in (to access the user profile)</td>
                <td colspan="2">1 (20)</td>
                <td colspan="2">2 (40)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Caregivers support (logo)</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (20)</td>
              </tr>
              <tr valign="top">
                <td colspan="6">
                  <bold>Top left (7 mentions)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>A search tool</td>
                <td colspan="2">2 (40)</td>
                <td colspan="2">2 (40)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Finding resources</td>
                <td colspan="2">2 (40)</td>
                <td colspan="2">1 (20)</td>
              </tr>
              <tr valign="top">
                <td colspan="6">
                  <bold>Top right (10 mentions)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The definition of a caregiver</td>
                <td colspan="2">3 (60)</td>
                <td colspan="2">0 (0)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>The question, “are you a caregiver for an elderly person?”</td>
                <td colspan="2">2 (40)</td>
                <td colspan="2">2 (40)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Examples of what is a caregiver</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">2 (40)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Caregiver of an older person</td>
                <td colspan="2">0 (0)</td>
                <td colspan="2">1 (20)</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>The top left section, where the search tool is located, was among the elements that were perceived less frequently. It was perceived by 7 participants, with only 4 participants mentioning the search tool, which corresponds to the <italic>finding resources objective</italic>. <xref rid="figure3" ref-type="fig">Figure 3</xref> shows the home page displayed to the participants.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Home page display.</p>
          </caption>
          <graphic xlink:href="humanfactors_v8i3e26532_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>After the 5ST, for the second home page display (without a time limit), all service providers answered that they thought the website was for <italic>finding resources to refer or help caregivers</italic>. One service provider also mentioned the requirement of registering its organization. All caregivers answered that they could search or find resources or service providers; 2 of them insisted on the fact that they could find respite resources.</p>
      </sec>
      <sec>
        <title>Step 2: Task Scenarios</title>
        <sec>
          <title>Summary</title>
          <p>We identified 151 problems with the task scenarios, which were classified according to the categories of the 3 frameworks. Some participants were not able to perform all the tasks because of programming errors. When problems were programming errors, they were classified as N/A (not applicable) in each category. This was also done if the focus on the task seemed to interfere with the participant’s perception, for example, if the participant did not see an item they were asked about (the phone number of the helpline for caregivers) because the focus was not on that item but on the task (finding a resource in their region). In those cases, we did not classify the problems, as the task could have affected the interpretation of a category. Most problems (49/151, 32.5%) occurred during the creation of a profile for service providers. The other tasks with a considerable number of problems for service providers were <italic>finding resources</italic> (18/151, 11.9%) and <italic>adding an activity</italic> (10/151, 6.6%). For caregivers, 11.3% (17/151) of problems occurred during the task <italic>finding a resource in their region</italic> and 8.6% (13/151) of problems during the task <italic>identifying their own needs</italic>. The following sections provide a description of these problems.</p>
        </sec>
        <sec>
          <title>ISO Classification</title>
          <p><xref ref-type="table" rid="table3">Table 3</xref> presents findings related to the ISO usability framework. The table presents the number of problems in each category, an example for each with data input number, participant ID, and the transcript or description of the observation. Service providers are identified as SP# and caregivers as C#. It also presents the task where the problems occurred and the type of problem.</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Problems with the website, classified according to the International Organization for Standardization framework.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="190"/>
              <col width="130"/>
              <col width="170"/>
              <col width="280"/>
              <col width="200"/>
              <thead>
                <tr>
                  <td colspan="2">Usability criteria (ISO<sup>a</sup> 9241-210)</td>
                  <td>Problems, n (%)</td>
                  <td>Task (example)</td>
                  <td>Verbalization or observation (example)</td>
                  <td>Problem detected (example)</td>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td colspan="3">
                    <bold>Effectiveness</bold>
                  </td>
                  <td>Finding a resource in their region</td>
                  <td>“So, I will go to Find resources, I will search for the region first” [#23, C1]</td>
                  <td>The participant writes nothing in the search bar before clicking on the search button</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>68 (45)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP<sup>b</sup> (n=68)</td>
                  <td>50 (73.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=68)</td>
                  <td>18 (26.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Efficiency</bold>
                  </td>
                  <td>Creating a profile</td>
                  <td>“It is really annoying to have to scroll. I don’t know if I can just write it, how does it work? it is not simple.” [#6, SP1]</td>
                  <td>Too much scrolling to choose the city</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>49 (32.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=49)</td>
                  <td>31 (63.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=49)</td>
                  <td>18 (36.7)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Satisfaction</bold>
                  </td>
                  <td>Finding a resource in their region</td>
                  <td>Participant is using the advanced research functionality; “No, it isn’t the right solution, there are no options!” [#83, C2]</td>
                  <td>The participant is looking for the word <italic>activity</italic> in the advanced research</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>18 (11.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=18)</td>
                  <td>9 (50)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=18)</td>
                  <td>9 (50)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Context of use</bold>
                  </td>
                  <td>Creating a profile</td>
                  <td>Participant is clicking on the log-in (the one for the caregiver) and then clicks on creating a profile. The participant receives an error message. [#88, SP4]</td>
                  <td>The participant did not see the access dedicated to service providers</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>4 (2.6)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=4)</td>
                  <td>4 (100)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">N/A<sup>c</sup> (n=151)</td>
                  <td>12 (7.9)</td>
                  <td>Question asked after finding a resource in their region</td>
                  <td>“Did you see the phone number for the help line?” [#21, C1, interviewer]; “I was focusing on the resource, I would have seen it after.” [participant]</td>
                  <td>The participant did not see the phone number (focus on the task)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>ISO: International Organization for Standardization.</p>
              </fn>
              <fn id="table3fn2">
                <p><sup>b</sup>SP: service provider.</p>
              </fn>
              <fn id="table3fn3">
                <p><sup>c</sup>N/A: not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <p>Almost half of the problems (68/151, 45%) were classified as <italic>effectiveness</italic> and occurred mainly for service providers during part 1 (50/68, 74%). A total of 32.5% (49/151) were classified as <italic>efficiency</italic>, again mostly by service providers (31/49, 63%). A few problems (18/151, 11.9%) were related to <italic>satisfaction</italic>. Four problems were classified as <italic>context of use</italic>. These problems were identified by a single participant, and most of them (3/4, 75%) could be explained by the fact that this participant was visually impaired. The problems coded as <italic>context of use</italic> included the following: (1) the participant tried to connect or create a profile using the caregiver access instead of the service provider access, (2) insufficient color contrast, (3) and the size of user interface elements.</p>
        </sec>
        <sec>
          <title>Nielsen Heuristic Classification</title>
          <p>Regarding the classification using Nielsen heuristics, <italic>match between the system and the real world</italic> was the most important heuristic principle identified, representing 19.9% (30/151) of problems (<xref ref-type="table" rid="table4">Table 4</xref>). This heuristic was mostly identified for problems arising for service providers (21/30, 70%) when performing the c<italic>reate a profile</italic> task (12/30, 40%). Other frequently mentioned usability principles included <italic>help and documentation</italic> (25/151, 16.6%), <italic>user control and freedom</italic> (22/151, 14.6%), <italic>error prevention</italic> (21/151, 13.9%), and <italic>recognition rather than recall</italic> (18/151, 11.9%), all of which were again mostly for service providers during the <italic>create a profile</italic> task.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Classification of problems according to Nielsen heuristics.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="190"/>
              <col width="130"/>
              <col width="170"/>
              <col width="280"/>
              <col width="200"/>
              <thead>
                <tr>
                  <td colspan="2">Heuristic principle</td>
                  <td>Problems, n (%)</td>
                  <td>Task (example)</td>
                  <td>Verbalization or observation (example)</td>
                  <td>Problem detected (example)</td>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td colspan="3">
                    <bold>Match between the system and the real world</bold>
                  </td>
                  <td>Create a profile</td>
                  <td>At the end of the task, the interviewer is pointing on the screen to the access for service providers. The participant says, “It’s locked!” [#108, SP5]</td>
                  <td>The lock icon is perceived as an item locked on the screen</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>30 (19.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP<sup>a</sup> (n=30)</td>
                  <td>21 (70)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=30)</td>
                  <td>9 (30)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Help and documentation</bold>
                  </td>
                  <td>Create a profile</td>
                  <td>“What is my username? What was asked before to connect, my email address?” [#7, SP1]</td>
                  <td>The participant enters their email in the field for the website instead of the email field</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>25 (16.6)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=25)</td>
                  <td>19 (76)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=25)</td>
                  <td>6 (24)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>User control and freedom</bold>
                  </td>
                  <td>Create a profile</td>
                  <td>“I have a video of a caregiver online on my website.” [#16, SP1]</td>
                  <td>There is no option to add a hyperlink to a video, only to upload one</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>22 (14.6)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=22)</td>
                  <td>13 (59.1)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=22)</td>
                  <td>9 (40.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Error prevention</bold>
                  </td>
                  <td>Create a profile</td>
                  <td>The participant clicks on the log-in instead of the create a profile button (#48, SP3)</td>
                  <td>The create a profile button is beneath the connection button</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>21 (13.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=21)</td>
                  <td>14 (66.7)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=21)</td>
                  <td>7 (33.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Recognition rather than recall</bold>
                  </td>
                  <td>Add a research result in their favorites</td>
                  <td>“I could add it in the favourite of my browser...Here I don’t know what to do” [#135, C3]</td>
                  <td>The favorite button is not appearing when the user is not connected</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>18 (11.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=18)</td>
                  <td>11 (61.1)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=18)</td>
                  <td>7 (38.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Visibility of system status</bold>
                  </td>
                  <td>Find a resource in their region</td>
                  <td>She is clicking on the search button and nothing seems to happen (#147, C4)</td>
                  <td>The system is not providing information about the action performed</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>8 (5.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=8)</td>
                  <td>5 (62.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=8)</td>
                  <td>3 (37.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Esthetic and minimalist design</bold>
                  </td>
                  <td>Find resources</td>
                  <td>“And here you have the XYZ Volunteer Center...Three times!” [#25, SP2]</td>
                  <td>The same research result is appearing 3 times</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>6 (3.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=6)</td>
                  <td>3 (50)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=6)</td>
                  <td>3 (50)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Help users recognize, diagnose, and recover from errors</bold>
                  </td>
                  <td>Add a document</td>
                  <td>An error message appears: “I assume it is because I did not upload a document?” [#39, SP2]</td>
                  <td>The upload of a document failed</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>4 (2.6)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=4)</td>
                  <td>3 (75)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Caregiver (n=4)</td>
                  <td>1 (25)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Consistency and standards</bold>
                  </td>
                  <td>Create a profile</td>
                  <td>The participant did not enter the postal code or the region of the city. (#53, SP3)</td>
                  <td>The input fields for the postal code and region are located beside the other input field, on the right side, rather than below them</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>2 (1.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=2)</td>
                  <td>2 (100)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="3">
                    <bold>Flexibility and efficiency of use</bold>
                  </td>
                  <td>Add an activity</td>
                  <td>“If the activity added appears below, it is a bit annoying. We don’t know if it worked or not.” [#36, SP2]</td>
                  <td>The added activity is located under the field for adding an activity</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>2 (1.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td>SP (n=2)</td>
                  <td>2 (100)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">N/A<sup>b</sup> (n=151)</td>
                  <td>13 (8.6)</td>
                  <td>Find a resource in their region</td>
                  <td>The participant clicks on support group, but nothing happens. (#139, C3)</td>
                  <td>Link is not working (programming error)</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table4fn1">
                <p><sup>a</sup>SP: service provider.</p>
              </fn>
              <fn id="table4fn2">
                <p><sup>b</sup>N/A: not applicable.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Garrett Elements of UX Classification</title>
          <p><xref ref-type="table" rid="table5">Table 5</xref> presents the results of the analysis using the Garrett framework. Most of the problems (113/151, 75.8%) were classified in the <italic>skeleton plane</italic>, especially in the <italic>interface design</italic> (54/151, 35.8%) and <italic>information design</italic> (50/151, 33.1%) dimensions. For <italic>interface design</italic>, 65% (35/54) of problems occurred for service providers, mostly to <italic>create a profile</italic> (20/54, 37%). For <italic>information design</italic>, 80% (40/50) of problems occurred for service providers, mostly to <italic>create a profile</italic> (24/50, 48%). Only one problem was categorized in the <italic>user needs</italic> category, and it was also classified for <italic>context of use</italic> in the ISO categorization. This problem reflects an accessibility problem for visually impaired users, meaning that the prototype did not address the specific needs of visually impaired users.</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Classification of problems with Garrett elements of user experience.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="30"/>
              <col width="30"/>
              <col width="160"/>
              <col width="130"/>
              <col width="170"/>
              <col width="280"/>
              <col width="200"/>
              <thead>
                <tr>
                  <td colspan="3">Plane and user experience element</td>
                  <td>Problems, n (%)</td>
                  <td>Task (example)</td>
                  <td>Verbalization or observation (example)</td>
                  <td>Problem detected (example)</td>
                </tr>
              </thead>
              <tbody>
                <tr>
                  <td colspan="7">
                    <bold>Strategy</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Product objectives</td>
                  <td>0 (0)</td>
                  <td>N/A<sup>a</sup></td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>User needs</bold>
                  </td>
                  <td>Finding resources</td>
                  <td>Even if the user is not able to see the entire page at once, she is still able to find the item on the screen, such as the search button. (#86, SP4)</td>
                  <td>The website is not offering options for visually impaired people</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>1 (0.7)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP<sup>b</sup> (n=1)</td>
                  <td>1 (100)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="7">
                    <bold>Scope</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Functional requirements</td>
                  <td>0 (0)</td>
                  <td>N/A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Content requirements</td>
                  <td>0 (0)</td>
                  <td>N/A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr>
                  <td colspan="7">
                    <bold>Structure</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>Interaction design</bold>
                  </td>
                  <td>Finding a resource in their region</td>
                  <td>“I can ask a question, can’t I?” [#82, C2]</td>
                  <td>The participant would like to ask a question instead of using the search engine</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>19 (12.5)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP (n=19)</td>
                  <td>11 (57.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Caregiver (n=19)</td>
                  <td>8 (42.1)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">Information architecture</td>
                  <td>0 (0)</td>
                  <td>N/A</td>
                  <td>N/A</td>
                  <td>N/A</td>
                </tr>
                <tr>
                  <td colspan="7">
                    <bold>Skeleton</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>Information design</bold>
                  </td>
                  <td>Creating a profile</td>
                  <td>“What does 24-h surveillance mean? It’s not clear.” [#112, SP5]</td>
                  <td>The wording is not understood</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>50 (33.1)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP (n=50)</td>
                  <td>40 (80)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Caregiver (n=50)</td>
                  <td>10 (20)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>Interface design</bold>
                  </td>
                  <td>Finding a resource in their region</td>
                  <td>The participant clicks on the description of a support group and nothing happens. (#77, C2)</td>
                  <td>Only the title is clickable</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>54 (35.8)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP (n=54)</td>
                  <td>35 (64.8)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Caregiver (n=54)</td>
                  <td>19 (35.2)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>Navigation design</bold>
                  </td>
                  <td>Finding a resource in their region</td>
                  <td>The participant and the interviewer are retyping the initial website address to return to the home page. (#65, C1)</td>
                  <td>The return to the home page with the logo is not understood</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>9 (6)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP (n=9)</td>
                  <td>3 (33.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Caregiver (n=9)</td>
                  <td>6 (66.7)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="7">
                    <bold>Surface</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="3">
                    <bold>Sensory design</bold>
                  </td>
                  <td>Finding a document</td>
                  <td>“What we are trying to do is to colour code the organization in blue, the activities in pink, and the document in purple. You didn’t notice the colour coding?” [#84, C2, interviewer]; “Not at all! I don’t see the point.” [C2]</td>
                  <td>The participant did not notice the change of color depending on the type of result</td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Total (n=151)</td>
                  <td>6 (3.9)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>SP (n=6)</td>
                  <td>4 (66.7)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="2">
                    <break/>
                  </td>
                  <td>Caregiver (n=6)</td>
                  <td>2 (33.3)</td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                  <td>
                    <break/>
                  </td>
                </tr>
                <tr>
                  <td colspan="7">
                    <bold>N/A</bold>
                  </td>
                </tr>
                <tr>
                  <td>
                    <break/>
                  </td>
                  <td colspan="2">No classification (n=151)</td>
                  <td>12 (7.9)</td>
                  <td>Finding a resource in their region</td>
                  <td>The participant is entering information in the advance research engine without looking at the results first. (#129, C3)</td>
                  <td>Due to a programming error, results are not showing besides the advance research box, but below it</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table5fn1">
                <p><sup>a</sup>N/A: not applicable.</p>
              </fn>
              <fn id="table5fn2">
                <p><sup>b</sup>SP: service provider.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>Combining the Frameworks</title>
          <p>Combining all 3 frameworks of analysis provides a comprehensive picture of the identified problems. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> presents the problems in terms of the dimension of the Garrett framework and the category of ISO usability criteria. The combination also identifies the Nielsen heuristic usability guideline the problem does not address. This table indicates that for <italic>interface design,</italic> problems were mainly identified for <italic>effectiveness</italic> (22/54, 41%) and efficiency (24/54, 44%), with several problems of <italic>error prevention</italic> (ie, when trying to connect to their profile). Problems are also found for <italic>effectiveness</italic> (19/50, 38%) and <italic>efficiency</italic> (25/50, 50%) in <italic>information design,</italic> concerning especially the <italic>match between the system</italic> <italic>and the real world</italic>, mostly for service providers during the creation of their profile and the <italic>help and documentation</italic> (eg, caregiver was looking for the word <italic>Respite</italic> and did not think of entering it in the search engine). The combination of frameworks allows a better understanding of usability problems and provides greater insight into the improvements needed. The numbers in the cells indicate the number of problems at the intersection of the row and the column.</p>
        </sec>
      </sec>
      <sec>
        <title>Step 3: Semistructured Interview</title>
        <sec>
          <title>Overview</title>
          <p>This section presents the questions and translations of the transcripts, including answers to each question. Service providers are identified as SP [#] and caregivers as C [#]. Question 1 was asked during task performance, and the results were included at that point.</p>
        </sec>
        <sec>
          <title>Question 2</title>
          <p>The second question was as follows: “Is the website easy to use?”—Seven participants answered this question. Answers varied among participants: 3 answered “yes” (SP4, C1, and C5), 1 specifying that it was easy to understand and that the screen was not overloaded (C1). Two answers seemed ambivalent:</p>
          <disp-quote>
            <p>We find resources when it [website] works properly. If I am looking for an organization but I don’t know the organizations...Finding resources, I don’t know the resources, it is not clear.</p>
            <attrib>SP1</attrib>
          </disp-quote>
          <disp-quote>
            <p>Middle. Knowing if it [the search] worked or not. But visually it’s quite easy, not overloaded. It is easy to search.</p>
            <attrib>C3</attrib>
          </disp-quote>
          <p>One participant answered negatively:</p>
          <disp-quote>
            <p>It makes me feel incompetent. I can’t immediately find what I’m looking for.</p>
            <attrib>SP5</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Question 3</title>
          <p>The third question was: “Is the organization of the website logical and optimal?”—Seven participants answered this question. Two were positive:</p>
          <disp-quote>
            <p>Personally, I think it’s OK. I will sit with the caregiver and find resources.</p>
            <attrib>C5</attrib>
          </disp-quote>
          <disp-quote>
            <p>Oh yes! We have a lot to learn. If I had it, I would learn a lot!</p>
            <attrib>C4</attrib>
          </disp-quote>
          <p>Three participants said it was clear, but not optimal (SP4, SP5, and C3). Similarly, 2 participants mentioned it could be better (SP2), 1 commenting on the information: “For me, information needs to be precise, I don’t want to get lost in things that will take time” [C2].</p>
        </sec>
        <sec>
          <title>Question 4</title>
          <p>Next, the following question was asked to six participants: “Did you find information easily?”—Only 1 answer was fully positive: “Yes, indeed. It should have info for each organization” [C1].</p>
          <p>Other answers were more mitigated: “Yes and no. For now, there is not a lot in it” [SP4], with some commenting on the fact that they needed the interviewer to complete the task (C3 and C4). Two were negative:</p>
          <disp-quote>
            <p>Not really. I was not able to get results.</p>
            <attrib>SP2</attrib>
          </disp-quote>
          <disp-quote>
            <p>It was too long.</p>
            <attrib>C2</attrib>
          </disp-quote>
          <p>One participant commented on the information he was not able to find easily:</p>
          <disp-quote>
            <p>I expected to arrive directly in the activities, because now, I have to go through the list before getting to the activities. Especially because it is presented...In the list, the organizations were first, then the activities and after the documents. There should be some logic to it.</p>
            <attrib>C1</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Question 5</title>
          <p>The fifth question was as follows: “When navigating on the website, is it easy to know where you are?”—All participants who answered this question (n=8) said they were mostly able to figure out where they were. Three participants answered “yes” (SP2, SP4, and C5); one answered “Quite easily” [C2]; and another answered “Yes, I think” [C4]. Other answers were ambivalent, with participants providing some explanation:</p>
          <disp-quote>
            <p>The first time no, but after yes.</p>
            <attrib>C3</attrib>
          </disp-quote>
          <disp-quote>
            <p>It’s because we could not see the rest. I knew where I was in the section I could reach.</p>
            <attrib>SP1</attrib>
          </disp-quote>
          <disp-quote>
            <p>I knew where I was in the website. But, when I clicked here [browser Back button], I expected to go back to the page I was before, but it brings me back to the beginning.</p>
            <attrib>C1</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Question 6</title>
          <p>The following question was answered by only 1 participant: “Generally speaking, are you satisfied with this website?”</p>
          <disp-quote>
            <p>More or less. Contrasts should be adjusted for older and colour-blind people.</p>
            <attrib>SP4</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Question 7</title>
          <p>The following question was: <bold>“</bold>Do you feel comfortable using this website?”—Two of those who answered this question (n=4) answered “yes” (SP4 and C3). One specified that she would use it with a digital tablet (C2). Another (SP2) mentioned that he would be somewhat comfortable using it, even with the current problems. He was referring to one of the programming problems.</p>
        </sec>
        <sec>
          <title>Question 8</title>
          <p>For the last question: “Would you like to use this website for your tasks?”—Again, 2 (of a total of 3) participants answered simply “yes” (SP4 and C3). One participant indicated that he would use it with caregivers:</p>
          <disp-quote>
            <p>Of course, I would use it! I would use it with the caregiver to help him develop his ability to find information with this tool.</p>
            <attrib>SP6</attrib>
          </disp-quote>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study aims to assess the usability and UX of the 2 objectives of an early co-designed prototype. Findings from step 1 (users’ first impressions) indicate that participants were able to identify the 2 main objectives of the website. Moreover, even if participants were ambivalent regarding information retrieval, (answers from question 3 during step 3) and the ease of use of the website (answers for question 2 during step 3), they were still comfortable and interested in using the website (answers from questions 5 to 7 during step 3). On the other hand, results from the task scenarios (step 2) tend to indicate that there were more usability problems for the <italic>offering resources</italic> objective, especially when service providers were trying to create their profile. However, this was not the website’s main objective, as the co-design study first aimed to conceive an eHealth tool to support the help-seeking process of caregivers. The second objective (<italic>offering resources</italic>) emerged early during the co-design process, that is, during the identification of functional and content requirements [<xref ref-type="bibr" rid="ref23">23</xref>]. As mentioned by Luck [<xref ref-type="bibr" rid="ref38">38</xref>], in participatory design research, knowledge is constructed through practice, and one cannot entirely foresee the direction of the experiment. This was the case, for example, for the co-design study by Tironi [<xref ref-type="bibr" rid="ref39">39</xref>], in which new knowledge about the ontological perspective of users forced the redefinition of the initial protocol.</p>
      </sec>
      <sec>
        <title>Required Improvements on Accessibility</title>
        <p>A second finding relates to accessibility. Accessibility “means removing barriers that might prevent someone from using something, regardless of their access needs” [<xref ref-type="bibr" rid="ref40">40</xref>]. Accessibility problems were found during task scenarios (step 2) for 1 service provider. Due to a visual impairment, this participant was unable to see the entire page at once. The participant was using a special device to enlarge the interface on the screen. Even if it is uncommon to identify <italic>context of use</italic> as a usability category (other studies generally use the effectiveness, efficiency, satisfaction triad), we chose to include it in our study to see whether we would be able to classify problems in that category, and we were able to do so. The special needs of this participant were not addressed. We recognize that no participant with a visual impairment was included during the co-design process [<xref ref-type="bibr" rid="ref22">22</xref>]. To maximize the potential of addressing all user needs, participants with special needs should have been included in the co-design process. As mentioned by Cahill [<xref ref-type="bibr" rid="ref41">41</xref>], co-design or participatory action research is precisely an appropriate method for <italic>including excluded perspectives</italic> and challenging typical knowledge production. From a social justice perspective, other co-design studies should include users with impairments, as special techniques to co-design with them are offered in the literature [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>].</p>
      </sec>
      <sec>
        <title>Combination of Frameworks</title>
        <p>The combination of the 3 frameworks was a novel contribution. It has broadened the perspective and enhanced the strength of our study. As pointed out by Lacerda and von Wangenheim [<xref ref-type="bibr" rid="ref44">44</xref>] in their systematic literature review, current usability models have many problems (lack of information on the intended use, data collection instruments, and assessment process), leading researchers to seek other sources or combine different models and methods. In our study, the use of the ISO framework was particularly helpful in revealing an important accessibility issue. The use of the Garrett framework was decisive in identifying the dimensions in which the problem was located. Nielsen heuristics helped us to understand how to improve the website in further iterations of the prototype. Each framework provided useful insights to understand the usability and UX of our prototype. However, the combination of the analyses of all 3 frameworks was even more informative. For example, we were able to identify that most problems were located in the <italic>interface</italic> and <italic>information design</italic> and were <italic>effectiveness</italic> problems (users being unable to complete the task) or <italic>efficiency</italic> problems (the level of difficulty in performing the task). Moreover, we were able to get a better idea of how to address the problems, knowing which heuristics they were not addressing, which were often the <italic>match between the system and the real world</italic> and <italic>help and documentation</italic>.</p>
      </sec>
      <sec>
        <title>Challenges and Limitations</title>
        <p>This study has some limitations. First, scenarios were created by the research team and imposed on the participants. This may have affected the results, as the focus was on the task and might have hindered access to other useful information. Second, the data were analyzed by only 1 expert or researcher. The results were presented to the research team, who agreed on the big picture without determining proper intercoder agreement. Third, programming errors interfered with some tasks, which may have led to the loss of useful information on usability. These problems were identified as programming errors, but the participants were not able to perform the task. If it had been possible to perform the task, other usability problems might have been identified for the task. During the analysis, we also realized that there was a possible mapping issue between the different categories of the frameworks. For example, “The participant did not see the phone number” could have been identified as either <italic>effectiveness</italic> or <italic>efficiency</italic>. The interpretation relies on what the analyst was focusing on. It could be coded as <italic>effectiveness</italic> if we consider that the user needs to call the phone number, and it could be coded as <italic>efficiency</italic> if the phone number is one method (among several) to access information. Thus, the combination of the 3 conceptual frameworks does not bring a mutually exclusive categorization, but it reduces the risk of blind spots. Regardless of the category, we were still able to identify that the phone number was not perceived and needed more emphasis.</p>
        <p>Other limitations were related to the study participants. First, the participants had a high level of education, as most had a university degree (n=8). Although this might represent the population of service providers, it is not representative of the caregiver population. In Québec, only 27.6% of caregivers had a university degree [<xref ref-type="bibr" rid="ref45">45</xref>]. The second limitation was the age gap between the <italic>offering resources</italic> group and the <italic>finding resources</italic> group. Age is a determining factor in the use of internet products [<xref ref-type="bibr" rid="ref7">7</xref>]. However, the <italic>finding resources</italic> group was mostly caregivers of functionally dependent older persons. Statistics indicate that these caregivers are often older themselves [<xref ref-type="bibr" rid="ref5">5</xref>], which could explain the gap. The third limitation was the number of participants. Although we had 10 users, all of them were not testing exactly the same pages. Five users were testing each objective of the website. Nevertheless, looking at the results, we still consider that most of the problems seemed to emerge during this usability and UX assessment, without an absolute confirmation on the saturation of problems. As this study was exploratory and targeted an early version of the website, we are confident that we have collected sufficient information to improve the prototype.</p>
        <p>Our results are transferable to a very limited extent to other eHealth systems. They are indeed related to a specific interactive product (website) dedicated to specific users (caregivers and service providers). Nevertheless, our analysis proposition combining the ISO [<xref ref-type="bibr" rid="ref13">13</xref>], Nielsen heuristic [<xref ref-type="bibr" rid="ref16">16</xref>], and elements of UX [<xref ref-type="bibr" rid="ref20">20</xref>] is highly applicable to the usability or UX evaluation of other eHealth systems.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study provided improvement possibilities for a prototype co-designed with caregivers and service providers. We were able to identify several usability and UX problems. The 3 frameworks used for the analysis allowed us to understand the nature of the problem (ISO) [<xref ref-type="bibr" rid="ref13">13</xref>] and the dimension where it lies (elements of UX) [<xref ref-type="bibr" rid="ref20">20</xref>], as well as provide potential problem-solving solutions based on the predicted judgmental operations (Nielsen heuristics) [<xref ref-type="bibr" rid="ref16">16</xref>]. Thus, we will continue the co-design process to address those problems by recruiting service providers and caregivers to co-design a new version of the prototype. Our analytical method, based on the 3 conceptual frameworks and their combination, broadened the perspective of the problems encountered. This combination of frameworks for usability and UX analysis is a novel contribution that is transferable to other eHealth systems, which contributes to the advancement of knowledge in the eHealth community.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Synthesis of results combining the 3 analysis frameworks.</p>
        <media xlink:href="humanfactors_v8i3e26532_app1.pdf" xlink:title="PDF File  (Adobe PDF File), 59 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">5ST</term>
          <def>
            <p>5-second test</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">ISO</term>
          <def>
            <p>International Organization for Standardization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">UX</term>
          <def>
            <p>user experience</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The funds for this study were provided by the <italic>Québec amis des aînés</italic> program of the <italic>Ministère de la Famille (Québec)</italic>.</p>
    </ack>
    <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 Myths</article-title>
          <source>Canada Health Infoway</source>
          <access-date>2021-06-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.infoway-inforoute.ca/en/myths">https://www.infoway-inforoute.ca/en/myths</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Blom</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Zarit</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Groot Zwaaftink</surname>
              <given-names>RB</given-names>
            </name>
            <name name-style="western">
              <surname>Cuijpers</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Pot</surname>
              <given-names>AM</given-names>
            </name>
          </person-group>
          <article-title>Effectiveness of an Internet intervention for family caregivers of people with dementia: results of a randomized controlled trial</article-title>
          <source>PLoS One</source>
          <year>2015</year>
          <volume>10</volume>
          <issue>2</issue>
          <fpage>e0116622</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0116622"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0116622</pub-id>
          <pub-id pub-id-type="medline">25679228</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-12462</pub-id>
          <pub-id pub-id-type="pmcid">PMC4334515</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guay</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Auger</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Demers</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mortenson</surname>
              <given-names>WB</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Gélinas-Bronsard</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmed</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Components and outcomes of internet-based interventions for caregivers of older adults: systematic review</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>09</month>
          <day>19</day>
          <volume>19</volume>
          <issue>9</issue>
          <fpage>e313</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/9/e313/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7896</pub-id>
          <pub-id pub-id-type="medline">28928109</pub-id>
          <pub-id pub-id-type="pii">v19i9e313</pub-id>
          <pub-id pub-id-type="pmcid">PMC5627044</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>Irani</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Niyomyart</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Hickman</surname>
              <given-names>RL</given-names>
            </name>
          </person-group>
          <article-title>Systematic review of technology-based interventions targeting chronically ill adults and their caregivers</article-title>
          <source>West J Nurs Res</source>
          <year>2020</year>
          <month>11</month>
          <volume>42</volume>
          <issue>11</issue>
          <fpage>974</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1177/0193945919897011</pub-id>
          <pub-id pub-id-type="medline">31941418</pub-id>
          <pub-id pub-id-type="pmcid">PMC8096122</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="web">
          <article-title>L’appui pour les proches aidants d’aînés. Portrait statistique des proches aidants de personnes de 65 ans et plus au Québec</article-title>
          <source>L'Appui</source>
          <year>2016</year>
          <access-date>2021-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.lappui.org/Organisations/Boite-a-outils/Portrait-statistique-des-proches-aidants-d-aines-au-Quebec">https://www.lappui.org/Organisations/Boite-a-outils/Portrait-statistique-des-proches-aidants-d-aines-au-Quebec</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Charmarkeh</surname>
              <given-names>Houssein</given-names>
            </name>
          </person-group>
          <article-title>Les personnes âgées et la fracture numérique de « second degré » : l’apport de la perspective critique en communication</article-title>
          <source>Revue française des sciences de l’information et de la communication</source>
          <year>2015</year>
          <month>01</month>
          <day>23</day>
          <volume>6</volume>
          <issue>1</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://rfsic.revues.org/1294"/>
          </comment>
          <pub-id pub-id-type="doi">10.4000/rfsic.1294</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>Blank</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Groselj</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Dimensions of Internet use: amount, variety, and types</article-title>
          <source>Info Commun Soc</source>
          <year>2014</year>
          <month>02</month>
          <day>28</day>
          <volume>17</volume>
          <issue>4</issue>
          <fpage>417</fpage>
          <lpage>35</lpage>
          <pub-id pub-id-type="doi">10.1080/1369118X.2014.889189</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>Peek</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Wouters</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>van Hoof</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Luijkx</surname>
              <given-names>KG</given-names>
            </name>
            <name name-style="western">
              <surname>Boeije</surname>
              <given-names>HR</given-names>
            </name>
            <name name-style="western">
              <surname>Vrijhoef</surname>
              <given-names>HJ</given-names>
            </name>
          </person-group>
          <article-title>Factors influencing acceptance of technology for aging in place: a systematic review</article-title>
          <source>Int J Med Inform</source>
          <year>2014</year>
          <month>04</month>
          <volume>83</volume>
          <issue>4</issue>
          <fpage>235</fpage>
          <lpage>48</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1386-5056(14)00017-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2014.01.004</pub-id>
          <pub-id pub-id-type="medline">24529817</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(14)00017-3</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wolstenholme</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ross</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Cobb</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bowen</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Participatory design facilitates person centred nursing in service improvement with older people: a secondary directed content analysis</article-title>
          <source>J Clin Nurs</source>
          <year>2017</year>
          <month>05</month>
          <volume>26</volume>
          <issue>9-10</issue>
          <fpage>1217</fpage>
          <lpage>25</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/27191790"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/jocn.13385</pub-id>
          <pub-id pub-id-type="medline">27191790</pub-id>
          <pub-id pub-id-type="pmcid">PMC5413812</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sanders</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Stappers</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Co-creation and the new landscapes of design</article-title>
          <source>CoDesign</source>
          <year>2008</year>
          <month>03</month>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>5</fpage>
          <lpage>18</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.tandfonline.com/doi/full/10.1080/15710880701875068"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/15710880701875068</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baecker</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Richards</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Field Evaluation of a Collaborative Memory Aid for Persons With Amnesia and Their Family Members</article-title>
          <source>Proceedings of the 12th international ACM SIGACCESS Conference on Computers and Accessibility</source>
          <year>2010</year>
          <conf-name>ASSETS'10</conf-name>
          <conf-date>May 6-9, 2010</conf-date>
          <conf-loc>Orlando, Floria, USA</conf-loc>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://portal.acm.org/citation.cfm?doid=1878803.1878815"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/1878803.1878815</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="book">
          <source>Usability BT - Design dictionary: Perspectives on design terminology. Inrlhoff M, Marshall T.  editors</source>
          <year>2008</year>
          <publisher-loc>Basel</publisher-loc>
          <publisher-name>Birkhauser Basel</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <article-title>Usability: Definitions and Concepts</article-title>
          <source>ISO Online Browsing Platform (OBP)</source>
          <year>2018</year>
          <access-date>2021-06-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/obp/ui/#iso:std:iso:9241:-11:ed-2:v1:en">https://www.iso.org/obp/ui/#iso:std:iso:9241:-11:ed-2:v1:en</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The usability engineering life cycle</article-title>
          <source>Computer</source>
          <year>1992</year>
          <month>03</month>
          <volume>25</volume>
          <issue>3</issue>
          <fpage>12</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1109/2.121503</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>Tversky</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kahneman</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Judgment under uncertainty: heuristics and biases</article-title>
          <source>Science</source>
          <year>1974</year>
          <month>10</month>
          <day>27</day>
          <volume>185</volume>
          <issue>4157</issue>
          <fpage>1124</fpage>
          <lpage>31</lpage>
          <pub-id pub-id-type="doi">10.1126/science.185.4157.1124</pub-id>
          <pub-id pub-id-type="medline">17835457</pub-id>
          <pub-id pub-id-type="pii">185/4157/1124</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <article-title>Usability Heuristics for User Interface Design</article-title>
          <source>Nielsen Norman Group</source>
          <year>2020</year>
          <access-date>2018-05-15</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/articles/ten-usability-heuristics/">https://www.nngroup.com/articles/ten-usability-heuristics/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bevan</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Classifying and Selecting UX and Usability Measures</article-title>
          <source>Proceedings of the International Workshop on Meaningful Measures: Valid Useful User Experience Measurement (VUUM)</source>
          <year>2008</year>
          <conf-name>VUUM2008</conf-name>
          <conf-date>June 18, 2008</conf-date>
          <conf-loc>Reykjavik, Iceland</conf-loc>
          <fpage>13</fpage>
          <lpage>18</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Carver</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Scheier</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>On the structure behavioral self-regulation</article-title>
          <source>Handbook of Self-Regulation</source>
          <year>2000</year>
          <publisher-loc>ProQuest Ebook Central</publisher-loc>
          <publisher-name>Academic Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hassenzahl</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>User Experience (UX): Towards an Experiential Perspective on Product Quality</article-title>
          <source>Proceedings of the 20th Conference on l'Interaction Homme-Machine</source>
          <year>2008</year>
          <conf-name>IHM'08</conf-name>
          <conf-date>July 5-9, 2008</conf-date>
          <conf-loc>San Fransisco, USA</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1512714.1512717</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="book">
          <source>The Elements of User Experience Internet</source>
          <year>2011</year>
          <publisher-loc>Berkley, CA</publisher-loc>
          <publisher-name>New Riders</publisher-name>
        </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>Latulippe</surname>
              <given-names>LK</given-names>
            </name>
            <name name-style="western">
              <surname>Guay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Éthier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sévigny</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dubé</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Provencher</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Poulin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Giguere</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Tremblay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Carignan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giroux</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Supporting the process of help-seeking by caregivers of functionally dependent older persons through electronic health: protocol for a multicenter co-design</article-title>
          <source>JMIR Res Protoc</source>
          <year>2019</year>
          <month>04</month>
          <day>26</day>
          <volume>8</volume>
          <issue>4</issue>
          <fpage>e11634</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.researchprotocols.org/2019/4/e11634/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11634</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Giroux</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Tremblay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Latulippe</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Provencher</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Poulin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Giguere</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dubé</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Sévigny</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Guay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ethier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Carignan</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Promoting identification and use of aid resources by caregivers of seniors: co-design of an electronic health tool</article-title>
          <source>JMIR Aging</source>
          <year>2019</year>
          <month>08</month>
          <day>22</day>
          <volume>2</volume>
          <issue>2</issue>
          <fpage>e12314</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2019/2/e12314/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12314</pub-id>
          <pub-id pub-id-type="medline">31518284</pub-id>
          <pub-id pub-id-type="pii">v2i2e12314</pub-id>
          <pub-id pub-id-type="pmcid">PMC6744817</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tremblay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Latulippe</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Giguere</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Provencher</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Poulin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Dubé</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Guay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ethier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sévigny</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Carignan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giroux</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Requirements for an electronic health tool to support the process of help seeking by caregivers of functionally impaired older adults: co-design approach</article-title>
          <source>JMIR Aging</source>
          <year>2019</year>
          <month>07</month>
          <day>7</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e12327</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2019/1/e12327/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12327</pub-id>
          <pub-id pub-id-type="medline">31518279</pub-id>
          <pub-id pub-id-type="pii">v2i1e12327</pub-id>
          <pub-id pub-id-type="pmcid">PMC6715009</pub-id>
        </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>Latulippe</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tremblay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Poulin</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Provencher</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Giguere</surname>
              <given-names>AM</given-names>
            </name>
            <name name-style="western">
              <surname>Sévigny</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dubé</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Éthier</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Guay</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Carignan</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Giroux</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Prioritizing the needs of caregivers of older adults to support their help-seeking process as a first step to developing an ehealth tool: the technique for research of information by animation of a group of experts (TRIAGE) method</article-title>
          <source>JMIR Aging</source>
          <year>2019</year>
          <month>05</month>
          <day>23</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e12271</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aging.jmir.org/2019/1/e12271/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12271</pub-id>
          <pub-id pub-id-type="medline">31518269</pub-id>
          <pub-id pub-id-type="pii">v2i1e12271</pub-id>
          <pub-id pub-id-type="pmcid">PMC6716487</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rubin</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Chisnell</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>How to Plan, Design, and Conduct Effective Tests</article-title>
          <source>Wiley Publishing Inc</source>
          <year>2008</year>
          <access-date>2018-08-30</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.wiley.com/go/permissions">http://www.wiley.com/go/permissions</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>Usability: lessons learned … and yet to be learned</article-title>
          <source>Int J Hum Comput Interact</source>
          <year>2014</year>
          <month>06</month>
          <day>18</day>
          <volume>30</volume>
          <issue>9</issue>
          <fpage>663</fpage>
          <lpage>84</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.tandfonline.com/action/journalInformation?journalCode=hihc20"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/10447318.2014.930311</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>Faulkner</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Beyond the five-user assumption: benefits of increased sample sizes in usability testing</article-title>
          <source>Behav Res Methods Instrum Comput</source>
          <year>2003</year>
          <month>08</month>
          <volume>35</volume>
          <issue>3</issue>
          <fpage>379</fpage>
          <lpage>83</lpage>
          <pub-id pub-id-type="doi">10.3758/bf03195514</pub-id>
          <pub-id pub-id-type="medline">14587545</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="web">
          <article-title>OBS Studio</article-title>
          <source>Wikipedia</source>
          <year>2021</year>
          <access-date>2021-07-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://en.wikipedia.org/wiki/OBS_Studio">https://en.wikipedia.org/wiki/OBS_Studio</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sherwin</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>5-Second Usability Test (Video)</article-title>
          <source>NNGroup</source>
          <access-date>2018-04-22</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/videos/5-second-usability-test/?lm=user-testing-facilitation-techniques&#38;pt=youtubevideo">https://www.nngroup.com/videos/5-second-usability-test/?lm=user-testing-facilitation-techniques&#38;pt=youtubevideo</ext-link>
          </comment>
        </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>Gronier</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Measuring the first impression: testing the validity of the 5 second test internet</article-title>
          <source>J Usab Stud</source>
          <year>2016</year>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>-</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://uxpajournal.org/measuring-testing-validity-5-second-test/"/>
          </comment>
          <pub-id pub-id-type="doi">10.5555/3040226.3040228</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tirkkonen-Condit</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Think-Aloud Protocols</article-title>
          <source>Conference on Human Factors in Computing Systems</source>
          <year>2010</year>
          <conf-name>CHI'10</conf-name>
          <conf-date>June 9-11, 2010</conf-date>
          <conf-loc>Atlanta, GA</conf-loc>
          <fpage>2381</fpage>
          <lpage>2390</lpage>
          <pub-id pub-id-type="doi">10.1016/b0-08-044854-2/00479-x</pub-id>
        </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>Chevalier</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kicka</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Web designers and web users: influence of the ergonomic quality of the web site on the information search</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>2006</year>
          <month>10</month>
          <volume>64</volume>
          <issue>10</issue>
          <fpage>1031</fpage>
          <lpage>48</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijhcs.2006.06.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Facets of simplicity for the smartphone interface: a structural model</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>2012</year>
          <month>02</month>
          <volume>70</volume>
          <issue>2</issue>
          <fpage>129</fpage>
          <lpage>42</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijhcs.2011.09.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Studying information seeking on the non-english web: an experiment on a Spanish business web portal</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>2006</year>
          <month>09</month>
          <volume>64</volume>
          <issue>9</issue>
          <fpage>811</fpage>
          <lpage>29</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijhcs.2006.04.009</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lewis</surname>
              <given-names>JR</given-names>
            </name>
          </person-group>
          <article-title>IBM computer usability satisfaction questionnaires: psychometric evaluation and instructions for use</article-title>
          <source>Int J Hum Comput Stud</source>
          <year>1995</year>
          <month>01</month>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>57</fpage>
          <lpage>78</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pdfs.semanticscholar.org/7601/5a17ea1a864e9e32e0259b9f82451fbc29c1.pdf?_ga=2.57471337.291676742.1536069325-1567072580.1536069325"/>
          </comment>
          <pub-id pub-id-type="doi">10.1080/10447319509526110</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wechsung</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Naumann</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>André</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Evaluation methods for multimodal systems: a comparison of standardized usability questionnaires</article-title>
          <source>Perception in Multimodal Dialogue Systems</source>
          <year>2008</year>
          <publisher-loc>Verlag Berlin Heidelberg</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Miles</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Huberman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Saldaña</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Qualitative Data Analysis: a Methods Sourcebook</source>
          <year>2014</year>
          <publisher-loc>Thousand Oaks, CA</publisher-loc>
          <publisher-name>Sage Publications</publisher-name>
          <fpage>a</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luck</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Participatory design in architectural practice: changing practices in future making in uncertain times</article-title>
          <source>Design Stud</source>
          <year>2018</year>
          <month>11</month>
          <volume>59</volume>
          <fpage>139</fpage>
          <lpage>57</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.destud.2018.10.003"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.10.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tironi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Speculative prototyping, frictions and counter-participation: a civic intervention with homeless individuals</article-title>
          <source>Design Stud</source>
          <year>2018</year>
          <month>11</month>
          <volume>59</volume>
          <fpage>117</fpage>
          <lpage>38</lpage>
          <pub-id pub-id-type="doi">10.1016/j.destud.2018.05.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Firth</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <source>Practical Web Inclusion and Accessibility: A Comprehensive Guide to Access Needs</source>
          <year>2019</year>
          <publisher-loc>New York, USA</publisher-loc>
          <publisher-name>Apress</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cahill</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Including excluded perspectives in participatory action research</article-title>
          <source>Design Stud</source>
          <year>2007</year>
          <month>05</month>
          <volume>28</volume>
          <issue>3</issue>
          <fpage>325</fpage>
          <lpage>40</lpage>
          <pub-id pub-id-type="doi">10.1016/j.destud.2007.02.006</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Metatla</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Bryan-Kinns</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Stockman</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Designing with and for people living with visual impairments: audio-tactile mock-ups, audio diaries and participatory prototyping</article-title>
          <source>CoDesign</source>
          <year>2015</year>
          <month>03</month>
          <day>24</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>35</fpage>
          <lpage>48</lpage>
          <pub-id pub-id-type="doi">10.1080/15710882.2015.1007877</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luck</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Haenlein</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bright</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Project briefing for accessible design</article-title>
          <source>Design Studies</source>
          <year>2001</year>
          <month>5</month>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>297</fpage>
          <lpage>315</lpage>
          <pub-id pub-id-type="doi">10.1016/s0142-694x(00)00031-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lacerda</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>von Wangenheim</surname>
              <given-names>CG</given-names>
            </name>
          </person-group>
          <article-title>Systematic literature review of usability capability/maturity models</article-title>
          <source>Comput Stand</source>
          <year>2018</year>
          <month>01</month>
          <volume>55</volume>
          <fpage>95</fpage>
          <lpage>105</lpage>
          <pub-id pub-id-type="doi">10.1016/j.csi.2017.06.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <article-title>Les proches aidantes et les proches aidants au Québec - Analyse différenciée selon les sexes</article-title>
          <source>Conseil du statut de la femme</source>
          <year>2018</year>
          <access-date>2021-06-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.csf.gouv.qc.ca/wp-content/uploads/por_proches_aidants20180419_web.pdf">https://www.csf.gouv.qc.ca/wp-content/uploads/por_proches_aidants20180419_web.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
