Jaws（和其他屏幕阅读器）是否从输入值属性或屏幕上的文本读取？
如果我有一个通过 AJAX 更新的表单，则原始值字段（因为它输出到浏览器）可能与表单字段现在包含的文本不匹配。
我从一位盲人用户那里得知，我有时会提供帮助，Jaws 9 及更高版本对丰富的互联网应用程序（特别是 AJAX 和 DOM 更改）提供了强大的支持，但我不确定这种支持是否可以追溯到 Jaws 7（因为它们的发布）历史暗示）。
基本上，有两个问题：
如果我加载完全空白且未设置任何值的表单，然后使用 AJAX 在页面加载时加载数据（或在用户点击按钮后），Jaws 会读取插入的值吗？< /p>
如果我加载设置了值的表单，并且通过 AJAX 更改这些值，读者会读取值中或屏幕上的内容吗？
我希望在这种情况下，旧版本的缺陷会对我有利，并且它总是读取屏幕上（输入字段中）的任何内容并忽略这些值。并且它期望表单值发生变化，因此它读取当前的任何内容，而不仅仅是加载的内容。
但当然，我宁愿确切地知道，也不愿事后才知道。
If I have a form that updates via AJAX, there is a chance that the original value field (as it was output to the browser) will not match the text that the form field now has inside.
I know from a blind user that I help on occasion that Jaws 9 and later has strong support for rich internet applications (specifically AJAX and DOM changes) but I'm not sure if this support goes back as far as Jaws 7 (as their release history implies).
Basically, there are two concerns:
If I load the form totally blank with no values set, and then use AJAX to load the data on page load (or after user hits a button), will Jaws read the inserted values?
If I load the form with values set and those values change via AJAX will the reader read what is in the values or on screen?
My hope is that this is a case where deficiencies of the older versions will work to my favor, and that it always reads whatever is on screen (in the input fields) and disregards the values. And that it expects form values to change so it reads whatever is current, not just what loads.
But of course I'd rather know for sure rather than find out otherwise later.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
屏幕阅读器与自己的界面版本（“虚拟缓冲区”）进行交互。与网页交互的屏幕阅读器（至少是 JAWS）实际上似乎结合了从 DOM 读取节点和扫描屏幕上显示的内容。所以，我想答案是“视情况而定”。正如 @pst 所建议的，如果可能的话，没有什么可以替代由屏幕阅读器用户进行实际测试。
您的解决方案选项看起来有点像这样：
有关与屏幕阅读器等辅助软件进行通信的现代方法，请查看 WAI ARIA。 Gez Lemon 写了一篇很好的WAI ARIA 简介 - 不错值得花时间通读。
较旧的屏幕阅读器不擅长更新虚拟缓冲区，但 JAWS 7.1 及更高版本为开发人员提供了一种机制。 Gez Lemon 再次在他的博客中提供帮助：改进 Ajax 应用程序JAWS 用户。如果您想更深入地研究这一点，可以阅读一些很好的背景阅读材料和 James Edwards 的研究 这也值得一读。
Screen readers interact with their own version of interfaces - a "virtual buffer". Screen readers (well, JAWS, at least) interacting with web pages actually seem to do a combination of reading nodes from the DOM and scanning what is displayed on the screen. So, I guess the answer is "it depends". As @pst suggests, there's no replacement for actually getting this tested, and by a screen reader user if at all possible.
Your options for solutions look a bit like this:
For a modern approach to communicating with assistive software like screen readers, check out WAI ARIA. Gez Lemon has written a good Introduction to WAI ARIA - well worth taking the time to read through.
Older screen readers are not good at updating the virtual buffer, but JAWS 7.1 and later provide developers with a mechanism for this. Again, Gez Lemon helps out here on his blog in Improving Ajax applications for JAWS users. If you want to delve deeper into this, there's some good background reading and research by James Edwards that's worth a read too.