Windows 标准助记符
Windows有没有助记符标准？
例如——菜单栏、菜单栏上的操作（例如 Alt+f 到文件菜单，但 ctrl+s 在文件菜单下进行保存）和控件。
我这么问是因为我们有一个包含许多控件的搜索屏幕，并且我们正在尝试确定访问字段以及上述字段的快捷键。
是否有任何 Microsoft 官方文件或 RFC 文档可供我们阅读并在会议上展示，以找出如何正确处理此问题。
到目前为止我发现的唯一的就是这个 - 这对一些人有帮助，但没有详细介绍。
此外，我可以找到一本书来帮助我设计这些东西吗？
社区对双重助记词有何看法？ （例如 ctrl a、w）
谢谢！
Are there any mnemonic standards for Windows?
For example -- the menu bar, actions on the menu bar (e.g. Alt+f to file menu but ctrl+s to do the save under the file menu), and controls.
I'm asking because we have a search screen with many controls and we're trying to decide shortcut keys to get to fields and such described above.
Is there anything official at Microsoft or some RFC document that we could read and present in a meeting to figure out how to properly handle this.
The only thing I've found so far is this -- which helps some, but doesn't go in to great detail.
Further, is there maybe a book I can get to help me with designing such things?
How does the community feel about double mnemonics? (e.g. ctrl a, w)
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您需要查看用户体验交互指南。
特别是访问密钥部分。
You want to look at the User Experience Interaction Guidelines.
Particularly, the Access Keys part.
关于双重助记符：
只有当您的用户拥有高水平的专业知识时，我才会考虑这些。如果他们日复一日地使用你的产品并且变得非常熟练，那么双重助记符可能会带来回报。但对于许多用户来说，它们可能很难发现、记住和使用。 （我每天大部分时间都使用 Visual Studio，并且我只记住并使用极少数可用的双重助记符 - 只是那些我经常使用的命令。）在这种情况下，它们不值得花费精力实施它们。
如果您认为您的用户可能具有这种水平的专业知识，我仍然建议简单的可用性测试，因为这不是一个常见的习语；尽管“专家”级功能很难在走廊式可用性测试中评估。然而，作为程序员，我们众所周知无法判断可用性，因此在投入大量精力之前，一定要与真实用户进行某种测试和测量！
Regarding double mnemonics:
I would consider these only if your users are going to have a high level of expertise. If they use your product day in day out and become very proficient with it, then double mnemonics may pay their way. But for many users they are likely to be hard to discover, remember and use. (I use Visual Studio most of every day, and I only remember and use a very few of the double mnemonics available -- just the ones for commands that I use very frequently.) In which case they would not be worth the effort required to implement them.
If you think your users may have this level of expertise I would still recommend simple usability testing, because this is not a common idiom; though "expert" level features are hard to evaluate in hallway-style usability tests. Nevertheless, as programmers we are notoriously unable to judge usability, so definitely test and measure somehow with real users before putting significant effort into this!