JavaScript 和 JAWS - 以及 SCORM？
我目前正在增强一个用户界面来检查各种可访问点，然后我在细则中读到了规范中的某个地方，我正在做的事情必须与 JAWS 兼容。
通常情况下，保持简单、直观并遵守规则就可以了——但是当涉及到 SCORM 时呢？我正在处理一个框架集、大量 JavaScript、一个陈旧的学习管理系统，它非常令人畏惧。
在通过框架集交付的页面上下文中是否可以遵守 JAWS 并使用 JavaScript 负载？我应该更加惊慌并索取更多钱吗？
此时提供代码将涉及完成测试模块并将其打包，不幸的是我的预算不允许这种级别的提问，所以我希望有人可以仅根据信息提供一些帮助/指导 - 如果您需要更多，请问！
I'm currently enhancing a user interface to check off various accessibility points, and then I read somewhere in a spec deep down in the fine print that what I'm doing must be JAWS compatible.
Normally that's fine, keep things simple, intuitive and abide by rules - but what about when SCORM is involved? I'm dealing with a frameset, reams of JavaScript, an aged Learning Management System, and its pretty daunting.
Is compliance with JAWS in the context of pages delivered through framesets and using loads of JavaScript possible? Should I be freaking out even more and demanding more money?
Providing code at this point would involved completing a test module and packaging it, unfortunately my budget doesn't allow for this level of question-asking, so I am hoping someone can offer some help/guidance based on information alone - if you need more, please ask!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你可以做到，你只需要小心。框架和 JavaScript 可能不利于可访问性，但如果使用不当，它们只会导致问题。
SCORM 需要框架（框架集或 iframe），许多人正确地说框架不利于可访问性。事实是，如果构建不当（或深度嵌套），它们肯定会使网站难以访问，但如果在创建时考虑到最佳实践（例如提供清晰的标题和结构），JAWS 等辅助浏览技术就可以处理它们。 WebAIM 有一个有关框架可访问性的优秀教程。
至于 JavaScript，JS 在大多数辅助技术中普遍可用（98.4% 根据最近的一项调查），所以它不是一个引人注目的问题。然而，如果您使用 JavaScript 来动态修改 DOM 或引入交互性（创建新的标记、动画、使 DIV 等静态元素可点击等），那么 JavaScript 对于可访问性来说可能非常危险。辅助技术有时不知道 JavaScript 在页面最初加载后修改了页面的内容，因此访问者无法知道他/她面前有新内容。如果您使用 JavaScript 动态更改页面内容，请务必使用 WAI -ARIA 技术。
SCORM 的 JavaScript 是完全不同的主题。就浏览器而言，SCORM 的 JavaScript 只是处理课程到 LMS 的通信，并且不会即时更改任何页面内容。这意味着 SCORM 的 JS 应该与 JAWS 无关，因为它不会影响页面的标记，也不会以任何方式影响 DOM。
You can do it, you just have to be careful. Frames and JavaScript can be bad for accessibility, but they will only cause problems if improperly used.
SCORM requires frames (a frameset or iframe), and many people rightly say frames are bad for accessibility. The truth is, they can certainly make sites less accessible if poorly constructed (or deeply nested), but assistive browsing technology like JAWS can handle them if they're created with best practices in mind, such as providing clear titles and structure. WebAIM has a good tutorial on frame accessibility.
As for JavaScript, JS is generally available in most assistive technology (98.4% according to a recent survey), so it isn't a showstopper. However, JavaScript can be very dangerous for accessibility if you're using it to dynamically modify the DOM or introduce interactivity (create new markup, animations, make static elements like DIVs clickable, etc.). Assistive technology sometimes doesn't know that JavaScript has modified the content of a page after the page initially loaded, so the visitor has no way of knowing there's new content right in front of him/her. If you use JavaScript to dynamically alter your page's content, be sure to use WAI-ARIA techniques.
SCORM's JavaScript is a different topic altogether. As far as the browser is concerned, SCORM's JavaScript simply handles the course-to-LMS communication, and doesn't change any of the page content on-the-fly. This means SCORM's JS should have no bearing on JAWS, because it doesn't affect your page's markup, and doesn't affect the DOM in any way.