![]() In other words, once a user has located a potential record of interest, don’t force them to move their eyes back and forth between column 1 and column 20 because those are the most relevant columns. The default order of the columns should reflect the importance of the data to the user and related columns should be adjacent.This design will allow users to scan and locate a record of interest. The (default ) first column should be a human-readable record identifier instead of a “mystery meat” automatically generated ID. ![]() At one point, the participant engages in a hierarchical search of the table, moving his eyes between the first column, second column, then skipping to the fourth and sixth columns before moving to the next row of data and repeating the procedure.ĭesigning to support this task involves a few different things: ![]() An eyetracking gazeplot shows a participant fixating back and forth between the table’s data and the filters above. The reasons users will choose one of those interactions can be hard to predict and it’s based on the specifics of the data table, as well as on their expectations of what will be the least effortful way to find what they’re looking for. This process might involve filtering, sorting, using a search feature (or using the browser’s built-in CTRL-F feature on the page), or simply visually scanning down the table. When users engage in this type of task, they may seek a specific item (whose name or other pertinent details they already know) or may look for several items that meet a few criteria they have in mind.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |