beta text-to-speech design guidelines for coolreader
DESCRIPTION
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 - PowerPoint PPT PresentationTRANSCRIPT
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
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
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
1. menu: icon, list
2. alert : confirmation popup, edit popup, notice popup, setting popup, list popup, iconic popup
3. keypad
(3) changed status
• information on title area
• highlighted text
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
• 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
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
• 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.
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 6
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 1. Information page > book contents
user actioncausing display
of book contents
case1. entry to book page case2. page movement by flicking
feed forward information1. component 2. label
button next page
“button(pause)next page”
case3. access via Tap Zone Actions
user actionaccessinga feature
feed-back information1. action 2. type 3. status
clicked - page 22
“clicked(pause)page 22”
feed-back information1. action 2. type 3. status
- - page 7
“page 22”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 7
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 2. List
user actioncausing
open the list
case1. content list case2. option list
user actioncausing
open the list
feed-back information1. action 2. type 3. status
clicked - books
“clicked(pause)books”
feed-back information1. action 2. type 3. status
clicked - key actions
“clicked(pause)key actions”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 8
Implementation of TTS featuresThis 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 actioncausing
open the list
tappinggesture
feed-forward information1. component 2. label
list item left back by 10 pages
“list item(pause)left back by 10 pages”
release
down key
feed-back information1. action 2. type 3. status
clicked - key actions
“clicked(pause)key actions”
feed-back information1. action 2. type 3. status
selected - -
“selected”
information1. component 2. label
list item left back by 10 pages
3. action 4. type 5. status
selected - -“list item(pause)left back by 10
pages(pause)selected”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 9
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 3. Tab
select optionmenu
case1. tab + list case2. tab + text information
selectbook
info option
information1. action 2. type 3. status
clicked - -4. component 5. label
tab button view“clicked(pause)tab
button(pause)view”
information1. action 2. type 3. status
clicked - -4. component 5. label
tab button version“clicked(pause)tab
button(pause)version”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 10
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 3. Tab
select optionmenu
case1. tab + list selected by tapping
feed-forward information1. component 2. label
font facedroid sans
“font face droid sans”
releasetappinggesture
Note. As to movement of focus by keypad operation, please refer to “navigation keys/D-pad operation design guideline”.
information1. action 2. type 3. status
clicked - -4. component 5. label
tab button view“clicked(pause)tab
button(pause)view”
feed-back information1. action 2. type 3. status
clicked - font face
“clicked(pause)font face”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 11
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 3. Tab
select optionmenu
case1. tab + list focused and selected by operating down key
down key enter key
information1. action 2. type 3. status
clicked - -4. component 5. label
tab button view“clicked(pause)tab
button(pause)view”
information1. component 2. label
- font facedroid sans
3. action 4. type 5. statusselected - -
“font face droid sans(pause)selected”
feed-back information1. action 2. type 3. status
clicked - font face
“clicked(pause)font face”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 12
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 4. menu
releasemenu
touch key
case1. grid menu case2. list menu
select ‘more’
on the menuicon
feed-forward information1. component 2. label
button menu
“button(pause)menu”
feed-back information1. action 2. type 3. status
grid menu -
“grid menu”
feed-back information1. action 2. type 3. status
clicked list menu -
“clicked(pause)list menu”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 13
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 4. menu
releasemenu
touch key
case3. iconic menu
feed-back information1. action 2. type 3. status
menu buttons -
“menu buttons”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 14
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 4. menu
releasemenu
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 2nd tts info, if right key is pressed, it stops speaking it and starts the 3rd information.
feed-forward information1. component 2. label
button menu
“button(pause)menu”
feed-back information1. action 2. type 3. status
grid menu -
“grid menu”
information1. component 2. label
button open file3. action 4. type 5. status
- - -
“button(pause) open file”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 15
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 5. popup
case1. popup-alert
feed-back information1. action 2. type 3. status
- alert apply changes?
“alert(pause) apply changes?”
case2. popup-edit
feed-back information1. action 2. type 3. status
- alertenter page
number“alert(pause) enter page
number”
case3. popup-list
feed-back information1. action 2. type 3. status
- alert go to
“alert(pause) go to”
case4. popup-notice
feed-back information1. action 2. type 3. status
- notice
selection~ screen(whole
contents)“notice(pause) whole
contents”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 16
Implementation of TTS featuresThis 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 information1. action 2. type 3. status
clicked - font face
“clicked(pause)font face”
enter 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”.
feed-forward information1. component 2. label
unselected AR Crystallhei DB
“unselected(pause)AR Crystallhei DB”
enter
feed-back information 11. action 2. type 3. status
selected - -
“selected”
feed-back information 21. action 2. type 3. status
- - -4. component 5. label
tab button view
“tab button(pause)view”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 17
Implementation of TTS featuresThis 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 information1. component 2. label
unchecked Night mode“unchecked(pause)night
mode”
feed-back information1. action 2. type 3. status
checked - -
“checked”
enter
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 18
Implementation of TTS featuresThis 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 information1. component 2. label
edit box filename
“edit box(pause)file name”
down
feed-back information1. action 2. type 3. status
clicked - find book
“clicked(p)find book”
feed-forward information1. component 2. label
- author
“author”
Cool Reader design guide v0.1
Copyright© 2010-2011 by Ohio State University. All Rights Reserved. Page 19
Implementation of TTS featuresThis document shows a sample of implementation of TTS by type of interface.
Interface type 9. grid
case1. 3 x 3 grid
down right
feed-back information1. action 2. type 3. status
clicked - Tap zone actions
“clicked(p)tap zone actions”
feed-forward information1. component 2. label
button previous page
“button(pause)previous page”
feed-forward information1. component 2. label
button forward
“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 information1. component 2. label
button previous page
“button(pause)previous page”
feed-forward information1. component 2. label
button back by 10 pages
“button(pause)back by 10 pages”