Design Usability
  Home arrow Design Usability arrow Page 4 - Accessibility and Dreamweaver MX 2004
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Moblin 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DESIGN USABILITY

Accessibility and Dreamweaver MX 2004
By: Apress Publishing
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 10
    2004-09-29

    Table of Contents:
  • Accessibility and Dreamweaver MX 2004
  • Accessibility Overview
  • Defining Disabilities
  • Assistive Technologies
  • Accessibility Standards
  • Accessibility in Dreamweaver MX 2004
  • Adding Media, Frames and Forms
  • Adding Tables
  • Accessibility Validation
  • Cascading Stylesheets
  • Accessible Authoring Environment

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Accessibility and Dreamweaver MX 2004 - Assistive Technologies


    (Page 4 of 11 )

    Users with disabilities frequently rely on specialized hardware and software tools to access web content. These tools, known as assistive technologies, range from screen readers to touch screens and head pointers.

    Blind users frequently use software called a screen reader that reads the contents of a web page out loud. Two common (and previously mentioned) screen readers are JAWS, from Freedom Scientific, and Window-Eyes, from GW Micro. Screen readers enable users to hear, rather than view, the contents of a web page; however, a screen reader can read only text, not images or animations. It is essential, therefore, that images and animations be assigned text descriptions that screen readers can read. These text descriptions are called alternative text, or alt text.

    Users with impaired mobility may rely on the keyboard instead of the mouse to navigate web pages. In Internet Explorer, pressing Tab moves the focus of the browser among all available links on a page. The border around links in IE lets the user know where the current focus of the browser is positioned. Pressing Enter activates links, giving the same effect as clicking a mouse button. In Figure 3-1, notice the border around the link for the Apress TechZone logo.

    Assistive devices include a touch screen, which allows an individual to navigate the page using her or his hands without requiring the fine-motor control needed to use the mouse, and a head pointer, which is simply a stick placed in a person’s mouth or mounted on a head strap that the person uses to interact with a keyboard or a touch screen.


    Figure 3-1.  Note the border indicating the current focus.

    In these cases, it is very important that essential components of the page work without a mouse. Rollovers, drop-down menus, and interactive simulations are all examples of elements that typically depend on the mouse for user interaction. The designer or developer of these elements must ensure that keyboard-defined events are included with mouse-defined events. A quick test using the keystrokes available in IE can provide a valuable glimpse of the difficulties a web page may present for users with disabilities who cannot use a mouse. For example, a user can move to any focusable object, including links, form controls, and embedded objects, by pressing the Tab key; pressing the Enter key will activate selected links. Pressing Ctrl+Tab moves between frames. This replicates some of the ways users who cannot use a mouse must interact with a web page.

    This chapter is from ASP Web Development with Macromedia Dreamweaver MX 2004, by Rachel Andrew et al., (Apress, 2004, ISBN: 1590593499). Check it out at your favorite bookstore today.

    Buy this book now.

    More Design Usability Articles
    More By Apress Publishing


     

    DESIGN USABILITY ARTICLES

    - Create Great JavaScript and CSS Menus Simply
    - Design Principles that Shape a Web Site
    - Creating Aqua Style Images
    - Easy as A,B,C – dynamic A to Z indexes
    - EasyChart: a Usability Teaching Tool to Demo...
    - Building Friendly Pop-up Windows
    - Back to School: Design Usability
    - Using HTML_QuickForm To Manage Web Forms, Pa...
    - Using HTML_QuickForm To Manage Web Forms, Pa...
    - More Website Knick Knack
    - Browsers as Test Platforms
    - Website Knick Knack
    - Dynamic Page Elements-Cloak and Dagger Web D...
    - Accessibility and Dreamweaver MX 2004






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway
    Stay green...Green IT