Archive for July, 2007

Chapter 24 Accessibility 1231 the tables (Adult web hosting) with screen-reader

Friday, July 27th, 2007

Chapter 24 Accessibility 1231 the tables with screen-reader requirements in mind. For example, the CAST eReader, a screen reader developed by the Center for Applied Special Technology (www.cast.org), starts at the top-left-hand cell and reads columns from left to right, top to bottom. This technique of reading data from a table is referred to as linearized. Figure 24.14 creates a simple table listing the costs of various fruits; later, we provide this table to the CAST eReader to demonstrate its linear reading of the table. The CAST eReader reads the table in Fig. 24.14 as follows: Price of Fruit Fruit Price Apple $0.25 Orange $0.50 Banana $1.00 Pineapple $2.00 This reading does not present the content of the table adequately: The reading neither specifies caption and header information nor links data contained in cells to the column headers that describe them. WCAG 1.0 recommends using Cascading Style Sheets (CSS) instead of tables, unless a table s content linearizes in an understandable manner. 1 2 4 5 6 7 8 9 10 11 12 16 17 18 19 20

Price of Fruit

21 22

23 24
25

26

27

28 29

30

31

32

33 Fig. 24.14 Fig. 24.1FiFig. 24.14g. 24.14 Fig. 24.14 XHTML table without accessibility modifications. (Part 1 of 2.)
We recommend high quality webhost to host and run your jsp application: christian web host services.

1230 Accessibility Chapter 24 of the (Web hosting ecommerce) control calling

Thursday, July 26th, 2007

1230 Accessibility Chapter 24 of the control calling the method is the same as that of nameLabel. Here, we use method GetType of class Type, which returns an instance of class Type; this class represents information about a particular class. We call method GetType on object sender. Eventhandler argument sender is a reference to the control that triggered the event. When the condition at line 116 evaluates to true (i.e., the control that triggered the event is name- Label), lines 118 120 execute. Line 118 casts sender to a Label (now that we know it is one) and assigns it to Labeltemporary. Lines 119 120 call speaker s method Speak, which provides the string that should be converted to speech. A similar process is performed to determine whether the mouse is over a TextBox (line 125) and to generate the appropriate audio (lines 127 130). Lastly, if the control over which the mouse is hovering is neither a Labelnor a TextBox, it must be the Button; lines 136 137 tell the user to click the button to submit information. Method submitButton_Click (lines 142 149) executes when the user clicks the Button. This event handler calls speaker s method Speak, providing as an argument a thankyou message, and then exits the application. Line 82 sets the Text property of submitButton to “&Submit”. This is an example of providing keyboard access to the functionality of the application. Recall that, in Chapter 13, we assigned shortcut keys by placing “&” in front of the letter that would become the shortcut key. Here, we do the same for submitButton pressing Alt+S on the keyboard is equivalent to clicking the submitButton. We establish the tab order in this application by setting the TabIndex and TabStop properties. The TabIndex properties of the controls are assigned in lines 46, 60, 67, 74, 81, 91 and 98. The TextBoxes are assigned the tab indices 1 3, in order of their appearance (vertically) on the form. The Button is assigned tab index 4, and the rest of the controls are given tab indices 5 8. We want the tab order to include only the TextBoxes and the Button. The default setting for the TabStop property of Labels is false thus, we do not need to change it; the labels will not be included in the tab order. The TabStop property of TextBoxes and Buttons is true, which means that we do not need to change the values for those controls either. The TabStop property of speaker, however, is trueby default. We set it to false, indicating that we do not want speaker included in the tab order. In general, those controls with which the user cannot directly interact should have their TabStop properties set to false. The last accessibility feature in this application involves setting the accessibility properties of the controls so that client accessibility applications can access and process the controls properly. Lines 44, 50 51, 57 58, 64 65, 71 72, 78 79, 88 89 and 95 96 set the AccessibleDescription properties of all the controls (including the Form). Lines 45, 52, 59, 66, 73, 80, 90 and 97 set the AccessibleName properties of all the controls (again including the Form). The IsAccessible property is not visible in the Properties window during design time, so we must write code to set it to true. Line 35 sets the IsAccessible property of TextToSpeechto true. Lines 38 39 loop through each control on the form and set each IsAccessible property to true. The Form and all its controls now will be visible to client accessibility applications. 24.8 Accessibility in XHTML Tables Complex Web pages often contain tables that format content and present data. However, many screen readers are incapable of translating tables correctly unless developers design
From our experience, we are can tell you that you can find a reliable and cheap webhost service at Java Web Hosting services.

Chapter 24 Accessibility 1229 111 // tell user (Web hosting bandwidth)

Thursday, July 26th, 2007

Chapter 24 Accessibility 1229 111 // tell user over which control mouse is 112 private void controls_MouseHover( 113 object sender, System.EventArgs e ) 114 { 115 // if mouse is over Label, tell user to enter information 116 if ( sender.GetType() == nameLabel.GetType() ) 117 { 118 Label temporary = ( Label) sender; 119 speaker.Speak( “Please enter your ” + temporary.Text + 120 ” in the textbox to the right” ); 121 } 122 123 // if mouse is over TextBox, tell user what 124 // information was entered 125 else if ( sender.GetType() == nameTextBox.GetType() ) 126 { 127 TextBox temporary = ( TextBox ) sender; 128 speaker.Speak( “You have entered ” + 129 ( temporary.Text == “” ? “nothing” : 130 temporary.Text ) + ” in the ” + temporary.Name ); 131 } 132 133 // otherwise, user is over Button, so tell user to click 134 // it to submit information 135 else 136 speaker.Speak( 137 “Click on this button to submit your information” ); 138 139 } // end method controls_MouseHover 140 141 // thank user for information submission 142 private void submitButton_Click( 143 object sender, System.EventArgs e ) 144 { 145 speaker.Speak( 146 “Thank you, your information has been submitted.” ); 147 148 Application.Exit(); 149 } 150 151 } // end class TextToSpeech Fig. 24.13 Fig. 24.1FiFig. 24.13g. 24.13 Fig. 24.13 Application with accessibility features. (Part 4 of 4.) Method controls_MouseHover determines which type of control the mouse is hovering over and generates the appropriate audio. Line 116 determines whether the type
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

1228 Accessibility Chapter (Web hosting) 24 59 this.nameTextBox.AccessibleName = “User

Wednesday, July 25th, 2007

1228 Accessibility Chapter 24 59 this.nameTextBox.AccessibleName = “User Name TextBox”; 60 this.nameTextBox.TabIndex = 1; 61 this.nameTextBox.MouseHover += 62 new System.EventHandler( this.controls_MouseHover ); 63 64 this.phoneTextBox.AccessibleDescription = 65 “Enter Phone Number”; 66 this.phoneTextBox.AccessibleName = “Phone Number TextBox”; 67 this.phoneTextBox.TabIndex = 2; 68 this.phoneTextBox.MouseHover += 69 new System.EventHandler( this.controls_MouseHover ); 70 71 this.passwordTextBox.AccessibleDescription = 72 “Enter Password”; 73 this.passwordTextBox.AccessibleName = “Password TextBox”; 74 this.passwordTextBox.TabIndex = 3; 75 this.passwordTextBox.MouseHover += 76 new System.EventHandler( this.controls_MouseHover ); 77 78 this.submitButton.AccessibleDescription = 79 “Submit the Information”; 80 this.submitButton.AccessibleName = “Submit Information”; 81 this.submitButton.TabIndex = 4; 82 this.submitButton.Text = “&Submit”; 83 this.submitButton.Click += 84 new System.EventHandler( this.submitButton_Click ); 85 this.submitButton.MouseHover += 86 new System.EventHandler( this.controls_MouseHover ); 87 88 this.passwordLabel.AccessibleDescription = 89 “Password Label”; 90 this.passwordLabel.AccessibleName = “Password Label”; 91 this.passwordLabel.TabIndex = 7; 92 this.passwordLabel.MouseHover += 93 new System.EventHandler( this.controls_MouseHover ); 94 95 this.speaker.AccessibleDescription = 96 “Give Information about Form”; 97 this.speaker.AccessibleName = “Speaker”; 98 this.speaker.TabIndex = 8; 99 this.speaker.TabStop = false; 100 101 this.AccessibleDescription = “Registration Form”; 102 this.AccessibleName = “Registration Form”; 103 } 104 105 [STAThread] 106 static void Main() 107 { 108 Application.Run( new TextToSpeech() ); 109 } 110 Fig. 24.13 Fig. 24.1FiFig. 24.13g. 24.13 Fig. 24.13 Application with accessibility features. (Part 3 of 4.)
You want to have a cheap webhost for your apache application, then check apache web hosting services.

Chapter 24 Accessibility 1227 6 using System.Collections; 7 (Web site traffic)

Wednesday, July 25th, 2007

Chapter 24 Accessibility 1227 6 using System.Collections; 7 using System.ComponentModel; 8 using System.Windows.Forms; 9 using System.Data; 11 // helps users navigate form with aid of audio cues 12 public class TextToSpeech : System.Windows.Forms.Form 13 { 14 private System.Windows.Forms.Label nameLabel; 15 private System.Windows.Forms.Label phoneLabel; 16 17 private System.Windows.Forms.TextBox nameTextBox; 18 private System.Windows.Forms.TextBox phoneTextBox; 19 private System.Windows.Forms.TextBox passwordTextBox; 21 private System.Windows.Forms.Button submitButton; 22 23 private System.Windows.Forms.Label passwordLabel; 24 25 private AxHTTSLib.AxTextToSpeech speaker; 26 27 private System.ComponentModel.Container components = null; 28 29 // default constructor public TextToSpeech() 31 { 32 InitializeComponent(); 33 34 // set Form to be visible to accessibility applications 35 this.IsAccessible = true; 36 37 // let all controls be visible to accessibility applications 38 foreach ( Control current in this.Controls ) 39 current.IsAccessible = true; } 41 42 private void InitializeComponent() 43 { 44 this.nameLabel.AccessibleDescription = “User Name”; 45 this.nameLabel.AccessibleName = “User Name”; 46 this.nameLabel.TabIndex = 5; 47 this.nameLabel.MouseHover += 48 new System.EventHandler( this.controls_MouseHover ); 49 this.phoneLabel.AccessibleDescription = 51 “Phone Number Label”; 52 this.phoneLabel.AccessibleName = “Phone Number Label”; 53 this.phoneLabel.TabIndex = 6; 54 this.phoneLabel.MouseHover += 55 new System.EventHandler( this.controls_MouseHover ); 56 57 this.nameTextBox.AccessibleDescription = 58 “Enter User Name”; Fig. 24.13 Fig. 24.1FiFig. 24.13g. 24.13 Fig. 24.13 Application with accessibility features. (Part 2 of 4.)
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.

Best web hosting site - 1226 Accessibility Chapter 24 Property Purpose AccessibleRole Member

Tuesday, July 24th, 2007

1226 Accessibility Chapter 24 Property Purpose AccessibleRole Member of the AccessibleRoleenumeration. Represents the role of this control in the application this information might help the accessibility client application determine what actions it should take. IsAccessible Contains a boolvalue specifying whether the control is visible to accessibility client applications. Fi Fig. 24.12 Fig. 24.12Fig. 24.1Fi2g. 24.12g.242.1 Properties of class Controlrelated to accessibility. (Part 2 of 2.) The application in Fig. 24.13 uses a text-to-speech control, tab stops and class Control s accessibility-related properties. It consists of a form with three Labels, three TextBoxes and a Button, enabling a user to submit the information. Submitting the information simply terminates the application the application is intended only to demonstrate the use of the text-to-speech control. The accessibility features in this program work as follows: When the mouse is over a Label, the text-to-speech control prompts the user to enter the appropriate information in the TextBoxlocated to the right of the Label. If the mouse is over a TextBox, the contents of the TextBoxare spoken. Lastly, if the mouse is over ButtonSubmit, the user is told that the button should be clicked to submit the information. The tab order is the following: The TextBoxes where the user inputs the name, phone number and password, then the Button. The Labels and text-to-speech control are not included in the tab order, because the user cannot interact with them, and their inclusion would serve no purpose. The accessibility properties are set so that accessibility client applications will obtain appropriate information about the controls. Please note that only the relevant code generated by Visual Studio .NET is included in Fig. 24.13. To use the text-to-speech control, first add it to the Toolbox. This is accomplished by selecting Customize Toolbox from the Tools menu. The Customize Toolbox dialog pops up check the box next to the TextToSpeech Class option. Click OK to dismiss the dialog box. The VText control now is in the ToolBox and can be dragged onto a form int he same way that any other control. The application has three Labels that prompts for the user s name, phone number and password. Three corresponding TextBoxes accept the user s input and, a Buttonallows the user to submit the form. Line 25 declares a text-to-speech control named speaker. We want the user to hear audio descriptions of controls when the mouse is located over those controls. Lines 112 139 define the controls_MouseHover event handler we attach this method to the three TextBoxes and the Button as the event handler for the MouseHoverevent. 1 // Fig. 24.13: TextToSpeech.cs 2 // Providing audio for people with visual impairments. 3 4 using System; 5 using System.Drawing; Fig. 24.13 Fig. 24.1FiFig. 24.13g. 24.13 Fig. 24.13 Application with accessibility features. (Part 1 of 4.)
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.

Chapter 24 Accessibility 1225 5. Never signal information (Web hosting plans)

Tuesday, July 24th, 2007

Chapter 24 Accessibility 1225 5. Never signal information with sound only someone accessing the information might not have speakers or might have hearing impairments.1 6. Test the application without using either a mouse or a keyboard. Access to an application s functionality should not be limited to one input device. For more information on these and other design guidelines for accessible applications, please refer to the Visual Studio .NET documentation under the overview subsection of the index topic accessibility. This section provides links to discussions of how to design more accessible Windows and ASP.NET applications. One specific way that programmers can make their applications more accessible is to use a text-to-speech control in their programs. A text-to-speech control can convert text into speech a computerized voice speaks the words provided as text to the control. Text-tospeech controls facilitate access for people who cannot see the screen. Another way to make applications more accessible is to use tab stops. A tab stop occurs when the user presses the Tab key, causing the focus to transfer to another control. The order in which the controls gain focus is called the tab order, which is determined by the TabIndexvalue of the controls (controls gain focus in ascending order). Each control also has a TabStopproperty if this property is true, the control is included in the tab order; otherwise, it is not. Using the TabIndexand TabStopproperties makes it simple to create more easily navigable applications. If these properties are set incorrectly, the logical ordering of the application might not be maintained. Consider an application that has TextBoxes in which a user inputs a first name, a last name and an address. The logical tab order would take the user from the TextBoxfor the first name to the one for the last name and then to the one for the address. A third and important way in which programmers can increase the accessibility of their applications is to use specific classes provided by .NET. Class Control, for example, has many properties designed for conveying information to users. These applications can then, in turn, find the required information stored as properties. Figure 24.12 lists some properties of class Controlthat are designed to provide information to users. Property Purpose AccessibleDescription Describes the control to an accessibility client application. For example, a CheckBoxthat says “NewUser”would not require more description, but a CheckBoxwith an image of a cat would have its AccessibleDescriptionproperty set to something like, “ACheckBoxwithanimageofacat onit”. AccessibleName Contains a short name or identifier for the control. Fi Fig. 24.12 Fig. 24.12Fig. 24.1Fi2g. 24.12g.242.1 Properties of class Controlrelated to accessibility. (Part 1 of 2.) 1. “Basic Principles of Accessible Design,” .NET Framework Developer s Guide, Visual Studio .NET Online Help
Check Tomcat Web Hosting services for best quality webspace to host your web application.

1224 Accessibility Chapter 24 Tab No Tabs Fig.

Tuesday, July 24th, 2007

1224 Accessibility Chapter 24 Tab No Tabs Fig. 24.11 Fig. 24.1Fg. 24.FFi11ig. 24.11ig.Console windows with tabs and without tabs. 24.11 24.7 Accessibility in C# Visual Studio .NET provides extensive accessibility features and also presents guidelines for creating accessible applications in its development environment. Similar recommendations guide the development of C# applications that are accessible to people with disabilities. It is important that C# programmers gear applications toward as many potential users as possible, rather then toward only the average user. WIth some modifications, most applications can be made accessible to a wide variety of individuals. General guidelines for designing accessible applications are: 1. Use larger-sized fonts this helps people with visual impairments see the text. 2. Create flexible applications that provide keyboard shortcuts for all features within the application this allows people to use the application without employing a mouse. 3. Allow information to be conveyed to the user both in a visual and in an audio context. 4. Use graphics and images whenever helpful visual cues can increase accessibility for people who have trouble reading text on the screen.
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.

Chapter 24 (Http web server) Accessibility 1223 application to operation selection

Monday, July 23rd, 2007

Chapter 24 Accessibility 1223 application to operation selection apply shortcuts mapping scheme key designation Fig. 24.9 Fig. 24.Fig. 24.FF9ig. 24.9ig.9Shortcut key creation. 24. Fig. 24.10 Fig. 24.10Fig. 24.FF10ig. 24.10ig.24.10Removing tabs from Visual Studio environment.
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Christian web host - 1222 Accessibility Chapter 24 pasted from the clipboard).

Monday, July 23rd, 2007

1222 Accessibility Chapter 24 pasted from the clipboard). To create a shortcut key, begin by selecting Options from the Tools menu. In the Options window, select the Keyboard item from the Environment directory. From the Keyboard mapping scheme drop-down list, select a scheme and click the Save As button. Then, assign a name to the scheme in the Save Scheme dialog box and click OK. Enter the task of the shortcut key in the Show commands containing text box. For example, if we were creating a shortcut key for the paste function, we would enter Paste in the text box, or we would select the proper task from the selection list directly below the text box. Then, in the Use new shortcut drop-down list, select the applications that will use the shortcut key. If the shortcut key will be used in all applications, select Global. Finally, in the Press shortcut key(s) text box, assign a shortcut key to the task in the form non-text key + text key. Valid non-text keys include Ctrl, Shift and Alt; valid text keys include A Z, inclusive. [Note: To enter a non-text key, select the key itself do not type the word Ctrl, Shift or Alt. It is possible to include more than one non-text key as part of a shortcut key. Do not enter the + symbol.] Thus, a valid shortcut key might be Ctrl+Alt+D. After assigning a shortcut key, select Assign and then OK. Figure 24.9 illustrates the process of creating a shortcut key for the NewBreakpoint function. The shortcut key (Ctrl+Alt+D) is valid only in the Text Editor. 24.6.5 Rearranging Windows Some screen readers have difficulty interpreting user interfaces that include multiple tabs; this is because most screen readers can read information on only one screen. To accommodate such screen readers, Visual Studio allows developers to customize their user interfaces so that only the console window appears. To remove tabs, select Options from the Tools menu. Then, in the Options window, select the General item from the Environment directory. In the Settings section, select the MDI environment radio button and click OK. Figure 24.10 depicts the Options window, and Fig. 24.11 illustrates a console window with and without tabs. Fig. 24.8 Fig. 24.Fig. 24.FF8ig. 24.8ig.8Adding tabs to the Toolbox. 24.
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.


Fruit Price
Apple $0.25