CN101419528B - Data processing device - Google Patents

Abstract

A data processing device includes a display unit, a user type determination unit and a display control unit. The display unit displays display data including first display data for a visually impaired user and second display data for a visually impaired user. The user type determination unit determines whether the user is visually impaired or sees. The display control unit controls the display unit so as to display the first display data when the user type determination unit determines that the user is visually impaired, and when the user type determination unit determines that the user can see The second display data is displayed.

Description

data processing device

Cross References to Related Applications

This application claims priority from Japanese Patent Application No. 2007-276110 filed on October 24, 2007 and Japanese Patent Application No. 2007-305558 filed on November 27, 2007. The entire contents of each of these priority applications are hereby incorporated by reference.

technical field

The invention relates to a data processing device and a data processing system.

Background technique

A conventional data processing program called a screen reader is used to convert text data displayed on a personal computer (hereinafter referred to as "PC") into sounds that can be played audibly to assist people with visual impairments to use Ordinary PCs. One such data processing program designed to support the use of a PC by the visually impaired is disclosed in Japanese Unexamined Patent Application Publication No. 2002-288071. Such a program provides a display area within an operation screen of a browser for acquiring and displaying World Wide Web (WWW) data. The display area is used to display menus with links or other data, so that users with visual impairment can obtain WWW data through simple operations. When the browser acquires menu data for visually impaired users other than WWW data, the program can display this menu data within the browser's operation screen, making the browser more user-friendly for visually impaired users. The browser audibly renders menu data for visually impaired users displayed within the browser window, while the screen reader audibly renders WWW data.

However, in the technique of Japanese Unexamined Patent Application Publication No. 2002-288071, menu items for visually impaired users displayed in the browser are also included in WWW data displayed on the browser. Therefore, the user hears the same data being repeated by the browser and the screen reader, making it more difficult to understand what information is displayed on the browser's operating screen. Alternatively, if the browser provides an operating screen for the visually impaired that is accessible to the visually impaired and an operating screen for the sighted or sighted that is accessible to the sighted, the requirement The user performs an operation of selecting or switching an operation screen to a desired screen. This is particularly inconvenient for visually impaired users, for whom each operation is time-consuming.

Contents of the invention

In view of the above circumstances, it is an object of the present invention to provide a data processing apparatus capable of displaying information for visually impaired users within a plurality of operation screens including a screen for visually impaired users and a screen for seeing users. User-friendly operation screen.

In order to achieve the above and other objects, the present invention provides a data processing device including a display unit, a user type determination unit, and a display control unit. The display unit displays display data including first display data for a visually impaired user and second display data for a sighted user. The user type determining unit determines whether the user is visually impaired or sees. The display control unit controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays when the user type determination unit determines that the user is visually impaired. The second display data.

According to another aspect, the present invention provides a data processing method comprising: determining whether a user is visually impaired or can see; and displaying first display data for a visually impaired user when said user is visually impaired is determined, and Second display data for a visible user is displayed when the user is determined to be visible.

According to another aspect, the present invention provides a computer-readable recording medium storing a data processing program including instructions for: determining whether a user is visually impaired or can see; and, when First display data for a visually impaired user is displayed when the user is determined to be visually impaired, and second display data for a visually impaired user is displayed when the user is determined to be visually impaired.

According to another aspect, the invention provides a data processing system comprising first data processing means and second data processing means. The first data processing device comprises a display unit which displays display data comprising first display data for a visually impaired user and second display data for a sighted user. The second data processing means includes a user type determination unit and a display control unit. The user type determining unit determines whether the user is visually impaired or sees. The display control unit controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays when the user type determination unit determines that the user is visually impaired. The second display data.

Description of drawings

Certain features and advantages, as well as other objects of the present invention, will become apparent from the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram showing an electronic structure of a PC according to a first embodiment of the present invention;

Figure 2A is a screenshot showing an example of a UI for a visually impaired user;

Figure 2B is a screenshot showing an example of a UI for a visible user;

FIG. 3A is a flowchart illustrating steps within an initial setup process performed on a PC;

Figure 3B is a screenshot showing an example of a dialog box;

FIG. 4 is a flowchart illustrating steps within the main process executed on a PC;

FIG. 5 is a flowchart illustrating steps within a user type determination process;

FIG. 6A is a flowchart illustrating steps within a user status acquisition process;

FIG. 6B is a flowchart illustrating steps within the operation acquisition process;

FIG. 7 is a flowchart illustrating steps in screen switching processing A;

FIG. 8 is a flowchart illustrating steps in screen switching processing B;

Figure 9A is a screenshot showing an example of a dialog box for a visually impaired user;

Figure 9B is a screenshot showing an example of a dialog box for a visible user;

FIG. 10 is a flowchart illustrating steps in use state acquisition processing according to the first variation of the first embodiment;

FIG. 11A is a flowchart illustrating steps in use state acquisition processing according to a second modification of the first embodiment;

FIG. 11B is a flowchart illustrating steps in the operation acquisition process according to the third modification of the first embodiment;

FIG. 11C is a flowchart illustrating steps in the operation acquisition process according to the fourth modification of the first embodiment;

12 is a flowchart illustrating steps in user type determination processing according to a fifth variation of the first embodiment;

13A is a screenshot showing an example of a UI displayed on an LCD for a visually impaired user;

FIG. 13B is a screenshot showing an example of a user's UI displayed on an LCD for viewing the display;

FIG. 14A is a flowchart illustrating steps within a function execution process executed by a PC according to the second embodiment;

14B is a screenshot showing an example of a scanner function operation screen for a visually impaired user displayed on the LCD;

FIG. 15A is a flowchart illustrating steps in function execution processing B according to the second embodiment;

FIG. 15B is a screen shot showing an example of a scanner function operation screen displayed on the LCD for the user to view the display;

FIG. 16A is a block diagram showing an electronic configuration of a PC according to a third embodiment;

FIG. 16B is a flowchart illustrating steps in the user type monitoring process performed by the PC according to the third embodiment; and

Fig. 17 is a flowchart illustrating steps within application start processing executed by a PC according to the third embodiment.

Detailed ways

A data processing apparatus according to an embodiment of the present invention will be described with reference to the drawings, in which similar parts and components are designated by the same reference numerals to avoid duplication of description.

First, a data processing apparatus according to a first embodiment of the present invention will be described with reference to FIGS. 1-9B.

In the first embodiment, application X is installed on PC1. The application X has a screen switching function for automatically switching between these operating screens for the visually impaired user and for the sighted user. When running, the application program X is used to determine whether the user of the PC 1 is visually impaired or sees, and switches its operation screen to a screen suitable for the user.

FIG. 1 is a block diagram showing an electrical configuration of a PCI mounted first embodiment.

When the application X as described above runs on the PC 1 and displays an operation screen convenient for the visible user, the application X can switch the operation screen to a screen beneficial to the visually impaired user when the user performs an input operation. This configuration is convenient for vision-impaired users because each operation is time-consuming for such users.

The application program X is a program capable of using various functions possessed by the multifunction peripheral (MFP) 100 connected to the PC 1 via the LAN 200 , including a facsimile function, a printer function, a scanner function, and a copier function. MFP 100 is also connected to telephone network 300 required for transmitting data with a facsimile function.

PC 1 is mainly configured by CPU 11 , ROM 12 , RAM 13 , hard disk 14 , keyboard 15 , mouse 16 , LCD 17 , speaker 18 , timing circuit 19 and LAN interface 20 , all of which are connected to each other via bus 26 .

The CPU 11 is used to control various functions possessed by the PC 1 and each component connected to the bus 26 according to fixed values and programs stored on the ROM 12 , RAM 13 , and hard disk 14 or according to signals exchanged via the LAN interface 20 .

ROM12 is a non-rewritable memory for storing control programs executed on PC1. The RAM 13 is a rewritable volatile memory for temporarily storing various data when the CPU 11 performs operations on the PC 1 .

The RAM 13 is provided with a condition matching flag storage area 13a, a key operation flag storage area 13b, a mouse operation flag storage area 13c, a condition matching count storage area 13d, a key input count storage area 13e, a mouse input count storage area 13f, a mouse over button name storage area 13g and user type storage area 13h.

The condition compliance flag storage area 13a stores a condition compliance flag for indicating whether the user setting on the PC 1 indicates a setting for assisting a visually impaired user. PC settings designed to assist visually impaired users may include, for example, settings performed when the installation is designed to assist visually impaired users to use the PC and on-the-fly operations for reducing the speed of the mouse cursor or increasing the size of text displayed on the LCD 17. Settings within the system (hereinafter abbreviated as "OS"). The condition conformity flag is set to "valid" (such as "1") when the above-mentioned condition is satisfied, and is set to "invalid" (such as "0") when the above-mentioned condition is not satisfied or when the flag is initialized.

The key operation flag storage area 13b stores a key operation flag indicating whether or not the user has performed a specified key operation on the keyboard 15 (for example, has pressed a key). The key operation flag is set to "effective" ("on") (such as "1") when the user has performed a designated key operation on the keyboard 15, and when the designated key operation has not been performed or when the Set to "off" (e.g. "0") when the above flag is used.

The mouse operation flag storage area 13c stores a mouse operation flag indicating whether or not the user has performed a specified mouse operation (for example, a mouse click) on the mouse 16 . The mouse operation flag is set to "valid" (for example, "1") when the user has performed a specified mouse operation on the mouse 16, or is set when the specified mouse operation has not been performed or when the flag is initialized is "invalid" (for example, "0").

The condition meeting count storage area 13d stores a count indicating the number of user settings on the PC 1 that are performed to help a visually impaired user. For example, the count stored in the conditional match count storage area 13d is incremented by "1" for each user setting on the PC that is designed to assist visually impaired users, including those that are designed to assist visually impaired users. The installation of the software of the PC, the OS setting for reducing the speed of the mouse cursor, or the OS setting for increasing the size of the text displayed on the LCD 17 is used.

The key input count storage area 13 e stores a count indicating the number of times the operator has performed a specified key operation on the keyboard 15 . For example, each time the user performs a specified key operation on the keyboard 15, the count in the key input count storage area 13e is incremented by "1".

The mouse input count storage area 13 f stores a count indicating the number of times the user has performed a specified mouse operation on the mouse 16 . For example, the count stored in the mouse input count storage area 13f is incremented by "1" every time the user performs a designated mouse operation.

The mouse-over button name storage area 13g stores the names of designated buttons displayed on the LCD 17 over which the mouse cursor passes in the order in which the buttons are passed. For example, when the mouse cursor passes over a button to which the button name "scan" is assigned, the button name "scan" is stored in the mouse-over button name storage area 13g. If the mouse cursor then passes over a button to which the button name "Copy" is assigned, the button name "Copy" is stored in addition to "Scan" in the order in which the buttons were passed.

The user type storage area 13h stores a user type indicating whether the user is visually impaired or sees. The type of the user operating the PC 1 is determined in accordance with user type determination processing described later with reference to FIG. 5 . If the user is determined to be a visually impaired user within this process, a user type indicating that the user is visually impaired (for example, "1") is stored in the user type storage area 13h. If it is determined that the operator is a visible user, a user type indicating a visible user (for example, "2") is stored in the user type storage area 13h. The user type storage area 13h is initialized to "0".

The hard disk 14 is a rewritable nonvolatile memory. Therefore, data stored on the hard disk 14 can be retained even after the power to the PC 1 is turned off. The hard disk 14 is provided with an OS storage area 14a, a screen reader storage area 14b, and an application program X storage area 14c.

The OS storage area 14a stores the OS and OS settings. The OS is a basic program designed to manage components connected to the bus 26 and is required when an operator uses the PC 1 . For example, the OS manages the entire display area of the LCD 17 as described below. The OS is provided with a plurality of setting options associated with input operations, as described below. By selecting one of the many options offered for each setting, the user can customize the PC 1 for a more enjoyable experience. Programs running on the PC 1 can display text, images, and the like within a limited display area on the LCD 17 allowed by the OS. For example, the user can set the speed of the mouse cursor displayed on the LCD 17 to be faster or slower than the specified default speed, and can set the size of the text data displayed on the LCD 17 to be larger than the specified default text size or smaller.

Therefore, when a program running on the PC 1 displays text or images on the LCD 17, the program must first request allocation of a display area of a desired size to the OS. Hereinafter, a display area of a desired size allocated (allowed) by the OS will be referred to as a window, and each program will be considered to acquire a window from the OS when the OS allocates the window. When a program running on PC1 acquires a window from the OS, the program can freely display text and images within the confines of the window.

Regardless of whether there are multiple programs running on PC1 each of which has acquired a window or whether there is a single program which has acquired multiple windows, the OS manages each window independently so that each window can be displayed on the LCD 17 .

When the program terminates execution after acquiring the window, or when the acquired window from the OS becomes unnecessary, the program can eliminate the window from the LCD 17 by returning the acquired window to the OS. Hereinafter, the act of returning a window to the OS to remove the window from the LCD 17 will be referred to as closing the window.

The OS is also provided with a number of setting options associated with input operations, as described below. By picking one of the many options offered for each setting, the user can customize the PC 1 for a more enjoyable experience.

The screen reader storage area 14b stores a screen reader (sound expression software) designed to convert text data displayed on the LCD 17 into sound. Screen readers are used to assist users with visual impairments. When the user performs a key operation to select text data displayed on the LCD 17 , the screen reader converts the selected text data into a sound signal, and outputs the sound signal through the speaker 18 . For example, if the user selects one of the buttons BT1-BT11 displayed on the LCD 17 (described in more detail later with reference to FIG. 2A), the screen reader converts the button name of the selected button into a sound signal, and the A sound signal is outputted in such a way that a visually impaired person can operate the PC 1 according to the sound.

Application program X storage area 14 c stores application program X that facilitates use of the functions of MFP 100 connected to PC 1 via LAN 200 . Since the screen reader operates simultaneously when the visually impaired user uses the application X, the screen reader can convert text data displayed within the operation screen of the application X into sound data output through the speaker 18 . Therefore, the visually impaired user can operate the application program X according to the sound.

The application program X storage area 14c stores a program for executing the initial setting process shown in the flowchart of FIG. 3A, the main process shown in the flowchart of FIG. 4, the user program shown in the flowchart of FIG. Type determination processing, use state acquisition processing shown in the flowchart of FIG. 6A , operation acquisition processing shown in the flowchart of FIG. 6B , screen switching processing A shown in the flowchart of FIG. Screen switching process B shown in the flowchart of 8.

The application X storage area 14c is provided with a visually impaired UI storage area 14c1, a sighted UI storage area 14c2, a switching flag storage area 14c3, a confirmation display flag storage area 14c4, and a UI type storage area 14c5.

The visually impaired UI storage area 14c1 stores a user interface (UI) for visually impaired users (described later in more detail with reference to FIG. 2A ), which is an operation screen facilitating input operations for visually impaired users. The visible user UI storage area 14c2 stores a UI for the visible user (described later in more detail with reference to FIG. 2B ), which is an operation screen that facilitates input operations by the visible user.

The switching flag storage area 14c3 stores a switching flag for indicating whether to switch the operation screen displayed on the LCD 17 to the UI for the visually impaired user or the UI for the visible user according to the characteristics of the user's input operation . When the toggle flag is set to “valid” (for example, “1”), the operation screen displayed on the LCD 17 is converted into a UI for a visually impaired user or a UI for a visible user according to the characteristics of the input operation . If the toggle flag is set to "invalid" (for example, "0"), the operation screen displayed on the LCD 17 is not changed.

The confirmation display flag storage area 14c4 stores a confirmation display flag for indicating whether to display one of the dialog boxes described below with reference to FIG. Wish to switch the operation screen.

When switching the operation screen displayed on the LCD 17 according to the characteristics of the user's input operation, if the confirmation display flag is set to "valid" (for example, "1"), a dialog box B or C is displayed on the LCD 17 (see FIG. 9 ) , which is used to determine if the user wants to switch action screens. If the operator inputs an instruction for switching the screen, then the operation screen is switched. However, if it is determined that the display flag is set to "invalid" (such as "0"), the dialog box B or C for confirming whether the user wishes to switch the operation screen is not displayed, and the operation screen displayed on the LCD 17 is switched without switching. Consider operator input.

The UI type storage area 14c5 stores a UI type indicating whether a UI for a visually impaired user or a UI for a sighted user should be displayed on the LCD 17 . When the UI type storage area 14c5 stores the user type (such as "1") indicating the user with visual impairment, the UI for the visually impaired user is displayed on the LCD 17, and when the UI type storage area 14c5 stores the user type indicating the visual impairment When the UI type (for example, "2") of the visible user's UI is selected, the UI for the visible user is displayed on the LCD 17 . The user type stored in the UI type storage area 14c5 is initially set to "0". In other words, when the application program X is started, an operation screen corresponding to the UI type stored in the UI type storage area 14c5 is displayed on the LCD 17 .

The keyboard 15 is an input device having a plurality of keys. When the operator presses these keys, an input signal corresponding to the pressed key is input into the PC 1 . The mouse 16 is a pointing device for indicating a display position using a mouse cursor displayed on the LCD 17 . When the user uses the mouse 16 to move the position of the mouse cursor, an input signal corresponding to the amount of movement is input to the PC 1, and the display position of the mouse cursor is moved according to the input signal.

The mouse 16 has mouse buttons that the user can operate while moving the position of the mouse cursor. When the user operates this button, a specified input signal is input into PC1. By operating the keyboard 15 and the mouse 16, the user can modify various settings and the like within the OS, and can use the application program X and the like.

The LCD 17 is used to display operation procedures and processing states during execution of operations and data corresponding to keys pressed on the keyboard 15 and operations performed using the mouse 16 . The speaker 18 outputs the sound signal provided by the screen reader as sound. The timer circuit 19 is a circuit well known in the art, which has a timer function for keeping the current time and date.

The LAN interface 20 is a well-known circuit in the art for connecting one end of a LAN cable to a connection port of the LAN interface 20 and connecting the other end to the LAN 200 to communicate with various external devices connected to the LAN 200. communication.

Next, a UI for a visually impaired user and a UI for a sighted user will be described with reference to FIGS. 2A and 2B .

The UI for sight-impaired users and the UI for sighted users are operation screens of the application X. One of these operation screens is displayed on the LCD 17 while the application program X is running. The user can use various functions of the MFP 100 by performing an input operation according to the UI for the visually impaired user and the UI for the sighted user.

In order to display one of the operation screens on the LCD 17, the application X acquires a window from the OS corresponding to the shape of the operation screen, and displays the operation screen within the acquired window. The user can use the functions of the MFP 100 by performing an input operation conforming to the UI for visually impaired users and the UI for sighted users within this window on the LCD 17 .

2A is a screen shot showing an example of a UI for visually impaired users stored in the visually impaired UI storage area 14c1, and FIG. See a screenshot of an example of the user UI. The UI for visually impaired users has a limited number of images and a large amount of text data, and enables visually impaired users to perform all operations using a screen reader.

As shown in FIG. 2A , in the upper region of the UI for visually-impaired users, a selection box SB1 in which a setting button BT1 for indicating which MFP 100 can be used with the application X is displayed and a setting button BT1 are provided. Text data, the setting button BT1 is used to set various options within the application program X.

On the left side, the UI for visually impaired users has: a scan button BT2 for using the scanner function on the MFP 100; a photo media capture button BT3 for using the photo media capture function on the MFP 100; Copy button BT4 for the copy function used on the MFP100; PC-FAX button BT5 for the PC-FAX function used on the MFP100; device setting button BT6 for various operations set in the MFP100 ; A screen switching button BT7 for switching the operation screen displayed on the LCD 17 to a UI for a visible user.

In the central area, the UI for visually impaired users includes: an image button BT8 for displaying on the LCD 17 an image data file scanned using the scanner function; an OCR button BT9 for using the OCR function to scan according to the usage An image data file scanned by the browser function to create a text data file; an e-mail button BT10 for sending e-mail; and a file button BT11 for displaying various files stored in the hard disk 14 on the LCD 17.

A device setting button BT6 is provided for performing various settings within the MFP 100 . A screen switching button BT7 is provided for switching the operation screen displayed on the LCD 17 to a UI for a visible user. While part of the UI is for a visually impaired user, when the processing of S80 (see FIG. 7 ) is executed in screen switching processing A described later, a screen switching button BT7 is displayed on the LCD 17 .

By providing a screen switching button BT7 within the UI for visually impaired users, a user who can see can switch the UI for visually impaired users displayed on the LCD 17 to one for viewing by operating this screen switching button BT7. UI of the visible user without waiting for the CPU 11 to determine whether the operator of the PC 1 is visually impaired or visible within the main process of FIG. 4 described later. Therefore, the addition of this button is convenient for the visible user.

In the first embodiment, the button name displayed on the screen switching button BT7 is formed of an image, so a screen reader cannot express the name audibly. Therefore, the existence of the screen switching button BT7 is not declared to the visually impaired user. Therefore, since the visually impaired user cannot recognize the screen switching button BT7, it is impossible for the visually impaired user to perform an input operation on the screen switching button BT7 to convert the UI for the visually impaired user into that for the visually impaired user. UI. Therefore, this configuration reduces the risk of a visually impaired user mistakenly switching the UI for the visually impaired on the LCD 17 to the UI for the sighted.

Also, the screen switching button BT7 is configured to accept an input operation only via the mouse 16 . Because it is difficult for a visually impaired user to perform an input operation using the mouse 16, it is impossible for the visually impaired user to perform an input operation on the screen switching button BT7 to convert the UI for the visually impaired user displayed on the LCD 17 to a screen for viewing. Visible user UI. Thus, this configuration reduces the chances of a vision-impaired user mistakenly converting the UI for the vision-impaired user to the UI for the sighted user.

In the first embodiment, the button name "Settings" has been assigned to the setting button BT1, "Scan" to the scan button BT2, "Photo Media Capture" to the photo media capture button BT3, and "Photo Media Capture" to the copy button BT4. "Copy", "PC-FAX" is assigned to the PC-FAX button BT5, "Device setting" is assigned to the device setting button BT6, "Screen switching" is assigned to the screen switching button BT7, "Image" is assigned to the image button BT8 ", "OCR" is assigned to the OCR button BT9, "E-mail" is assigned to the E-mail button BT10, and "File" is assigned to the file button BT11.

The screen reader can convert the button names for all the buttons BT1-BT11 and all the texts displayed in the selection box SB1 provided on the UI into sound signals in order to assist visually impaired users to perform input operations.

Using the UI for the visually impaired user as described above, the user can use the keyboard 15 and mouse 16 to operate the buttons BT1 - BT11 and the selection box SB1 to use functions on the MFP 100 . Here, the user first has to perform an operation for recognizing one of the buttons BT1-BT11 or the selection box SB1 as an operation target, and then has to input an instruction for performing the operation.

The buttons BT1-BT11 or the selection box SB1 that have been recognized as operation targets, that is, buttons or boxes that have been placed in a state where an execution instruction can be input are referred to as "input focus". The input focus is said to have shifted when a different button BT1-BT11 or selection box SB1 is designated. When the input focus has been set to one of the buttons BT1-BT11 or the selection box SB1, a rectangular frame called a cursor is displayed along the outline of the button or frame set as the input focus so that the user can recognize the button or frame Which of the has been set as the input focus.

For example, when performing an input operation using the keyboard 15 , the user performs a recognition operation by pressing a Tab key provided on the keyboard 15 . Each time the user presses the Tab key, the input focus moves through buttons BT1-BT11 and selection box SB1 one at a time in the specified order. The user repeatedly presses the Tab key until the input focus has reached the desired button or box. When the desired input focus has been set, the user presses the return key to perform the operation of the button BT1-BT11 or the selection box SB1 selected as the input focus. In order to simplify the description, it is assumed below that the execution command input to the button displayed on the LCD 17 indicates that this button is pressed, and which UI for the visually impaired user is displayed (even in the dialog box A described later with reference to FIG. 3B , for example). case) or whether the input operation is performed using the keyboard 15 or the mouse 16 is irrelevant.

Each time the input focus is set to one of the buttons BT1-BT11 or the selection box SB1, the screen reader will use the button name for the buttons BT1-BT11 or the text data displayed inside the selection box SB1 that has been set as the input focus converted into the sound output from the speaker 18 .

When the recognition operation is performed using the mouse 16, the recognition operation and the execution instruction are performed simultaneously. For example, by moving the display position of the mouse cursor displayed on the LCD 17 over the display position of one of the buttons BT1-BT11 or the selection box SB1, and pressing the mouse button (referred to as "mouse click"), the user can A recognition operation is performed and an execution instruction for a specific button BT1-BT11 or selection box SB1 is input.

Next, a UI for a visible user will be described with reference to FIG. 2B . FIG. 2B is a screenshot showing an example of a UI for a visible user, which is an operation screen of application X. FIG. By performing an input operation according to the UI for the visible user, the user can use various functions of the MFP 100 . The UI for the visible user is also configured such that the user can perform input operations using the mouse 16 on various images. Input operations can be performed using the mouse 16 in fewer steps than using the keyboard 15 . Therefore, the visible user can perform an input operation using the mouse 16 more easily than using the keyboard 15 .

In the upper area of the UI for the visible user are provided: a selection box SB21 in which the MFP 100 usable by the application program X is displayed as text data, and a setting button BT21. BT21 is used to set various options within App X.

On the left side, UI for visible user is provided with: scan button BT22 for using the scanner function within MFP100; photo media capture button BT23 for using photo media capture within MFP100 function; copy button BT24 for use in the copy function in MFP100; PC-FAX button BT25 for use in the PC-FAX function in MFP100; and device setting button BT26 for use in MFP100 Options.

On the right side, the UI for the visible user is provided with: an image graphic button GBT21 for displaying on the LCD 17 an image data file or the like of an image scanned using the scanner function; an OCR graphic button GBT22 for The OCR function is used to create a text data file from the image data file for the image scanned using the scanner function; an e-mail graphic button GBT23 for sending e-mail; and a file graphic button GBT24 for displaying on the LCD 17 Various files stored in the hard disk 14 are displayed.

In the first embodiment, the button name "Settings" has been assigned to the setting button BT21, "Scan" to the scan button BT22, "Photo Media Capture" to the photo media capture button BT23, and "Copy" to the copy button BT24. ", assign "PC-FAX" to the PC-FAX button BT25, assign "Device Setting" to the device setting button BT26, assign "Image" to the image graphic button GBT21, assign "OCR" to the OCR graphic button GBT22, and assign "OCR" to the E-mail graphic button The button GBT23 sets "e-mail", and assigns "document" to the file graphic button GBT24.

The screen reader is configured to convert the button names of the buttons BT21-BT26 and the text data displayed in the selection box SB21 provided within the UI for the visible user into sound signals. However, because the graphic buttons GBT21-GBT24 are configured as images, screen readers cannot convert this data into sound signals.

Therefore, it is difficult for a vision-impaired user to perform an input operation on the graphic buttons GBT21-GBT24. Therefore, if an input operation is performed on one of the graphic buttons GBT21-GBT24, it can be assumed that the visible user has performed the input operation.

In other words, since the existence of the graphic buttons GBT21-GBT24 is not declared to the visually-impaired user, it is difficult for the visually-impaired user to recognize the graphic buttons GBT21-GBT24, and therefore, it is impossible for the user to perform an input operation on one of these graphic buttons. Therefore, if an input operation is performed on one of the graphic buttons GBT21-GBT24, it can be assumed that the visible user has performed the input operation.

Since the method of using the keyboard 15 or the mouse 16 to perform a recognition operation to recognize one of the buttons BT21-BT26 or the selection box SB21, or to input an execution instruction is the same as that described about the UI for a visually impaired user, this is not repeated. description of the method.

Also, the graphic buttons GBT21-GBT24 cannot be recognized by operations on the keyboard 15. FIG. In other words, only by moving the display position of the mouse cursor on the LCD 17 over the desired display position of the graphic buttons GBT21-GBT24 and performing a mouse click, the recognition operation and execution instruction can be input for the graphic buttons GBT21-GBT24.

Since it is difficult for a visually impaired user to perform input operations using the mouse 16, any input operation performed on the graphic buttons GBT21-GBT24 can be assumed with greater certainty to be performed by a visible user.

Next, the initial setting process executed by the CPU 11 of the PC 1 will be described with reference to FIG. 3A . FIG. 3A is a flowchart illustrating steps within an initial setup process.

The initial setting process of S10 is performed to set the switch flag according to the user input operation, and initialize the confirmation display flag and the UI type. When the application program X is stored in the application program X storage area 14c, the CPU 11 executes initial setting processing.

In S1 of the initial setting process, the CPU 11 displays a dialog A on the LCD 17 for prompting the user to confirm whether or not to use an operation screen for transitioning to the most suitable for the user in accordance with various user settings for the PC 1 and characteristics of input operations. screen switching function. Dialog box A is described here with reference to FIG. 3B.

The dialog box is an operation screen for displaying messages requesting the user to input instructions for processing to be performed, for displaying messages requesting confirmation from the user, and for receiving input from the user in response to these messages. In this initial setting process, the CPU 11 acquires a window from the OS, and displays the dialog A within the acquired window.

FIG. 3B is a screenshot showing an example of dialog A. FIG. The dialog box A is a window for displaying a message prompting the user to confirm whether to use the screen switching function by inputting an instruction.

The dialog box A is provided with: a text box TB31, a button BT31 and a button BT32, a message prompting the user to confirm whether to use the screen switching function is displayed in the text box TB31, and the user uses the button BT31 to input an instruction to use the screen switching function , the user uses the button BT32 to input an instruction not to use the screen switching function.

The text box TB31 includes, for example, text data "By monitoring the input operation performed by the user, the screen type can be automatically switched to a design suitable for the user's operation method". In addition, the button name "Yes" is assigned to the button BT31, and the button name "No" is assigned to the button BT32.

The screen reader is configured to convert the text data displayed in the text box TB31 and the button names of the buttons BT31 and BT32 provided in the dialog box A into sound signals for the convenience of visually impaired users. The user's input action.

The switching flag stored in the switching flag storage area 14c3 is set to "valid" when the user selects the button BT31 using an input operation, and is set to "disabled" when the user selects the button BT32. After selecting one of the buttons BT31 and BT32, the window in which the dialog A is displayed is closed.

Returning to the flowchart in FIG. 3A, in S2, the CPU 11 determines whether or not the user has performed an operation of pressing the Yes button BT31 in the dialog box A displayed on the LCD 17. If the YES button BT31 is pressed (S2: YES), in S3, the CPU 11 sets the switching flag stored in the switching flag storage area 14c3 to "valid". However, if the NO button BT32 is pressed (S2: NO), in S4, CPU11 sets a switching flag to "invalid".

If the switching flag has been set to "valid", the CPU 11 converts the operation screen displayed on the LCD 17 into a UI for a sight-impaired user or a UI for a sighted user according to the characteristics of the user's input operation. However, if the switching flag has been set to "invalid", the CPU 11 does not change the operation screen displayed on the LCD 17 .

In S5, the CPU 11 initializes the confirmation display flag stored in the confirmation display flag storage area 14c4 to "valid", and in S6, stores the UI type ( "2" in the first embodiment). Subsequently, the CPU 11 ends the initial setting processing.

Therefore, when the UI type stored in 14c5 indicates the UI for the visually impaired user, the CPU 11 displays the UI for the visually impaired user on the LCD 17, and when the UI type indicates the UI for the visible user , CPU 11 displays UI for the visible user on LCD 17 .

Through the initial setting process shown in FIG. 3A , the CPU 11 can set the switching flag in accordance with the input operation performed by the user, and can initialize the confirmation display flag and the value of the UI type when the application program X is installed on the hard disk 14 .

Next, main processing executed by the CPU 11 of the PC 1 will be described with reference to FIG. 4 .

FIG. 4 is a flowchart illustrating steps within the main process. The main process is used to switch the current operation screen to an operation screen suitable for the user according to various user settings for the PC 1 and characteristics of the user's input operation. Once the application program X is executed first, the CPU 11 will execute the main process. While the application program X is running, the CPU 11 executes main processing at specified intervals (for example, every 30 minutes).

In S11 of the main process, the CPU 11 initializes each storage area 13a-13h provided in the RAM 13. At S12, the CPU 11 determines whether or not the switching flag stored in the switching flag storage area 14c3 is set to "valid". If the switching flag is set to "valid" (S12: YES), the CPU 11 executes user type determination processing in S13. The user type determination process of S13 determines whether the user is a vision-impaired user or a seeing user. However, if the switching flag is "invalid" (S12: NO), the CPU 11 ends the main processing without executing S13-S20. The user type determination processing will be described in detail below.

In S14, the CPU 11 acquires and determines the user type determined in the user type determination process of S13. If the user type is determined to be a visually impaired user (S14: visually impaired user), that is, if the user type storage area 13h stores the user type for indicating a visually impaired user, then at S15, the CPU 11 reads the user type in the UI type storage area. The UI type stored in 14c5.

In S16, the CPU 11 determines whether the UI type read in S15 indicates a visible user. If the user type indicates a visible user (S16: YES), in S17, the CPU 11 executes the screen switching process A, and then ends the main process. The screen switching process A is for switching the UI for the visible user displayed on the LCD 17 to the UI for the visually impaired user. However, if the user type indicates a visually impaired user (S16: NO), the CPU 11 ends the main processing without executing the processing of S17. The screen switching processing A will be described in detail below.

Or, if the CPU 11 determines that the user type determined in S13 is a visible user (S14: visible user), that is, the user type storage area 13h stores the user type indicating a visible user, then in S18, The CPU 11 reads the UI type stored in the UI type storage area 14c5.

In S19, the CPU 11 determines whether the UI type read in S18 indicates a visually impaired user. If the user type indicates a visually impaired user (S19: YES), in S20, the CPU 11 executes the screen switching process B, and then ends the main process. The screen switching process B is for switching the UI for the visually impaired user displayed on the LCD 17 to the UI for the visible user. The screen switching processing B will be described in detail below. However, if the user type indicates a visible user (S19: NO), the CPU 11 ends the main processing without executing the processing in S20.

Through the main processing described in FIG. 4, the CPU 11 can switch the operation screen to an operation screen suitable for the user in accordance with various user settings for the PC 1 and characteristics of the user's input operation. Therefore, even if the UI for the visually impaired user is displayed on the LCD 17, when the visually impaired user performs an input operation, the operation screen is switched to the UI for the visually impaired user, so that the processing is More user-friendliness for users, wherein each operation is time-consuming for said vision-impaired users. The process is also user-friendly for the visible user because when the visible user performs an input operation, the UI for the visually impaired user displayed on the LCD 17 is switched to the UI for the visible user. UI.

Next, the user type determination processing of S13 will be described with reference to FIG. 5 .

FIG. 5 is a flowchart illustrating steps within the user type determination process. This processing is performed to determine whether the user of the PC 1 is a vision-impaired user or a sighted user based on various user settings for the PC 1 and the characteristics of the user's input operation.

In S31 of the user type determination process, the CPU 11 initializes the key input count storage area 13e and the mouse input count storage area 13f. In S32, the CPU 11 executes use state acquisition processing. Here, the use state acquisition process executed by the CPU 11 will be described with reference to FIG. 6A .

FIG. 6A is a flowchart illustrating steps within a usage state acquisition process. This process is performed to obtain user settings for the PC 1 and to determine whether settings have been made to facilitate use by a visually impaired person.

In S51 of the use status acquisition process, the CPU 11 determines whether or not a screen reader has been installed (stored) in the screen reader storage area 14b. If the screen reader is installed in the screen reader storage area 14b (S51: YES), in S52, the CPU 11 sets the conditional compliance flag stored in the conditional compliance flag storage area 13a of the RAM 13 to "valid". However, if the screen reader is not installed (S51: NO), then in S53, the CPU 11 sets the condition matching flag to "invalid". Subsequently, the CPU 11 ends the use state acquisition processing.

By using the status acquisition process, when the screen reader is installed on the hard disk 14, the CPU 11 can set the condition compliance flag to "valid" for indicating that the PC 1 is configured for a visually impaired user. Since screen readers are mainly used by visually impaired people, it can be considered highly likely that PC1 is operated by a visually impaired user when a screen reader has been installed on PC1.

Returning to the flowchart in FIG. 5, in S33, the CPU 11 determines whether or not the conditional compliance flag stored in the conditional compliance flag storage area 13a has been set to "valid". If the condition met flag is set to "valid" (S33: YES), then at S34, the CPU 11 executes an operation acquisition process. If the conditional match flag is set to "invalid" (S33: NO), the CPU 11 skips the processing in S34-41, and proceeds to S42.

Here, the operation acquisition process of S34 executed by the CPU 11 will be described with reference to FIG. 6B .

FIG. 6B is a flowchart illustrating steps within the operation acquisition process at S34. This operation acquisition processing is executed to acquire input operations performed using the keyboard 15 and input operations performed using the mouse 16 .

At S61 where the operation acquisition process starts, the CPU 11 acquires a key operation performed using the keyboard 15 or a mouse operation performed using the mouse 16 , and at S62 , determines whether the acquired input operation is performed within the application program X. If the acquired input operation is performed within the application program X (S62: YES), the CPU 11 ends the operation acquisition process. However, if the acquired input operation is not performed within the application program X (S62: NO), the CPU 11 returns to S61, and repeats the processing within S61-S62.

Through the operation acquisition processing shown in FIG. 6B , the CPU 11 can acquire input operations performed within the application program X from various input operations using the keyboard 15 and mouse 16 .

Returning to FIG. 5, in S35, the CPU 11 determines whether the input operation acquired in S34 is an input operation of pressing one of the Tab key, the Control key and the Tab key, the Space key, the Alt key, and the arrow key. If the acquired input operation is one of the above keys (S35: YES), at S36, the CPU 11 increments the value stored in the key input count storage area 13e by "1".

In S37, the CPU 11 determines whether or not the count stored in the key input count storage area 13e has exceeded "10". If the count has exceeded "10" (S37: Yes), at S38, the CPU 11 stores a user type ("1" in the first embodiment) for indicating a user with visual impairment in the user type storage area 13h. , and then the user type determination processing ends.

However, if the count is not greater than "10" (S37: NO), the CPU 11 returns to S34, and repeats the processing in S34-S37 as described above.

Also, if the CPU 11 determines at S35 that the acquired input operation is not one of the above-enumerated operations (S35: NO), at S39 the CPU 11 determines whether the acquired input operation is a mouse click. If the acquired input operation is a mouse click (S39: YES), at S40, the CPU 11 increments the count in the mouse input count storage area 13f by "1". In S41, the CPU 11 determines whether or not the count stored in the mouse input count storage area 13f has exceeded "5". If the count has exceeded "5" (S41: Yes), then in S42, the CPU 11 stores the user type ("2" in the first embodiment) for indicating the visible user in the user type storage area 13h , and then the user type determination processing ends.

However, if the CPU 11 determines in S39 that the acquired input operation is not a mouse click (S39: NO), the CPU 11 returns to S34, and repeats the processing in S34-S39 as described above. Also, if the CPU 11 determines in S41 that the count is not greater than "5" (S41: NO), the CPU 11 returns to S34, and repeats the processing in S34-S41 as described above.

Since it is difficult for a vision-impaired user to perform an input operation while viewing the operation screen, it is considered less likely that a vision-impaired user will perform an input operation using the mouse 16 than a sighted user. And, because a visible user can perform an input operation while viewing an operation screen, a visible user is more likely to use the mouse 16 to perform an input operation than a visually impaired user, because it is possible to perform an input operation on the mouse 16 than on a keyboard. 15 fewer operations to complete the task.

Therefore, when more input operations are performed using the keyboard 15 as determined in S37, it can be considered that the visually impaired user is operating the PC 1, and when more input operations are performed using the mouse 16 as determined in S41 When the input operation is performed, it is visible that the user is operating PC1.

The PC 1 is configured to allow input operations using both the keyboard 15 and the mouse 16 . However, characteristics within these input operations can be easily detected because a difference in characteristics is noticeable between input operations performed by a sight-impaired user and a sighted user.

Through the user type determination process shown in FIG. 5, the CPU 11 can determine whether the user is visually impaired based on the user settings for the PC 1 and the number of input operations performed using the keyboard 15 or the number of input operations performed using the mouse 16. Or visible. Also, the CPU 11 may store a user type indicating a visually impaired user in the user type storage area 13h when determining that the user is visually impaired, and store a user type indicating in the user type storage area 13h when determining that the user is visually impaired. The user type of the visible user.

Next, the screen switching process A of S17 executed by the CPU 11 of the PC 1 will be described with reference to FIG. 7 .

FIG. 7 is a flowchart illustrating steps within screen switching processing A. FIG. This processing is performed for switching the UI for the visible user displayed on the LCD 17 to the UI for the visually impaired user.

The processing is for displaying the screen switching button BT7 in the display area of the UI for the visually impaired user when the operation screen has been switched to the visually impaired user.

In S71 of the start of the screen switching process A, the CPU 11 determines whether or not the confirmation display flag stored in the confirmation display flag storage area 14c4 is set to "valid". If the confirmation display flag is set to "valid" (S71: Yes), at S72, the CPU 11 displays a dialog B on the LCD 17 for prompting the user to confirm whether to convert the operation screen to a UI for visually impaired users. However, if it is confirmed that the display flag is set to "invalid" (S71: NO), the CPU 11 skips the processing in S72-S75, and proceeds to S76.

Here, dialog B will be described with reference to FIG. 9A .

FIG. 9A is a screenshot showing an example of dialog B. FIG. The dialog B is a window for displaying a message for prompting the user to confirm whether to convert the operation screen to a UI for a visually impaired user by inputting an instruction.

The dialog box B is provided with: a text box TB41 for displaying a message prompting the user to confirm whether to convert the operation screen to a UI for visually impaired users, a check box CB41, a yes button BT41, and a no button BT42. , the check box CB41 is used to allow the user to input an instruction to display the dialog box B that will not be displayed on the LCD17 in the future, and the Yes button BT41 allows the user to input an instruction to convert the operation screen to a UI for users with visual impairments, The NO button BT42 allows the user to input an instruction not to transition the operation screen to the UI for the visually impaired user.

The text box TB41 displays, for example, text data "You can convert the screen to a window suitable for keyboard operation corresponding to voice expression software". Also, text data "Do not show this message in the future" is displayed on the right portion of the check box CB41. In addition, button names "Yes" and "No" are assigned to the Yes button BT41 and the No button BT42, respectively.

This configuration facilitates input operations by visually impaired users because the screen reader can convert the text data displayed in the text box TB41, the text data displayed in the right part of the check box CB41, and the buttons provided in the dialog box B The button names of BT41 and BT42 are converted into sound signals.

If the user performs an input operation to press the Yes button BT41, the operation screen on the LCD 17 is shifted to the UI for the visually impaired user. If the NO button BT42 is pressed, the operation screen remains unchanged. When one of the buttons BT41 and BT42 is pressed, the window in which the dialog B is displayed is closed.

If the user has entered a check mark in check box CB41 when button BT41 or BT42 is pressed, CPU 11 sets the confirmation display flag stored in confirmation display flag storage area 14c4 to "invalid".

Returning to FIG. 7, in S73, the CPU 11 determines whether or not the Yes button BT41 has been pressed in the dialog B. If the YES button BT41 has been pressed (S73: YES), at S74, the CPU 11 determines whether a check mark has been inserted into the check box CB41.

When the check mark has been inserted into the check box CB41 of dialog B (S74: YES), at S75, the CPU 11 sets the confirmation display mark stored in the confirmation display mark storage area 14c4 to "invalid".

However, if the check mark has not been input into the check box CB41 (S74: NO), the CPU 11 skips S75, and proceeds to S76.

At S76, the CPU 11 stores the UI type ("1" in the first embodiment) for indicating the visually impaired user in the UI type storage area 14c5. At S77, CPU 11 converts the operation screen displayed on LCD 17 into an operation screen corresponding to the UI type stored in UI type storage area 14c5, ie, UI for visually impaired users. Specifically, the CPU 11 closes the window in which the UI for the visible user is displayed, acquires a new window from the OS, and displays the UI for the visually impaired user within the newly acquired window. At S80 , the CPU 11 displays the screen switching button BT7 (see FIG. 2A ) in the display area of the UI for the visually impaired user on the LCD 17 , and then ends the screen switching process A.

However, if the NO button BT42 is pressed in the dialog B (S73: NO), then in S78, the CPU 11 determines whether a check mark has been input into the check box CB41.

If the check mark is inserted into the check box CB41 (S78: YES), at S79, the CPU 11 sets the check mark stored in the check mark storage area 14c4 to "invalid". However, if the check mark is not inserted into the check box CB41 (S78: NO), the CPU 11 ends the screen switching process A without executing the process in S79.

If the confirmation display flag is set to "valid" when switching the UI for visible users displayed on the LCD 17 to the UI for visually impaired users, then the display is switched by the screen shown in FIG. Processing A, the CPU 11 may display a dialog B on the LCD 17 for prompting the user to confirm whether to switch the operation screen to the UI for the visually impaired user. Also, when the dialog box B is displayed, the CPU 11 may convert the operation screen displayed on the LCD 17 into a UI for the visually impaired user on the condition that the user inputs an instruction to convert the operating screen into a UI for the visually impaired user. UI. Therefore, this configuration can prevent the UI for the visually impaired user from being displayed on the LCD 17 when the user is a visual user.

In other words, by providing the screen switching button BT7 within the display area of the UI for the visually impaired user when the UI is displayed on the LCD 17, the visible user can switch the screen switching button BT7 for the visually impaired user to the screen switching button BT7. The UI for the visually impaired user is switched to the UI for the visible user without waiting for the CPU 11 to determine the type of user within the main process of FIG. 4 .

Next, the screen switching process B of S20 executed by the CPU 11 will be described with reference to FIG. 8 .

FIG. 8 is a flowchart illustrating steps within screen switching processing B. FIG. This processing is performed for switching the UI for the visually impaired user displayed on the LCD 17 to the UI for the sighted user. In S81 of the start of the screen switching process B, the CPU 11 determines whether or not the confirmation display flag stored in the confirmation display flag storage area 14c4 is set to "valid". If the confirmation display flag is set to "effective" (S81: Yes), then at S82, CPU 11 displays a dialog box C on LCD 17 for prompting the user to confirm whether the operation screen is converted to be used for the visible user. UI. However, if the confirmation display flag is set to "invalid" (S81: NO), the CPU 11 skips the processing in S82-S85, and proceeds to S86.

Here, dialog C will be explained with reference to FIG. 9B. FIG. 9B is a screenshot showing an example of dialog C. FIG. The dialog box C is a window for displaying a message prompting the user to confirm whether to convert the operation screen to a UI for the user to see by inputting an instruction.

The dialog box C is provided with: a text box TB51 for displaying a message prompting the user to confirm whether to convert the operation screen to a UI for the visible user, a check box CCB51, a yes button BT51, and a no button BT52. , the check box CCB51 is used to allow the user to insert an instruction that the dialog box C will not be displayed on the LCD17 in the future, and the yes button BT51 allows the user to input an instruction to convert the operation screen into a visible UI for the user. The NO button BT52 is used to allow the user to input an instruction not to convert the operation screen into a UI for the user to see.

The text box TB51 displays, for example, text data "You can switch the screen to a viewable window suitable for mouse operations (note: information within the screen cannot be read by a screen reader, and input operations cannot be performed using a keyboard)". Also, text data "Do not show this message in the future" is displayed on the right of the check box CB51. In addition, button names "Yes" and "No" are assigned to the Yes button BT51 and the No button BT52, respectively.

Because the text data and other content displayed within dialog C is not declared to the visually impaired user, it will be difficult for the visually impaired user to recognize the content within dialog C. Therefore, it is impossible for the visually impaired user to perform an input operation on the button BT51 within the dialog C to convert the UI for the visually impaired user into the UI for the visually impaired user. Therefore, this configuration reduces the chance that a visually impaired user who operates the PC 1 mistakenly switches the UI for the visually impaired user displayed on the LCD 17 to the UI for the visually impaired user.

The screen reader cannot convert the text data displayed in the text box TB51 and on the right side of the check box CB51 and the button names of the buttons BT51 and BT52 provided in the dialog C into sound signals.

Also, the dialog box C is configured to accept input operations using the mouse 16 only. Therefore, only when the Yes button BT51 is clicked using the mouse 16, the operation screen on the LCD 17 is switched to the UI for the visible user. In other words, since such an input operation is difficult to be performed by a visually impaired user, it can be assumed that a user who performs an input operation within the dialog C is a visible user. Since it is difficult for the visually impaired user to perform an input operation using the mouse 16, it is impossible for the visually impaired user to click the Yes button BT51 to convert the UI for the visually impaired user to the UI for the visible user. Therefore, this configuration reduces the chance that a visually impaired user who operates the PC 1 mistakenly switches the UI for the visually impaired user displayed on the LCD 17 to the UI for the visually impaired user. When the NO button BT52 is pressed, the operation screen is not switched. Also, when the Yes button BT51 or the No button BT52 is pressed, the window in which the dialog C is displayed is closed.

Also, since the message transition to the UI for the visible user is suppressed for the visually impaired user, the visually impaired user can avoid such unnecessary input operations, making the system more user-friendly.

When the user performs an input operation on the mouse 16 to press the Yes button BT51, the operation screen on the LCD 17 is switched to a UI for the visible user. If the NO button BT52 is pressed, the operation screen is left unchanged.

Also, if the user has inserted a check mark in the check box CB41 when the Yes button BT51 or the No button BT52 is pressed, the CPU 11 sets the confirmation display mark stored in the confirmation display mark storage area 14c4 to "invalid".

Returning to FIG. 8, at S83, the CPU 11 determines whether or not the Yes button BT51 within the dialog C displayed on the LCD 17 has been pressed using a mouse click operation. If the Yes button BT51 has been clicked (S83: YES), at S84, the CPU 11 determines whether a check mark has been inserted in the check box CB51.

If the check mark has been inserted in the check box CB51 (S84: YES), at S85, the CPU 11 sets the confirmation display flag stored in the confirmation display flag storage area 14c4 to "invalid".

However, if a check mark has not been inserted into check box CB51 (S84: NO), CPU 11 skips S85, and proceeds to S86.

At S86, the CPU 11 stores the UI type ("2" in the first embodiment) for indicating the visible user in the UI type storage area 14c5. In S87, the CPU 11 switches the operation screen displayed on the LCD 17 into an operation screen corresponding to the UI type stored in the UI type storage area 14c5, that is, the UI for the visible user, and then ends the screen switching process B. . In other words, the CPU 11 closes the window in which the UI for the visually impaired user is displayed, acquires a new window from the OS, displays the UI for the visual user within the newly acquired window, and ends the processing.

However, if the CPU 11 determines in S83 that the No button BT52 is pressed in the dialog C (S83: NO), then in S88 the CPU 11 determines whether a check mark is inserted into the check box CB51.

If the check mark is inserted into the check box CB51 (S88: YES), at S89, the CPU 11 sets the check display flag stored in the check display mark storage area 14c4 to "invalid".

However, if the check mark is not inserted into the check box CB51 (S88: NO), the CPU 11 ends the screen switching process B without executing the process in S89.

If the confirmation display flag is set to "valid" when the UI for the visually impaired user displayed on the LCD 17 is switched to the UI for the visible user, by the screen switching process shown in FIG. 8 B. The CPU 11 may display a dialog C on the LCD 17 for prompting the user to confirm whether to convert the operation screen to a UI for the user to see. Also, when the dialog box C is displayed, the CPU 11 can switch the operation screen displayed on the LCD 17 to the UI for the visible user on condition that the user inputs an instruction to switch to the UI for the visible user . Therefore, since the user must use the mouse 16 to perform an input operation in order to convert the operation screen into a UI for a visible user, it is impossible for a visually impaired user to mistakenly convert the operation screen into a UI for a visible user. UI.

In the first embodiment, the CPU 11 can determine whether the user is visually impaired or visible according to the user settings for the PC 1 and the characteristics of the user's input operation, and convert the operation screen to the most suitable screen for the user. Therefore, when the visually impaired user performs an input operation, even when the UI for the visually impaired user is displayed on the LCD 17, the operation screen is switched to the UI for the visually impaired user, thereby making the system sensitive to the visually impaired. Impaired users are more user friendly, wherein each operation is time consuming for visually impaired users. Moreover, when a visible user performs an input operation, even when a UI for a visually impaired user is displayed on the LCD 17, the operation screen is switched to a UI for a visible user, so that the system is Visible users are more user friendly.

Also, by providing the screen switching button BT7 in the UI for visually impaired users, before the CPU 11 determines the type of the user in the user type determination process of FIG. The UI for the visually impaired user displayed on the LCD 17 is switched to the UI for the visible user. Therefore, the addition of this button is convenient for the visible user.

Next, the use state acquisition process executed by the CPU 11 of the PC 1 as a first variation of the use state acquisition process (see FIG. 5 ) in S32 will be described with reference to FIG. 10 . Although the CPU 11 acquires a single user setting for the PC 1 in the usage status acquisition processing of the first embodiment, in the usage status acquisition processing according to the first variation, the CPU 11 acquires a plurality of user settings for the PC 1, and determines whether Each of these settings is implemented to facilitate use by visually impaired users.

FIG. 10 is a flowchart illustrating steps within the use state acquisition process according to the first variation of the first embodiment.

In S91 of the use status acquisition process, the CPU 11 initializes the conditional match count memory 13d. In S92, the CPU 11 determines whether the speed of movement of the mouse cursor within the OS setting is slower than the default setting established when the OS is installed. Specifically, the CPU 11 determines that the speed of the mouse cursor is set to "slow". If the mouse cursor speed is set slower than the default setting (S92: YES), then in S93, the CPU 11 increments the count value stored in the condition meeting count storage area 13d by "1". However, if the cursor mouse is not set slower than the default setting (S92: NO), the CPU 11 skips S93, and proceeds to S94.

At S94, the CPU 11 determines whether the text size set in the OS setting for the text size displayed on the screen is larger than the default setting established when the OS is installed. Specifically, the CPU 11 determines whether the text size is set to "large". If the text size is set larger than the default setting (S94: YES), in S95, the CPU 11 increments the count value in the condition meeting count storage area 13d by "1". However, if the text size is not set larger than the default setting (S94: NO), the CPU 11 skips S95, and proceeds to S96.

At S96, the CPU 11 determines whether the screen reader is installed (stored) in the screen reader storage area 14b. If the screen reader is installed on the screen reader storage area 14b (S96: YES), then at S97, the CPU 11 increments the count value stored in the condition meeting count storage area 13d by "1". However, if the screen reader is not installed (S96: NO), CPU 11 skips S97, and proceeds to S98.

At S98, the CPU 11 determines whether the screen reader is operating. If the screen reader is running (S98: YES), at S99, the CPU 11 increments the count value stored in the condition meeting count storage area 13d by "1". However, if the screen reader is not operating (S98: NO), the CPU 11 skips S99, and proceeds to S100.

At S100, the CPU 11 determines whether or not the count stored in the condition meeting count storage area 13d exceeds "2". If the count exceeds "2" (S100: YES), in S101, the CPU 11 sets the conditional compliance flag stored in the conditional compliance flag storage area 13a to "valid", and then ends the use state acquisition process. However, if the count is not greater than "2" (S100: NO), then at S102, the CPU 11 sets the conditional compliance flag to "invalid", and then ends the use state acquisition processing.

Through the use status acquisition processing shown in FIG. 10, the CPU 11 acquires a plurality of user settings for the PC1, and when the number of settings for facilitating use by a visually impaired user exceeds "2", it can be set by assuming that the PC1 To facilitate use by visually impaired users, set the conditional match flag to "active". In other words, if the number of settings performed to facilitate use of the PC 1 by a visually impaired user exceeds "2", the user is likely to be visually impaired.

Next, operation acquisition processing according to second, third, and fourth variations that are variations of the operation acquisition processing of the first embodiment will be described with reference to FIGS. 11A-11C .

First, the operation acquisition processing in the second variation will be explained. Fig. 11A is a flowchart illustrating steps within an operation acquisition process according to the second variation of the first embodiment. Although the operation acquisition processing of S34 in the first embodiment is for acquiring an input operation within its own program, this processing is performed to acquire user execution within a plurality of application programs preset as targets of operation acquisition. input operation.

In S111 of the operation acquisition process, the CPU 11 acquires a key operation performed on the keyboard 15 or a mouse operation performed on the mouse 16 . In S112, the CPU 11 determines whether the input operation acquired in S111 is performed in one of the target application programs. If the acquired input operation is performed within one of the target application programs (S112: YES), the CPU 11 ends the operation acquisition process. However, if the acquired input operation is not performed in one of the target application programs (S112: NO), the CPU 11 returns to S111, and repeats the processing in S111-112.

Through the operation acquisition processing shown in FIG. 11A , the CPU 11 can acquire an input operation performed in one of a plurality of application programs preset as a target of operation acquisition from among input operations performed using the keyboard 15 and mouse 16 .

For example, if an application that aims at operation acquisition and can input operations using the keyboard 15 and mouse 16 mainly uses the mouse 16 to input operations when the user can see it, when the input operation is performed using the keyboard 15, it is difficult to It is possible that the user is visually impaired. In other words, since there is a considerable difference between the characteristics of input operations performed by a visually impaired user and a seeing user, it is possible to determine with greater accuracy whether the user is visually impaired or is Visible. Examples of applications in which input is mainly performed using a pointing device are image processing programs and application X.

Next, operation acquisition processing in the third embodiment will be described. Fig. 11B is a flowchart of steps within the operation acquisition process according to the third embodiment. This processing is for acquiring input operations performed within applications other than word processing software such as MS Word (registered trademark) and spreadsheet software such as MS Excel (registered trademark).

In S113 of the operation acquisition process, the CPU 11 acquires a key operation performed on the keyboard 15 or a mouse operation performed on the mouse 16 . In S114, the CPU 11 determines whether the input operation acquired in S113 is performed in the word processing program. If the acquired input operation is performed in an application program other than the word processing program (S114: NO), in S115, the CPU 11 determines whether the acquired input operation is performed in a spreadsheet program.

If the acquired input operation is performed within an application other than the spreadsheet program (S115: NO), the CPU 11 ends the operation acquisition process.

However, if the CPU 11 determines in S114 that the acquired input operation is performed in a word processing program (S114: Yes), or determines in S115 that the acquired input operation is performed in a spreadsheet program (S115: Yes), the CPU 11 returns S113, and repeat the processing in S113-S115.

Through the operation acquisition processing shown in FIG. 11B , the CPU 11 can acquire input operations performed in application programs other than word processing or spreadsheet programs from input operations performed using the keyboard 15 and mouse 16 .

Here, the keyboard 15 is commonly used to perform input operations within word processing and spreadsheet programs, regardless of whether the user is visually impaired or sees, showing little difference in the characteristics of the input operations. Thus, by not capturing input operations performed within word processing and spreadsheet programs, it is possible to determine with a greater degree of accuracy whether a user is visually impaired or can see.

Next, the operation acquisition processing according to the fourth modification will be explained. FIG. 11C is a flowchart illustrating steps in the operation acquisition process in the fourth variation. In this process, when word processing software such as MS Word (registered trademark) or spreadsheet software such as MS Excel (registered trademark) is running on the PC 1, no input operation is acquired.

In S116 of the operation acquisition process, the CPU 11 acquires a key operation performed on the keyboard 15 or a mouse operation performed on the mouse 16 . At S117, the CPU 11 determines whether a word processing program is running. If the word processing program is not running (S117: NO), at S118, the CPU 11 determines whether the spreadsheet program is running. If the spreadsheet program is not running (S118: NO), the CPU 11 ends the operation acquisition processing.

If the CPU 11 determines in S117 that the word processing program is running (S117: YES) or in S118 that the spreadsheet program is running (S118: YES), the CPU 11 returns to S116, and repeats the processing in S116-S118.

By the operation acquisition processing shown in FIG. 11C , the CPU 11 can acquire input operations from among input operations performed using the keyboard 15 and mouse 16 while the word processing program or the spreadsheet program is running.

Furthermore, the method for determining whether a word processing program or spreadsheet program is running and determining not to capture input operations when such a program is running is less effective than determining whether each Input operations are easier to operate.

Next, user type determination processing in the fifth variation of the first embodiment will be explained. This processing is a variation of the user type determination processing (FIG. 5) in the first embodiment.

Fig. 12 is a flowchart illustrating steps within user type determination processing according to the fifth modification of the first embodiment. This processing is performed to determine whether the operator of the PC 1 is visually impaired or visible according to the nature of the input operation performed to display the menu bar on the LCD 17 .

In S121 of the user type determination process, the CPU 11 initializes the key input count storage area 13e. In S32, the CPU 11 executes the use state acquisition process shown in FIG. 6A. In S122, the CPU 11 determines whether or not the conditional compliance flag stored in the conditional compliance flag storage area 13a is set to "valid". If the conditional match flag is set to "valid" (S122: YES), at S34, the CPU 11 executes the operation acquisition process shown in FIG. 6B. However, if the conditional compliance flag is set to "invalid" (S122: No), the CPU 11 skips the processing in S34-S127, and proceeds to S128,

In S123, the CPU 11 determines whether the input operation acquired in S34 is the Alt key. If the acquired input operation is the Alt key (S123: YES), in S124, the CPU 11 increments the count value stored in the key input count storage area 13e by "1".

At S125, the CPU 11 determines whether or not the count value stored in the key input count storage area 13e exceeds "10". If the count exceeds "10" (S125: Yes), then at S126, the CPU 11 stores the user type ("1" in the fifth variation) for indicating a user with visual impairment in the user type storage area 13h of the RAM 13 ), and then end the user type determination processing.

However, if the count value is not greater than "10" (S125: NO), the CPU 11 returns to S34, and repeats the processing in S34-S125 as described above.

Also, if the CPU 11 determines in S123 that the Alt key operation is not acquired (S123: NO), then in S127, the CPU 11 determines whether the acquired input operation is a mouse click for displaying a menu bar. If the acquired input operation is a mouse click (S127: Yes), then at S128, the CPU 11 stores the user type ("2" in the fifth variation) in the user type storage area 13h for indicating the visible user. ), and then the user type determination processing ends.

However, if the CPU 11 determines in S127 that the acquired input operation is not a mouse click for displaying the menu bar (S127: NO), the CPU 11 returns to S34, and repeats the processing in S34-S127 as described above.

In most application programs, the user usually displays a menu bar on the LCD 17, and selects a desired process within the menu bar to execute this process. Therefore, the operation for displaying the menu bar on the LCD 17 is frequently performed within the input operation.

When the menu bar is displayed on the LCD 17 using the keyboard 15, it is possible that a visually impaired user is using the application. If the menu bar is displayed on the LCD 17 using the mouse 16, it may be visible to the user.

Through the user type determination process described in FIG. 12, the CPU 11 can determine whether the operator of the PC 1 is visually impaired or visible according to the user settings for the PC 1, and can determine whether to use the keyboard 15 or the mouse 16 to Input is performed to display the operation of the menu bar on the LCD 17 .

Although the present invention has been described in detail with reference to the first embodiment and its variations, it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit of the present invention. .

For example, in S80 (see FIG. 7 ) of the screen switching process A according to the first embodiment, the PC 1 displays the screen switching button BT7 in the display area of the UI for the visually impaired user. However, the PC1 may be configured to display this screen switching button BT7 outside the display area of the UI for the visually impaired user.

Specifically, a screen switching button BT7 may be displayed at a predetermined position within the display area of the LCD 17 (eg, within the lower right corner of the display area), as shown in FIG. 13A . In this case, the visible user can easily find the screen switching button BT7 by looking at the predetermined position even when the display on the LCD 17 is mixed with a plurality of operation screens. Therefore, the visible user can easily convert the UI for the visually impaired user to the UI for the visible user, even when the display on the LCD 17 is mixed, making the configuration useful for the visually impaired. See the user is user friendly. When the UI for the visible user is displayed on the LCD 17, the screen switching button BT7 is not displayed on the LCD 17, as shown in FIG. 13B.

In the first embodiment as described above, when the screen switching button BT7 is pressed, the UI for the visually impaired user displayed on the LCD 17 is switched to the UI for the visible user. However, a check box CB may be provided within the display area of the UI for sight-impaired users to designate whether to convert the UI for sight-impaired users to the UI for sighted users. By pressing the setting button BT1 when the check box CB is checked, the PC 1 can be configured to change the operation screen to a UI for a visible user.

Next, the PC 101 according to the second embodiment will be described with reference to FIGS. 14A-15B. The PC 101 has the same configuration as the PC 1 according to the first embodiment, except that the PC 101 also executes function execution processes A and B.

Therefore, although the PC 1 according to the first embodiment displays the screen switching button BT7 in the display area of the UI when the UI for the visually impaired user is displayed on the LCD 17, when the UI for the visually impaired user PC 101 according to the second embodiment also displays screen switching button BT7 in the display area of the operation screen for each function on LCD 7 when one of buttons BT1-BT11 (excluding screen switching button BT7) is pressed in the UI.

As described in FIG. 2A, the UI for visually impaired users and the UI for visible users are provided with buttons BT1-BT11 (except the screen switching button BT7) and buttons BT21-BT26 and graphic buttons GBT21-GBT24, respectively. , for using various functions of the MFP100. When the user presses one of these buttons, an operation screen for the function corresponding to the pressed button is displayed on the LCD 17 .

The function's operation screen enables the user to perform settings for the application X or use the functions of the MFP 100 and input instructions for setting options.

Next, function execution processing A performed by the CPU 11 of the PC 10 will be described with reference to FIG. 14A . FIG. 14A is a flowchart illustrating steps within a function execution process.

The function execution process is executed to display an operation screen corresponding to the function of the buttons BT1-BT11 pressed by the user (except for the screen switching button BT7) when the UI for the visually impaired user is displayed on the LCD 17, and to display the operation screen in the function The screen switching button BT7 is displayed in the display area of the operation screen. This processing is repeatedly performed while application X is running. The function execution processing is stored in, for example, the application program X storage area 14c.

In S211 of the function execution process, the CPU 11 determines whether the user presses one of the buttons BT1-BT11 in the UI for the visually impaired user. The CPU 11 waits while one of the buttons BT1-BT11 is not pressed (S211: NO). When one of the buttons BT1-BT11 is pressed (S211: YES), at S212, the CPU 11 determines whether the pressed button is the screen switching button BT7.

If the pressed button is the screen switching button BT7 (S212: YES), at S20, the CPU 11 executes the screen switching process B in FIG. 8 as described above, and returns to S211.

However, when the pressed button is not the screen switching button BT7 (S212: No), at S213, the CPU 11 displays on the LCD 17 the operation for the function corresponding to the pressed buttons BT1-BT11 (except the screen switching button BT7) Screen. Specifically, the CPU 11 acquires a window from the OS, and displays an operation screen for a function corresponding to the pressed button within the acquired window.

In S214, the CPU 11 displays the screen switching button BT7 in the display area of the operation screen of the function, and returns to S211.

For example, when the user presses the scan button BT2 using the keyboard 15 or the mouse 16 while the UI for a visually impaired user is displayed on the LCD 17, the CPU 11 displays a scanner function operation screen for scanning using the MFP 100 on the LCD 17. scanner function, and then, a screen switching button BT7 is displayed in the display area of this scanner function operation screen.

FIG. 14B is a screenshot showing an example of the scanner function operation screen displayed on the LCD 17 when the user presses the scan button BT2 within the UI for visually impaired users.

The scanner function operation screen shown in FIG. 14B includes a save format selection button SB61, a resolution selection button SB62, a scan type selection button SB63, a screen switching button BT7, an OK button BT61 and a cancel button BT62.

A save format selection button SB61 enables the user to select one of a plurality of options for a format for saving an image file generated when an original document is scanned using the scanner function of the MFP 100 . The resolution selection button SB62 enables the user to select one of a plurality of options for the resolution of image data generated when an original document is read using the scanner function.

The scan type selection button SB63 enables the user to select one of a plurality of selections for the number of colors within image data generated when an original document is scanned using the scanner function. The screen switching button BT7 enables the user to switch the operation screen displayed on the LCD 17 into a UI for the user to see.

The OK button BT61 accepts settings of the saving format, resolution, and number of colors of image data, and issues an instruction to start scanning the document. When the OK button BT61 is pressed, the original document arranged on the scanning surface of the MFP 100 is scanned according to the settings selected using the selection buttons SB61-SB63 to generate image data. The cancel button BT62 is used to close the scanner function operation screen displayed on the LCD 17 without performing a scanning operation.

As described above, if the user presses the scan button BT2 while displaying the UI for visually impaired users on the LCD 17, the CPU 11 displays the scanner function operation screen on the LCD 17, and further scans in the display area of the scanner function operation screen. Display screen switching button BT7.

The above description is just one example for displaying the scanner function operation screen on the LCD 17 when the scan button BT2 is pressed. Similar operation screens for other functions are displayed on the LCD 17 when the corresponding buttons BT1-BT11 (excluding the screen switching button BT7 ) are pressed, but descriptions of these operation screens are not provided.

By the function execution process A shown in FIG. 13A, the CPU 11 can display operations for functions corresponding to the buttons BT1-BT11 pressed by the user (excluding the screen switching button BT7) within the UI for the visually impaired user. screen, and a screen switching button BT7 may be further displayed in the display area of the operation screen of the function.

Therefore, irrespective of which operation screen is displayed, the visible user can simply select the screen switching button BT7 to convert the UI for the visually impaired user displayed on the LCD 17 into the UI for the visible user, so that This configuration is convenient for visible users.

Also, if the display on the LCD 17 is cluttered with multiple windows including operation screens for other programs besides the UI for the visually impaired user and the operation screens for other functions, the visible user remains The screen switching button BT7 can be easily found only by finding one of the UI for the visually impaired user and the operation screen for the function. Therefore, the visible user can easily convert the UI for the visually impaired user to the UI for the visible user even when the display on the LCD 17 is mixed, thereby making this configuration useful for the visually impaired. Visible users are convenient.

Next, function execution processing B in the second embodiment will be explained. FIG. 15A is a flowchart illustrating steps within function execution processing B. FIG.

The function execution process is for displaying the function corresponding to this button on the LCD17 when the user selects one of the buttons BT21-BT26 or the graphic buttons GBT21-GBT24 in the visible user UI displayed on the LCD17. Handling of the operation screen. While the application program X is running, the function execution process B is repeatedly executed by the PC 101 . This application program that executes the function execution process B is stored in, for example, the application program X storage area 14c.

In S221 of the function execution process, the CPU 11 determines whether the user has pressed one of the buttons BT21-BT26 or the graphic buttons GBT21-GBT24 within the UI for the visible user. When none of these buttons is pressed (S221: NO), the CPU 11 continues to wait. When one of the buttons is pressed (S221: YES), then at S222, the CPU 11 displays on the LCD 17 an operation screen corresponding to the function of the pressed button.

Specifically, the CPU 11 acquires a window from the OS, and displays an operation screen for a function corresponding to the pressed button within the acquired window. Subsequently, the CPU 11 returns to S381, and repeats the processing in S221-S222.

For example, if the user selects the scan button BT22 using the keyboard 15 or the mouse 16 while the UI for the visible user is displayed on the LCD 17, the CPU 11 displays a scanner function operation screen on the LCD 17 to use the scanner function of the MFP 100 . Also, the screen switching button BT7 is not displayed in this operation screen.

FIG. 15B is a screenshot showing an example of the scanner function operation screen displayed on the LCD 17 when the user selects the scan button BT22 within the UI for visible users. In the example of FIG. 14B , the scanner function operation screen is provided with a save format selection button SB61 , a resolution selection button SB62 , a scan type selection button SB63 , an OK button BT61 and a cancel button BT62 . Selection buttons SB61-SB63 and buttons BT61 and BT62 are the same as those in FIG. 13B, and therefore, descriptions of these buttons are not repeated.

As shown in FIG. 15B , when the user selects the scan button BT22 within the UI for visible user, only the scanner function operation screen is displayed on the LCD 17 . The screen switching button BT7 is not displayed.

The above description is only an example of the scanner function operation screen displayed on the LCD 17 when the scan button BT22 is pressed. Operation screens for other functions are similarly displayed on the LCD 17 when one of the other buttons BT21-BT26 or the graphic buttons GBT21-GBT24 is pressed, but descriptions of these operation screens will not be provided.

By performing the processing B by the function shown in FIG. 15A, when the user presses one of the buttons BT21-BT26 or the graphic buttons GBT21-GBT24 in the UI for visible users displayed on the LCD 17, the CPU 11 can display the The operation screen corresponding to the function of this button.

In the second embodiment as described above, when the user presses one of the buttons BT1-BT11 (excluding the screen switching button BT7) in the UI for visually impaired users displayed on the LCD 17, the CPU 11 displays on the LCD 17 the An operation screen corresponding to the function of the pressed button, and a screen switching button BT7 is further displayed in the display area of the operation screen of the function. Therefore, the visible user can easily switch the UI for the visually impaired user to the UI for the visible user by operating the screen switching button BT7 within the operation screen for any function. Therefore, this configuration is user-friendly to the visible user.

Also, if the display on the LCD 17 is cluttered with multiple windows including operation screens for other programs besides the UI for the visually impaired user and the operation screens for other functions, the visible user remains The screen switching button BT7 can be easily found just by finding one of the UI for the visually impaired user and the operation screen for the function. Therefore, the visible user can easily convert the UI for the visually impaired user to the UI for the visible user even when the display on the LCD 17 is mixed, thereby making this configuration useful for Visible users are convenient.

Next, the PC 1001 according to the third embodiment will be explained. In the third embodiment, the application program Y and the startup program are installed on the PC1001. Application Y has an operation screen for visually impaired users and an operation screen for sighted users. Launcher is used to start application Y. When run, the startup program determines whether the user of PC 1001 is a visually impaired user or a sighted user. Next, when the user issues an instruction to start the application program Y, the launcher instructs the application program Y to display an operation screen most suitable for the user.

For example, if a visually impaired user issues an instruction to start application Y having a plurality of operation screens while the above-mentioned startup program is running on PC1001, the startup program starts application Y so that application Y is displayed on LCD 17. Defective user most convenient to operate the screen. Therefore, this configuration is user-friendly for a visually impaired user, for whom each operation is time-consuming.

First, the configuration of the PC 1001 according to the third embodiment will be explained.

FIG. 16A is a block diagram showing the electrical configuration of the hard disk 34 provided in the PC 1001. Since the electronic structure of the PC 1001 is the same as that of the PC 1 (see FIG. 1 ) according to the first embodiment except for the hard disk 34, only the structure of the hard disk 34 will be described here.

The hard disk 34 is a rewritable nonvolatile memory capable of retaining data even after the power to the PC 31 is turned off. The hard disk 34 is provided with an OS storage area 34a, a screen reader storage area 34b, a startup program storage area 34c, and an application program Y storage area 34d.

The OS storage area 34a has the same configuration as the OS storage area 14a described in the first embodiment, and the screen reader storage area 34b has the same configuration as the screen reader storage area 14b described in the first embodiment. Structure. Therefore, descriptions of these storage areas are not repeated here.

The startup program storage area 34c stores a startup program for starting the program when the user issues an instruction to start the program, and instructing the program to display an operation screen most suitable for the user. The startup program storage area 34c stores programs for executing the user type monitoring processing shown in FIG. 16B and the application start processing illustrated in the flowchart of FIG. 17 .

The startup program storage area 34c is also provided with a command execution flag storage area 34c1, a command table storage area 34c2, and an argument table storage area (argument table memory area) 34c3.

The command execution flag storage area 34c1 stores a command execution flag indicating whether to start the program when the user issues an instruction to execute the program and instructing the program to display an operation screen most suitable for the user. The startup program starts a program that the user has issued an instruction to start, and instructs the program to display an operation screen most suitable for the user when the command execution flag is set to "valid" ("1" in the third embodiment).

However, when the command execution flag is set to "invalid" ("0" in the third embodiment), the startup program only starts the program that the user has issued an instruction to start. In this case, the program displays a designated operation screen set as a default screen (for example, a UI for a visible user). When the monitoring program is installed on the hard disk 34, the user can be prompted to set the command execution flag to "valid" or "invalid", or the user can be allowed to set the flag to "" by operating on the keyboard 15, mouse 16, etc. valid" or "invalid".

The command table storage area 34c2 stores commands for starting the application program Y. The argument table storage area 34c3 stores: a display command (command option or command argument) for instructing application Y to display a UI for visually impaired users on LCD 17 when application Y is started, and, A display command for instructing the application Y to display a UI for a visible user on the LCD 17 .

When a display command is input to the OS contents after specifying a command for the OS to start the application Y, the OS starts the application Y. When the application program Y starts execution, the CPU 11 displays the UI for the visually impaired user or the UI for the visible user on the LCD 17 in accordance with the command of the display command.

Application program Y storage area 34d stores application program Y, which is a program that can be executed on PC 1001 . The application program Y may be, for example, the application program X described in the first embodiment. The application program Y storage area 34d provides a visually impaired person UI storage area 34d1 and a sighted person UI storage area 34d2.

The visually impaired UI storage area 34d1 stores a UI for visually impaired users, which is an operation screen for facilitating the visually impaired user to perform an input operation. For example, the visually impaired UI storage area 34d1 stores the UI for visually impaired users shown in FIG. 2A. The visible person UI storage area 34d2 stores the UI for the visible user, which is an operation screen for facilitating the input operation of the visible user. For example, the visible person UI storage area 34d2 stores the UI for the visible user shown in FIG. 2B.

Next, user type monitoring processing executed by the CPU 11 of the PC 1001 will be described with reference to FIG. 16B.

Figure 16B is a flowchart illustrating steps within the user type monitoring process. This processing is performed to monitor the operator of the PC 31 to determine whether the user is visually impaired or sees based on the user's settings for the PC 1001 and the characteristics of the user's input operation.

In S311 of the user type monitoring process, the CPU 11 initializes the condition of the RAM 13 to meet the flag storage area 13a (FIG. 1). Specifically, the CPU 11 stores a user type ("2" in the third embodiment) indicating a visible user in the user type storage area 13h (FIG. 1).

In S312, the CPU 11 determines whether or not the command execution flag stored in the command execution flag storage area 34c1 is set to "valid". If the command execution flag is set to "valid" (S312: YES), at S13, the CPU 11 executes the user type determination process shown in FIG. 5 . In S313, the CPU 11 waits for a specified time (for example, 10 minutes), and then returns to S312 to repeat the processing in S312-S313 as described above. If the CPU 11 determines in S312 that the command execution flag is "invalid" (S312: NO), the CPU 11 ends the user type monitoring process.

Also, when the user issues an instruction of activation and command, the CPU 11 of the PC 1001 can execute to display an operation screen most suitable for the user. For example, the CPU 11 can execute the application startup process shown in FIG. 17 .

FIG. 17 is a flowchart illustrating steps within the application launch process. This processing is performed to start the program when the user issues an instruction to start the program and order the program to display an operation screen most suitable for the user.

In S321, the CPU 11 determines which application stored on the hard disk 34 is instructed to start. In this description, it will be assumed that application Y has been instructed to start. In S322, the CPU 11 reads the user type stored in the user type storage area 13h (FIG. 1), and in S323 determines the type of the user specified by the user type.

If the user type indicates a visually impaired user, then in S324, the CPU 11 adds a display command (command option) for displaying a UI for a visually impaired user on the LCD 17 to the execution command for the application program Y, and sends a command to the OS Enter this command inside to start application Y. Subsequently, the CPU 11 ends the application startup processing.

However, if the user type indicates a visible user, then in S325, the CPU 11 adds a display command (command option) for displaying a UI for a visible user on the LCD 17 to the execution command for the application program Y. , and enter this command into the OS to start application Y. Subsequently, the CPU 11 ends the application startup processing.

Through the application start processing described in FIG. 17, the CPU 11 can start the program when the user issues an instruction to start the program, and can instruct the program to display the most convenient operation screen for the user.

As described above, when the startup program according to the third embodiment is run on the PC 1001, the CPU 11 can determine whether the user of the PC 1001 is a visually impaired user or a visually impaired user based on the user settings for the PC 1001 and the characteristics of the user's input operation. and when the user issues an instruction to start the program, the program on the PC 1001 can be started while instructing the program to display an operation screen most suitable for the user. Therefore, if a vision-impaired user issues an instruction for starting a program, the UI for the vision-impaired user of the program is displayed on the LCD 17, making this configuration user-friendly for the vision-impaired user. Also, if a visible user issues an instruction to start a program, the program's UI for the visible user is displayed on the LCD 17, making this configuration user-friendly for the visible user .

Although the present invention has been described in detail with reference to the above-mentioned embodiment and its variations, it will be apparent to those skilled in the art that various changes can be made therein without departing from the spirit of the present invention. and modify.

For example, each variation of the first embodiment described above (usage state acquisition processing, operation acquisition processing, and user type determination processing) can also be applied to the second and third embodiments.

Also, in the use state acquisition process ( FIG. 10 ) according to the first variation of the first embodiment, if more than two conditions are satisfied in the determination steps ( S92 , S94 , S96 and S98 ), the CPU 11 determines that the Settings for PC1 to benefit visually impaired users. However, if at least one of the conditions is satisfied, the CPU 11 may determine that the settings for the PC 1 have been established for the visually impaired user. In addition, in the determining steps of S51 (FIG. 6) and S96 (FIG. 10), CPU 11 may determine whether a screen reader has been set to convert text data on LCD 17 into sound data, or whether a screen reader has been set for starting Screen reader settings as OS settings. In this case, the screen reader storage area 14b may store settings for determining whether the screen reader automatically converts text data into sound, and the OS storage area may store settings for determining whether to activate the screen reader.

In the first embodiment as described above, the operation screen of the application program X is switched to the UI for the visually impaired user or the UI for the sighted user. However, when a plurality of applications having a UI for a visually impaired user or a UI for a visible user are stored on the hard disk 14 or the like and run on the PC 1, the operation screen of each application can be switched .

Also, the processing according to the third embodiment uses the example of starting the application Y. However, if a plurality of application programs having a UI for a visually impaired user and a UI for a visible user are stored on the hard disk 34 when an instruction for starting each application program is issued, the CPU 11 may The corresponding application is launched simultaneously with issuing a command to display an operation screen most suitable for the user. In this case, a command is stored in the command table storage area 34c2 for instructing the startup of each application program stored on the hard disk 34, and a display command (command option) is stored in the startup program storage area 34c to command Each application displays a UI for sight-impaired users on the LCD 17 and is used to instruct each application to display a UI for sighted users on the LCD 17 .

Also, although a mouse is used as an example of a pointing device in the embodiments and variations, any device capable of specifying a display position of a cursor, such as a touchpad, a trackball, or a trackpad, may be used.

Also, when a dialog box is displayed on the LCD 17 within the screen switching process B (FIG. 8), if an input operation on the Yes button BT51 or the No button BT52 is not received within a specified time after the dialog box is displayed, the CPU 11 may determine No button BT52 is pressed.

In the user type determination process (FIG. 5), the CPU 11 counts the number of times a specified key is pressed, but it may also count any key if it is normally used within the application program X and OS.

Claims (10)

1. A data processing device, comprising: a display unit that displays display data including first display data for a visually impaired user and second display data for a sighted user; a user type determination unit that determines whether the user is visually impaired or sees; and a display control unit that controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays the second display data when the user type determination unit determines that the user is visually impaired. Display Data, Wherein, an operating system and a screen reader are installed in the data processing device; Wherein, the data processing device also includes: a first memory capable of storing settings of the operating system; and a second memory capable of storing settings for the screen reader, Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the setting of the operating system and the characteristics of the user input operation, or the setting of the screen reader, Wherein, the data processing device further includes a pointing unit, the pointing unit has a moving member and a button, the user can use the moving member to move the indicator on the display unit and designate the display position of the indicator, the user can inputting user data corresponding to the display position of the pointer using the button; Wherein, the display data includes text; Wherein, the operating system controls the moving speed of the indicator and the size of the text displayed on the display unit, Wherein, the user type determination unit determines that the user is visually impaired when at least two of the following conditions are met: (a) the screen reader is installed, (b) the screen reader is being executed, (c) the moving speed of the pointer is set slower than the default moving speed of the pointer preset in the operating system, (d) the size of the text is set slower than the default moving speed preset in the operating system The default size of text is large. the 2. The data processing apparatus according to claim 1, wherein the screen reader is mountable in the data processing apparatus, and Wherein, the user type determining unit determines that the user is visually impaired when the screen reader has been installed on the data processing device. 3. The data processing device according to claim 1, further comprising: an input unit with which a user can input user data; and an input state determination unit that determines an input state, and Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the input state. 4. The data processing apparatus according to claim 3, wherein the input unit comprises: a pointing unit having a moving member with which a user can move a pointer on the display unit and specifying a display position of the pointer, and a button with which the user can input User data for the display position of the indicator; and a key input unit having a plurality of keys with which a user can input user data, and Wherein, when the input state determining unit determines that the plurality of keys are pressed more than a first specified number of times, the user type determining unit determines that the user is visually impaired. 5. The data processing apparatus according to claim 3, wherein the input unit includes a pointing unit having a moving member and a button with which a user can move a pointer on the display unit and specifying a display position of the pointer, the user can input user data corresponding to the display position of the pointer using the button; and a key input unit having a plurality of keys with which a user can input user data, and Wherein, when the input state determining unit determines that the button is pressed more than a second specified number of times, the user type determining unit determines that the user is visible. 6. A data processing device, comprising: a display unit that displays display data including first display data for a visually impaired user and second display data for a sighted user; a user type determination unit that determines whether the user is visually impaired or sees; and a display control unit that controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays the second display data when the user type determination unit determines that the user is visually impaired. Display Data, The data processing device also includes: a connector connectable to a sound output unit for outputting sound; a sound control unit, when the user type determination unit determines that the user has a visual defect, the sound control unit controls the sound output unit to output a sound for asking the user whether to display the first display data, Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the setting of the operating system and the characteristics of the user input operation, or the setting of the screen reader, Wherein, the data processing device also includes: a key input unit having a plurality of keys with which a user can input data; and a pointing unit having a moving member with which a user can move a pointer on the display unit and specifying a display position of the pointer, and a button with which the user can input user data for the display position of the indicator, and Wherein, when the input data for instructing to display the first display data is input by using the key input unit after the sound output unit outputs the sound, the display control unit controls the display unit to display the first display data. Display Data. 7. A data processing device, comprising: a display unit that displays display data including first display data for a visually impaired user and second display data for a sighted user; a user type determination unit that determines whether the user is visually impaired or sees; and a display control unit that controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays the second display data when the user type determination unit determines that the user is visually impaired. Display Data, The data processing device also includes: a connector connectable to a sound output unit for outputting sound; a sound control unit, when the user type determination unit determines that the user has a visual defect, the sound control unit controls the sound output unit to output a sound for asking the user whether to display the first display data, Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the setting of the operating system and the characteristics of the user input operation, or the setting of the screen reader, Wherein, the data processing device also includes: a key input unit having a plurality of keys with which a user can input data; and a pointing unit having a moving member with which a user can move a pointer on the display unit and specifying a display position of the pointer, and a button with which the user can input user data for the display position of the indicator, Wherein, when the user type determination unit determines that the user can see, the display control unit controls the display unit to display an inquiry display, the inquiry display is used to ask the user whether to display the second display data, and Wherein, when the user uses the pointing unit to input data indicating to display the second display data according to the inquiry display, the display control unit controls to display the second display data. 8. A data processing device, comprising: a display unit that displays display data including first display data for a visually impaired user and second display data for a sighted user; a user type determination unit that determines whether the user is visually impaired or sees; and a display control unit that controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays the second display data when the user type determination unit determines that the user is visually impaired. Display Data, Wherein, when the display unit displays the first display data, the display control unit controls the display unit to also display request data, and the request data is used to ask the user whether to display data on the display unit switching from said first display data to said second display data, and Wherein, when the user indicates to convert the first display data into the second display data according to the display request data, the display control unit controls the display unit to display the second display data, Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the setting of the operating system and the characteristics of the user input operation, or the setting of the screen reader, Wherein, the data processing device further includes a pointing unit, and the user can use the pointing unit to move a pointer on the display unit to designate a display position, Wherein, when the user uses the pointing unit to specify to convert the first display data into the second display data according to the request data, the display control unit controls the display unit to display the second display data . 9. A data processing method, comprising: determine whether the user is visually impaired or can see; and displaying the first display data when it is determined that the user is visually impaired, and displaying the second display data when it is determined that the user is visually impaired, wherein said determining comprises determining whether the user is visually impaired or visible based on operating system settings and characteristics of user input operations, or screen reader settings, wherein the user is determined to be visually impaired when at least two of the following conditions are met: (a) said screen reader is installed, (b) said screen reader is being implemented, (c) the indicator's The moving speed is set to be slower than the default moving speed of the pointer preset in the operating system, and (d) the size of the characters is set to be larger than the default size of the characters preset in the operating system. 10. A data processing system comprising: a first data processing device comprising a display unit that displays display data comprising first display data for a visually impaired user and second display data for a sighted user; and A second data processing device, comprising: a user type determination unit that determines whether the user is visually impaired or sees; and a display control unit that controls the display unit to display the first display data when the user type determination unit determines that the user is visually impaired, and displays the second display data when the user type determination unit determines that the user can see data, wherein an operating system and a screen reader are installed in the data processing system; Wherein, the data processing provision also includes: a first memory capable of storing settings of the operating system; and a second memory capable of storing settings for the screen reader, Wherein, the user type determination unit determines whether the user is visually impaired or visible according to the setting of the operating system and the characteristics of the user input operation, or the setting of the screen reader, Wherein, the data processing system further includes a pointing unit, the pointing unit has a moving member and a button, and the user can use the moving member to move the pointer on the display unit and designate the display position of the pointer, and the user can inputting user data corresponding to the display position of the pointer using the button; Wherein, the display data includes text; Wherein, the operating system controls the moving speed of the indicator and the size of the text displayed on the display unit, Wherein, the user type determining unit determines that the user is visually impaired when at least two of the following conditions are met: (a) the screen reader is installed, (b) the screen reader is being executed, (c) the moving speed of the pointer is set slower than the default moving speed of the pointer preset in the operating system, (d) the size of the text is set slower than the default moving speed preset in the operating system The default size of text is large. the

Images