Measuring user rated language quality: Development and validation of the user interface Language Quality Survey (LQS)

Written text plays a special role in user interfaces. Key information in interaction elements and content are mostly conveyed through text. The global context, where software has to run in multiple geographical and cultural regions, requires software developers to translate their interfaces into many different languages. This translation process is prone to errors – therefore the question of how language quality can be measured is important. This paper presents the development of a questionnaire to measure user interface language quality (LQS). After a first validation of the instrument with 843 participants, a final set of 10 items remained, which was tested again (). The survey showed a high internal consistency (Cronbach׳s α) of .82, acceptable discriminatory power coefficients (.34–.47), as well as a moderate average homogeneity of .36. The LQS also showed moderate correlation to UMUX, an established usability metric (convergent validity), and it successfully distinguished high and low language quality (discriminative validity). The application to three different products (YouTube, Google Analytics, Google AdWords) revealed similar key statistics, providing evidence that this survey is product-independent. Meanwhile, the survey has been translated and applied to more than 60 languages

Response to the Reviews on Bargas-Avila et al. (2009) ‘Intranet Satisfaction Questionnaire: Development and Validation of a Questionnaire to Measure User Satisfaction with the Intranet'

This article contains the response to the reviews regarding the development and validation of the Intranet Satisfaction Questionnaire (ISQ), which measures user satisfaction with the Intranet. Where appropriate additional data analysis and interpretation is provided, the data show further evidence for the good validity, reliability and sensitivity of this tool. In addition, we provide a short preview of a follow-up publication and show that the ISQ can differentiate effectively between bad and good Intranet

User-friendly locations of error messages in web forms: Put them on the right side of the erroneous input field

There are many ways of placing error messages in web forms. A study of web conventions shows that the most common approach is to display error messages embedded in the form at the top of the entire form. Six frequent locations (right, left, above and below the erroneous input field, as well as on the top and at the bottom of the form) were tested in an online study with n = 303 participants. Results of efficiency, effectiveness and satisfaction show that the locations near the erroneous input field lead to a significantly better performance than the error messages on the top and at the bottom of the form; in addition error messages on the right side of the erroneous input field were subjectively evaluated as the most satisfying and intuitive by participants. The results indicate possible improvements for online shops, where error messages are currently mostly placed on the top of the for

Enhancing online forms: Use format specifications for fields with format restrictions to help respondents

Field format restrictions are often used in online forms to impose certain formatting and content rules on users, such as minimum password length or date entry format. In this study, the question whether and how format restrictions for fields in online forms should be communicated to Internet users was explored. In an online study with n = 166 participants, four ways to communicate format restrictions were investigated: (1) no visual format restriction, (2) format examples, (3) format specifications, and (4) both format restrictions (examples and specifications). Results show that providing details of any format restriction to users in advance leads to significantly fewer errors and trials. The most efficient way to communicate field format restrictions to users is by stating the imposed rule (format specification). Providing an additional example neither helps nor constrains user

Designing usable web forms: empirical evaluation of web form improvement guidelines

This study reports a controlled eye tracking experiment (N = 65) that shows the combined effectiveness of 20 guidelines to improve interactive online forms when applied to forms found on real company websites. Results indicate that improved web forms lead to faster completion times, fewer form submission trials, and fewer eye movements. Data from subjective questionnaires and interviews further show increased user satisfaction. Overall, our findings highlight the importance for web designers to improve their web forms using UX guidelines

Usable error message presentation in the World Wide Web: Do not show errors right away

Online form validation can be performed in several ways. This article discusses two empirical studies with 77 and 90 participants, which have found evidence that the best way of presenting error messages is to provide the erroneous fields after users have completed the whole form. Immediate error feedback recommended by the International Organization for Standardization (ISO) showed the worst performance in these studies. Where presented with immediate feedback, users often simply ignored the messages on the screen and continued completing the form as if nothing happened. These results lead to the postulation of the "Modal Theory of Form Completion”: Users are in either "Completion” or "Revision Mode” when filling out online forms. These modes affect the users' way of interaction with the system: During Completion Mode the users' disposition to correct mistakes is reduced, therefore error messages are often ignore

Error prevention in online forms: Use color instead of asterisks to mark required-fields

In this study, a simple but important user interface design choice is examined: when marking required-fields in online forms, should GUI designers stick with the often used asterisk that many form design guidelines cite as the de-facto web standard, or should they choose a colored background as a new design solution to visually signal which input fields are required? An experiment with 24 participants was conducted to test the hypotheses that efficiency, effectiveness and satisfaction ratings of colored required-fields exceed those of asterisk-marked required-fields. Results indicate that colored required field marking leads to fewer errors, faster form fill-in in and higher user satisfactio

Mental models for web objects: Where do users expect to find the most frequent objects in online shops, news portals, and company web pages?

In interface development, it is crucial to reflect the users' expectations and mental models. By meeting users' expectations, errors can be prevented and the efficiency of the interaction can be enhanced. Applying these guidelines to website development reveals the need to know where users expect to find the most common web objects like the search field, home button or the navigation. In a preliminary online study with 136 participants, the most common web objects were identified for three web page types: online shops, news portals, and company web pages. These objects were used for the main study, which was conducted with 516 participants. In an online application, prototypical websites had to be constructed by the participants. Data analysis showed that Internet users have distinct mental models for different web page types (online shop, news portal, and company web page). Users generally agree about the locations of many, but not all, web objects. These mental models are robust to demographic factors like gender and web expertise. This knowledge could be used to improve the perception and usability of website

The organization of interaction design pattern languages alongside the design process

This work explores the possibility of taking the structural characteristics of approaches to interaction design as a basis for the organization of interaction design patterns. The Universal Model of the User Interface (Baxley, 2003) is seen as well suited to this; however, in order to cover the full range of interaction design patterns the model had to be extended slightly. Four existing collections of interaction design patterns have been selected for an analysis in which the patterns have been mapped onto the extended model. The conclusion from this analysis is that the use of the model supports the process of building a pattern language, because it is predictive and helps to complete the language. If several pattern writers were to adopt the model, a new level of synergy could be attained among these pattern efforts. A concluding vision would be that patterns could be transferred freely between pattern collections to make them as complete as possibl