| Literature DB >> 30634581 |
Julia Kupis1, Sydney Johnson2, Gregory Hallihan3, Dana Lee Olstad4.
Abstract
The Automated Self-Administered Dietary Assessment Tool (ASA24) is a web-based tool that guides participants through completion of a 24-h dietary recall and automatically codes the data. Despite the advantages of automation, eliminating interviewer contact may diminish data quality. Usability testing can assess the extent to which individuals can use the ASA24 to report dietary intake with efficiency, effectiveness, and satisfaction. This mixed-methods study evaluated the usability of the ASA24 to quantify user performance and to examine qualitatively usability issues in a sample of low-income adults (85% female, 48.2 years on average) participating in a nutrition coupon program. Thirty-nine participants completed a 24-h dietary recall using the ASA24. Audio and screen recordings, and survey responses were analyzed to calculate task times, success rates, and usability issue frequency. Qualitative data were analyzed thematically to characterize usability issues. Only one participant was able to complete a dietary recall unassisted. We identified 286 usability issues within 22 general usability categories, including difficulties using the search function, misunderstanding questions, and uncertainty regarding how to proceed to the next step; 71.4% of participants knowingly misentered dietary information at least once. Usability issues may diminish participation rates and compromise the quality of ASA24 dietary intake data. Researchers should provide on-demand technical support and designers should improve the intelligence and flexibility of the ASA24's search functionality.Entities:
Keywords: 24-h dietary recall; Automated Self-Administered Dietary Assessment Tool (ASA24); dietary assessment; human factors; low socioeconomic status; usability
Mesh:
Year: 2019 PMID: 30634581 PMCID: PMC6357069 DOI: 10.3390/nu11010132
Source DB: PubMed Journal: Nutrients ISSN: 2072-6643 Impact factor: 5.717
Moderator-participant interactions and data sources in the three session types.
| Moderator Probing | Participant Think-Aloud | Audio and Screen Recording | Survey Completion Data | |
|---|---|---|---|---|
| Unmoderated | × | × | × | ✓ |
| Semi-Moderated | × | × | ✓ | ✓ |
| Moderated | ✓ | ✓ | ✓ | ✓ |
Figure 1Participant tasks and sub-tasks while completing a dietary recall with the Automated Self-Administered Dietary Assessment Tool (ASA24).
Participant characteristics according to moderation group.
| Moderated ( | Semi-Moderated ( | Unmoderated 1 ( | Total ( | |
|---|---|---|---|---|
|
| 43.9 ± 20.3 | 43.5± 17.7 | 57.2 ± 18.4 | 48.2 ± 19.0 |
|
| 4 (40.0) | 4 (33.3) | 7 (58.3) | 15 (44.1) |
|
| 6 (60.0) | 8 (66.7) | 5 (41.7) | 19 (55.9) |
|
| ||||
| Women | 7 (70.0) | 10 (83.3) | 12 (100.0) | 29 (85.3) |
| Men | 3 (30.0) | 2 (16.7) | 0 (0.0) | 5 (14.7) |
|
| ||||
| Excellent | 0 (0.0) | 1 (8.3) | 0 (0.0) | 1 (2.9) |
| Very Good | 0 (0.0) | 1 (8.3) | 3 (25.0) | 4 (11.8) |
| Good | 8 (80.0) | 7 (58.3) | 7 (58.3) | 22 (64.7) |
| Fair | 1 (10.0) | 3 (25.0) | 2 (16.7) | 6 (17.7) |
| Poor | 1 (10.0) | 0 (0.0) | 0 (0.0) | 1 (2.9) |
|
| ||||
| Less than high school | 1 (10.0) | 3 (25.0) | 4 (33.3) | 8 (23.5) |
| High school | 5 (50.0) | 1 (8.3) | 0 (0.0) | 6 (17.6) |
| Trade certificate/diploma | 1 (10.0) | 3 (25.0) | 0 (0.0) | 4 (11.8) |
| Certificate or diploma below Bachelor’s | 3 (30.0) | 4 (33.3) | 7 (58.3) | 14 (41.9) |
| Bachelor’s degree | 0 (0.0) | 0 (0.0) | 1 (8.3) | 1 (2.9) |
| Above Bachelor’s degree | 0 (0.0) | 1 (8.3) | 0 (0.0) | 1 (2.9) |
|
| ||||
| Full-time employment | 0 (0.0) | 2 (16.7) | 2 (16.7) | 4 (11.8) |
| Part-time employment | 1 (10.0) | 1 (8.3) | 1 (8.3) | 3 (8.8) |
| Unemployed: Looking for work | 1 (10.0) | 0 (0.0) | 1 (8.3) | 2 (5.9) |
| Unemployed: Not looking for work | 0 (0.0) | 4 (33.3) | 2 (16.7) | 6 (17.7) |
| Student | 1 (10.0) | 0 (0.0) | 0 (0.0) | 1 (2.9) |
| Retired | 3 (30.0) | 1 (8.3) | 5 (41.7) | 9 (26.5) |
| Other | 4 (40.0) | 4 (33.3) | 1 (8.3) | 9 (26.5) |
|
| 5 (50.0) | 7 (58.3) | 5 (41.7) | 17 (50.0) |
|
| ||||
| Native Canadian | ||||
| Immigrant: English-speaking country | 9 (90.0) | 12 (100) | 10 (83.3) | 31 (91.2) |
| Immigrant: Non-English- | 1 (10.0) | 0 (0.0) | 2 (16.7) | 3 (8.8) |
| speaking country | 0 (0.0) | 0 (0.0) | 0 (0.0) | 0 (0.0) |
|
| ||||
| Single, never married | 1 (10.0) | 4 (33.3) | 4 (3.3) | 9 (26.5) |
| Living common-law | 3 (30.0) | 1 (8.3) | 0 (0.0) | 4 (11.8) |
| Married | 1 (10.0) | 2 (16.7) | 1 (8.3) | 4 (11.8) |
| Separated | 2 (20.0) | 2 (16.7) | 0 (0.0) | 4 (11.8) |
| Divorced | 3 (30.0) | 1 (8.3) | 6 (50.0) | 10 (29.4) |
| Widowed | 0 (0.0) | 1 (8.3) | 1 (8.3) | 2 (5.9) |
| Did not answer | 0 (0.0) | 1 (8.3) | 0 (0.0) | 1 (2.9) |
|
| ||||
| Food secure | 1 (10.0) | 1 (8.3) | 3 (25.0) | 5 (14.7) |
| Marginally food insecure | 2 (20.0) | 2 (16.7) | 0 (0.0) | 4 (11.8) |
| Moderately food insecure | 3 (30.0) | 3 (25.0) | 7 (58.3) | 13 (38.2) |
| Severely food insecure | 4 (40.0) | 6 (50.0) | 2 (16.7) | 12 (35.3) |
|
| ||||
| Yes | 8 (80.0) | 11 (91.7) | 12 (100.0) | 31 (91.2) |
| No | 2 (20.0) | 0 (0.0) | 0 (0.0) | 2 (5.9) |
| Did not answer | 0 (0.0) | 1 (8.3) | 0 (0.0) | 1 (2.9) |
|
| ||||
| Computer | 7 (58.3) | 7 (58.3) | ||
| Smartphone | 3 (25.0) | 3 (25.0) | ||
| No Preference | 2 (16.7) | 2 (16.7) | ||
| Did not answer | 1 (8.3) | 1 (8.3) |
1 Not all participants in the unmoderated group completed the sociodemographic questionnaire; 2 Some participants chose both computer and smartphone as preferred methods to access the internet.
Figure 2Task success rates for the three groups: unmoderated (n = 17), semi-moderated (n = 12), and moderated (n = 10).
Figure 3Average task completion times for each task in the moderated (n = 10) and semi-moderated (n = 11) groups. Error bars represent one standard deviation above and below the mean.
Figure 4Average number of individual usability issues encountered by participants in the moderated (n = 10) and semi-moderated (n = 11) groups across all four tasks in the ASA24. Error bars represent one standard deviation above and below the mean.
Figure 5Proportional frequency (%) of each general usability issue across all ASA24 tasks for participants in the moderated (n = 10) and semi-moderated (n = 11) groups.
Figure 6Percentage (%) of participants in the semi-moderated (n = 11) and moderated (n = 10) groups that were observed being affected by each general usability issue at least once.
Descriptions and examples of usability issues related to Effectiveness.
| Usability Issue | Definition | Example/Application |
|---|---|---|
| Question not completed—unknown to user | User does not answer questions because they do not realize they are mandatory. | Occurred most often in the “frequently forgotten foods” section in which some participants did not realize they had to respond to each question and not just the questions they found applicable (although the system later forced them to provide an answer). |
| Undo/go back function unclear | It is unclear to user how to undo an action or revert back to a previous screen. | Occurred when participants wanted to edit a meal that had already been submitted as well as general confusion whilst navigating through the tool. |
| Next step unclear | User is confused about how to proceed, particularly when transitioning from one task to the next. | The language on some buttons did not match the participant’s expectations (e.g., the button to begin adding details read “add details” but participants expected to click a button labeled “next”). Buttons were also often located “below the fold” meaning that participants had to scroll down to see them. |
| How to complete task unclear | User knows what goal they want to accomplish but are unsure how to do so. | Many participants were unsure how to begin entering their meals or had other questions about how to do so. For example, “I made pizza last night so do they want me to put in pizza dough, sauce, cheese?” |
| Submits incorrect information—unknown to user | User misinterprets task and enters incorrect information but do not realize that they have made an error. | Occurred most often when participants were entering food items. Most of these issues were clear to the moderators. However, when moderators suspected that participants had entered something incorrectly without realizing it, they asked the participant to clarify what they had intended to do. For example, entering “coconut” instead of “coconut sugar”, but believing they had entered coconut sugar. |
| Question skipped | User chooses not to answer a question. | Occurred when participants decided not to answer a question that was asked (although the system later forced them to provide an answer). |
| Descriptive entered with food item | User enters either the size, amount, number of food items, or other adjectives in the search bar along with the item itself. | Occurred when entering foods in the search bar (the ASA24 does not recognize adjectives). For example, searching for “cold cereal” instead of “cereal”. |
| String of items entered in search bar | User enters several food items into the search bar, not realizing that items must be entered individually. | Occurred when entering foods in the search bar. For example, entering “eggs and toast and water and coffee” into the search bar. |
Descriptions and examples of usability issues related to Efficiency.
| Usability Issue | Definition | Example/Application |
|---|---|---|
| User-specific terminology missing | Users search for food items in terms familiar to them that the system did not recognize. | Occurred when entering foods in the search bar. For example, searching for “Palm Bay” instead of the system recognized “vodka cooler”. |
| System asks irrelevant question | User is asked questions that are not relevant based on answers they have previously given. | Occurred most frequently during “add details” tasks. For example, asking participants where they obtained the ingredients for their tap water. |
| Search item missing/inaccurate | Users search for food items in common language but the system returns either no results or inaccurate results. | Occurred when entering foods in the search bar. See |
| Next button results in lost content | Users proceed to the next task without correctly submitting the previous task. After realizing the error and reverting back, content previously entered has been lost. | Occurred most often when participants selected “finish with this meal” (similar to the function of a “next” button) before correctly adding all food items to the meal. |
| Submits incorrect information—known to user | Users deliberately enter incorrect information as determined via the participant’s verbalization that they were doing so. | Occurred in situations where the participant felt it was too much work to enter the information accurately, because they weren’t sure what the correct information was, or because they wanted to enter the information accurately but did not know how to do so. For example, “This is assuming I only had one burger so I am just going to say 3 patties because realistically I had 3 burgers.” |
| Misclick | Users click in a location that is different from where they need to click to accomplish a task. | Occurred often when the participants clicked “next”, which took them to the “add details” task when they had not finished reporting all of their meals. |
| Misspell | User makes a spelling mistake when searching for or entering a food item. | Occurred when entering foods in the search bar or via free text. |
| Filter results feature used incorrectly | User misinterprets the list of food items returned from search and/or uses it incorrectly. | Occurred when participants reviewed the list of food items returned from search. For example, the ASA24 offers functionality to filter the search results. One participant interpreted those filter options as ingredients for the food items they were entering, which resulted in confusion. |
Food items searched by the user that did not return the desired result, and the resulting food item selected by the user.
| Food Item Searched by User | Food Item(s) Selected by User |
|---|---|
| Apricots | Could not/did not enter item |
| Greek yogurt | Fruit-flavoured yogurt |
| Coconut cookie | Sugar cookie |
| English muffin | Multigrain bread |
| Cherries | Fruit salad |
| Coconut sugar | Coconut |
| Green smoothie | Fruit smoothie |
| Spring water | Bottled water |
| Gluten free bread | Whole wheat bread |
| Garlic powder | Could not/did not enter item |
| French vanilla cream | Half and half cream |
| Rice bowl | Could not/did not enter item |
| Chocolate covered almonds | Candy |
| Salt | Could not/did not enter item |
| Pepper | Could not/did not enter item |
| Chipotle steak sandwich | Steak |
| Tacos | Taco |
| Onion (as addition to hamburger) | Could not/did not enter item |
| Tomato (as addition to hamburger) | Could not/did not enter item |
| Dill pickle (as addition to hamburger) | Could not/did not enter item |
Descriptions and examples of usability issues related to Satisfaction.
| Usability Issue | Definition | Example/Application |
|---|---|---|
| Desired answer option not available | Response options did not reflect the desired response options of the user | Occurred most frequently when answering whether the amount of food eaten was “usual”, “much more than usual”, or “much less than usual”. Many participants felt that “more than usual” or “less than usual” would have provided a more accurate picture of the quantity eaten. |
| Desired system feature not available | System features do not allow users to report intake accurately in a convenient way | Many participants wanted an easier way to accurately represent their diet than what was offered by the system. For example, many wanted to report water consumed intermittently throughout the day as opposed to entering each instance of water consumption individually. |
Descriptions and examples of usability issues related to Comprehension.
| Usability Issue | Definition | Example/Application |
|---|---|---|
| Question not understood | Users do not understand the meaning of a question | Participants often misunderstood questions. This occurred most frequently during the “add details” task, when the system switched from requesting details about one item, to requesting details about another, but participants did not notice that they were now being asked to add details of a new food item. |
| Terminology not understood | Users do not understand the terminology contained within a question | Participants often did not understand specific words used in certain questions. For example, when users were asked to report meals, both “dinner” and “supper” were response options which led to user confusion. |
| Example answers not available | Users are not presented with the same answer options as presented in the question | There was a mismatch between the way some questions were phrased and the available response options. For example, one participant was asked “String cheese: was it regular, reduced fat, low fat, non-fat, or something else?” and the answer options in the dropdown menu were “part skim”, “other”, and “don’t know”. |
| Food images confusing | Food images are not representative of items actually consumed | Occurred when food images did not resemble the items that participants had eaten. For example, one participant who had sliced their zucchini lengthwise became confused when the system showed a zucchini that was sliced width-wise. |