哪种屏幕阅读器最适合测试站点可访问性以及如何配置它？
哪种屏幕阅读器最适合测试网站可访问性以及如何配置该屏幕阅读器来测试网站（或者默认屏幕阅读器设置就可以）以及应该使用哪种浏览器来测试屏幕阅读器的可访问性？
免费或商业并不重要。哪一个可以提供最好的测试，然后网站应该可以通过所有其他屏幕阅读器在全世界范围内尽可能地访问？
我的目的是让网站尽可能多。
Which screen reader would be best to test site accessibility and how to configure that screen reader to test website (or default screen-reader setting would be ok) and which browser should be used to test accessibility with screen-readers?
Free or commercial it doesn't matter . Which can give best testing then site should be accessible in whole world as much as possible with all other screen readers?
my purpose is to make site as much as possible.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我将在这个答案的序言中声明我是一个完全失明的人，只使用 Jaws 作为屏幕阅读器。我也玩过 NVDA，但经验有限。 Jaws 是至少在美国使用最广泛的屏幕阅读器。如果您只能使用一个屏幕阅读器，我会选择使用默认设置。 Internet Explorer 和 Firefox 都可以与 Jaws 配合使用，并且都被广泛使用。您可以用来测试辅助功能的另一个屏幕阅读器是 NVDA 这是一个运行良好的开源屏幕阅读器可以使用 Firefox，但不能使用 Internet Explorer。我想说，如果成本是一个问题，请使用 NVDA 和最新版本的 Firefox，如果您的网站可以使用该设置访问，那么它很可能可以与 Jaws 一起使用。有关屏幕阅读软件的完整列表，请参阅此
安装并启动屏幕阅读器还不够进行良好的可访问性测试。在关闭显示器并拔下鼠标之前，您不会知道您的网站的可访问性如何。熟练使用屏幕阅读器来做到这一点需要时间。我认识的唯一有视力的人是高效的屏幕阅读器用户，要么为屏幕阅读器公司工作，要么以辅助技术培训为工作。因此，虽然您可以使用屏幕阅读器来测试网站的可访问性，但实际测试的学习曲线相当高。
I will preface this answer by stating I’m a totally blind individual who uses Jaws as there only screen reader. I've played around with NVDA as well but have l9imited experience with it. Jaws is the most widely used screen reader at least in the US. If you can only use one screen reader I would pick it with the default settings. Both Internet Explorer and Firefox work with Jaws and both are widely used. Another screen reader you could use to test accessibility is NVDA this is an open source screen reader that works well with Firefox but not internet explorer. I would say if cost is an issue use NVDA with the latest version of Firefox, and if your site is accessible using that setup it will most likely work with Jaws. For a complete list of screen reading software see this
Installing and starting a screen reader isn't enough to do good accessibility testing. You won't know how accessible your site is until you turn off your monitor and unplug your mouse. Getting good enough at using any screen reader to do that will take time. The only sighted people I know that are efficient screen reader users either work for the screen reader companies, or do assistive technology training as their job. So while you can use a screen reader to test your site's accessibility the learning curve for a realistic test is quite high.
为了直接回答您的问题，我将在您的目标浏览器中使用具有默认设置的 JAWS。如果您只能负担一份许可证，请为您的开发人员使用 NVDA 或 Chromevox，并向您的辅助功能专家提供 JAWS 的副本。
请记住，虽然确保您的网站与屏幕阅读器完美配合非常重要，但这只能帮助盲人。还有许多其他类型的残疾（例如听力、运动和认知障碍），要真正实现无障碍，您的网站也需要支持这些用户。
WCAG 2.0 是让尽可能多的人访问您的网站的最佳标准。不过，有很多 WCAG 2.0 文档，因此我会从 webaim.org 开始，http://webaim。 org/standards/wcag/checklist 如果您是新手，但请使用真实的东西当您准备好时，http://www.w3.org/TR/WCAG20/。
另外，请记住，即使它与屏幕阅读器一起“工作”，也可能会很烦人（盲人用户很少从上到下阅读，请确保您使用带有标题和 ARIA 标签的坚实结构），或者它可能不会提供盲人用户获得的信息量与视力正常的用户获得的信息量相同。例如，用户通过表单进行 Tab 键切换时，将错过文本输入旁边的帮助文本（修复：使用 CSS 隐藏标签中的副本，使帮助文本成为实际标签，或使用 ARIA 描述） - 这是一种很好的方法确保它不仅仅是“有效”，而是让您的 JAWS 测试人员不熟悉该站点。
To answer your question directly, I would use JAWS with default settings in your target browser. If you can only afford one license, then use NVDA or Chromevox for your developers and give your Accessibility expert the copy of JAWS.
Keep in mind that while making sure your site works perfectly with a screenreader is very important, this only helps the blind. There are many other types of disabilities (e.g., hearing, motor, and cognitive disabilities) and to truly be accessible, your site needs to support those users too.
WCAG 2.0 is the best standard for making your site accessible to as many people as possible. There is A LOT of WCAG 2.0 documentation though, so I would start at webaim.org, http://webaim.org/standards/wcag/checklist if you are new to it, but do use the real thing http://www.w3.org/TR/WCAG20/ when you are ready.
Also, keep in mind that even if it "works" with a screenreader, it may be annoying (blind users rarely read top-to bottom, make sure you put in solid structure with headings and ARIA lankmarks) or it may not be giving a blind user the same amount of information that a sighted user might get. For example, helper text next to text inputs will be missed by a user tabbing through a form (fixes: hide a copy in the label with CSS, make the helper text the actual label, or use ARIA-describedby) - a good way to make sure it more than just "works" is to have your JAWS tester not be familiar with the site.