User Experience Design optimization: Content Accessibility

The vast majority of peer-contact accessibility is likely to begin with the WCAG1.0WCAG1.0 (which is important in the English abbreviations) developed by the Wai organization of the consortium, and most domestic designers have referred to Junchen's 06- year Translation Web Content Accessibility Guide 1.0(December 11, 2008, WCAG2.0 English edition ), which mentions several key factors to ensure good page design presentation, as well as 14 guidelines:

1. Provide the same text substitution for the audio-visual content;
2. Do not rely solely on color to provide information;
3. Proper use of markup language and style sheets;
4. Clarify the use of natural language;
5. Create a well choreographed table;
6. Ensure that the page can be well presented under new technology;
7. Ensure users can handle changes in time-sensitive content;
8. Ensure the direct accessibility of embedded user interface;
9. Device-independent design;
10. Use a transition solution;
11. Use the technology and specifications recommended by the consortium;
12. Provide content guidance information;
13. Provide clear navigation mechanism of content;
14. Make sure the document content is clear and simple.

Microsoft MSDN's explanations for WAI, WCAG, and Section 508 refer to WCAG1.0 and the Section 508 specification points from the U.S. federal government respectively. Section 508 Bill Subpart B has 16, the original translation of the very long-winded, according to their own understanding to simplify the following:

2. The equivalent text should be provided for each non text element.
4. The equivalent substitution of any multimedia demo should be synchronized with the demo.
6. Ensure that all information conveyed through the color is not colored or available, such as through the context or tag.
8. Documents should be organized so they can be read without the associated style sheet.
10. Provides redundant text links for each active region of the server-side image map.
12. Provides a client-side image map, not a server end, unless the zone cannot be defined with the available geometry.
14. Identifies row and column headings for the datasheet.
16. For data tables with multiple row and column logic levels, you should mark the associated data cells and header Single-cell.
18. Use text that helps frame identification and navigation to add a caption to the frame.
20. Avoid flashing the screen if the frequency is greater than 2Hz and less than 55Hz.
22. When compliance is not possible in any other way, a plain text page with equivalent information or functionality should be provided to allow the Web site to conform to the rules and synchronize accordingly.
24. When you use scripting language to display content or create interface elements, you should set aside the fallback to ensure that the functional text is consistent.
26. When requesting clients to use Plug-ins or applications to interpret page content, you must provide the appropriate plugin or program link.
28. Allows users to use assistive technology to access and submit information, fields, and features required for online electronic forms, including all instructions and hints.
30. Provides methods that allow users to skip duplicate navigation links.
32. When a timed response is required, the user should be warned and given sufficient time to indicate that more time is required.

The peers who are familiar with WCAG and Section 508 may have realized that they meet only part of the accessibility requirements, not a complete solution. Carefully, WCAG has a prerequisite for Web "content" accessibility; Section 508 is a bit broader, but it's a bill rather than a technical standard.

Actually very good understanding, can enter the site to enjoy the service, enjoy the service can experience the function, experience the function to see the content, "content" accessibility is only web accessibility site, service, function, content level one. For example, forcibly set the home page and the window is accessible to the site; 404 pages and forced registrations are service-accessible, and no site search and N-ary links are available for functional accessibility.

After figuring out the technical positioning, the field of vision can be broadened to see the problem is not so vague. For example, the majority of Internet workers to optimize the "Web user Experience" work, there is always a commitment to minimize the risk of change, to obtain the maximum return on the mentality. There are not too many resources and time to do a lot of things, and want to see the effect immediately, for any designer is an absolute challenge. In my experience, such customers need "accessibility design" optimization, and they understand that the "Web user Experience" optimization effort is the only way to go.

Most of the time, when it comes to optimizing professional websites that require expertise to drive design improvements, we often have no constructive suggestions for the "predictability" of the information architecture and the "usability" optimization of the interaction design. Therefore, the place that can be able to do well is only for "accessibility" optimization improvement. This shows that on the one hand, we should pay more attention to and understand the accessibility, on the other hand should pay attention to avoid the limitations of the accessibility of content.

If you understand from the product perspective, it seems that Internet products are always equated with web2.0, UCD design theory is closely related to the development. And for the web1.0 Web site's user experience optimization, I think the accessibility effect is much greater than usability, because such sites do not have complex user behavior, interaction logic, and application scenarios.