search

umgc / fall2022

SWEN 670 Fall 2022 cohort
Creative Commons Zero v1.0 Universal
4 stars 3 forks source link

Investigate tools for voice input #230

Closed mdconatser closed 2 years ago

mdconatser commented 2 years ago

Consider entirely removing the custom voice input in order to allow users with OS-level voice input to be able to use that. Need to ensure pages work correctly with OS-level voice control.

Consider tools we might be able to leverage for better voice input, like AI natural language processing (NLP) libraries or ones specifically dealing with human input of times (TimeAgo?).

Document findings of approaches considered, and why they should be selected or excluded as we need this information in the TDD. Place findings in the documents as a draft, no need for extensive polishing within this task. Some content may be moved out later to the Programmers Guide.

Additionally, if implementation appears to be simple, developing a proof of concept (or locating an existing one built by someone else) would also be great for our next presentation.

mdconatser commented 2 years ago

from the professor in response to me asking about if it would be acceptable to remove the "custom" voice input for selecting individual screen elements and recommend our applications just ensure that we support the native OS accessibility tools: "The UI/UX is left to the team. The higher-level requirement is that the app should be easy to use be someone who is visually impaired as well as someone who is not. If the team believes that using the OS Screen Reader is more appropriate, please note the reasoning behind your decision, proceed with it, and then show the client the improved interface."

mdconatser commented 2 years ago

thinking we should continue pursuing removing the current implementation and enhancing support for the native iOS "voice control" and android equivalent.