1986848 - Voice Access can't select text or move the cursor when targeting words at the edges of some text boxes

Status: NEW

(Core :: Disability Access APIs, defect)

Description

[James Teh [:Jamie]]

STR:

1. Turn on Windows Voice Access.
2. Open https://www.google.com/
3. In the Google search box, type: fire fox
4. Say: move before fire
   • Expected: Voice Access moves the cursor.
   • Actual: Voice Access reports: "Sorry, something went wrong. Please try again."
5. Press home then press space to insert a space before "fire".
6. Say: move before fire
   • Correct result: Voice Access moves the cursor.
7. Say: move before fox
   • Expected: Voice Access moves the cursor.
   • Actual: Voice Access reports: "Sorry, something went wrong. Please try again."
8. Press end then press space to insert a space after "fox".
9. Say: move before fox
   • Correct result: Voice Access moves the cursor.

Notes:

1. This doesn't happen if there is nothing before/after the text box in the document.
2. This applies to selection commands as well; "select fire", etc.
3. "Select previous word" also seems to misbehave for a word at the end of such a text box with no space afterward.
4. Distilled test case: data:text/html,before<input value="fire fox">after
5. Curiously, if you separate the input from the text on both sides with a space, this fixes things for "fire", but not "fox":
   data:text/html,before <input value="fire fox"> after
6. This works as expected in Edge.
7. This likely has something to do with Voice Access not respecting the DocumentRange of the text box and thus bleeding into adjacent text accessible via the text pattern. IMO, this is a Voice Access bug, but we'll probably have to live with it given that it doesn't cause problems in Edge.
8. I guess we'll need to separate objects with a space when returning text from UiaTextRange::GetText or similar.
9. However, there might also be weirdness here with UiaTextRange::FindText. We need to figure out what Voice Access is doing here.