30.07.2013 Views

Visual Basic.NET How to Program (PDF)

Visual Basic.NET How to Program (PDF)

Visual Basic.NET How to Program (PDF)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 24 Accessibility 1209<br />

browser “reads” text that the user selects, allowing the user <strong>to</strong> control the speed and volume<br />

at which the browser reads the contents of the Web page. The WeMedia Browser free<br />

download is available at www.wemedia.com.<br />

IBM Home Page Reader (HPR) is another browser that “reads” text selected by the<br />

user. The HPR uses IBM ViaVoice technology <strong>to</strong> synthesize an audible voice. A trial version<br />

of HPR is available at www-3.ibm.com/able/hpr.html.<br />

24.5 Maximizing Readability by Focusing on Structure<br />

Many Web sites use XHTML tags for aesthetic purposes, ignoring the tags’ intended functions.<br />

For example, the heading tag often is used erroneously <strong>to</strong> make text large and<br />

bold rather than <strong>to</strong> indicate a major section head for content. This practice might create a<br />

desired visual effect, but it also causes problems for screen readers. When the screen–reader<br />

software encounters the tag, it might verbally inform the user that a new section has<br />

been reached. If this is not in fact the case, the tag might confuse users. Therefore,<br />

developers should use h1 only in accordance with its XHTML specifications (e.g., <strong>to</strong> markup<br />

a heading that introduces an important section of a document). Instead of using h1 <strong>to</strong><br />

make text large and bold, developers can use CSS (Cascading Style Sheets) or XSL (eXtensible<br />

Stylesheet Language) <strong>to</strong> format and style the text. For further examples of this nature,<br />

refer <strong>to</strong> the WCAG 1.0 Web site at www.w3.org/TR/WCAG10. [Note: The<br />

tag also can be used <strong>to</strong> make text bold; however, screen readers emphasize bold<br />

text, which affects the inflection of what is spoken.]<br />

Another accessibility issue is readability. When creating a Web page intended for the<br />

general public, it is important <strong>to</strong> consider the reading level (i.e., level of difficulty <strong>to</strong> read<br />

and understand) at which content is written. Web-site designers can make their sites easier<br />

<strong>to</strong> read by using shorter words. Furthermore, slang terms and other nontraditional language<br />

could be problematic for readers from other countries, and developers should limit the use<br />

of such words.<br />

WCAG 1.0 suggests using a paragraph’s first sentence <strong>to</strong> convey its subject. When a<br />

Web site states the point of a paragraph in its first sentence, it is easier both <strong>to</strong> find crucial<br />

information and <strong>to</strong> bypass unwanted material.<br />

The Gunning Fog Index, a formula that produces a readability grade when applied <strong>to</strong><br />

a text sample, can evaluate a Web site’s readability. To obtain more information about the<br />

Gunning Fog Index, visit www.trainingpost.org/3-2-inst.htm.<br />

24.6 Accessibility in <strong>Visual</strong> Studio .<strong>NET</strong><br />

<strong>Visual</strong> Studio .<strong>NET</strong> provides guidelines for the design of accessible software within its programming<br />

environment. For instance, one guideline recommends reserving the use of color<br />

for the enhancement or emphasis of information, instead of for aesthetic purposes. A second<br />

guideline recommends providing information about objects (e.g., desk<strong>to</strong>p icons and<br />

open windows) <strong>to</strong> the accessibility aids (specialized software that renders applications <strong>to</strong><br />

individuals with disabilities). Such information might include the name, location and size<br />

of a window. A third guideline recommends designing user interfaces so that they can accommodate<br />

user preferences. For example, people with visual disabilities should be able <strong>to</strong><br />

modify the font size of a user interface. A fourth guideline recommends allowing users <strong>to</strong><br />

adjust the time setting for applications that have time constraints. For example, users with

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!