1 / 19

Beta Text-To-Speech Design Guidelines for CoolReader

Beta Text-To-Speech Design Guidelines for CoolReader. Table of Contents. Type of auditory information General rules for auditory information User interaction and Auditory information Implementation of TTS features Interface type 1. Information page > book contents Interface type 2. List

kendis
Télécharger la présentation

Beta Text-To-Speech Design Guidelines for CoolReader

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Beta Text-To-Speech Design Guidelines for CoolReader

  2. Table of Contents • Type of auditory information • General rules for auditory information • User interaction and Auditory information • Implementation of TTS features • Interface type 1. Information page > book contents • Interface type 2. List • Focused list • Interface type 3. Tab • tab + list selected by tapping • tab + list focused and selected by operating down key • Interface type 4. menu • menu icon focused by operating right key • Interface type 5. popup • Interface type 6. radio button • Interface type 7. checkbox • Interface type 8. edit fields • Interface type 9. grid

  3. Type of auditory information • Assumption on division into two types of auditory information: gesture-based interaction • in the case of key interaction, all could be TTS information given by key input • Type 1. Feed-Forward information given when selecting an interface component • (1) characteristic of the component • button • ratio-button: TTS label- “unselected” or “selected” • check box : TTS label- “unchecked” or “checked” • tab button • list item • edit box • (2) text label of the component • Type 2. Feedback information given after releasing the selected • (1) action that the user does on the component • clicked • unselected/selected • unchecked/checked • (2) type of interface that is not full-sized scene • menu: icon, list • alert : confirmation popup, edit popup, notice popup, setting popup, list popup, iconic popup • keypad • (3) changed status • information on title area • highlighted text

  4. General rules for auditory information • Distinguish different types • when two or more different types of information are spoken, there should be a short pause between types to enhance understandability. • e.g. Button(pause)options(pause)clicked(pause)settings • the length of pause will be determined while checking with a working prototype. • 2. Priority of auditory information • Priority will be put as follows when multiple types of auditory information need to be spoken at once. • Priority 1. Characteristic of the component • Priority 2. Label of component • Priority 3. Action • Priority 4. Changed status • e.g. button(characteristics) options(label) clicked(action) settings(changed status) • Note: Exception • Information given when tab type of interface is access: priority- Action > changed status > characteristic of component > label (page 8) • 3. Type 1. feed-forward information • (1) If the type of interface consists of one kind of component, e.g. menu (only with button), radio-button (only with radio-button) • auditory information on the characteristic of component will be given once for the first selection (focus). (e.g. page 11, page 17) • 4. Type 2. feedback information • (1) The information on user action will be given only when • (a) depth of information hierarchy is changed • (b) the action changes the status of check box or radio button • the action makes one of list items focused • (2) The information on type of interface will be given in the case of non-full sized interface • (3) The information on changed status will not be given if the descriptive label for the status is already given from feed-forward information

  5. User interaction and Auditory information • Regarding type 1 information, • 1. Movement of focus while speaking out • if the highlighted focus is being moved or the another item is selected while being given TTS auditory information, • it speaks out auditory information on the newly selected item with ignoring what it have been speaking out. (page 12) • 2. User input and the point of time of feed-forward information (only gesture-based interaction) • time delay: once a user touches the screen, pertinent information may have to be given a certain amount of time after touching because defining the type of gesture may need time. • e.g. tapping vs. flicking • the length of pause will be determined while checking with a working prototype. (maybe 0.1sec) • 3. Finger movement for gesture input and information abbreviation (only gesture-based interaction) • if the touching finger is being moved faster than the time delay, the auditory information will not be given.

  6. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 1. Information page > book contents case3. access via Tap Zone Actions case1. entry to book page case2. page movement by flicking user action causing display of book contents user action accessing a feature

  7. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 2. List case1. content list case2. option list user action causing open the list user action causing open the list

  8. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 2. Focused list case1. option list focused by (1) tapping (2) operating down key user action causing open the list tapping gesture release down key

  9. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab case1. tab + list case2. tab + text information select option menu select book info option

  10. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab case1. tab + list selected by tapping select option menu tapping gesture release  Note. As to movement of focus by keypad operation, please refer to “navigation keys/D-pad operation design guideline”.

  11. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab case1. tab + list focused and selected by operating down key select option menu down key enter key

  12. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu case1. grid menu case2. list menu release menu touch key select ‘more’ on the menu icon

  13. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu case3. iconic menu release menu touch key

  14. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu case1. menu icon focused by operating right key release menu touch key right key • Note. while speaking out the 2ndtts info, if right key is pressed, • it stops speaking it and starts the 3rd information. • Note: This shows the sample operated by physical keypad input. • Detail information on difference with gesture-based input in terms of flow will be referred to “physical vs. gesture input guideline”.

  15. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 5. popup case1. popup-alert case2. popup-edit case3. popup-list case4. popup-notice

  16. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 6. radio button case1. radio button on list interface enter down enter • Note: This shows the sample operated by physical keypad input. • Detail information on difference with gesture-based input in terms of flow will be referred to “physical vs. gesture input guideline”.

  17. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 7. checkbox case1. check box in options down enter • Note: This shows the sample operated by physical keypad input. • Detail information on difference with gesture-based input in terms of flow will be referred to “physical vs. gesture input guideline”.

  18. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 8. edit fields case1. multiple edit fields down down • Note: This shows the sample operated by physical keypad input. • Detail information on difference with gesture-based input in terms of flow will be referred to “physical vs. gesture input guideline”.

  19. Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 9. grid case1. 3 x 3 grid down right • Note: • 1) The layout of interface need to be modified. • 2) see “key operation guideline” as to how the focus would move as a user presses the navigation key.

More Related