One challenging aspect of web usability testing is that the vast number of variables that come into play can create problems of interpretation with the results. One approach that can begin to address these challenges is to code and categorize specific sub-parts of web apps to better understand common usage and application.
For example, coding the sub-sets of text within selected Web-based forms would allow for greater insight into the preferred structures and styles. Further, this coding practice could provide a key or map to relate with effective practice. One form of text that could be studied and coded is assistive text, such as a set of initial instructions or input field validation messages, which are currently used in most web-based forms and can be referred to collectively as microcopy (Porter).
In terms of researching this issue, the primary, initial focus revolves around the question of what forms of microcopy are most commonly used in web-based forms, specifically in regards to structure and style. The presumption would be that most uses of microcopy would not be exactly duplicated and style and formatting would vary for most forms. The presumption is based on experience in developing hundreds of Web-based forms for organizations, including three healthcare-focused organizations, as well as the lack of technical group, governing body or authority on standard usage of microcopy and related form information. For example, the foundational elements of most web technologies are specifications, such as the HTML specification, and are set by groups like the W3C . In the case of the HTML spec, there are a strict set of rules for use and understanding in order to deliver an expected result. In the case of microcopy, however, no such standards or rules yet exist in a commonly agreed upon fashion.
In the second part of the post, I’ll discuss the details of methods used to survey a small sample of forms as well as the observations, challenges, results and possiblities for future study.
Use of Microcopy in Request for Appointment Forms, part 1
One challenging aspect of web usability testing is that the vast number of variables that come into play can create problems of interpretation with the results. One approach that can begin to address these challenges is to code and categorize specific sub-parts of web apps to better understand common usage and application.
For example, coding the sub-sets of text within selected Web-based forms would allow for greater insight into the preferred structures and styles. Further, this coding practice could provide a key or map to relate with effective practice. One form of text that could be studied and coded is assistive text, such as a set of initial instructions or input field validation messages, which are currently used in most web-based forms and can be referred to collectively as microcopy (Porter).
In terms of researching this issue, the primary, initial focus revolves around the question of what forms of microcopy are most commonly used in web-based forms, specifically in regards to structure and style. The presumption would be that most uses of microcopy would not be exactly duplicated and style and formatting would vary for most forms. The presumption is based on experience in developing hundreds of Web-based forms for organizations, including three healthcare-focused organizations, as well as the lack of technical group, governing body or authority on standard usage of microcopy and related form information. For example, the foundational elements of most web technologies are specifications, such as the HTML specification, and are set by groups like the W3C . In the case of the HTML spec, there are a strict set of rules for use and understanding in order to deliver an expected result. In the case of microcopy, however, no such standards or rules yet exist in a commonly agreed upon fashion.
In the second part of the post, I’ll discuss the details of methods used to survey a small sample of forms as well as the observations, challenges, results and possiblities for future study.