什么是适合残障用户的标记语言？
假设您正在开发一个网站，盲人用户将成为您目标市场的重要组成部分。如果网站包含文档编辑功能，那么什么是合适的所见即所得工具？是像 Markdown、Textile 这样的语言吗？ > 和 Wiki 格式 真的很容易理解还是对盲人用户来说不方便？
Suppose you're developing a web site and blind users will be a significant chunk of your target market. If the web site includes document editing functionality, what would be appropriate WYSIWYM tools? Are languages like Markdown, Textile and Wiki Formatting really accessible or are they inconvenient to blind users?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我是一个盲人程序员，虽然我没有使用过你提到的大多数语言，但我发现任何 Markdown 语言都相当容易使用，如果你有学习的愿望的话。我在 wiki 中使用 HTML 或多种标记语言都没有问题。部分取决于用户对您网站的投入程度。如果这是一个不经常访问或访问时间很短的网站，那么无论用户是否失明，他们都不太可能花时间学习所需的标记。不幸的是，我还没有找到一个可访问的 JavaScript WYSIWYG 编辑器，但我发现手动输入标记更容易，所以没有费力寻找。
I'm a blind programmer and while I haven't used most of the languages you mention I've found that any markdown language is fairly easy to use if you have the desire to learn it. I've had no problem using either HTML or several markup languages for wiki's. Part of it will depend on how invested the users are in your site. If it's a site that will be visited infrequently or for short periods of time, it's much less likely that a user will take the time to learn the required markup whether they are blind or not. Unfortunately, I have not found an accessible JavaScript WYSIWYG editor but I find it easier to manually enter the markup so haven't looked very hard.
第一个问题是：语义结构有多重要？你能摆脱纯文本吗？您可以进行简单的解析，例如将空白行视为段落标记，将一系列以 * 开头的行视为项目符号列表，识别 URL 并将其放入链接等。
作为一名盲人开发人员，我在理解语言方面没有问题就像 Markdown 一样。但如果这是我不熟悉的语法，只有当我希望经常使用该网站或非常关心其内容时，我才会学习它。
最后我想到两个想法：虽然我在使用 TinyMCE 时确实遇到了一些可访问性方面的挑战，但您可以开发一些更简单的东西 - 提供少于 10 个格式选项，例如插入超链接、制作列表、居中文本、设置样式（例如标题）等 最后，
当我与非技术盲人交谈时，他们通常只是在 Word 中编写内容并粘贴到 wiki 或博客文章中。当我第一次听到这句话时，听起来很奇怪，但确实有道理。因此，理想的解决方案是接受粘贴内容。
最后 - 这取决于这有多重要，以及您想要花费多少努力。也许具有实时预览功能的 Markdown 编辑器（如本网站所示）、用于插入 URL 等简单格式的按钮以及粘贴富文本的功能会勾选所有框:-)
the first question is: how important is semantic structure? could you get away with plain text. You could do simple parsing like treating blank lines as paragraph markers, treating a series of lines which begin with * as a bulleted list, identify URLs and make them into links, etc.
As a blind developer myself, I have no problem in understanding languages like Markdown. But if it's a syntax I'm unfamiliar with, I'll only learn it if I expect to use the site very often, or care deeply about the content.
Two final thoughts come to mind: while I certainly experience some accessibility challenges using TinyMCE, you could develop something much simpler - provide less than 10 formatting options, like inserting hyperlinks, making lists, centering text, setting the style (such as heading) etc.
And lastly, when I talk to non-technical blind people, they often just write their content in Word and paste into a wiki or blog post. This sounded strange when I first heard it, but it does make sense. So an ideal solution would accept pasted in content.
In closing - it depends how important this is, and how much effort you want to expend. Maybe a Markdown editor with a live preview (like on this site), buttons for inserting simple formatting like URLs, and the ability to paste in rich text would tick all boxes :-)
在网页上，盲人用户最容易访问的嵌入式文本编辑器是使用标准 HTML 的编辑器，例如
如果所见即所得工具是使用标准可访问的 HTML 构建的，那么盲人用户可以轻松地在其中输入文本，并完全确信他们在正确的位置输入文本。那么问题就变成了：哪种标记语言更好？它们都需要记忆，但有些可能比其他的更直观。找出最佳方案的一种方法是对各种目标用户进行可用性测试。还要确保提供简单、易于访问的语法帮助。
On a web page, the most accessible embedded text editor for blind users is one that uses standard HTML, such as a
<textarea>element, with a corresponding<label>element:If a WYSIWYM tool is built using standard accessible HTML, then blind users can easily enter text into it, with full confidence that they're entering text in the right place. Then the question becomes: Which is the better markup language? They all require memorization, but some may be more intuitive than others. One way to find out which is best would be to do some usability testing with a wide variety of target users. Also be sure to providing easy, accessible access to syntax help.
想象一下您在纯文本 80x4 显示屏中工作（只需打开控制台并适当调整大小），然后使用 vi/emacs/ed，您很快就会意识到哪些标记会妨碍您。
尝试做尽可能多的工作来理解纯文本，否则使用像 POD 这样的轻标记，最后像 AsciiDoc 这样的东西非常强大，但需要培训。
Picture yourself working in pure text 80x4 display (just open a console and resize appropriately), then use vi/emacs/ed and you'll soon realize what markup will get in the way.
Try to do as much work as possible to understand plain text, else use light markup like POD, finally things like AsciiDoc are very powerful but needs training.
我不了解 WYSIWYG/WYSIWYM 工具，但我确实知道在编写您自己的编辑器代码时遵守 W3C 标准（尤其是他们的 HTML5 和 CSS3 草案）将会有很大帮助。
在 CSS 中，您可以指定语音的速度和语调。在 HTML 中，您可以指定屏幕阅读器兼容的替代文本（许多元素中的
alt属性）。请务必了解何时使用abbr和acronym元素。当您希望屏幕阅读器阅读缩写词的含义时，请使用前者，而当缩写词应作为单词阅读时（例如 ASAP、NATO 和 OS），请使用后者。对于编辑器本身，我建议创建一个使用 div 和 span 的所见即所得编辑器。屏幕阅读器将轻松理解文档的结构。对于当前行，使用文本框；对于未编辑的所有其他行，立即将内容转换为有效的 HTML。
如果您找到了好工具，请务必将其发布在这里。我也在找一个。 :-)
I don't know about WYSIWYG/WYSIWYM tools, but I do know that complying with W3C standards (especially their HTML5 en CSS3 drafts) while writing your own editor code will help a lot.
In CSS you can specify speed and intonation of speech. In HTML you can specify alternative text (
altattribute in many elements) that screen readers are compatible with. Be sure to know when to use theabbrand theacronymelements. Use the former when you want the screen reader to read the meaning of an abbreviation and the latter when the acronym should be read as a word (e.g. ASAP, NATO and OS).For the editor itself, I recommend creating a WYSIWYG editor that uses divs and spans. Screen readers will understand easily the structure of a document. For the current line, use a text box; for every other line that's not being edited, convert the contents immediately to valid HTML.
If you find a good tool, be sure to post it here. I'm looking for one too. :-)