CTU > Reference Desk > Policies >  Web Policies and Standards Guide for ACES/AAES/COAG
 

Home Page Web Development Policies Introduction Official and Unofficial Websites Before You Start Obtaining and Using Templates Organization and Design Guide Text and Style Guide Usability and Accessibility Images and Graphics Guide Using AAES/ ACES/COAG Logos and Wordmarks


USABILITY AND ACCESSIBILITY

Sometimes the hardest thing for Web developers to realize is that the site they are developing is not primarily for them. The second hardest thing to realize is that a Web site's impact goes beyond the Web. A visitor's perception of a Web site affects that person's view of the product or service represented by the site. So your Web site affects your department, program or unit's credibility, image and perceived value.

Your site should be developed for your organization’s audience—the audiences of the Alabama Agricultural Experiment Station, the Alabama Cooperative Extension System and the College of Agriculture at Auburn University (AAES/ACES/COAG). Your site should focus on audience needs, expectations and user patterns. For more information on usability and accessibility, visit the ACES/AG IT Web development site (see usability and accessibility resources)

Additionally, accessibility is an important component of usability. It's so important that it gets its own section below. Remember that your site's usability will make the difference between satisfied and dissatisfied visitors. Its implications go beyond the Web, so it's worth your attention.

Usability: Basic Principles
Accessibility: Basic Principles


Usability: Basic Principles

• Keep your audience in mind during the entire site development process.

• Make it obvious. Design your site and your navigation so it's immediately clear where things are and how to use the site.

• Make it accurate. Information should be correct and fresh. The site should be free of typographical and other errors.

• Make it fast. Your pages--especially your home page--should load very quickly in all browsers, approximately 15 seconds or less on a 56K modem.

• Make it valuable. Give your users what they came for--and then some.

• Make it searchable. Provide a search function, and optimize your site for presentation on search engines.

• Design it professionally. Presentation matters.

• Keep it up to date. Refresh your content; give the visitor a reason to return.

• Keep your promises. Respond quickly to e-mail and comments. Keep links updated (NO "under construction" pages!).

• Make yourself (or someone else) accessible by e-mail. We recommend using the Securemail form. For more information, visit the ACES/AG IT Web development site (see securemail).

 

Accessibility: Basic Principles

It is important to make your site as accessible as possible for visitors who have some form of disability-- conditions such as blindness, colorblindness or conditions affecting motor coordination. The World Wide Web Consortium (W3C) has developed guidelines for developing Web sites that accommodate these disabilities. Review the Web Accessibility Initiative.

Section 508 of the U.S. Rehabilitation Act is also based on these general standards. Section 508 was "enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals." Section 508 Web-based standards are summarized here.

Rules of thumb to help you make your site accessible and compliant with AAES/ACES/COAG Web standards include the following (similar suggestions are found under the W3C Web Accessibility Initiative):

• If you are using images or graphics of any kind, including graphs and charts, on your site, use ALT tags to describe these elements.

• If you are using image maps, use client-side image maps and ALT text for hot spots.

• If your site has audio or video components, provide captions and transcripts of audio and written descriptions of video.

• For links in text, describe the link rather than using "click here” or providing the URL directly.

• Use a consistent structure in organizing the pages of your Web site.

• Do not use non-breaking spaces ( ) for text alignment on pages.

• If you are using scripts, applets or plug-ins, provide alternative content for all features that may not be accessible in every browser.

• Do not use frames.

• If you wish to use Flash, do not use Flash as the primary or exclusive navigation tool on your site. Use it only as an auxiliary component of your site. Also, create a mirror site that does NOT require Flash.

• Use the accessibility verification tools available on the ACES/AG IT Web development site (see usability and accessibility resources).