使用 jQuery 508 是否兼容?

发布于 12-02 13:38 字数 259 浏览 1 评论 0 原文

我正在开发一个 ASP.NET 网站,该网站需要符合第 508 条 规定。我很困惑,好像我应该使用 JavaScript 还是根本不使用 JavaScript。

我什至可以使用 jQuery 的 slideUp()/slideDown() 来显示/隐藏部分吗?我可以使用 jQuery UI 的日期选择器和模式对话框吗?

I am working on an asp.net website that needs to be section 508 compliant. I'm confused as if I'm supposed to use JavaScript or not at all.

Can I even use jQuery's slideUp()/slideDown() to show/hide sections? Can I use jQuery UI's datepicker and modal dialog boxes?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

绝對不後悔。 2024-12-09 13:38:50

简而言之,是的。一般来说,jQuery UI 团队非常了解可访问性问题,并在大多数(如果不是全部)小部件上使用 ARIA (http://www.w3.org/WAI/intro/aria)。

话虽这么说,但符合 508 和“可访问”是不同的事情。标准有多种,其中“508”标准是最不严格的。

如今,99% 的页面都使用支持动态 JavaScript 的控件,并且具有不同程度的可访问性。大多数问题发生在人们使用自己的控件而不是使用像 jQuery UI 这样的良好控件库时。

适用的规则是这样的:

(l) 当页面使用脚本语言来显示内容或
创建界面元素,脚本提供的信息
应使用辅助工具可以阅读的功能性文本进行标识
技术

例如,jQuery 的对话框小部件在页面上使用标记来显示对话框内容,因此可以通过辅助技术 (AT) 进行访问。 AT 是否正确解释内容不一定是您关心的问题,至少在符合 508 方面是这样。这是因为存在各种类型的 AT 与各种操作系统、浏览器等相结合。

在显示和隐藏内容的情况下,从技术上讲,隐藏的内容一旦显示就可以由 AT 解释。这里的问题是 AT 如何知道 DOM 何时发生变化。这取决于AT。在这里,您可以动态更新 ARIA 状态以通知 AT,但 AT 不一定尊重和/或实施 ARIA 标准。

In short yes. In general the jQuery UI team is very aware of accessibility issues and uses ARIA (http://www.w3.org/WAI/intro/aria) on most if not all of their widgets.

That being said, however being 508 compliant and "accessible" are different things. There are various standards, with "508" compliance being the least strict you can be.

99% of pages these days use dynamic JavaScript enabled controls, with varying degrees of accessiblity. Most of the problems occur when people roll their own controls instead of use a good control library like jQuery UI.

The applicable rule is this:

(l) When pages utilize scripting languages to display content, or to
create interface elements, the information provided by the script
shall be identified with functional text that can be read by assistive
technology

jQuery's dialog widget, for example, uses markup on the page for the dialog content, so it is accessible for assistive technology (AT). Whether the AT properly interprets the content is not necessarily your concern, at least in regard to being 508 compliant. This is because there are various types of AT in combination with various OS, browsers etc.

In the case of showing and hiding content, technically the hidden content is interpretable by AT once it is shown. The issue here is how the AT knows when the DOM changes. That depends on the AT. Here you can dynamically update ARIA states to inform the AT, but the AT won't necessarily respect and/or implement the ARIA standards.

没有伤那来痛 2024-12-09 13:38:50

聚会有点晚了,但谷歌上出现了这个链接,所以我想添加一些想法。这个话题有很多值得考虑的地方。

SSB Bart 小组对 jQuery Ui 控件的状态做了很好的总结。

https://www.ssbbartgroup.com/blog/ 2013/07/03/jquery-ui-accessibility-analysis/

但是,自从那篇文章以来,我看到了一些更改,例如选项卡控件。当我对任何主要网站(例如 jQuery UI,甚至声称“完全可访问”的 bootstrap/foundation)进行快速测试时,我通常可以发现问题。

在测试可访问性时,我通常使用以下通用方法。

  1. 运行自动化测试,例如 http://wave.webaim.org /toolbar/http://squizlabs.github.io/HTML_CodeSniffer/
  2. 测试一下一切可以通过键盘访问并具有焦点指示器
  3. 实际运行 Jaws 或 Voice over 等屏幕阅读器,与基线进行比较,例如来自 http:// /whatsock.com/
  4. 使用普遍接受的键盘使用指南来测试控件:http://access.aol.com/dhtml-style-guide-working-group/

这样做时,您可以看到每个 jQuery Ui 控件在哪里失败和没有失败。他们尝试的并不可怕,但它和几乎所有主要框架都存在一些漏洞。

关于滑动和向下滑动本身并不重要。重要的是您使用的按钮是否可以通过键盘访问并且您使用正确的 aria 标签,例如 aria-hidden 等。请参阅 "="">http://www.w3.org/TR/wai-aria/states_and_properties 来指示隐藏内容。

A little late to the party but this link came up on google so thought i would add some thoughts. This subject has a lot to consider.

SSB Bart group did a great summary of the state of the jQuery Ui controls.

https://www.ssbbartgroup.com/blog/2013/07/03/jquery-ui-accessibility-analysis/

However, since that post I've seen changes being made for example to the tab control. When I do quick tests of any major sites like jQuery UI and even bootstrap/foundation which claim to be "fully accessible" i can usually find issues.

When testing for accessibility I usually use the following general methodology..

  1. Run automated tests like http://wave.webaim.org/toolbar/ and http://squizlabs.github.io/HTML_CodeSniffer/
  2. Test that everything is keyboard accessible and has a focus indicator
  3. Actually run a screen reader like Jaws or Voice over comparing against a base line such as examples from http://whatsock.com/
  4. test the controls use the generally accepted guidelines for keyboard usage: http://access.aol.com/dhtml-style-guide-working-group/

In doing so you can see where each jQuery Ui control fails and doesn't. Its not horrible they try but there are some holes in it and pretty much all of the major frameworks.

Concerning slide and and slide down that doesnt matter on itself. What matters is if the button you are using is keyboard accessible and you use the right aria tags such as aria-hidden ect.. See http://www.w3.org/TR/wai-aria/states_and_properties to indicate the hidden content.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文