<?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">v9i3e37894</article-id>
      <article-id pub-id-type="pmid">36178714</article-id>
      <article-id pub-id-type="doi">10.2196/37894</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>Defining Recommendations to Guide User Interface Design: Multimethod Approach</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>Mohamad Ali</surname>
            <given-names>Nazlena</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Choemprayong</surname>
            <given-names>Songphan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Diehl</surname>
            <given-names>Ceci</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0728-7492</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Martins</surname>
            <given-names>Ana</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5220-0528</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Almeida</surname>
            <given-names>Ana</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7349-457X</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Silva</surname>
            <given-names>Telmo</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9383-7659</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Ribeiro</surname>
            <given-names>Óscar</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-4740-7951</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Santinha</surname>
            <given-names>Gonçalo</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4732-5959</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Rocha</surname>
            <given-names>Nelson</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3801-7249</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Silva</surname>
            <given-names>Anabela G</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <address>
            <institution>Center for Health Technology and Services Research</institution>
            <institution>School of Health Sciences</institution>
            <institution>University of Aveiro</institution>
            <addr-line>Campus Universitário Santiago</addr-line>
            <addr-line>Aveiro, 3810-193</addr-line>
            <country>Portugal</country>
            <phone>351 234 372 444</phone>
            <email>asilva@ua.pt</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4386-5851</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Digital Media and Interaction Research Centre (DigiMedia)</institution>
        <institution>Department of Communication and Art</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Center for Health Technology and Services Research</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Center for Health Technology and Services Research</institution>
        <institution>School of Health Sciences</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Center for Health Technology and Services Research</institution>
        <institution>Department of Education and Psychology</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Governance, Competitiveness and Public Policies</institution>
        <institution>Department of Social, Political and Territorial Sciences</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>Institute of Electronics and Informatics Engineering of Aveiro</institution>
        <institution>Department of Medical Sciences</institution>
        <institution>University of Aveiro</institution>
        <addr-line>Aveiro</addr-line>
        <country>Portugal</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Anabela G Silva <email>asilva@ua.pt</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <season>Jul-Sep</season>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>30</day>
        <month>9</month>
        <year>2022</year>
      </pub-date>
      <volume>9</volume>
      <issue>3</issue>
      <elocation-id>e37894</elocation-id>
      <history>
        <date date-type="received">
          <day>10</day>
          <month>3</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>13</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>29</day>
          <month>6</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>18</day>
          <month>7</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Ceci Diehl, Ana Martins, Ana Almeida, Telmo Silva, Óscar Ribeiro, Gonçalo Santinha, Nelson Rocha, Anabela G Silva. Originally published in JMIR Human Factors (https://humanfactors.jmir.org), 30.09.2022.</copyright-statement>
      <copyright-year>2022</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/2022/3/e37894" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>For the development of digital solutions, different aspects of user interface design must be taken into consideration. Different technologies, interaction paradigms, user characteristics and needs, and interface design components are some of the aspects that designers and developers should pay attention to when designing a solution. Many user interface design recommendations for different digital solutions and user profiles are found in the literature, but these recommendations have numerous similarities, contradictions, and different levels of detail. A detailed critical analysis is needed that compares, evaluates, and validates existing recommendations and allows the definition of a practical set of recommendations.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to analyze and synthesize existing user interface design recommendations and propose a practical set of recommendations that guide the development of different technologies.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Based on previous studies, a set of recommendations on user interface design was generated following 4 steps: (1) interview with user interface design experts; (2) analysis of the experts’ feedback and drafting of a set of recommendations; (3) reanalysis of the shorter list of recommendations by a group of experts; and (4) refining and finalizing the list.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The findings allowed us to define a set of 174 recommendations divided into 12 categories, according to usability principles, and organized into 2 levels of hierarchy: generic (69 recommendations) and specific (105 recommendations).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study shows that user interface design recommendations can be divided according to usability principles and organized into levels of detail. Moreover, this study reveals that some recommendations, as they address different technologies and interaction paradigms, need further work.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>user interface design</kwd>
        <kwd>usability principles</kwd>
        <kwd>interaction paradigm</kwd>
        <kwd>generic recommendations</kwd>
        <kwd>specific recommendations</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>In the context of digital solutions, user interface design consists of correctly defining the interface elements so that the tasks and interactions that users will perform are easy to understand [<xref ref-type="bibr" rid="ref1">1</xref>]. Therefore, a good user interface design must allow users to easily interact with the digital solution to perform the necessary tasks in a natural way [<xref ref-type="bibr" rid="ref2">2</xref>]. Considering that a digital solution is used by an individual with specific characteristics in a particular context [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>], when developing a digital solution, designers must pay attention to a high number of components of user interface design, such as color [<xref ref-type="bibr" rid="ref8">8</xref>] typography [<xref ref-type="bibr" rid="ref1">1</xref>], navigation and search [<xref ref-type="bibr" rid="ref9">9</xref>], input controls, and informational components [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
      <p>Digital solutions and their interfaces must be accessible to all audiences and aimed at universal use in an era of increasingly heterogeneous users [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref17">17</xref>]. Therefore, designers should also be aware of broad and complex issues such as context-oriented design, user requirements, and adaptable and adaptive interactive behaviors [<xref ref-type="bibr" rid="ref5">5</xref>]. The universal approach to user interface design follows heuristics and principles systematized by different authors over the years [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>], but these are generic guidelines, and examples of how they can be operationalized in practice are scarce.</p>
      <p>The literature presents many user interface design recommendations for varied digital solutions and users [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]. However, the absence of a detailed critical analysis that compares, evaluates, and validates existing recommendations is likely to facilitate an increasing number of similar recommendations [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. Although existing recommendations refer to specific technologies, forms of interaction, or end users, the content of some recommendations is generic and applicable to varied technologies and users, such as “always create good contrast between text and page background” [<xref ref-type="bibr" rid="ref30">30</xref>]; “color contrast of background and front content should be visible” [<xref ref-type="bibr" rid="ref23">23</xref>]; “leave space between links and buttons” [<xref ref-type="bibr" rid="ref30">30</xref>]; and “allow a reasonable spacing between buttons” [<xref ref-type="bibr" rid="ref31">31</xref>]. These illustrative examples highlight the need to aggregate, analyze, and validate existing recommendations on user interface design. Accordingly, this study aimed to synthesize existing guidelines into a practical set of recommendations that could be used to guide user interface design for different technologies. This is important because it contributes to the standardization of good practices and will conceivably allow for better interface design achieved at earlier stages of product development.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Background</title>
        <p>In a previous work, 244 interface recommendations were identified, and they formed the basis for this study [<xref ref-type="bibr" rid="ref32">32</xref>]. The identification of the 244 recommendations combined multiple sources: (1) our previous work [<xref ref-type="bibr" rid="ref33">33</xref>], (2) a purposive search on Scopus database, and (3) inputs provided by experts in the field of interface design. The references identified through all 3 steps were extracted into an Excel (Microsoft) database with a total of 1210 recommendations. We screened this database and looked for duplicated recommendations. During this analysis, very generic recommendations were also deleted, and recommendations addressing similar content were merged. The resulting database, with 194 recommendations, was analyzed by 10 experts in user interface design recruited among SHAPES (Smart and Health Ageing through People Engaging in Supportive Systems) [<xref ref-type="bibr" rid="ref34">34</xref>] project partners, who added another 62 recommendations, resulting in 256 recommendations. A further analysis identified 12 duplicated references that were deleted, resulting in a final list of 244 recommendations. The large number of recommendations was deemed impractical, and further action was necessary. Building on this prior research, a set of recommendations on user interface design were engendered following 4 steps: (1) interview with user interface design experts, (2) analysis of the experts’ feedback and drafting of a set of recommendations, (3) reanalysis of the shorter list of recommendations by a group of experts, and (4) refining and finalizing the list. Each of these steps is detailed below, and the whole process is illustrated in <xref rid="figure1" ref-type="fig">Figure 1</xref>.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Steps of analysis of the user interface design recommendations.</p>
          </caption>
          <graphic xlink:href="humanfactors_v9i3e37894_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Interview With User Interface Design Experts</title>
        <p>An Excel file with the 244 user interface design recommendations was sent to external experts in the field of user interface design. For an individual to be considered an expert, they had to meet at least 1 the following criteria: (1) have designed user interfaces for at least 2 projects/digital solutions or (2) have participated in the evaluation of user interfaces for at least 2 projects/digital products.</p>
        <p>An invitation email was sent to experts explaining the objectives of the study, along with a supporting document with the 244 recommendations. They were asked to analyze the recommendations and report on (1) repetition/relevance, (2) wording, (3) organization, and (4) any other aspect they felt relevant. They were given approximately 4 weeks to analyze the 244 recommendations and send their written analysis and comments back to us. Subsequently, they were asked to attend a Zoom (Zoom Video Communications) meeting aimed at clarifying their views and discussing potential contradictory comments. The written comments (sent in advance by the experts) were used to prepare a PowerPoint (Microsoft) presentation where recommendations and respective comments (anonymized) from all experts were synthetized. This presentation was used to guide the Zoom meeting discussion. To maximize the efficiency of the discussion, recommendations without any comments and those that received similar comments from different experts were not included in the presentation. For recommendations with contradictory comments, the facilitator led a discussion and tried to reach a consensus. For recommendations with comments from a single expert, the facilitator asked for the opinion of other experts. The Zoom meeting was facilitated by one of the authors (AIM) and assisted by another (author CD) who took notes. The facilitator encouraged the discussion and exchange of opinions from all experts participating in each meeting. The Zoom meetings were recorded, and the experts’ arguments were transcribed and analyzed using content analysis by 2 authors (AIM and AGS) with experience in qualitative data analysis. Written comments sent by the experts as well as comments and relevant notes made during the meeting were transposed into a single file and subject to content analysis. After transcription, the notes were independently read by both the aforementioned authors and grouped into themes, categories, and subcategories with similar meaning [<xref ref-type="bibr" rid="ref35">35</xref>]. Themes, categories, and subcategories were then compared, and a consensus was reached by discussion.</p>
      </sec>
      <sec>
        <title>Analyzing Experts’ Feedback and Drafting a Set of Recommendations</title>
        <p>The authors of this manuscript (internal experts), including individuals with expertise on content analysis and on user interface design and usability, participated in a series of 6 meetings that were approximately 2 to 3 hours in duration each. These meetings, which took place between January and April 2021 and were held online, aimed to analyze the comments made by external experts in the previous step. Based on the experts’ comments, each recommendation was either (1) not changed (if no comments were made by the experts), (2) deleted, (3) merged with other complementary recommendations, (4) rewritten, or (5) broken up into more than 1 recommendation. The decisions were based on the number of experts making the same suggestion, alignment with existing guidelines, and coherence with previous decisions for similar recommendations. In addition, based on external experts’ suggestions, the recommendations were organized as follows: (1) hierarchical levels according to level of detail and interdependency, (2) usability principles, and (3) type of technology and interaction paradigm.</p>
      </sec>
      <sec>
        <title>Reanalyzing the Shorter List of Recommendations</title>
        <p>To further validate decisions made by the internal panel and explore the possibility of reducing the number of recommendations, the set of recommendations resulting from the previous step (and its respective organization according to hierarchical levels and principles) was reanalyzed by an additional external panel of experts. Once again, to be considered an expert, individuals had to meet the previously identified criteria for experts (have designed user interfaces for at least 2 projects/digital products or have participated in the evaluation of user interfaces for at least 2 projects/digital products). An online individual interview was conducted in May 2021 with each expert by one of the authors (CD). Experts had to answer 3 questions about each of the recommendations: (1) Do you consider this recommendation useful? (Yes/No); (2) Do you consider this recommendation mandatory? (Yes/No); and (3) Do you have any observation/comment on any recommendations or on its organization? The first question was used to determine the inclusion or exclusion of recommendations, and the second one was used to inform on the priority of recommendations through the possibility of having 2 sets of recommendations: 1 mandatory and 1 optional. The third question aimed to elicit general comments on both individual recommendations and their organization. Consensus on the first 2 questions was defined as 70% or more of the experts signaling a recommendation with “Yes” and less than 15% of experts signaling the same recommendation with “No.” Qualitative data from the third question was independently analyzed by 2 authors (CD and AGS) using content analysis, as previously described.</p>
      </sec>
      <sec>
        <title>Refining and Finalizing the List of Recommendations</title>
        <p>The internal panel of experts (the authors of this study) had an online meeting in which findings of the previous step were presented and discussed, and amendments to the existing list of recommendations were decided to generate the final list of user interface design recommendations.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study focused on the analysis of previously published research and recommendations; therefore, ethical approval was considered unnecessary.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Interview With User Interface Design Experts</title>
        <p>A total of 9 experts participated in this step of the study: 5 females and 4 males with a mean age of 39.1 (SD 4.3) years. The participants were user interface designers (n=3, 33%) and user interface researchers (n=6, 67%) who had a background in design (n=6, 67%), communication and technology sciences (n=2, 22%), or computer engineering (n=1, 11%). A total of 3 meetings with 1 to 3 participants were conducted with a mean duration of 2 hours. Of the 244 recommendations, 166 (68%) were commented on by at least 1 expert.</p>
        <p>Regarding the analysis of the interviews and written information sent by the experts, it was possible to aggregate commentaries into 2 main themes: (1) wording and content of recommendations and (2) organization of recommendations. The first theme was divided into 5 categories: (1) not changed (if no comments were made by the experts); (2) deletion of recommendations (because they were not useful or were contradictory); (3) merging of recommendations (to address complementary aspects of user interface design); (4) rewriting of recommendations (for clarity and coherence); and (5) splitting recommendations into more than 1 (because they included different aspects of user interface design). Of the 244 recommendations, external experts suggested that 108 should be merged (usually pairs of recommendations but could also include more than 2 recommendations), 29 should be rewritten, 4 should be split into more than 1, and 44 should be deleted. Among the recommendations, 78 received no comment. For 19 recommendations, it was not possible to reach consensus in the interview phase.</p>
        <p>The second theme (organization of the recommendations) was divided into 2 categories: (1) hierarchization of recommendations and (2) grouping of recommendations. This last category was subdivided into 2 subcategories: (1) grouping of recommendations according to usability principles and (2) grouping of recommendations according to whether they apply to digital solutions in general or to specific digital solutions/interaction paradigms. Examples of quotations that support these categories and subcategories are presented in <xref ref-type="table" rid="table1">Table 1</xref>. Regarding the grouping of recommendations according to usability principles, the categories proposed by 5 experts (<xref ref-type="table" rid="table1">Table 1</xref>) were reorganized and merged into 12 categories: feedback, recognition, flexibility, customization, consistency, errors, help, accessibility, navigation, privacy, visual component, and emotional component. The mapping of the categories proposed by the experts and the 12 categories (named principles) are presented in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Categories and subcategories of the theme “organization of recommendations,” quotations supporting the categories, and number of experts that made comments in each category/subcategory.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="220"/>
            <col width="170"/>
            <col width="480"/>
            <col width="130"/>
            <thead>
              <tr valign="top">
                <td>Categories</td>
                <td>Subcategories</td>
                <td>Citations (examples)</td>
                <td>Experts, n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Hierarchization<break/>  <break/>  </td>
                <td>N/A<sup>a</sup></td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>There are recommendations with different levels of detail, and they are all placed at the same level; some recommendations correspond to guidelines, others are practical design indications. [E<sup>b</sup>6, male]</p>
                    </list-item>
                  </list>
                  <break/>
                  <break/>
                  <list list-type="bullet">
                    <list-item>
                      <p>It would be interesting to organize the recommendations based on the relationship between them. A high-level recommendation contains low level recommendations. [E8, male]</p>
                    </list-item>
                  </list>
                  <break/>
                  <break/>
                  <list list-type="bullet">
                    <list-item>
                      <p>It makes sense to split into layers. I suggest dividing them into recommendations applicable to all and into standards, with a very high level of detail (button size, space between buttons etc). [E1, female]</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>4 (44)</td>
              </tr>
              <tr valign="top">
                <td>Grouping of recommendations</td>
                <td>Design<break/>principles</td>
                <td><list list-type="bullet"><list-item><p>During our analysis, we organized the requirements into categories to assist us. [E7, female]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>To be able to do the analysis, I had to code each recommendation to more easily identify the ones that could be grouped according to that category and thus detect repetitions and redundancies. [E6, male]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>To make it easier, I created categories according to Nielsen's 10 usability heuristics and 5 design principles. [E3, female]</p></list-item></list><break/><break/>Of the 9 experts, 5 suggested categories for grouping recommendations:<break/><break/><break/><list list-type="bullet"><list-item><p>Feedback; users/confusion, errors; human-computer dialogue; system behavior; navigation; presentation; system; users; instruction/information; user control; personalization; system; screen reader; users/cognitive load; system/devices; instructions; user/emotions; design considerations; gamification; users/sensory. [E7, female]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>System status; feedback; task execution; navigation/ interaction; organization/structure of information; attention-orientation; information hierarchy; iconography; visual composition of information and of interaction elements; naming; navigation; accessibility; input device and interaction; attention-orientation; learnability; interface customization; complexity and density of information; typography/legibility and formatting; media controllers; color and contrast; navigation/task execution; information representation/mental models. [E6, male]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>Feedback; visibility; multimodality; help; recognition; mental burden; control; design; real world; language; flexibility; errors; consistency; accessibility; personalization; search history; animation; efficiency; number of steps; shortcuts; hierarchy; legibility; color; cultural context; security; body; discovery; emotion; gamification; predictive; privacy. [E3, female]</p></list-item></list><break/><break/><italic>Feedback; text information; user profile; layout; navigation; content; tasks; errors; consistency; input; ergonomic; emotional; security; gamification</italic>. [E2, female]<break/><break/><break/><list list-type="bullet"><list-item><p>Visual dimension; dimension of information architecture; dimension of social presence; interaction dimension and dimension of user experience. [E1, female]</p></list-item></list></td>
                <td>7 (78)</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>Generic vs specific to technology/ interaction paradigms</td>
                <td><list list-type="bullet"><list-item><p>The recommendations focus on different types of interactive products (feet, audio interaction, robotics, etc). It would make sense in the end, too, to organize and separate the recommendations by product types. [E6, male]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>I noticed that some recommendations distinguish interaction modalities (with voice, gestures, use of the feet, etc). I selected those that were general and those that were specific for these groups. [E3, female]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>All recommendations were put in the same bag, regardless of the detail. I think we are using design principles, guidelines, and standards. Standards only make sense when applied to a specific system, and it is very difficult to classify them without having in mind the system being evaluated. Design standards are derived from design principles and guidelines but applied to specific products. What is being done here is very rich and interesting, but it can lead to a “Frankenstein product,” because the recommendations depend on several factors. I think that at this point you should work with principles, point out the guidelines and check the recommendations for the different products. [E1, female]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>As we are talking about recommendations that cut across different types of interactive products (feet, audio interaction, robotics, etc), it would make sense in the end, too, to organize and separate the recommendations by product types. [E6, male]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>They are related in the area of interaction, but each one talks about a different interface. [E3, female]</p></list-item></list><break/><break/>Of the 9 experts, 3 suggested categories for grouping recommendations:<break/><break/><break/><list list-type="bullet"><list-item><p>Voice interaction; feet interaction; robot. [E7, female]</p></list-item></list><break/><break/><list list-type="bullet"><list-item><p>Generic; generic/user centered. [E6, male]</p></list-item><list-item><p>Voice; feet; real world; robot; touch; click; text; gestures. [E2, female]</p></list-item></list></td>
                <td>3 (33)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>N/A: not applicable.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>E: expert.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
      </sec>
      <sec>
        <title>Analysis of Experts’ Feedback and Reanalysis of the Recommendations</title>
        <p>Based on the external expert’s comments, the recommendations were reanalyzed. Of the 244 recommendations, 61 (25%) were deleted because they were duplicated or redundant, 48 (19.7%) were merged with other complementary recommendations, 62 (25.4%) were rewritten for clarification and language standardization, 14 (5.7%) were split in 2 or more recommendations, and 59 (24.2%) were not changed. This resulted in a preliminary list of 175 recommendations. <xref ref-type="table" rid="table2">Table 2</xref> compares the external experts’ recommendations and internal experts’ final decision.</p>
        <p>The 175 recommendations were then categorized into 12 mutually exclusive principles (feedback, recognition, flexibility, customization, consistency, errors, help, accessibility, navigation, privacy, visual, and emotional) and within each principle, organized into 2 levels of hierarchy according to the specificity/level of detail.</p>
        <p>Of the 175 recommendations, 70 were categorized as level 1 and were generic recommendations applied to all digital solutions, and 105 recommendations were linked to 1 first level recommendation and subdivided by type of digital solution/interaction paradigm. The recommendations of both levels are linked, as level 2 recommendations detail how level 1 recommendations can be implemented. For example, the level 1 recommendation that “the system should be used efficiently and with a minimum of fatigue” is linked to a set of level 2 recommendations targeted at specific interaction paradigms, such as feet interaction and robotics: (1) “In feet interaction, the system should minimize repetitive actions and sustained effort, using reasonable operating forces and allowing the user to maintain a neutral body position,” and (2) “In robotics, the system should have an appropriate weight, allowing the person to move the robot easily (this can be achieved by using back drivable hardware).” <xref ref-type="table" rid="table3">Table 3</xref> shows the distribution of the 175 recommendations.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Comparison of external expert’s recommendations and internal experts’ decision.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="400"/>
            <col width="350"/>
            <thead>
              <tr valign="top">
                <td>Type of action</td>
                <td>External experts’ recommendations (N=263)<sup>a</sup>, n (%)</td>
                <td>Internal experts’ decision (N=244), n (%)</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Deleted</td>
                <td>44 (16.7)</td>
                <td>61 (25)</td>
              </tr>
              <tr valign="top">
                <td>Merged</td>
                <td>108 (41.1)</td>
                <td>48 (19.7)</td>
              </tr>
              <tr valign="top">
                <td>Rewritten</td>
                <td>29 (11)</td>
                <td>62 (25.4)</td>
              </tr>
              <tr valign="top">
                <td>Split</td>
                <td>4 (1.5)</td>
                <td>14 (5.7)</td>
              </tr>
              <tr valign="top">
                <td>Not changed</td>
                <td>78 (29.7)</td>
                <td>59 (24.2)</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>Consensus was not possible for 19 recommendations.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Distribution of recommendations by level and category.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="180"/>
            <col width="170"/>
            <col width="180"/>
            <col width="290"/>
            <col width="180"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Level 1, (N=70), n<break/>  <break/>  </td>
                <td>Level 2, (N=105), n</td>
                <td>Technology/interaction paradigm</td>
                <td>Total (N=175), n</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Feedback</td>
                <td>6</td>
                <td>5</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet Interaction: 1</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 1</p>
                    </list-item>
                    <list-item>
                      <p>Voice Interaction: 2</p>
                    </list-item>
                    <list-item>
                      <p>Web/Mobile: 1</p>
                    </list-item>
                  </list>
                </td>
                <td>11</td>
              </tr>
              <tr valign="top">
                <td>Recognition</td>
                <td>5</td>
                <td>12</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 1</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 1</p>
                    </list-item>
                    <list-item>
                      <p>Voice interaction: 5</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 5</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>17</td>
              </tr>
              <tr valign="top">
                <td>Flexibility</td>
                <td>6</td>
                <td>10</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 1</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 4</p>
                    </list-item>
                    <list-item>
                      <p>Voice interaction: 2</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 3</p>
                    </list-item>
                  </list>
                </td>
                <td>16</td>
              </tr>
              <tr valign="top">
                <td>Customization</td>
                <td>7</td>
                <td>6</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 1</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 1</p>
                    </list-item>
                    <list-item>
                      <p>Voice interaction: 3</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 1</p>
                    </list-item>
                  </list>
                </td>
                <td>13</td>
              </tr>
              <tr valign="top">
                <td>Consistency</td>
                <td>2</td>
                <td>2</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Voice interaction: 2</p>
                    </list-item>
                  </list>
                </td>
                <td>4</td>
              </tr>
              <tr valign="top">
                <td>Errors</td>
                <td>5</td>
                <td>7</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 3</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 1</p>
                    </list-item>
                    <list-item>
                      <p>Voice interaction: 3</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>12</td>
              </tr>
              <tr valign="top">
                <td>Help</td>
                <td>3</td>
                <td>2</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Robotics: 1</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 1</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>5</td>
              </tr>
              <tr valign="top">
                <td>Accessibility</td>
                <td>8</td>
                <td>23</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 8</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 4</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 11</p>
                    </list-item>
                  </list>
                  <break/>
                </td>
                <td>31</td>
              </tr>
              <tr valign="top">
                <td>Navigation</td>
                <td>6</td>
                <td>6</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 3</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 3</p>
                    </list-item>
                  </list>
                </td>
                <td>12</td>
              </tr>
              <tr valign="top">
                <td>Privacy</td>
                <td>3</td>
                <td>5</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Digital solutions: 5</p>
                    </list-item>
                  </list>
                </td>
                <td>8</td>
              </tr>
              <tr valign="top">
                <td>Visual component</td>
                <td>16</td>
                <td>22</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 5</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 2</p>
                    </list-item>
                    <list-item>
                      <p>Web/mobile: 15</p>
                    </list-item>
                  </list>
                </td>
                <td>38</td>
              </tr>
              <tr valign="top">
                <td>Emotional component</td>
                <td>3</td>
                <td>5</td>
                <td>
                  <list list-type="bullet">
                    <list-item>
                      <p>Feet interaction: 1</p>
                    </list-item>
                    <list-item>
                      <p>Robotics: 3</p>
                    </list-item>
                    <list-item>
                      <p>Digital solutions: 1</p>
                    </list-item>
                  </list>
                </td>
                <td>8</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Reanalysis of the Shorter List of Recommendations by Experts</title>
        <p>A total of 14 experts (8 females and 6 males) with a mean age of 35 (SD 8.8) years old provided feedback on recommendations. Experts were user interface designers (n=6, 43%) and user interface researchers (n=8, 57%) who had a background in design (n=8, 57%) or communication and technology sciences (n=6, 43%). The interviews lasted up to 2 hours each.</p>
        <p>All the 175 recommendations reached consensus for the usefulness question. However, for question 2 (Do you consider this recommendation mandatory?), there was consensus that 54 (77%) level 1 recommendations were mandatory. The remaining 16 (23%) level 1 recommendations were considered by 5 (36%) to 9 (64%) experts as not mandatory. For the 105 level 2 recommendations, there was consensus that 91 (87%) were mandatory, and the remaining 14 were not considered mandatory by 5 (36%) to 9 (64%) experts.</p>
        <p>Experts’ comments were aggregated into 5 main themes: (1) deletion or recategorizing of recommendations, (2) consistency, (3) contradiction, (4) asymmetry, and (5) uncertainty. It was suggested that 1 recommendation be deleted (“The system should be free from errors”), and another moved from the visual component category to the emotional component category. No other suggestions were made regarding the structure of the recommendations. There were comments related to the consistency, particularly regarding the need to use either British or American spelling throughout all recommendations and to consistently refer to “users” instead of “persons” or “individuals.” The remaining comments applied mostly to level 2 recommendations, for which experts identified contradictory recommendations (eg, accessibility: “In robotics, the system should meet the person’s needs, be slow, safe and reliable, small, easy to use, and have an appearance not too human-like, not patronizing or stigmatizing<italic>”</italic> vs emotional: “In robotics, the system should indicate aliveness by showing some autonomous behavior, facial expressions, hand/head gestures to motivate engagement, as well as changing vocal patterns and pace to show different emotions”). Experts also commented on the asymmetry across the number of level 2 recommendations linked to level 1 recommendations and on the asymmetry regarding the number of recommendations per type of technology and interaction paradigm. In addition, experts were uncertain about the accuracy of the measures indicated in the recommendations (eg, visual: “In robotics, the system graphical user interface and button elements should be sufficiently big in size, so they can be easily seen and used, about ~20 mm in case of touch screen, buttons” vs visual: “In feet interaction, the system should consider an appropriate interaction radius of 20 cm for tap, 30 cm at the front, and 25 cm at the back for kick”).</p>
      </sec>
      <sec>
        <title>Refining and Finalizing the List of Recommendations</title>
        <p>Based on the experts’ comments and issues raised in the previous step, the term “users” was adopted throughout the recommendations, 1 recommendation was removed, and 1 was moved from the visual component to the emotional component. In addition, all level 1 recommendations for which no consensus was reached on whether they were mandatory were considered not mandatory (identified by using the word “may” in the recommendation). The internal panel also recognized that level 2 recommendations cannot be used to guide user interface design in their current stage and that further work is needed. Therefore, a final list of 69 generic recommendations is proposed (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>To the best of our knowledge, this is the first study that attempted to analyze and synthetize existing recommendations on user interface design. This was a complex task that generated a high number of interdependent recommendations that could be organized into hierarchical levels of interdependency and grouped according to usability principles. Level 1 recommendations are generic and can be used to inform the user interface design of different types of technology and interaction paradigms. Meanwhile, level 2 recommendations are more specific and therefore apply to different types of technology and interaction paradigms. Furthermore, the level of detail and absence of evidence that they had been validated raised doubts about their validity.</p>
        <p>The external experts’ suggestions formed the basis for the internal experts’ (our) analysis. However, there is a discrepancy between the analysis of both panels of experts in terms of the number of recommendations that should be deleted, merged, rewritten, fragmented, or not changed. This was because when analyzing the recommendations, the internal panel verified that there were more recommendations to delete that were repeated or generic beyond those already identified by the external panel. It is likely that these were missed due to the high number of recommendations, which made the analysis a time-consuming and complex task. Furthermore, changing 1 recommendation in line with external experts’ suggestions resulted in subsequently having to change other recommendations for coherence and consistency, resulting in a higher number of recommendations that were rewritten. In addition, there was a lack of consensus among external experts, leaving the final decision to the internal experts (us), further contributing to discrepancies.</p>
        <p>Regarding the organization of the recommendations, the division into 2 hierarchical levels based on the specificity/level of detail resulted from the external experts’ feedback and aimed at making the consultation of the list of recommendations easier. This type of hierarchization in levels of detail was also used in previous studies aimed at synthetizing existing guidelines [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        <p>The recommendations were grouped into 12 categories, which closely relate to existing usability principles (feedback, recognition, flexibility, customization, consistency, errors, help, accessibility, navigation, and privacy [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref39">39</xref>]). Usability principles are defined as broad “rules of thumb” or design guidelines that describe features of the systems to guide the design of digital solutions [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Additionally, they are oriented to improve user interaction [<xref ref-type="bibr" rid="ref3">3</xref>] and impact the quality of the digital solution interface [<xref ref-type="bibr" rid="ref41">41</xref>]. Therefore, having the recommendations organized in a way that maps these principles helps facilitate a practical use of the recommendations proposed herein, as these usability principles are familiar to designers and are well established, well known, and accepted in the literature [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref42">42</xref>].</p>
        <p>The results showed an asymmetry in the number of recommendations categorized into each of the 12 usability principles (eg, for level 1, consistency has 2 recommendations while the visual component has 16 recommendations). This discrepancy suggests that some areas of user interface design such as the visual component might be better detailed, more complex, or more valued in the literature, but can also suggest that the initial search might not have been comprehensive enough, as it included a reduced number of databases [<xref ref-type="bibr" rid="ref32">32</xref>]. Nevertheless, the heterogeneity between categories does not influence its relevance, as it is the set of recommendations as a whole that influences the user design interface of a digital solution.</p>
        <p>The number of level 2 recommendations aggregated under each level 1 recommendation is also uneven. Most of the level 2 recommendations that resulted from this study concern web and mobile technologies because their utilization is widespread among the population [<xref ref-type="bibr" rid="ref43">43</xref>] and therefore more likely to have design recommendations reported in the literature [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref44">44</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. On the other hand, emerging technologies like robotics and interaction paradigms (eg, gestures, voice, and feet) represent new challenges for researchers, and recommendations are still being formulated, resulting in a lower number of specific recommendations that are published [<xref ref-type="bibr" rid="ref46">46</xref>-<xref ref-type="bibr" rid="ref49">49</xref>]. Moreover, the level 2 recommendations raised doubts among experts, namely regarding (1) the lack of consensus on whether they were mandatory or not, (2) apparent contradictions between recommendations, and (3) uncertainty regarding the accuracy of some recommendations, particularly those very specific (eg, the recommendations on the size of the buttons in millimeters). These aspects suggest that level 2 recommendations need further validation in future studies. No data was found on how the authors of the recommendations arrived at this level of detail and how the exact recommendation might vary depending on the target users [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref51">51</xref>], the type of technology [<xref ref-type="bibr" rid="ref49">49</xref>], interaction paradigm [<xref ref-type="bibr" rid="ref46">46</xref>], and the context of use [<xref ref-type="bibr" rid="ref52">52</xref>]. Validation of the level 2 recommendations might be performed by gathering expert’s consensus on the adequacy of recommendations by type of technology/interaction paradigm and involving real users to test if the specific user interfaces that fulfill the recommendations improve usability and user experience [<xref ref-type="bibr" rid="ref50">50</xref>,<xref ref-type="bibr" rid="ref53">53</xref>].</p>
        <p>We believe that level 1 recommendations apply to different users, contexts, and technologies/interaction paradigms and that the necessary level of specificity will be given by level 2 recommendations, which can be further operationalized into more detailed recommendations (eg, creating level 3 recommendations under level 2 recommendations). For example, recommendation 1 from the recognition category states that “the system should consider the context of use, using phrases, words, and concepts that are familiar to the users and grounded in real conventions, delivering an experience that matches the system and the real world,” which is an example of applicability to different contexts such as health or education. Similarly, recommendation 1 from the flexibility category states that “the system should support both inexperienced and experienced users, be easy to learn, and to remember, even after an inactive period,” also showing adaptability to different types of users. Nevertheless, the level of importance of each level 1 recommendation might vary. For example, recommendation 6 of the flexibility category, which states that “the system may make users feel confident to operate and take appropriate action if something unexpected happens,” was not considered mandatory by the panel of external experts. However, one might argue that it should be considered mandatory in the field of health, where the feeling of being in control and acting immediately if something unexpected happens is of utmost importance. Therefore, both level 1 and level 2 recommendations require further validation across different types of technology and interaction paradigms but also for different target users and contexts of use. Also required are investigations to determine whether their use results in better digital solutions, and particularly for the health care field, increases adhesion to and effectiveness of interventions.</p>
        <p>In synthesis, although this study constitutes an attempt toward a more standardized approach in the field of user interface design, the set of recommendations presented herein should not be seen as a final set but rather as guides that should be critically appraised by designers according to the context, type of technology, type of interaction, and the end users for whom the digital solution is intended.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The strengths of this proposed set of recommendations are that it was developed based on multiple sources and multiple rounds of experts’ feedback. However, although several experts were involved in different steps of the study, it cannot be guaranteed that the views of the included experts are representative of the views of a broader community of user interface design experts. Another limitation of this study is that the initial search for recommendations might not have been comprehensive enough. Nevertheless, external experts were given the possibility of adding recommendations to the list, and none suggested the need to include additional recommendations. The list of level 2 recommendations is a work in progress that should be further discussed and changed considering the technology/paradigm of interaction. Finally, some types of technologies and interaction paradigms are not represented in the recommendations (eg, virtual reality), and it would be important to have specific recommendations for all types of technologies and interaction paradigms in the future.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Mapping of the categories proposed by the experts and the final categories.</p>
        <media xlink:href="humanfactors_v9i3e37894_app1.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Final list of 69 generic recommendations proposed.</p>
        <media xlink:href="humanfactors_v9i3e37894_app2.docx" xlink:title="DOCX File , 19 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">SHAPES</term>
          <def>
            <p>Smart and Health Ageing through People Engaging in Supportive Systems</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This work was supported by the SHAPES (Smart and Health Ageing through People Engaging in Supportive Systems) project funded by the Horizon 2020 Framework Program of the European Union for Research Innovation (grant agreement 857159 - SHAPES – H2020 – SC1-FA-DTS – 2018-2020).</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="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garrett</surname>
              <given-names>JJ</given-names>
            </name>
          </person-group>
          <article-title>The elements of user experience: user-centered design for the web and beyond</article-title>
          <source>Choice Reviews Online</source>
          <year>2010</year>
          <publisher-loc>Upper Saddle River</publisher-loc>
          <publisher-name>Pearson Education</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stone</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Jarret</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Woodroffe</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Minocha</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>User Interface Design and Evaluation</source>
          <year>2005</year>
          <publisher-loc>Amsterdam, the Netherlands</publisher-loc>
          <publisher-name>Elsevier</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bevana</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kirakowskib</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Maissela</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>What is usability?</article-title>
          <source>Proceedings of the 4th International Conference on HCI</source>
          <year>1991</year>
          <conf-name>4th International Conference on HCI</conf-name>
          <conf-date>September 1-6</conf-date>
          <conf-loc>Stuttgart, Germany</conf-loc>
          <pub-id pub-id-type="doi">10.1201/9781482272574-76</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <source>World Wide Web Consortium (W3C)</source>
          <year>2019</year>
          <access-date>2021-12-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.w3.org/WAI/fundamentals/accessibility-intro/">https://www.w3.org/WAI/fundamentals/accessibility-intro/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stephanidis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <source>User Interfaces for All: Concepts, Methods, and Tools</source>
          <year>2000</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Shneiderman</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <source>Leonardo's Laptop Human Needs and the New Computing Technologies</source>
          <year>2003</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>MIT Press</publisher-name>
        </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>Meiselwitz</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Universal usability: past, present, and future</article-title>
          <source>Found Trends Hum-Comput Interact</source>
          <year>2009</year>
          <volume>3</volume>
          <issue>4</issue>
          <fpage>213</fpage>
          <lpage>333</lpage>
          <pub-id pub-id-type="doi">10.1561/1100000029</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ambrose</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ball</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>The Fundamentals of Graphic Design</source>
          <year>2019</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Bloomsbury Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Morville</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenfeld</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Information Architecture for the World Wide Web: Designing Large-Scale Web Sites</source>
          <year>2006</year>
          <publisher-loc>Sebastopol, CA</publisher-loc>
          <publisher-name>O'Reilly Media</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <source>Usability.gov</source>
          <access-date>2021-05-26</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.usability.gov/how-to-and-tools/methods/user-interface-elements.html">http://www.usability.gov/how-to-and-tools/methods/user-interface-elements.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Billi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Burzagli</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Catarci</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Santucci</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Bertini</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Gabbanini</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Palchetti</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>A unified methodology for the evaluation of accessibility and usability of mobile applications</article-title>
          <source>Univ Access Inf Soc</source>
          <year>2010</year>
          <month>3</month>
          <day>19</day>
          <volume>9</volume>
          <issue>4</issue>
          <fpage>337</fpage>
          <lpage>356</lpage>
          <pub-id pub-id-type="doi">10.1007/s10209-009-0180-1</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iwarsson</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ståhl</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Accessibility, usability and universal design--positioning and definition of concepts describing person-environment relationships</article-title>
          <source>Disabil Rehabil</source>
          <year>2003</year>
          <month>01</month>
          <day>21</day>
          <volume>25</volume>
          <issue>2</issue>
          <fpage>57</fpage>
          <lpage>66</lpage>
          <pub-id pub-id-type="doi">10.1080/dre.25.2.57.66</pub-id>
          <pub-id pub-id-type="medline">12554380</pub-id>
          <pub-id pub-id-type="pii">BFKB31E4W4ER0G65</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Keates</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>When universal access is not quite universal enough: case studies and lessons to be learned</article-title>
          <source>Univ Access Inf Soc</source>
          <year>2018</year>
          <month>10</month>
          <day>16</day>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>133</fpage>
          <lpage>144</lpage>
          <pub-id pub-id-type="doi">10.1007/s10209-018-0636-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Thatcher</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Waddell</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Henry</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Swierenga</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Urban</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Burks</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bohman</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>Constructing Accessible Web Sites</source>
          <year>2002</year>
          <publisher-loc>San Rafael, CA</publisher-loc>
          <publisher-name>Glasshaus</publisher-name>
          <fpage>A</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Accessibility guidelines for information/communication technology (ICT) equipment and services (ISO 9241-20:2008)</article-title>
          <source>International Standards Organization</source>
          <access-date>2021-12-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/40727.html">https://www.iso.org/standard/40727.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <article-title>Guidance on software accessibility (ISO 9241-171:2008)</article-title>
          <source>International Standards Organization</source>
          <access-date>2021-12-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/39080.html">https://www.iso.org/standard/39080.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <article-title>Software engineering quality model (ISO/IEC 9126-1:2001)</article-title>
          <source>International Standards Organization</source>
          <access-date>2021-12-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/22749.html">https://www.iso.org/standard/22749.html</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <article-title>Usability heuristics for user interface design</article-title>
          <source>Nielsen Norman Group</source>
          <access-date>2021-12-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/articles/ten-usabilityheuristics/">https://www.nngroup.com/articles/ten-usabilityheuristics/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vanderheiden</surname>
              <given-names>GC</given-names>
            </name>
          </person-group>
          <article-title>Design for people with functional limitations</article-title>
          <source>Handbook of Human Factors and Ergonomics</source>
          <year>2006</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Wiley</publisher-name>
          <fpage>2052</fpage>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <source>World Wide Web Consortium</source>
          <access-date>2021-12-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.w3.org/TR/WCAG21/">https://www.w3.org/TR/WCAG21/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garett</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Chiu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Young</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>A literature review: website design and user engagement</article-title>
          <source>Online J Commun Medi</source>
          <year>2016</year>
          <volume>6</volume>
          <issue>3</issue>
          <fpage>1</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.29333/ojcmt/2556</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>Matthew-Maich</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Harris</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Ploeg</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Markle-Reid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Valaitis</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahim</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gafni</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Isaacs</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Designing, implementing, and evaluating mobile health technologies for managing chronic conditions in older adults: a scoping review</article-title>
          <source>JMIR mHealth uHealth</source>
          <year>2016</year>
          <month>06</month>
          <day>09</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e29</fpage>
          <pub-id pub-id-type="doi">10.2196/mhealth.5127</pub-id>
          <pub-id pub-id-type="medline">27282195</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>Ahmad</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rextin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Kulsoom</surname>
              <given-names>UE</given-names>
            </name>
          </person-group>
          <article-title>Perspectives on usability guidelines for smartphone applications: An empirical investigation and systematic literature review</article-title>
          <source>Inf Softw Technol</source>
          <year>2018</year>
          <month>02</month>
          <volume>94</volume>
          <fpage>130</fpage>
          <lpage>149</lpage>
          <pub-id pub-id-type="doi">10.1016/j.infsof.2017.10.005</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>Holthe</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Halvorsrud</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Karterud</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hoel</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lund</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Usability and acceptability of technology for community-dwelling older adults with mild cognitive impairment and dementia: a systematic literature review</article-title>
          <source>CIA</source>
          <year>2018</year>
          <month>05</month>
          <volume>Volume 13</volume>
          <fpage>863</fpage>
          <lpage>886</lpage>
          <pub-id pub-id-type="doi">10.2147/cia.s154717</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Abdel-Wahab</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Rai</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Siddhanamatha</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Dodeja</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Suarez-Almazor</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Lopez-Olivo</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>A comprehensive scoping review to identify standards for the development of health information resources on the internet</article-title>
          <source>PLoS One</source>
          <year>2019</year>
          <month>6</month>
          <day>20</day>
          <volume>14</volume>
          <issue>6</issue>
          <fpage>e0218342</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0218342"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0218342</pub-id>
          <pub-id pub-id-type="medline">31220126</pub-id>
          <pub-id pub-id-type="pii">PONE-D-19-05366</pub-id>
          <pub-id pub-id-type="pmcid">PMC6586310</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Al-Razgan</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Khalifa</surname>
              <given-names>HS</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Shahrani</surname>
              <given-names>MD</given-names>
            </name>
          </person-group>
          <article-title>Heuristics for evaluating the usability of mobile launchers for elderly people</article-title>
          <year>2014</year>
          <conf-name>International Conference of Design, User Experience, and Usability</conf-name>
          <conf-date>June 22-27</conf-date>
          <conf-loc>Crete, Greece</conf-loc>
          <fpage>424</fpage>
          <pub-id pub-id-type="doi">10.1007/978-3-319-07668-3_40</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>Farage</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>KW</given-names>
            </name>
            <name name-style="western">
              <surname>Ajayi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Hutchins</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Design principles to accommodate older adults</article-title>
          <source>Glob J Health Sci</source>
          <year>2012</year>
          <month>02</month>
          <day>29</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>2</fpage>
          <lpage>25</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.5539/gjhs.v4n2p2"/>
          </comment>
          <pub-id pub-id-type="doi">10.5539/gjhs.v4n2p2</pub-id>
          <pub-id pub-id-type="medline">22980147</pub-id>
          <pub-id pub-id-type="pmcid">PMC4777049</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Del Ra</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Usability testing essentials</article-title>
          <source>SIGSOFT Softw Eng Notes</source>
          <year>2011</year>
          <month>09</month>
          <day>30</day>
          <volume>36</volume>
          <issue>5</issue>
          <fpage>49</fpage>
          <lpage>50</lpage>
          <pub-id pub-id-type="doi">10.1145/2020976.2021001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Norman</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <source>The Design of Everyday Things</source>
          <year>2013</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>Basic Books</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="web">
          <article-title>Usability guidelines for accessible web design</article-title>
          <source>Nielsen Norman Group</source>
          <year>2001</year>
          <access-date>2021-02-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nngroup.com/reports/usability-guidelines-accessible-web-design/">https://www.nngroup.com/reports/usability-guidelines-accessible-web-design/</ext-link>
          </comment>
        </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>Almao</surname>
              <given-names>EC</given-names>
            </name>
            <name name-style="western">
              <surname>Golpayegani</surname>
              <given-names>F</given-names>
            </name>
          </person-group>
          <article-title>Are mobile apps usable and accessible for senior citizens in smart cities?</article-title>
          <source>Proceedings of the 21st International Conference on Human-Computer Interaction</source>
          <year>2019</year>
          <conf-name>21st International Conference on Human-Computer Interaction</conf-name>
          <conf-date>July 26-31</conf-date>
          <conf-loc>Florida</conf-loc>
          <fpage>357</fpage>
          <lpage>375</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-030-22012-9_26</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <source>SHAPES User Experience Design and Guidelines and Evaluation</source>
          <year>2020</year>
          <access-date>2022-12-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://shapes2020.eu/wp-content/uploads/2020/11/D5.1-SHAPES-User-Experience-and-Guidelines.pdf">https://shapes2020.eu/wp-content/uploads/2020/11/D5.1-SHAPES-User-Experience-and-Guidelines.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Caravau</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Martins</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Almeida</surname>
              <given-names>AMP</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>T</given-names>
            </name>
            <collab>Ribeiro</collab>
            <name name-style="western">
              <surname>Santinha</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Rocha</surname>
              <given-names>NP</given-names>
            </name>
          </person-group>
          <article-title>Procedures of User-Centered Usability Assessment for Digital Solutions: Scoping Review of Reviews Reporting on Digital Solutions Relevant for Older Adults</article-title>
          <source>JMIR Hum Factors</source>
          <year>2021</year>
          <month>01</month>
          <day>13</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>e22774</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://humanfactors.jmir.org/2021/1/e22774/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/22774</pub-id>
          <pub-id pub-id-type="medline">33439128</pub-id>
          <pub-id pub-id-type="pii">v8i1e22774</pub-id>
          <pub-id pub-id-type="pmcid">PMC7840284</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="web">
          <source>SHAPES 2020</source>
          <access-date>2022-09-19</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://shapes2020.eu/">https://shapes2020.eu/</ext-link>
          </comment>
        </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>Bengtsson</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How to plan and perform a qualitative study using content analysis</article-title>
          <source>NursingPlus Open</source>
          <year>2016</year>
          <volume>2</volume>
          <fpage>8</fpage>
          <lpage>14</lpage>
          <pub-id pub-id-type="doi">10.1016/j.npls.2016.01.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chorianopoulos</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>User interface design principles for interactive television applications</article-title>
          <source>Int J Hum Comput Interact</source>
          <year>2008</year>
          <month>07</month>
          <day>30</day>
          <volume>24</volume>
          <issue>6</issue>
          <fpage>556</fpage>
          <lpage>573</lpage>
          <pub-id pub-id-type="doi">10.1080/10447310802205750</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gerhardt‐Powals</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Cognitive engineering principles for enhancing human‐computer performance</article-title>
          <source>Int J Hum Comput Interact</source>
          <year>1996</year>
          <month>04</month>
          <volume>8</volume>
          <issue>2</issue>
          <fpage>189</fpage>
          <lpage>211</lpage>
          <pub-id pub-id-type="doi">10.1080/10447319609526147</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <collab>Shneiderman</collab>
          </person-group>
          <article-title>Designing the user interface: Strategies for effective human-computer interaction</article-title>
          <source>Applied Ergonomics</source>
          <year>1993</year>
          <month>08</month>
          <volume>24</volume>
          <issue>4</issue>
          <fpage>295</fpage>
          <pub-id pub-id-type="doi">10.1016/0003-6870(93)90471-k</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>Lim</surname>
              <given-names>KC</given-names>
            </name>
            <name name-style="western">
              <surname>Selamat</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alias</surname>
              <given-names>RA</given-names>
            </name>
            <name name-style="western">
              <surname>Krejcar</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Fujita</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Usability measures in mobile-based augmented reality learning applications: a systematic review</article-title>
          <source>Appl Sci</source>
          <year>2019</year>
          <month>07</month>
          <day>05</day>
          <volume>9</volume>
          <issue>13</issue>
          <fpage>2718</fpage>
          <pub-id pub-id-type="doi">10.3390/app9132718</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Molich</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Heuristic evaluation of user interfaces</article-title>
          <year>1990</year>
          <conf-name>SIGCHI conference on Human factors in computing systems</conf-name>
          <conf-date>April 1-5</conf-date>
          <conf-loc>Washington, DC</conf-loc>
          <pub-id pub-id-type="doi">10.1145/97243.97281</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Middleton</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Bloomrosen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dente</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Hashmat</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Koppel</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Overhage</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Payne</surname>
              <given-names>TH</given-names>
            </name>
            <name name-style="western">
              <surname>Rosenbloom</surname>
              <given-names>ST</given-names>
            </name>
            <name name-style="western">
              <surname>Weaver</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>American</surname>
              <given-names>MIA</given-names>
            </name>
          </person-group>
          <article-title>Enhancing patient safety and quality of care by improving the usability of electronic health record systems: recommendations from AMIA</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>06</month>
          <volume>20</volume>
          <issue>e1</issue>
          <fpage>e2</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/cgi/pmidlookup?view=long&#38;pmid=23355463"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2012-001458</pub-id>
          <pub-id pub-id-type="medline">23355463</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2012-001458</pub-id>
          <pub-id pub-id-type="pmcid">PMC3715367</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>Nassar</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Common criteria for usability review</article-title>
          <source>Work</source>
          <year>2012</year>
          <volume>41 Suppl 1</volume>
          <fpage>1053</fpage>
          <lpage>7</lpage>
          <pub-id pub-id-type="doi">10.3233/WOR-2012-0282-1053</pub-id>
          <pub-id pub-id-type="medline">22316859</pub-id>
          <pub-id pub-id-type="pii">U5282267NX523131</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <source>International Telecommunication Union</source>
          <access-date>2022-12-14</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.itu.int/en/ITU-D/Regional-Presence/Europe/Documents/Publications/Digital-Trends_Europe-E.pdf">https://www.itu.int/en/ITU-D/Regional-Presence/Europe/Documents/Publications/Digital-Trends_Europe-E.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Roy</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Call</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Abts</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Development of usability guidelines for mobile health applications</article-title>
          <year>2019</year>
          <conf-name>21st International Conference on Human-Computer Interaction</conf-name>
          <conf-date>26-31 July</conf-date>
          <conf-loc>Florida</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-3-030-23525-3_68</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petersen</surname>
              <given-names>GB</given-names>
            </name>
            <name name-style="western">
              <surname>Nielsen</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Olsen</surname>
              <given-names>JV</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>RN</given-names>
            </name>
          </person-group>
          <article-title>Usability guidelines for developing and evaluating web-based mental health intervention: establishing a practical framework</article-title>
          <source>PsyArXiv</source>
          <comment>(forthcoming)</comment>
          <pub-id pub-id-type="doi">10.31234/osf.io/3ewz4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cohen</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Giangola</surname>
              <given-names>JB</given-names>
            </name>
            <name name-style="western">
              <surname>Balogh</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <source>Voice User Interface Design</source>
          <year>2004</year>
          <publisher-loc>Reading, MA</publisher-loc>
          <publisher-name>Addison Wesley</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Neto</surname>
              <given-names>AT</given-names>
            </name>
            <name name-style="western">
              <surname>Bittar</surname>
              <given-names>TJ</given-names>
            </name>
            <name name-style="western">
              <surname>Fortes</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Felizardo</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Developing and evaluating web multimodal interfaces - a case study with usability principles</article-title>
          <source>Proceedings of the 2009 ACM Symposium on Applied Computing</source>
          <year>2009</year>
          <conf-name>2009 ACM Symposium on Applied Computing</conf-name>
          <conf-date>March 12-18</conf-date>
          <conf-loc>New York, NY</conf-loc>
          <pub-id pub-id-type="doi">10.1145/1529282.1529306</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tsiporkova</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tourwé</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>González-Deleito</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Towards a semantic modelling framework in support of multimodal user interface design</article-title>
          <year>2011</year>
          <conf-name>13th IFIP Conference on Human-Computer Interaction</conf-name>
          <conf-date>September 5-9</conf-date>
          <conf-loc>Lisbon, Portugal</conf-loc>
          <pub-id pub-id-type="doi">10.1007/978-3-642-23768-3_101</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sarter</surname>
              <given-names>NB</given-names>
            </name>
          </person-group>
          <article-title>Multimodal information presentation: Design guidance and research challenges</article-title>
          <source>Int J Ind Ergon</source>
          <year>2006</year>
          <month>5</month>
          <volume>36</volume>
          <issue>5</issue>
          <fpage>439</fpage>
          <lpage>445</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ergon.2006.01.007</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Vu</surname>
              <given-names>KPL</given-names>
            </name>
            <name name-style="western">
              <surname>Proctor</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <source>The Handbook of Human Factors in Web Design</source>
          <year>2005</year>
          <publisher-loc>Boca Raton, FL</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref51">
        <label>51</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zajicek</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Interface design for older adults</article-title>
          <source>Proceedings of the 2001 EC/NSF Workshop on Universal Accessibility of Ubiquitous Computing: Providing for the Elderly</source>
          <year>2001</year>
          <conf-name>WUAUC'01</conf-name>
          <conf-date>May 22-25</conf-date>
          <conf-loc>Alcácer do Sal, Portugal</conf-loc>
          <pub-id pub-id-type="doi">10.1145/564526.564543</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref52">
        <label>52</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Badre</surname>
              <given-names>AN</given-names>
            </name>
          </person-group>
          <article-title>Shaping web usability</article-title>
          <source>Ubiquity</source>
          <year>2002</year>
          <month>02</month>
          <volume>2002</volume>
          <issue>February</issue>
          <fpage>1</fpage>
          <pub-id pub-id-type="doi">10.1145/763913.763910</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref53">
        <label>53</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Petrie</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Bevan</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>The evaluation of accessibility, usability, and user experience</article-title>
          <source>The Universal Access Handbook</source>
          <year>2009</year>
          <publisher-loc>Boca Raton, Florida</publisher-loc>
          <publisher-name>CRC Press</publisher-name>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
