Confound the screen readers and search engines.
屏幕阅读器和搜索引擎找不到它！
Can screen readers recognize the Web UI components?
屏幕阅读器能否识别这些WebUI组件？
Modern screen readers rely on mark-up (specifically, the label tag).
而新的屏幕阅读器则依据标示（尤其是标签tag）。
Works across modern Web browsers, screen readers, and wireless devices.
能够跨现代Web浏览器、屏幕阅读器和无线设备工作。
Screen readers for sight-impaired users read the menu item's title.
屏幕阅读器会阅读菜单项标题。
This helps screen readers identify the fields when the user moves into them.
这有助于在用户移至这些域时屏幕阅读器能够识别它们。
You will also need to help screen readers interpret the tables in your portlet.
您还需要帮助屏幕阅读器解释portlet中的表。
They want everything to be accessible and enabled for ATs such as screen readers.
他们希望每个东西都是易访问的，且对AT是有效的，如屏幕阅读器。
This provides a way for screen readers to understand the dynamic update of the contents.
这使屏幕阅读器能够理解内容的动态更新。
Spiders see only the HTML coding, just as screen readers work for visually impaired people.
爬行器只查看HTML代码，就像有视力障碍的用户所用的屏幕阅读器一样。
Two of the most important features of accessibility support are screen readers and magnifiers.
辅助选项支持的两大重要功能就是屏幕读取器和屏幕放大镜。
Your content can be visible to search engines and screen readers without jarring the human eye.
您可以使内容对于搜索引擎和屏幕阅读器是可见的，同时又对观看者隐藏了这些内容。
Screen readers read the alternate text aloud, and the image occupies only one pixel space.
屏幕读取器读取替换文字，而图像只占用一个像素的空间。
Screen readers that translate text to speech and "read" the software to people who are blind.
屏幕阅读器（Screenreader）将文本翻译成语音，并为盲人“读”的软件。
There have been a lot of advances with things like how well it works with screen readers and mobile phones.
像在屏幕阅读器和手机上工作得有多好之类的东西取得了许多进展。
The property is set to "Skip Navigation Links" by default, which makes screen readers skip the control.
默认情况下，此属性设置为“跳过导航链接”，让屏幕读取器跳过控件。
Instead, they must use ATs such as screen readers to interpret information on the screen in a meaningful way.
取而代之，他们必须使用诸如屏幕阅读器的AT，以有意义的方式解释屏幕上的信息。
Examples of accessibility AIDS include screen readers, speech recognition programs, and on-screen keyboards.
辅助功能助手的示例包括屏幕阅读程序、语音识别系统和屏幕键盘。
The alternate text of a hidden image read by screen readers to provide the ability to skip the list of links.
获取或设置屏幕读取器所读取的隐藏图像的替换文字，以提供跳过链接列表的功能。
That means that search engines, spiders, and screen readers all still have what they need to process and work with the page.
这意味着搜索引擎、搜索器和屏幕阅读器都能够获取需要的东西来处理页面。
It will not be hard to implement these keyboard features, but it is difficult to tell screen readers the attributes of this widget.
实现这些键盘特性并不困难，但是要将此小部件的属性通知给屏幕阅读器就不是一件很容易的事。
Braille computers, screen readers, and navigation tools based on spoken instructions find this continuous change hard to deal with.
盲文计算机、屏幕阅读器和基于语音指令的导航工具很难应付这种不断的变化。
Screen readers don't even bother with the limited semantics already in HTML, trying instead to figure out what the page looks like.
网页浏览者甚至不关心HTML中已经具备的少量语义，感兴趣的只是网页看起来效果怎样。
After adding this ARIA tag, when the window opens, screen readers such as JAWS 10 will be aware of it and can read the message to the users.
添加此aria标记之后，当窗口打开时，JAWS10等屏幕阅读器将能够察觉此事件，并且能够将消息读给用户。
However, with the advent of graphical user interfaces (GUIs), screen readers needed additional semantics to understand graphical screen objects.
然而，随着图形用户界面(graphical user interface, GUI)的出现，屏幕阅读器需要附加的语义来理解图形屏幕对象。
Search engines like Google recognize, categorize, and index your textual content, and screen readers can deal with the accurate textual content.
Google等搜索引擎可以识别、分类和索引您的文本内容，并且屏幕阅读器可以处理精确的文本内容。
Basically, you should enable keyboard interaction and try to "tell" screen readers what the widget is and what its current states and attributes are.
基本上，您应该启动键盘交互并尝试让屏幕阅读器知道小部件是什么以及它的当前状态和属性。
There is some criticism to using them, an example being the fact that screen readers used for accessibility might see those fields and read them.
有人批评使用它们，例如事实上，使用屏幕阅读器的可访问性可能会看到那些领域和阅读它们。
There is some criticism to using them, an example being the fact that screen readers used for accessibility might see those fields and read them.
有人批评使用它们，例如事实上，使用屏幕阅读器的可访问性可能会看到那些领域和阅读它们。
应用推荐