Web Design Core Issue 3: Designing for Users (8)

web| Design | problems

3. 11 accessibility

There is no way to consider the small differences between all people. In fact, the purpose of creating a site is for most people to like it. This leads us to combine the user base into a general female surfer under the age of 1 8 and so on, which may lead us to make some compromises. In this sense, however, the site is not designed to cater to the largest number of people who stumble upon your site in a statistically significant way. Try to please all different types of users to make the site easier to access. Don't forget that even if you think that some people have perfect physical and technical skills, they still have some difficulties.

It is no longer a good idea to provide accessibility to people with disabilities in vision, hearing, or other parts of the body. In fact, this is an essential requirement for many departments, especially those in government departments or those that incur serious criticism if they do not consider all users. For example, 1 9 8 6-Year Federal Restitution Act 5th 0 8 bar. The most interesting thing about this section is that the federal government must sign a contract to provide solutions to the problems of the disabled. These provisions will eventually apply to systems such as intranet, corporate extranet, or public network. At the same time consider the 1 9 9-2 American Disability Act (a D a), which claims that, in the case of employees exceeding 1 5, reasonable facilities should be provided for persons with disabilities. This also applies to creating an enterprise intranet or an enterprise extranet. But do not assume that creating an accessible site is for the purpose of not violating relevant laws or future legal provisions, and that, in fact, if you resolve accessibility issues, you will create sites that are more suitable for everyone. Often, creating accessible sites also benefits all users, regardless of their capabilities. Consider the books that speak, which were originally designed for the blind and later evolved into tape. Similarly, the slopes of the buildings and the wheelchair-designed roads provide convenience for all and reduce the number of people who cross the road or sprain their ankles. The World Wide Web (w. W. 3 o RG) has long advocated the ability to design sites for good accessibility and to improve the accessibility of the Web (W. W 3. o rg/w a i). WA I not only cares about designing accessible sites for people with disabilities, but also stands for anyone who designs more accessible sites (he may work in different environments that the designer thinks is "normal"). Remember, not all users have the same quick access devices and large displays as you do-or maybe you don't have the most advanced and fast devices that your users might have. From the guidelines for the World Wide Web, you should consider users under different operating restrictions:

• They may not be able to hear or see, or they cannot easily handle certain types of information (or even all the information).
• They may have difficulties in reading and understanding because of the linguistic limitations of knowledge.
• Because of the different access routes, they may not be able to use a keyboard or mouse, such as using a cellular phone or having a physical disability.
• They may lack the ideal environment, such as using text terminals, small screens and monochrome screens, or slow internet access devices.
• They may be in a vulnerable non-standard environment, such as in noisy internet cafes or when driving to visit the site.
• They may use older browsers, nonstandard browsers or operating systems, or use other user interfaces such as voice input. To address these issues, the World Wide Web forum (W 3 C) offers some suggestions for improving site accessibility. Here is a summary of the following: 1 provides equivalent auditory and visual content that can be replaced. In other words, don't just rely on a form of communication. If you use a graphics button, it's also a good idea to provide text links. If you use sound, it is best to provide a text form of the message about the Vice

Ben, wait.

2 do not rely solely on color. As discussed earlier in this chapter. Not all users can correctly detect color, if the simple use of color to convey information, those who can not distinguish a certain color or equipment lack of color users, or even graphic display equipment, can not correctly understand the content to be expressed. You should consider avoiding combinations of the same tonal colors, or combinations of colors that lack sufficient contrast-especially if they are displayed on a monochrome display or viewed by a colored blind person.

3 Proper use of tags and style sheets. Must use H T M L as the structure and the C s to express. In particular, avoid proprietary markup and expression elements and avoid the use of techniques that have different effects on different browsers. These issues will be discussed in more detail in Chapter 1th 3.

4 clarifying the use of natural language. Be sure to use terms and tags to display acronyms, definitions, references, and so on. In other words, more logical tags should be used. Further, be sure to clearly display the language used in the document for easy translation into other languages.

5 Create a table that can be gracefully converted. In short, when using C s in the future, do not use the table style-just use them to express flat data like spreadsheets. When working with tables, provide clear headings, columns, and reading headings, as well as other flags to represent the content.

6 Ensure that the features of the Web page can be transformed gracefully with new technology. This is the key idea throughout the book. Try to minimize the design limitations of new technologies in older versions of browsers. For example, if you use the J a V a S C R I p T, you should consider whether the Web page continues to be valid without supporting it.

7 Let the user control the change of time sensitive content. Make sure that objects or Web pages that move, blink, scroll, and automatically update can be paused or stopped by the user. In addition to being very annoying, those uncontrollable distractions also make it impossible for users to focus on site browsing.

8 Ensure that the embedded user interface is easy to access directly. If you use a user interface in a Web page-for example, Java applets have their own internal interface-make sure they are also easy to access.

9) for the device-independent design. Try to design a device-independent interface that includes different screen sizes, different viewing devices (cellular phones or computers), different operating devices such as a keyboard, or a combination of mouse and keyboard. A very important consideration is that the site should not only rely on the mouse to browse. Some users may feel that the mouse is more difficult to move, and more powerful users like to use the keyboard to navigate.

10. Use of temporary programmes. Because not all browsers fully support the same technology and standards. Be sure to provide an alternative to browsers that are not compatible in the short term.

11 Use the technology and guidelines of the World Wide Web forum. This is an unspoken but sometimes troublesome suggestion that should always be followed, at least ideologically. However, it is important to remember that the World Wide Web forum guidelines are nothing more than recommendations, and browsers often lack significant and consistent support for these specifications.

12 provide background and direction information. In a sense, it is trying to provide instructions or explanations for complex areas. The Web page should be designed to use "tooltips" or range annotations, and the meaning of the links becomes very clear, as the 6th chapter explains. Further, the design form should explain what is needed, and 1th 2 will discuss it. The most basic way is that the site should provide a help system.

13 provide a clear navigation mechanism. Basically, you should provide a navigation system that is easy to understand and be anchored to a location on the screen. Navigation assistance should also be provided, such as search engines, site images, or site indexes (chapters 7th and 8th).

14 ensure the document is clear and concise. Another very obvious suggestion is that simplicity can lead to greater accessibility. Usability is directly related to simplicity and consistency. You should try to keep the text simple. In addition to manual inspection, use such as b o b b y (w W. c a s T.) o rg/b o b y) Such tools are also easy to assess for site accessibility, as shown in Figure 3-7. b o b y will analyze a Web page to see if it meets certain accessibility conditions, such as the use of a L-t text.