我是一个 .Net 3.5 WinForm 应用程序，仅用于内部数据输入。主要是各种形式的文本框等。使用 Windows 7 语音识别，它似乎可以“开箱即用”地与我的应用程序配合使用。
我想知道这是否完全正确。我需要采取哪些步骤来确保我的应用程序具有最高水平的可用性？它是否为 UI 元素或其他元素使用标签。
我是否需要包含System.Speech.Recognition命名空间 rel="nofollow noreferrer">此处
任何指导或建议将不胜感激。主要是如何为元素提供特定的语音识别句柄。
I am a .Net 3.5 WinForm app that is used for Data Entry in house only. Mostly various forms of Textboxes etc. With Windows 7 Speech Recognition it seems like it works "out of the box" with my app for me.
What I am wondering is if that is completely true. What steps do I need to take to ensure the highest level of usability in my app? Does it use tags for the UI elements or something else.
Do I need to inclued the System.Speech.Recognition Namespace talked about here
Any guidance or advice would be greatly appreciated. Primarily, how to give an element a particular handle for Speech Recognition.
发布评论
评论（1）
Windows 语音识别使用文本服务框架进行听写；文本服务框架内置了对所有 Win32 纯编辑和 RichEdit 控件的支持，WPF 文本框也支持文本服务框架。因此，如果您的 WinForms 应用程序使用标准文本框，或者使用包装 Win32 richedit 或普通编辑控件的自定义文本框，则 Windows 语音识别将正常工作。
如果您还需要命令&控件，那么您需要确保您的控件具有正确的辅助功能属性。大多数情况下，您需要做的就是确保您的控件都设置了 AccessibleName 属性； AccessibleRole 属性几乎肯定应保留为“默认”。
Windows Speech Recognition uses Text Services Framework for dictation; Text Services Framework has built-in support for all Win32 plain edit and RichEdit controls, and the WPF Textbox has support for Text Services Framework as well. So if your WinForms app uses standard Textboxes, or if it uses custom Textboxes that wrap a Win32 richedit or plain edit control, Windows Speech Recognition will work fine.
If you also need command & control, then you need to make sure that your controls have the correct accessibility properties. Mostly, all you need to do is make sure that your controls all have AccessibleName properties set; the AccessibleRole property should almost certainly be left at 'Default'.