(PGA) Keyboard and self-voicing interaction for first discovery tool
This document has been moved to Google docs: https://docs.google.com/document/d/13yuw1ragr1HX2PNxFdir_bGsGO4cGHusVsU_mMESFto/edit
The following describes the keyboard and self-voicing interaction for the Size page of the first discovery tool. Please refer to the latest wireframes for reference (final version to be posted soon)
To keep the interaction as simple as possible we decided that for now, the icon toolbar at the bottom of the page will not be accessible through keyboard navigation. A keyboard-only user will be able to move through all of the screens in order using the back and next buttons; since there are few screens, the advantage of skipping around is minimal. The icons do provide important functionality in terms of indicating progress as well as informing the user of where they are within the overall order. For the non-visual user, this functionality is captured in the screen reader output as described below.
<GV: do you mean "not available through keyboard navigation - but you can with touch screen" ? or do you mean "icons can not be used for navigation" ? Latter is fine. Former of course is a violation of access guidelines.>
<AC: We mean the former: The icons will be accessible via mouse our touch screen, but not via keyboard. I'm not sure this constitutes enough of a "violation of access guidelines" that we shouldn't do it. The FD tool is a bit of a special case, and simplicity and ease of use is paramount. The keyboard-only user will still be able to navigate to every page, but their navigation within the page will be made simpler and easier with this restriction.>
General tab order:
land on page
progress indication read out (e.g. "this is the second step of 5 steps")
prompt/instructions read out (e.g. "adjust things to a size that you like best")
reminder to press h for help read out
adjusters in order (e.g. plus button then minus button, or Yes button then No button etc)
reset button (where applicable)
back button
next button
audio on/off button
help button
<GV: the order should follow what is on the screen (other than the intro text on landing on the page. Otherwise very confusing for everyone who is not totally blind >
<AC: the order does follow what is on the screen, it simply starts in the middle of the screen. Again, this is intended to make the process as simple and easy as possible. If the user has no interest in the mute and help buttons, it will be faster and easier for them to get through the tool if they don't have to tab past those buttons on every screen.>
<DA: I would add that it is important for the main content of the page to be prioritized - so that the first thing the user hears is the prompt, and the first thing they are able to interact with is the preference "adjuster">
EXAMPLE
User lands on text size page
focus is on the page
"This is the third step of 6 steps" is read out. The number of steps is the total number of pages, not the number of icons in the lower navigation.
<GV: not sure we can do this. We mentioned that the evaluation would be responsive - so that means that we will add or skip pages depending on what happens with the user. So we don't know the number of pages. also the number might be off-putting when we are done..
<AC: Right now, there is no such responsiveness in the designs. It is configurable, i.e. different instances can be set up with different preference screens, but the available screens does not change on the fly.>
<GV: better to keep it interesting – and a bit fun - rather than mechanical and oriented toward getting through step by step? I do like some kind of indicator of progress though. hmmmm periodic "you are now about 1/4 done? hmmmmmm>
<AC: Interesting idea... The actual text will be configurable, and we could do some user testing around that.>
Visible page instructions are read out (e.g. "Adjust the size until it is comfortable to see")
"Press 'h' for help" is read out
User presses Tab
focus is on the + button
"press Enter or spacebar to increase size" is read out
User presses Enter/spacebar
content changes size <Do we want to engrain wrong UI behavior in a new user. This is not how any control on any other ICT interface behaves. Maybe use spacebar? GV:>
<AC: use of Enter and Spacebar to activate a button is pretty standard fare.>
User presses Tab
focus moves to the - button
"press Enter or spacebar to decrease size" is read out <see above>
User presses Tab
focus moves to reset button
"press Enter or spacebar to reset size to original value" <Too cryptic? and not plain language. "hit spacebar now if you want to go back to what the font size was when you started"
User presses Enter/spacebar
size value is reset to default
"size has been reset"
User presses Tab
focus moves to back button
"press Enter or spacebar to go back to last page" is read out <etc>
User presses Enter
previous page loads, focus lands on page
"This is the second of six steps" is read out
Visible page instructions are read out (e.g. "Adjust the voice volume to a comfortable level")
"Press 'h' for help" is read out
Users tabs through the page to the back button
focus is on back
Users presses Tab
focus moves to next button
"select Enter or spacebar to go to the next step" is read out
User presses Enter/spacebar
Size page loads
"Two of six steps complete. This is the third step of 6 steps"
User tabs through to next button
focus is on next
User presses Tab
focus moves to audio button
"press Enter or spacebar to turn voice off" is read out
User presses Enter/spacebar
voice is turned off
"voice is off. select to turn voice on" is read out
User presses Enter/spacebar
voice is turned on
"voice is on" is read out
User presses Tab
focus moves to help
"press Enter or spacebar to get help" is read out
[details of what happens here are being worked out]
Open Questions
see (PGA) Open questions for first discovery tool interactions