1230 Accessibility Chapter 24 of the (Web hosting ecommerce) control calling
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.