| Literature DB >> 34566224 |
Amirmasoud Momenipour1, Salvador Rojas-Murillo2, Brandon Murphy3, Priyadarshini Pennathur3, Arunkumar Pennathur3.
Abstract
Study aims were to investigate how usable COVID-19 dedicated state public health websites in the US were, and whether case counts in different geographical regions in the US were related to website usability. 16 state websites representing the 2 highest and the 2 lowest case count states in each region were selected. Five experts used a heuristic evaluation procedure to independently rate all 16 websites on a severity scale of 0-4. Usability criteria published by the US Department of Health and Human Services and criteria on risk communication and data dashboards were used. Analyses involved cross tabulation of usability criteria with case counts, comparison of usability scores using Mood's median tests, test of differences in average usability scores using ANOVA and post-hoc tests, and identification of correlations between case counts and usability scores. Results from the Mood's median test showed that the median usability scores for the states were significantly different from each other at the 5% level of significance (df = 15, chi-square = 38.40; p = 0.001). ANOVA showed statistically significant differences between the mean usability scores for the states at the 5% level of significance (F = 6.33, p < 0.05). Although not statistically significant, results from a correlation analysis between case count and usability scores showed a negative correlation (r = -0.209, p = 0.437) indicating that the higher the case count, the better the usability score. Overall, the websites fared well on usability, but many websites were used as an information and data repository. These websites must communicate infection risk better. RELEVANCE TO INDUSTRY: The study applies to public health agency websites that communicate essential information during a pandemic.Entities:
Keywords: COVID-19; Emergency communication; Heuristic evaluation; Pandemic; Public health websites; Usability
Year: 2021 PMID: 34566224 PMCID: PMC8451240 DOI: 10.1016/j.ergon.2021.103216
Source DB: PubMed Journal: Int J Ind Ergon ISSN: 0169-8141 Impact factor: 2.656
Fig. 1Our study's evaluation and analyses methods architecture.
Fig. 2A snapshot from a consolidated Excel spreadsheet showing our individual ratings and comments for various usability criteria before our reconciliation analyses.
Usability rating scale used in our study.
| Usability rating | Meaning of the rating |
|---|---|
| 0 | Not a usability problem at all |
| 1 | Cosmetic usability problem only; need not be fixed unless extra time is available. |
| 2 | Minor usability problem; fixing this should be given low priority |
| 3 | Major usability problem; fixing this should be given high priority |
| 4 | Usability catastrophe; imperative to fix before release |
Fig. 3A snapshot from a consolidated Excel spreadsheet with our individual ratings and total scores for various usability criteria after our reconciliation analyses.
Assessment agreement consistency ratings and Fleiss Kappa Rates.
| Assessment Agreement Between Evaluators | Fleiss Kappa Rate | |||
|---|---|---|---|---|
| Strength of agreement | Incidence | Percentage | Incidence | Percentage |
| Poor | 0 | 0.0% | 8 | 5.4% |
| Slight | 5 | 3.4% | 9 | 6.1% |
| Fair | 20 | 13.5% | 29 | 19.6% |
| Moderate | 25 | 16.9% | 43 | 29.1% |
| Substantial | 37 | 25.0% | 24 | 16.2% |
| Almost Perfect | 61 | 41.2% | 35 | 23.6% |
Usability criteria with a 0.2 proportion score and above across all states.
| Criteria | Proportion score |
|---|---|
| Designating used links | 0.50 |
| Providing printing options | 0.45 |
| The webpage conveying overall risk information | 0.45 |
| Optimizing display density | 0.43 |
| Availability of page for mobile device viewing | 0.39 |
| Placing primary navigation menus in the left panel | 0.38 |
| Formatting information for reading and printing | 0.36 |
| Organizing information in the content clearly | 0.36 |
| Developing pages that will print properly | 0.32 |
| Ensuring the homepage looks like a homepage | 0.31 |
| Minimizing the number of clicks on pages | 0.30 |
| Using images to facilitate learning | 0.29 |
| Ordering list elements to maximize user performance | 0.28 |
| The data dashboard conveying the state of urgency | 0.28 |
| Enabling access to the homepage | 0.28 |
| Differentiating and grouping navigation elements | 0.27 |
| Providing feedback on user's location | 0.26 |
| Responsiveness to resizing the page on a desktop browser | 0.26 |
| Avoiding cluttered displays | 0.25 |
| Understanding and meeting user expectations | 0.25 |
| Organizing content to facilitate scanning | 0.25 |
| Placing important items at the top center | 0.24 |
| Establishing the levels of importance | 0.23 |
| Reducing the user's workload | 0.23 |
| Displaying information in a directly usable format | 0.22 |
| Using fluid layouts | 0.22 |
| Options to view pages in a language other than English | 0.22 |
| Limiting prose text on the homepage | 0.21 |
| Avoiding misleading cues to click on links | 0.21 |
| The data dashboard having minimalist aesthetics by reducing non-data ink | 0.21 |
Proportion scores for the main usability categories used in the study.
| Usability category | Proportion score |
|---|---|
| Navigation | 0.20 |
| The homepage | 0.17 |
| Page layout | 0.17 |
| Optimizing the user experience | 0.16 |
| Content organization | 0.15 |
| Design process and evaluation | 0.14 |
| Readability, findability, and responsiveness | 0.14 |
| Search | 0.13 |
| Links | 0.13 |
| Dashboard design | 0.12 |
| Lists | 0.12 |
| Headings, titles, and labels | 0.09 |
| Scrolling and paging | 0.08 |
| Text appearance | 0.07 |
| Graphics, images, and multimedia | 0.07 |
| Writing web content | 0.03 |
| Hardware and software | 0.03 |
| Screen-based controls (widgets) | 0.02 |
Usability criteria that obtained an average rating of 4 for at least one of the states that reported either a high case count or a low case count.
| Case count category (high and low) | Usability criteria with an average rating of 4 |
|---|---|
| High | Communicating the website's value and purpose Option to view the website in a language other than English Designing the search engine to search the entire site Providing a search option on each page in the website |
| Low | Option to view the website in a language other than English Designing the search engine to search the entire site Providing a search option on each page in the website Designing search around users' search terms |
Usability criteria that obtained an average rating of 3 for at least one of the states that reported either a high case count or a low case count.
| Case count category (high and low) | Usability criteria with an average rating of 3 |
|---|---|
| High | Presenting tabs effectively Using at least 12-point font Mobile device viewing GIS interface (zooming in and out to view detailed information, and providing situational awareness of activities and trends) Using fluid layouts Designating used links Clarifying clickable regions of images Minimizing user data entry Providing useful content Limiting prose text on the homepage Placing primary navigation menus in the left panel Providing consistent clickability cues Enabling access to the homepage Differentiating and grouping navigation elements |
| Low | Displaying only necessary information Using fluid layouts Desktop browser resizing Mobile device viewing Enabling access to the homepage Including actual data with the data graphics State of urgency (organizing information by color, graphs/trends, emergency/urgent alert that allow user to determine if a state of urgency exists) Supporting correct data interpretation (that is, helping the user understand information and perform actions like meaningful comparisons correctly Placing primary navigation menus in the left panel Differentiating and grouping navigation elements Using appropriate menu types Designating used links Ensuring that website images convey intended messages Enabling usable search results Conveying risk information Aligning items on a page Providing feedback on user's location during navigation |
Fig. 4An example of a well-designed homepage providing direct links (indicated by the red arrows) for language options. This page immediately translated all content into Spanish. The data dashboards also were translated into Spanish. (For interpretation of the references to color in this figure legend, the reader is referred to the Web version of this article.)
Fig. 5a and b representing two cases where the page conveyed overall risk information to the user.
Fig. 6A page with a search function built into the main landing page of the website.
Mood's median test results on median values of the total usability score each of us (5 evaluators) gave each state.
| Region and Case Count Code | Median | N ≤ Overall Median | N > Overall Median | Q3-Q1 | 95% CI on Median |
|---|---|---|---|---|---|
| WH1 | 93 | 1 | 4 | 24.0 | (65, 94) |
| WH2 | 73 | 2 | 3 | 52.0 | (60, 134) |
| WL1 | 54 | 4 | 1 | 30.0 | (32, 78) |
| WL2 | 42 | 5 | 0 | 7.5 | (36, 47) |
| MWH1 | 44 | 4 | 1 | 42.5 | (32, 102) |
| MWH2 | 50 | 5 | 0 | 15.0 | (34, 51) |
| MWL1 | 61 | 3 | 2 | 21.5 | (58, 94) |
| MWL2 | 74 | 1 | 4 | 16.5 | (63, 85) |
| EH1 | 38 | 4 | 1 | 40 | (32, 95) |
| EH2 | 59 | 3 | 2 | 21 | (55, 81) |
| EL1 | 62 | 3 | 2 | 19.0 | (52, 74) |
| EL2 | 54 | 4 | 1 | 13.5 | (52, 74) |
| SH1 | 93 | 0 | 5 | 31.5 | (90, 137) |
| SH2 | 77 | 0 | 5 | 16.0 | (75, 92) |
| SL1 | 106 | 0 | 5 | 20.5 | (93, 127) |
| SL2 | 90 | 1 | 4 | 56.0 | (62, 148) |
Mood's median test results on median values of the total usability score within high case count states. The computation of frequencies in the test are similar to the description for Table 7.
| Region and High Case Count States | Median | N ≤ Overall Median | N > Overall Median | Q3–Q1 | 95% Median CI |
|---|---|---|---|---|---|
| E-H1 | 38.0 | 4 | 1 | 40.0 | (32, 95) |
| E-H2 | 59.0 | 3 | 2 | 21.0 | (55, 81) |
| MW-H1 | 44.0 | 4 | 1 | 42.5 | (32, 102) |
| MW-H2 | 50.0 | 5 | 0 | 15.0 | (34, 51) |
| S–H1 | 93.0 | 0 | 5 | 31.5 | (90, 137) |
| S–H2 | 77.0 | 0 | 5 | 16.0 | (75, 92) |
| W–H1 | 93.0 | 1 | 4 | 24.0 | (65, 94) |
| W–H2 | 73.0 | 3 | 2 | 52.0 | (60, 134) |
Mood's median test results on median values of the total usability score within high case count states. The computation of frequencies in the test are similar to the description for Table 7.
| Region and Low Case Count States | Median | N ≤ Overall Median | N > Overall Median | Q3 – Q1 | 95% Median CI |
|---|---|---|---|---|---|
| E-L1 | 62.0 | 3 | 2 | 19.0 | (52, 74) |
| E-L2 | 54.0 | 4 | 1 | 13.5 | (52, 74) |
| MW-L1 | 61.0 | 3 | 2 | 21.5 | (58, 94) |
| MW-L2 | 74.0 | 0 | 5 | 16.5 | (63, 85) |
| S-L1 | 106.0 | 0 | 5 | 20.5 | (93, 127) |
| S-L2 | 90.0 | 1 | 4 | 56.0 | (62, 148) |
| W-L1 | 54.0 | 4 | 1 | 30.0 | (32, 78) |
| W-L2 | 42.0 | 5 | 0 | 7.5 | (36, 47) |
Fig. 7Normal probability plot for the overall usability scores. Each of the 16 states received a rating for every usability criterion from each of the 5 evaluators for a total of n = 80 sample points for the test of normality.
Fig. 8Anderson-Darling test for normality of the overall usability score.
Analysis of variance.
| Source | df | Adj SS | Adj MS | F-Value | P-Value |
|---|---|---|---|---|---|
| State | 15 | 31669 | 2111.3 | 6.33 | 0.000 |
| Error | 64 | 21336 | 333.4 | ||
| Total | 79 | 53005 |
Tukey's Post-Hoc Pairwise Comparisons of Usability Scores. In the table, W, S, MW and E denote West, South, Midwest and East respectively. H denotes a high case count, and L a low case count. 1 refers to a state, and 2 refers to the second state in that region selected in the study.
| Case Count Classification | Pairwise Differences between states coded by region and case counts | p-value (only the significantly different pairs reported) |
|---|---|---|
| Paired Differences between High and Low Case Count States | WL1-SH1 | 0.007 |
| SL1-EH2 | 0.034 | |
| SL1-MWH2 | 0.000 | |
| SL1-MWH1 | 0.001 | |
| WL2-WH2 | 0.02 | |
| WL2-WH1 | 0.037 | |
| MWH2-SL2 | 0.009 | |
| EH1-SL2 | 0.041 | |
| SL1-EH1 | 0.000 | |
| SH1-WL2 | 0.000 | |
| EL2-SH1 | 0.017 | |
| Paired Differences between Low Case Count States | SL1-EL1 | 0.016 |
| WL2-SL2 | 0.004 | |
| SL1-WL2 | 0.000 | |
| SL1-EL2 | 0.004 | |
| SL1-WL1 | 0.002 | |
| Paired Differences between High Case Count States | SH1-EH1 | 0.002 |
| SH1-MWH2 | 0.000 | |
| SH1-MWH1 | 0.004 | |
| MWH2-WH2 | 0.043 |
Case counts per 10,000 people and average website usability.
| State Population | State Case count (May 2020) | Case Count per 10,000 people | Average Usability | |
|---|---|---|---|---|
| High States | 9,986,857 | 50,079 | 50.144 | 0.075 |
| 19,453,561 | 155,456 | 79.911 | 0.085 | |
| 12,671,821 | 90,369 | 71.314 | 0.088 | |
| 8,882,190 | 143,905 | 162.015 | 0.111 | |
| 21,477,737 | 42,940 | 19.992 | 0.138 | |
| 39,512,223 | 74,936 | 18.965 | 0.141 | |
| 7,278,717 | 13,169 | 18.092 | 0.145 | |
| 28,995,881 | 45,198 | 15.587 | 0.175 | |
| Low States | 4,217,737 | 3541 | 8.395 | 0.069 |
| 7,614,893 | 17,951 | 23.573 | 0.092 | |
| 623,989 | 933 | 14.952 | 0.098 | |
| 3,565,287 | 36,085 | 101.212 | 0.106 | |
| 2,913,314 | 7886 | 27.068 | 0.115 | |
| 5,639,632 | 14,240 | 25.249 | 0.124 | |
| 705,749 | 6871 | 97.357 | 0.156 | |
| 1,792,147 | 1447 | 8.074 | 0.183 |
Fig. 9Correlation between case count per 10,000 people in each of the 16 states, and the average usability score in that state.
| Heuristics Category | Criteria | Relative Importance |
|---|---|---|
| Design Process and Evaluation | 2: Establish user requirements | 5 |
| 4: Involve Users in Establishing User Requirements | 5 | |
| 5: Set and State Goals | 5 | |
| 6: Focus on Performance Before Preference | 4 | |
| 7: Consider Many User Interface Issues | 4 | |
| 9: Set Usability Goals | 3 | |
| 10: Use Parallel Design | 2 | |
| 11: Use Personas | 1 | |
| 2: Optimizing user experience | 13: Do Not Require Users to Multitask While Reading | 3 |
| 4: Hardware and software | 5: Design for Commonly Used Screen Resolutions | 3 |
| 5. The homepage | 9: Attend to Homepage Panel Width | 2 |
| 6: Page layout | 13: Use Frames when Functions Must Remain Accessible | 1 |
| 7: Navigation | 10: Use Site Maps | 2 |
| 11: Use ‘Glosses’ to Assist Navigation | 1 | |
| 12: Breadcrumb Navigation | 1 | |
| 8: Scrolling and Paging | 4: Use Paging Rather Than Scrolling | 2 |
| 9: Headings, titles, and labels | 7: Use Headings in the Appropriate HTML Order | 3 |
| 8: Provide Users with Good Ways to Reduce Options | 2 | |
| 10: Links | 9: Ensure that Embedded Links are Descriptive | 3 |
| 10: Use ‘Pointing-and-Clicking’ | 3 | |
| 11: Text appearance | 9: Color-Coding and Instructions | 2 |
| 12: Lists | 6: Use Static Menus | 3 |
| 7: Start Numbered Items at One | 2 | |
| 8: Use Appropriate List Style | 2 | |
| 9: Capitalize First Letter of First Word in Lists | 1 | |
| 13: Screen-based controls (widgets) | 4: Do Not Make User-Entered Codes Case Sensitive | 4 |
| 5: Label Data Entry Fields Clearly | 4 | |
| 7: Put Labels Close to Data Entry Fields | 3 | |
| 10: Use Familiar Widgets | 3 | |
| 12: Partition Long Data Items | 3 | |
| 13: Use a Single Data Entry Method | 3 | |
| 14: Prioritize Pushbuttons | 3 | |
| 17: Do Not Limit Viewable List Box Options | 3 | |
| 18: Display Default Values | 3 | |
| 19: Place Cursor in First Data Entry Field | 2 | |
| 20: Ensure that Double-Clicking Will Not Cause Problems | 2 | |
| 21: Use Open Lists to Select One from Many | 2 | |
| 22: Use Data Entry Fields to Speed Performance | 2 | |
| 23: Graphics, Images, and Multimedia | 2 | |
| 24: Provide Auto-Tabbing Functionality | 2 | |
| 25: Minimize Use of the Shift Key | 1 | |
| 14: Graphics, images and multimedia | 3: Ensure that Images Do Not Slow Downloads | 4 |
| 9: Limit the Use of Images | 3 | |
| 12: Introduce Animation | 2 | |
| 14: Use Thumbnail Images to Preview Larger Images | 2 | |
| 16: Using Photographs of People | 1 | |
| 15: Writing web content | 8: Limit Prose Text on Navigation Pages | 3 |
| 9: Use Active Voice | 3 | |
| 10: Write Instructions in the Affirmative | 3 | |
| 17: Search | 3: Make Upper- and Lowercase Search Terms Equivalent | 4 |
| 6: Allow Simple Searches | 3 | |
| 8: Include Hints to Improve Search Performance | 3 | |
| 9: Provide Search Templates | 2 | |
| 18: Findability | 6: Presence of legacy sites |