From 2f4a9ea6f15f6f2c02e231ce7947321a166705eb Mon Sep 17 00:00:00 2001 From: Adrian Cochrane Date: Tue, 7 Apr 2020 17:09:11 +1200 Subject: [PATCH] Add new issue --- ISSUES/engine/help-wanted/webforms.md | 71 +++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 ISSUES/engine/help-wanted/webforms.md diff --git a/ISSUES/engine/help-wanted/webforms.md b/ISSUES/engine/help-wanted/webforms.md new file mode 100644 index 0000000..3c98b6f --- /dev/null +++ b/ISSUES/engine/help-wanted/webforms.md @@ -0,0 +1,71 @@ +# Webforms + +The core browser engine would deal in terms of loosely-defined links, but sometimes pages require more free-form input. +For this reason Rhapsode would require a mode to deal with webforms, which needs to be designed and implemented. Or maybe there'd be two modes, the second using extended markup to deliver a more lenient and conversational experience. You'd enter this mode by treating the
tag like a link. + +I would need to build upon this to bookmark webpages or search the Web. + +--- + +The experience I'm currently thinking about delivering for webforms, would step you through each non-prefilled input prompting you to fill it. +For each it'll announce the label and, more quietly, the input type possibly with brief instructions for filling it in. If it's a multichoice input, the options would be read out as well. Your input would be interpreted according to the input type. A pause or left/down arrow key would store that value and move on to the next input, or right/up would return to the previous form input. +If it's a multichoice or -associated input, it may then clarify which you mean in exactly the same way Rhapsode normally deals with links. +Once the form has been filled in, it'll read everything back out to you again (include any "hidden" inputs). At which point you can: + +* reenter any input by specifying it's label, +* assign shorthand names (to be resolved via the multichoice handling) for any values you've entered using the "petname" command, +* or submit the form using the "submit" command. + +--- + +As an extension on that form-filling experience that allows websites to cater specifically to Rhapsode's voice interface, we could add a Rhapsode-specific property onto `` elements linking to a list of newline-seperated natural phrases that can be used for filling in the form. + +"Placeholders" would occur within each phrase identifying form inputs by `name` attribute. + +To use an Alexa-derived example, this list could start with: + + I want a {pet}. + I want a {size} {pet}. + I want a {pet} {energy}. + I want a {pet} {temperament}. + I want a {temperament} {pet}. + I want a {size} {temperament} {pet}. + I want a {size} {temperament} {pet} {energy} at my apartment. + +Which would enhance interaction with: + + +
+
+
+ +
+
+ +
+
+ +
+
+
+ + +--- + +To activate this mode, I'm thinking of letting the autofocus attribute trigger it and listening for the text of the "submit" button. If there is no submit button, I'd instead listen for "enter/submit/fill-in form". +When the page is read aloud, you would hear this text at the start of the form with the usual audio cue. \ No newline at end of file -- 2.30.2