Does the accessibility Automation property Name ne

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I am looking into adding accessibility support to a WPF application. This article describes guidelines for introducing accessibility support into an application: 

Powered by Goldvk Forum ,the perfessional game raiders forum,including game raides,instance,Game Gold(wow gold ), equipment, pvp, quests, etc.

In this article it describes setting the Name property on controls, as follows: 

The Name for an automation element is assigned by the developer. The Name property should always be consistent with the label text on screen. For example, the Name must be “Browse…” for the button element with “Browse…” as the label. Do not include the control role or type information such as “button” or “list” in the Name. This will cause conflict with the text from LocalizedControlType property. The control type and control patterns are responsible for describing the functionality, not the Name, of an element. Find cheapestwow goldnew from us

The application additionally needs to support localization and different languages. My question is on the above mentioned Name property: Does it it need to be localized or is setting it with English text in XAML sufficient? you can wow gold kaufen from online shop with safe transaction.

Update: The answer is yes! Here is an additional article I found: Using UI Automation for Automated Testing , which states: 

NameProperty This is a text string that identifies or explains a control. NameProperty should be used with caution since it can be localized. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
aV3iU4sJ2f Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 January 2014 Location: Maine Status: Offline Points: 775	Post Options Post Reply Quote aV3iU4sJ2f Report Post Thanks(0) Quote Reply Topic: Does the accessibility Automation property Name ne Posted: 04 May 2014 at 07:26
	I am looking into adding accessibility support to a WPF application. This article describes guidelines for introducing accessibility support into an application: Powered by Goldvk Forum ,the perfessional game raiders forum,including game raides,instance,Game Gold(wow gold ), equipment, pvp, quests, etc. In this article it describes setting the Name property on controls, as follows: The Name for an automation element is assigned by the developer. The Name property should always be consistent with the label text on screen. For example, the Name must be “Browse…” for the button element with “Browse…” as the label. Do not include the control role or type information such as “button” or “list” in the Name. This will cause conflict with the text from LocalizedControlType property. The control type and control patterns are responsible for describing the functionality, not the Name, of an element. Find cheapestwow goldnew from us The application additionally needs to support localization and different languages. My question is on the above mentioned Name property: Does it it need to be localized or is setting it with English text in XAML sufficient? you can wow gold kaufen from online shop with safe transaction. Update: The answer is yes! Here is an additional article I found: Using UI Automation for Automated Testing , which states: NameProperty This is a text string that identifies or explains a control. NameProperty should be used with caution since it can be localized.