让视障人士可以访问网站？
谁能给我一些建议或者给我一些关于这方面的好的链接？
我很难找到比“向图像添加替代文本”更多的内容，而且我不确定信息的最新程度...
我得到了整个语义标记的内容，但也可能需要更多的指导。
也不确定在不同浏览器上的情况如何。
can anyone give me some tips or hook me up with some good links on this?
i'm having trouble finding much more than 'add alt text to the images' and i'm not sure how current the info is...
i get the whole semantic markup thing but could probably do with a bit more guidance on that too.
also not sure how things would work across different browsers.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
1) 对页面内容的每个部分使用 HTML 标题标签。标题标签为：h1、h2、h3、h4、h5、h6
2) 确保前面提到的标题标签以正确的层次结构顺序存在。例如，h1 标签比 h2 标签重要。屏幕阅读器使用这些标题标签来导航页面的内容。如果它们不存在或排序不正确，视觉障碍用户将无法导航页面的内容。
3) 在没有先提示用户文本将发生变化的情况下，不要使用 JavaScript 动态更改屏幕上的内容。如果 JavaScript 在屏幕阅读器读取内容之前更改了屏幕上的文本，则视觉障碍用户无法知道内容已更改。
4）不要为用户提供 1000 张图像。如果图像不能传达相关内容，则将其设为 CSS 背景图像。
5) 善用标题属性，尤其是锚标签。这可以告诉用户他们要去哪里。
6) 不要在图像上放置无法作为替代内容传达的文本。视力障碍者不阅读图像。
7) 确保所有元数据都是相关的。如果您更改任何内容，请务必不要忘记额外的描述性数据。
8) AJAX 打败了可访问性。善待 AJAX 的使用。
9）视觉障碍者，实际上几乎所有视觉用户，并不关心你的页面有多漂亮。他们来这里是为了获取信息、购物或其他特定目的。让您的数据易于理解并快速检索。如果用户无法进入、获得他们想要的东西，然后在创纪录的时间内退出，他们将永远不会回来。
10) 不要在 HTML 中使用任何表示标签或表示属性。使用样式表。如果您的 HTML 包含表示约定，它们可能无法访问。
11) 如果您的内容从上到下的视觉顺序与 HTML 中的书写顺序不同，则可能无法访问。保持事情有序且一致。用户期望内容从上到下流动，并且选项卡索引跟随内容流动。
12) 使用屏幕阅读器软件进行可用性测试。通过查看不可能知道页面的可访问性。
1) Use HTML's heading tags for each and every section of content on your pages. The heading tags are: h1, h2, h3, h4, h5, h6
2) Ensure the prior mentioned heading tags exist with the proper heirarchal sequence. For instance h1 tags are important than h2 tags. Screen readers use these heading tags to navigate the content of the page. If they not present or improperly ordered a visually impared user cannot navigate the page's content.
3) Don't use JavaScript to dynamically change the content on the screen without first prompting the user that text will change. If JavaScript changes text on the screen before a screen reader can read the content there is no way a visually impared user can know that content was changed.
4) Don't serve the user a 1000 images. If an image does not convey relevant content then make it a CSS background image.
5) Be gracious with the title attribute, especially on anchor tags. This can tell the user where they are about to go.
6) Don't put text on an image that cannot be conveyed as alternate content. The visually impared do not read images.
7) Ensure all your meta data is relevant. If you change any of your content be sure not to forget the extra bits of descriptive data.
8) AJAX defeats accessibility. Be kind with your use of AJAX.
9) The visually impared, and actually almost all visual users, do not care how pretty your pages are. They are there to get information, shop, or what ever other specific purpose. Make your data easy to understand and quick to retrieve. If a user cannot get in, get what they wanted, and then get out in record time they won't ever come back.
10) Do not use any presentation tags or presentation attributes in your HTML. Use a stylesheet. If your HTML contains presentation conventions they are probably not accessibile.
11) If your content exists in a different order visually than how it is written in the HTML, from top to bottom, it likely fails accessibility. Keep things orderly and consistent. Users expect content to flow from top to bottom and for tab indexing to follow the flow of content.
12) Do usability testing with screen reader software. It is not possible to know how accessible a page is by looking at.
我自己完全是瞎子，你会惊讶地发现这么多年过去了，有多少东西仍然没有替代属性......小心，仍然有很多神话，比如不允许使用图形（错误），表格不好（错误），框架不好（错误，尽管我意识到框架由于其他原因而不好。） 理想情况下，您应该有人对您的网站进行盲测。另一件事是，尝试制作实际执行按钮和/或链接操作的控件。可点击的 div 并不酷，因为它们做任何事情并不明显，并且根据您使用的辅助技术，您甚至可能无法单击它们。
I am totally blind myself, and you'd be amazed how much stuff still doesn't have alt attributes on it after all these years... Be careful, there are still a lot of myths out there, such as no graphics allowed (wrong), tables are bad (wrong) and frames are bad (wrong, though I realize frames are bad for other reasons.) Ideally you should have someone who is blind test your site. One other thing, try to make controls that actually do things buttons and/or links. Clickable divs aren't cool because it is not obvious that they do anything, and depending on which assistive technology you are using you may not even be able to click on them.
查看 Alertbox 的解释：
禁用用户和网络（该文章来自 1996 年） ...但问题仍然存在，如果今天不是更是如此的话）
...然后点击底部的链接，找到包含设计指南的 148 页报告（该文档受版权保护 2001 年，因此自原始版本以来它必须已更新） ）。
Check out this explaination from Alertbox:
Disabled Users and the Web (The article is from 1996...but the issues still hold true, if not more so today)
...then follow the link at the bottom to the 148 page report with Design Guidlines (the document is copyrighted 2001 so it must've been updated since the original).
这个术语是可访问性。请访问 W3C 的 WAI 网站。我一直发现 Juicy Studio 是讨论辅助功能的文章的宝贵资源。
The term for this is Accessibility. Take a look at the W3C's WAI Website. I've always found Juicy Studio to be an invaluable resource for articles discussing accessibility.
有一些难以掌握和实施的深入定义。示例包括网页内容无障碍指南 (WCAG) 和 第 508 条。
一个非官方的建议是让您的网站易于使用文本浏览器导航。不要依赖颜色或结构来传达内容。不要依赖小部件来实现重要功能。
编辑：我想补充一点，您不应该费心使用 JAWS 或其他屏幕阅读器来测试您的网站。您无法浏览网站更多的是由于您对屏幕阅读器缺乏经验，而不是网站无法访问。也就是说，让目标受众样本测试您网站的可用性是非常有益的。
编辑#2：正如评论中所讨论的，我的目的是传达您不应该根据您使用屏幕阅读器的体验来判断网站的可用性。也就是说，我建议从事 Web 开发的任何人都接触用于查看网站的浏览器/设备，包括屏幕阅读器。原始编辑中的措辞很糟糕。
There are in-depth definitions that are difficult to master and implement. Examples include Web Content Accessibility Guidelines (WCAG) and Section 508.
A less than official suggestion is to make your site easy to navigate with a text browser. Don't rely on colors or structure to convey content. Don't rely on widgets for important functionality.
EDIT: Thought I would add that you shouldn't bother testing your site with JAWS or another screen reader. Your inability to navigate a site would be more related to your inexperience with the screen reader rather than the inaccessibility of the site. That said, having a sample of your target audience test your site for usability is highly beneficial.
EDIT #2: As discussed in comments, I intended to convey that you shouldn't make judgements on a site's usability based on your experiences with a screen reader. That said, I would recommend that anyone in Web development have exposure to the browsers/equipment used to view web sites including screen readers. It was poor wording in the original edit.
好吧，看起来没有人提到 WAI-ARIA，它是为无障碍富人设计的互联网应用。 IE 使 Gmail 之类的东西可以访问。还有一个不错的搜索词可以找到这样的东西关于 wai-aria 的单独列表文章。已经相当支持了。
Well, it looks like no one mentioned WAI-ARIA which is for the Accessible Rich Internet Applications. IE making things like gmail accessible. And a decent search term to find things like this a list apart article on wai-aria. Already pretty supported.