A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.unity3d.com/Manual/../ScriptReference/Accessibility.AccessibilityRole.html below:

Unity - Scripting API: AccessibilityRole

AccessibilityRole

enumeration

Suggest a change Success!

Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.

Close Submission failed

For some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.

Close Your name Your email Suggestion*

Cancel

Description

Options for defining the role of an AccessibilityNode to assistive technologies.

You can use values from this enum to set the AccessibilityNode.role. This property helps inform assistive technologies how to interact with your AccessibilityNode. Setting accurate roles improves the usability and user experience of your UI by enabling assistive technologies to set clear expectations for users. A missing role can block a user from interacting with your UI, and an incorrect role can cause confusion and frustration. You can use the default value, AccessibilityRole.None, for nodes whose role is not described by any of the enum options. Some examples are container elements and highly customized controls.

Additional resources: mobile-accessibility.

The following example demonstrates assigning an AccessibilityRole to a UI element based on its VisualElement type.

Properties Property Description None The accessibility node has no roles. Button The accessibility node behaves like a button. Image The accessibility node behaves like an image. StaticText The accessibility node behaves like static text that can't change. SearchField The accessibility node behaves like a search field. KeyboardKey The accessibility node behaves like a keyboard key. Header The accessibility node behaves like a header that divides content into sections (for example, the title of a navigation bar). TabBar The accessibility node behaves like an ordered list of tabs. Slider The accessibility node behaves like a slider. The value of this node can be continuously adjusted through a range. Toggle The accessibility node behaves like a toggle.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4