键盘快捷键是否符合508标准 [英] Are Keyboard shortcuts mandatory for 508 compliance

问题描述

我在这方面进行了很多研究，似乎在SO和所有的网络上都有相互矛盾的答案。我明白，与第508节一致，并不等于可达性。最重要的是，UI / UX设计师被告知，下拉菜单中的键盘快捷键需要键盘快捷键才符合508标准。我看到Windows Forms应用程序有这个，但是对于Web开发我不认为这是强制性的兼容

我的其他问题被回答在这里：符合MVC 4网站508

解决方案

我部分同意薄，但同意剩下的留言的前两句话。

句子我我指的是：

他们应该是 - 可触摸的 - 键盘为508。我正在强调快捷方式和可以访问

Crixus说：

最大的事情是，UI / UX设计师被告知，下拉菜单中的键盘快捷键需要键盘快捷键为508兼容。

您需要澄清这一点。您是否意味着简单的< select> 或导航菜单的下拉菜单？正如Thinice在评论中所说，第508节只是说需要可以达到。问题变成：

如何向您的应用程序添加快捷键？您是通过accesskeys属性添加它们还是Gmail / Yahoo Mail如何添加快捷键？

我以为我对AccessKeys做了一个答案，但找不到。本质上，accesskeys听起来像是一件好事，但是如果您看到允许使用的按键不会干扰浏览器或辅助技术键，那么您是非常有限的。 Gez Lemon做了 AccessKeys的概述及其问题。如果你想做Yahoo！Mail方法，你需要做更多的工作。 Todd Kloots做了一个关于ARIA的演示，这可能是有帮助的。这导致我进入第二部分。如果您在网站上大量使用JavaScript来执行操作，则人们使用 1194.21（软件应用程序/操作系统）和 1194.22（网络）标准来评估站点。如果网站使用JS制作导航菜单（ YUI菜单示例），下拉行为需要通过键盘来实现。我会说这是：

§1194.21软件应用程序和操作系统。

（a）软件是设计为在具有键盘的系统上运行，产品功能应该可以从键盘执行，其中功能本身或执行功能的结果可以在文本上被辨别。

AND

（c）应提供当前焦点的明确的屏幕指示，随着输入焦点的变化，交互式界面元素之间移动。重点将以程序方式暴露，以便辅助技术可以跟踪焦点和焦点变化。

我说这两个标准都是使用的，因为（a）说你必须能够通过键盘进入导航区域。 （c）发挥作用，因为某些菜单可以选项卡到所有的父项目，但不能使用鼠标进入下拉菜单。我看到菜单，您可以选项卡到子菜单项，但菜单不会弹出打开。所以如果你只是使用键盘（移动性不便），而不是使用JAWS，你将不知道你在哪里。

我看到Windows Forms应用程序有这个，但是对于Web开发我不认为这是必须符合

我会说实际的应用程序，如Word，Outlook等，为常用命令提供快捷方式。如果你正在为一个Web应用程序做这个，我会考虑你有多少。这不是要遵守的强制性要件。如果您像导航栏一样，建议您使用 ARIA角色 role =navigation，以父元素为最佳做法。

I researched a lot on this and seem to be getting conflicting answers on SO and all of the web. I understand that with Section 508 that compliance DOES NOT equal accessibility.

Biggest thing is that the UI/UX designer is being told that keyboard shortcuts for the dropdown menu NEEDS to have keyboard shortcuts to be 508 compliant. I see Windows Forms applications having this, but for web development I do not think that is mandatory to be "compliant"

My other question that was answered is here: MVC 4 site 508 compliant

解决方案

I partially agree with thinice, but agree with the first two sentences of the comment left.

The sentences I am referring to are:

They should be -reachable- by keyboard for 508. I'm maintaining emphasis on the difference between a shortcut and being reachable

Crixus said:

Biggest thing is that the UI/UX designer is being told that keyboard shortcuts for the dropdown menu NEEDS to have keyboard shortcuts to be 508 compliant.

You need to clarify this. Do you mean a simple <select> or a drop down for a navigation menu? As Thinice stated in comments, Section 508 just says needs to be reachable. The question becomes:

how are you adding shortcut keys to your application? Are you adding them via the accesskeys attribute or how Gmail/Yahoo Mail adds shortcut keys?

I thought I did an answer about AccessKeys, but cannot find it. Essentially accesskeys sounds like a great thing, but if you look at the keys you are allowed to use that do not interfere with either browser or Assistive Technology keys, you are quite limited. Gez Lemon did an overview of AccessKeys, and their issues. If you want to do the Yahoo!Mail approach, you have to do a bit more work. Todd Kloots made a presentation about ARIA, which may be helpful. Which leads me into the second part. If you are using JavaScript heavily on a site to do stuff, people use both 1194.21 (software application/OS) and 1194.22 (web) standards to evaluate a site. If the site uses JS to make a navmenu (YUI menu example), the drop down behavior needs to be reachable by keyboard. I would say this falls under:

§ 1194.21 Software applications and operating systems.
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

AND

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.

I say both standards are used because (a) says you have to be able to get into the navigation area via the keyboard. (c) comes into play because some menus you can tab to all of the parent items, but you cannot get into the drop down part without a mouse. I have seen menus that you can tab to the sub-menu items, but the menu does not pop open. So if you just use the keyboard (mobility imparments), versus using JAWS, you will have no idea where you are.

I see Windows Forms applications having this, but for web development I do not think that is mandatory to be "compliant"

I would say actual applications, like Word, Outlook, etc., supply shortcuts to frequently used commands. If you are doing this for a web application, I would think about how many you do. This is not a mandatory piece to be compliant. If you are making like a navigation bar, I would recommend using ARIA roles, specifically role="navigation", on the parent element as a best practise.

这篇关于键盘快捷键是否符合508标准的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！