UI Automation clients such as assistive technologies can obtain role information by calling methods that the UI Automation framework exposes by using the control's AutomationPeer. The available roles in a UI Automation framework are defined in the AutomationControlType enumeration. You can use UI Automation tools to examine the role and value information for the controls, or you can read the documentation for the AutomationPeer implementations of each control. The controls and other UI elements that are part of the XAML vocabulary implement UI Automation support for reporting role and value as part of their definitions. But users of assistive technologies don't generally need to know about the containers and thus most containers aren't named. The container element might report that it is an element that has children in a Microsoft UI Automation representation, such that the assistive technology logic can traverse it. This is because it is the item content that should report a name and corresponding role, not its container. Most container elements such as panels do not promote their content as accessible name. In cases where a button contains only an image, use AutomationProperties.Name to provide a text-only equivalent of the button's intended action. See Labels and LabeledBy.īy default, the accessible name of a button or link is based on the visible text, using the same rules as described in Name from inner text. The accessible name for a form element should be the same as the label that is displayed for that element. Either use AutomationProperties.Name to provide a name, or use the captioning technique. The XAML Image element does not have a direct analog to the HTML alt attribute of img and similar elements. All of the text in that element is used as the name. Element typeįor TextBlock and RichTextBlock elements, an accessible name is automatically determined from the visible (inner) text. This table describes how to define or obtain an accessible name for various types of elements in a XAML UI. Such elements typically include images, input fields, buttons, controls, and regions. Set the accessible name for UI elements so that have a meaning that is important for understanding the content or interacting with the UI. This topic describes code to help your app expose the basic information that assistive technologies need.Īn accessible name is a short, descriptive text string that a screen reader uses to announce a UI element. Basic accessibility info is often categorized into name, role, and value.
0 kommentar(er)
