Junko Shirogane

Method to improve accessibility of rich internet applications

Currently numerous websites contain dynamic content, but it is difficult to create accessible websites with dynamic content compared to those with static content. Because many platforms can realize Rich Internet Applications (RIAs), it is important that this type of dynamic content become accessible. We propose a method to improve accessibility of RIAs. Our method consists of two phases. In the first phase, we develop libraries to realize accessibility of RIAs. In the second phase, the libraries are automatically applied to RIAs. As an example of platforms that realize RIAs, our research focuses on JavaFX Script.

Support method of usability evaluations for android applications based on operation histories

Due to the prevalence of tablets, the usability of the User Interfaces (UIs) must be improved, but the number of support methods for usability evaluations for tablets is small. Herein we propose a method to automatically evaluate usability based on operation histories, including action frequency and operation times, and statistical analysis. Because our approach easily detects UI design problems, the burdens on developers and costs can be reduced. Using a small-scale case study and test with about 20 participants, we show that our approach can detect detailed problems with usability via a mostly automated process.

GUI prototype generation from scenarios in the requirements elicitation phase

In the requirements elicitation phase, operation flows of software are often defined by scenarios. It is necessary to define appropriate operation flows as scenarios in terms of easily comprehended operation flows, efficiency, etc. Then scenarios are implemented as software Graphical User Interfaces (GUIs). If the operation flows are defined inappropriately, the implemented GUIs may require modifications in the late software development phase. Although defining appropriate operation flows is difficult in the requirements elicitation phase, operation flows of GUIs cannot be always modified in the late software development phase. Thus, it is necessary for end users to evaluate the appropriateness of operation flows in scenarios. Herein we propose a method to generate GUI prototypes from scenarios. By parsing the events in the target scenarios, which are written in a natural language, GUI prototypes are automatically generated. Using the generated GUI prototypes, the appropriateness of operation flows can be evaluated by end users. If problems arise, the GUI prototypes can be modified in the early requirements elicitation phase.

Support Method to Elicit Accessibility Requirements

Various accessibility guidelines have been developed to meet the increased demand for accessible software, but due to the numerous elements within these guidelines, applying all elements to target software is burdensome and expensive. Additionally, whether all the elements should be applied depends on the software’s purpose and target end users, who do not often clearly recognize difficulties. Moreover, accessibility requirements elicited in the late software development phase cannot always be applied. To ensure that these requirements are implemented properly, they must be elicited in the early software development phase by considering end users’ conscious and unconscious characteristics. Here a method to elicit accessibility requirements in the early software development phase is proposed. Specifically, end users complete checklists, which are designed to determine disabilities with respect to guidelines. Then guideline elements are prioritized and applied to the target software as specified by the accessibility requirements.

Web accessibility support for visually impaired users using link content analysis

Web pages are used for a variety of purposes. End users must understand dynamically changing content and sequentially follow page links to find desired material, requiring significant time and effort. However, for visually impaired users using screen readers, it can be difficult to find links to web pages when link text and alternative text descriptions are inappropriate. Our method supports the discovery of content by analyzing 8 categories of link types, and allows visually impaired users to be aware of the content represented by links in advance. This facilitates end users access to necessary information on web pages. Our method of classifying web page links is therefore effective as a means of evaluating accessibility.

GUI Change Method according to Roles of Widgets and Change Patterns

To develop usable software, it is necessary to develop Graphical User Interfaces (GUIs) in iterative steps, such as evaluating the usability of GUIs and improving GUIs. In improving GUIs, developers are often required to modify both the GUI and the logic code of the software. In our research, to facilitate GUI improvement, we propose a method of automatically searching for code to be modified and suggesting how to modify them. To search for appropriate code to be modified, we define the roles of widgets according to their purpose and the patterns for how to change GUIs. In our method, how to change GUIs is specified, and then the parts of source programs that are required to be modified are searched for. Also, we classify methods for each widget according to their functions. Using this classification, a method of modifying the code that is searched for is suggested.

Automatic generation of tutorial systems from development specification

Recent complicated software functions have made it difficult for end users to operate them. Thus, it becomes important to learn how to operate them easily and effectively. Employing a tutorial system is the most suitable approach for learning how to operate software functions. A tutorial system demonstrates the how to operate using the actual software. As a result, end users can learn the usage as if they were actually using the software. However, development of tutorial systems requires much time and costs. Therefore, we propose a method of generating tutorial systems based on use case diagrams, sequence diagrams and test cases. In our method, a generated tutorial system shows function names extracted from use case diagrams, the how to operate along with sequence diagrams, and text string input and item selection using data from test cases. The generated tutorial system is then added to the source code for use in AOP (aspect-oriented programming).

Notification messages considering human centered design

Messages to notify users of application states (hereafter notification messages) such as error, warning, confirmation, and information messages are often used in user interfaces. Generally, error messages are the most critical, while information messages are the least. However, the types of notification messages are determined in terms of what the application can or cannot process successfully instead of what the users feel are the most critical issues. Currently, human centered design (HCD) focuses on users’ aspects. HCD emphasizes users in application development to realize a high usability. Thus, we propose a strategy to realize notification messages considering HCD. Concretely, we analyze existing notification messages in terms of the criticality level by users and define new types of notification messages. In addition, we develop guidelines to implement notification messages effectively. Our strategy allows users to be appropriately notified based on the criticality.

Automatic generation of an operation procedure presentation system reusing user's input data

Users use software applications to achieve a goal. Occasionally they make mistakes in the operation path due to the complexity of large-scale applications, which requires them to back track to the appropriate operation step and reenter previously input data. This is burdensome for users. Herein a method is proposed to generate an operation support system that reuses previously input data in an inappropriate operation path as much as possible by navigating users to the appropriate operation path. Specifically, our method has an input reuse function for copying previously input data to similar input items as well as an operation procedure presentation function to highlight the operation procedure from the current step to the goal. Our integrated operation support can minimize users’ rework. To generate our system, developers must create an ontology, including concepts of label names of input items, correspondence between input items and label names, an activity diagram of the target application, and the operation procedure. Our system uses this information to compute the similarity of label names between input items, copy input data for similar input items, and present operation procedures to users.

Method to Define User Interfaces in the Requirements Analysis Phase

Many requirements for quality in use are elicited in the late development phase. However, if requirements are elicited in the late development phase, the development may return to the previous phase or some requirements cannot be realized due to costs and schedules. To reduce these cases, we propose a method to elicit the requirements in the requirements analysis phase. First, software developers analyze the user characteristics (UCs) of the target users and specify important quality characteristics (QCs) for quality in use and UI design items based on the relationships among UC, QC, and UI design items. Because UI design items are considerations to develop UIs, the specified UI design items are elicited as UI requirements. Thus, when important QCs are specified, UI requirements can be easily elicited by tracing the relationships from QCs to UI design items.