1. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 1 Beta Text-To-Speech Design Guidelines for CoolReader

2. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 2 Table of Contents 1.Type of auditory information 2.General rules for auditory information 3.User interaction and Auditory information 4.Implementation of TTS features 1) Interface type 1. Information page > book contents 2)Interface type 2. List a)Focused list 3)Interface type 3. Tab a)tab + list selected by tapping b)tab + list focused and selected by operating down key 4)Interface type 4. menu a)menu icon focused by operating right key 5)Interface type 5. popup 6)Interface type 6. radio button 7)Interface type 7. checkbox 8)Interface type 8. edit fields 9)Interface type 9. grid

3. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 1.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 2.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. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 4 General rules for auditory information 1. 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 (c)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. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 5 User interaction and Auditory information Regarding type 1 information, 1.Movement of focus while speaking out (1)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) (1)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 (2)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) (1)if the touching finger is being moved faster than the time delay, the auditory information will not be given.

6. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 user action causing display of book contents case1. entry to book pagecase2. page movement by flicking feed forward information 1. component2. label buttonnext page “button(pause)next page” case3. access via Tap Zone Actions user action accessing a feature feed-back information 1. action2. type3. status clicked-page 22 “clicked(pause)page 22” feed-back information 1. action2. type3. status --page 7 “page 22”

7. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 7 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 2. List user action causing open the list case1. content listcase2. option list user action causing open the list feed-back information 1. action2. type3. status clicked-books “clicked(pause)books” feed-back information 1. action2. type3. status clicked- key actions “clicked(pause)key actions”

8. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 feed-forward information 1. component2. label list item left back by 10 pages “list item(pause)left back by 10 pages” release down key feed-back information 1. action2. type3. status clicked- key actions “clicked(pause)key actions” feed-back information 1. action2. type3. status selected-- “selected” information 1. component2. label list item left back by 10 pages 3. action4. type5. status selected-- “list item(pause)left back by 10 pages(pause)selected”

9. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 9 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab select option menu case1. tab + listcase2. tab + text information select book info option information 1. action2. type3. status clicked-- 4. component5. label tab buttonview “clicked(pause)tab button(pause)view” information 1. action2. type3. status clicked-- 4. component5. label tab buttonversion “clicked(pause)tab button(pause)version”

10. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 10 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab select option menu case1. tab + list selected by tapping feed-forward information 1. component2. label font face droid sans “font face droid sans” releasetapping gesture  Note. As to movement of focus by keypad operation, please refer to “navigation keys/D-pad operation design guideline”. information 1. action2. type3. status clicked-- 4. component5. label tab buttonview “clicked(pause)tab button(pause)view” feed-back information 1. action2. type3. status clicked-font face “clicked(pause)font face”

11. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 11 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 3. Tab select option menu case1. tab + list focused and selected by operating down key down keyenter key information 1. action2. type3. status clicked-- 4. component5. label tab buttonview “clicked(pause)tab button(pause)view” information 1. component2. label - font face droid sans 3. action4. type5. status selected-- “font face droid sans(pause)selected” feed-back information 1. action2. type3. status clicked-font face “clicked(pause)font face”

12. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 12 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu release menu touch key case1. grid menucase2. list menu select ‘more’ on the menu icon feed-forward information 1. component2. label buttonmenu “button(pause)menu” feed-back information 1. action2. type3. status grid menu- “grid menu” feed-back information 1. action2. type3. status clickedlist menu- “clicked(pause)list menu”

13. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 13 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu release menu touch key case3. iconic menu feed-back information 1. action2. type3. status menu buttons - “menu buttons”

14. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 14 Implementation of TTS features This document shows a sample of implementation of TTS by type of interface. Interface type 4. menu release menu touch key case1. menu icon focused by operating right key right key  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”.  Note. while speaking out the 2 nd tts info, if right key is pressed, it stops speaking it and starts the 3 rd information. feed-forward information 1. component2. label buttonmenu “button(pause)menu” feed-back information 1. action2. type3. status grid menu- “grid menu” information 1. component2. label buttonopen file 3. action4. type5. status --- “button(pause) open file”

15. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 feed-back information 1. action2. type3. status -alert apply changes? “alert(pause) apply changes?” case2. popup-edit feed-back information 1. action2. type3. status -alert enter page number “alert(pause) enter page number” case3. popup-list feed-back information 1. action2. type3. status -alertgo to “alert(pause) go to” case4. popup-notice feed-back information 1. action2. type3. status -notice selection~ screen (whole contents) “notice(pause) whole contents”

16. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 feed-back information 1. action2. type3. status clicked-font face “clicked(pause)font face” enterdown  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”. feed-forward information 1. component2. label unselected AR Crystallhei DB “unselected(pause)AR Crystallhei DB” enter feed-back information 1 1. action2. type3. status selected-- “selected” feed-back information 2 1. action2. type3. status --- 4. component5. label tab buttonview “tab button(pause)view”

17. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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  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”. down feed-forward information 1. component2. label uncheckedNight mode “unchecked(pause)night mode” feed-back information 1. action2. type3. status checked-- “checked” enter

18. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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  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”. down feed-forward information 1. component2. label edit boxfilename “edit box(pause)file name” down feed-back information 1. action2. type3. status clicked-find book “clicked(p)find book” feed-forward information 1. component2. label -author “author”

19. Cool Reader design guide v0.1 Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 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 downright feed-back information 1. action2. type3. status clicked- Tap zone actions “clicked(p)tap zone actions” feed-forward information 1. component2. label buttonprevious page “button(pause)previous page” feed-forward information 1. component2. label buttonforward “button(pause)forward”  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. feed-forward information 1. component2. label buttonprevious page “button(pause)previous page” feed-forward information 1. component2. label buttonback by 10 pages “button(pause)back by 10 pages”