Alert Properties

The properties of the Alert widget are:

Enables you to control accessibility behavior and alternative text for the widget.

For more information on using accessibility features in your app, refer the Accessibility appendix in the Quantum Application Design Guidelines Guide.

Syntax

accessibilityConfig

Type

JSON Object

Read/Write

Read + Write

Remarks

  • The accessibilityConfig property is enabled for all the widgets which are supported under the Flex Layout.

NOTE: From Quantum Visualizer V9 SP2 GA version, you can provide i18n keys as values to all the attributes used inside the accessibilityConfig property. Values provided in the i18n keys take precedence over values provided in a11yLabel, a11yValue, and a11yHint fields.

The accessibilityConfig property is a JavaScript object which can contain the following key-value pairs.

Key Type Description ARIA Equivalent
a11yIndex Integer with no floating or decimal number. This is an optional parameter. Specifies the order in which the widgets are focused on a screen.

For all widgets, this parameter maps to the index properties.
a11yLabel String This is an optional parameter. Specifies alternate text to identify the widget. Generally the label should be the text that is displayed on the screen.

For all widgets, this parameter maps to the aria-labelledby property of ARIA in HTML.

NOTE: For the Image widget, this parameter maps to the alt attribute of ARIA in HTML.
a11yValue String This is an optional parameter. Specifies the descriptive text that explains the action associated with the widget. On the Android platform, the text specified for a11yValue is prefixed to the a11yHint. This parameter is similar to the a11yLabel parameter. If the a11yValue is defined, the value of a11yValue is appended to the value of a11yLabel. These values are separated by a space.
a11yHint String This is an optional parameter. Specifies the descriptive text that explains the action associated with the widget. On the Android platform, the text specified for a11yValue is prefixed to the a11yHint. For all widgets, this parameter maps to the aria-describedby property of ARIA in HTML.
a11yHidden Boolean This is an optional parameter. Specifies if the widget should be ignored by assistive technology. The default option is set to false. This option is supported on iOS 5.0 and above, Android 4.1 and above. For all widgets, this parameter maps to the aria-hidden property of ARIA in HTML.
a11yARIA Object
  • This is an optional parameter.
  • For each widget, the key and value provided in this object are added as the attribute and value of the HTML tags respectively.
  • Any values provided for attributes such as aria-labelledby and aria-describedby using this attribute, takes precedence over values given in a11yLabel and a11yHint fields.
  • When a widget is provided with the following key value pair or attribute using the a11yARIA object, the tabIndex of the widget is automatically appended as zero.
    • {"role": "main"}
    • aria-label
  • The aria-labelledby and aria-describedby properties are used to set the IDs of the widgets that describe the value to be provided. You must provide only the widget IDs and not the widget path.
    Consider a Login scenario with a Label widget with the text Username and a TextBox widget for entering the username. To read the text in the Label widget when the TextBox widget is in focus, provide the id of the Label widget to the aria-labelledby property. When you want to provide a little more description for the value entered in the TextBox, you can provide the id of the widget with the description to the aria-describedby property.
 This parameter is only available on the Desktop Web platform.
tagName String
  • Applicable only in the FlexContainer, FlexScrollContainer, Label, and Segment widgets.
  • From Quantum Visualizer V9 Service Pack 2 you can define the HTML tags using the tagName property. The HTML tag assigned to the tagName property replaces the default HTML tags of the Label and Segment widgets.
  • From the Quantum Visualizer V9 Service Pack 5 release, you can define the HTML tags for the FlexContainer, FlexScrollContainer widgets by using the tagName property.
  • This is a constructor-level property. You cannot modify the tags of the widgets during runtime.
  • For more information about the tagName attribute, click here.
 This parameter is only available on the Desktop Web platform.
a11yAttributes Array
  • Applicable only in the Label and RichText widgets.

  • The supported values for the a11yAttributes parameter in the Label widget are AccessibilityTypeNone (array value [0]), AccessibilityTypeHeader (array value [1]), and AccessibilityTypeStaticText(array value [2]).

    NOTE: On the Android platform, you can only provide the AccessibilityTypeHeader value for the a11yAttributes parameter. This parameter is only available on devices that run on Android 9 (and later) versions.

  • The supported values for the a11yAttributes parameter in the RichText widget are AccessibilityTypeNone (array value [0]) and AccessibilityTypeLink (array value [3]).
  • You can select one or more values for this parameter.
  • The default value for this parameter is AccessibilityTypeNone (array value [0]).
 This parameter is only available on the Android and iOS Native platforms.
a11yChildrenHidden Boolean
  • Applicable only in the FlexContainer and FlexScrollContainer widgets.
  • When you enable this property for a container widget, the container widget is hidden along with all its child elements.
  • If you set the value of this property as true, the a11yHidden property of the container and all of its child elements is ignored.
  • If a container widget has both the a11yChildrenHidden and the a11yHidden properties enabled, the a11yChildrenHidden property is applied as it takes higher precedence.
 This parameter is only available on the Android and iOS Native platforms.

Accessibility in Components

  • In a FlexForm containing direct widgets and components, while providing values to the aria-labelledby and the aria-describedby properties for widgets directly inside the FlexForm, you must not provide the Id of the widgets inside the components.
  • In a component containing direct widgets and child components, while providing values to the aria-labelledby and the aria-describedby properties for widgets directly inside the component, you must not provide the Id of the widgets inside the child components.

Android limitations

  • If the results of the concatenation of a11y fields result in an empty string, then accessibilityConfig is ignored and the text that is on widget is read out.
  • The soft keypad does not gain accessibility focus during the right/left swipe gesture when the keypad appears.
  • The i18n key support in accessibilityConfig property depends on the languages supported by the TTS(Text-To-Speech) engine of the mobile device. If the TTS engine of the mobile device does not support a language, the text provided in the accessibilityConfig property is not read by the TTS engine.

Accessibility in Desktop Web Platform

  • To use the accessibilityConfig property on the Desktop Web platform, ensure that you disable the Legacy JS Mode in the Project Settings > Responsive Web section.
  • When accessibilityConfig property is configured for any widget, the tabIndex attribute is added automatically to the accessibilityConfig property.
  • The behavior of accessibility depends on the Web browser, Web browser version, Voice Over Assistant, and Voice Over Assistant version.
  • Currently Desktop web applications support only a few ARIA tags. To achieve more accessibility features, use the attribute a11yARIA. The tags added to a11yARIA will be added to the DOM.

  • The tagName attribute supports the following tags in the Label Segment, FlexContainer, and FlexScrollContainer widgets:

    Widget Name Supported tags Example Remarks
    Label
    • label(default)
    • div
    • span
    • h1, h2, h3, h4, h5, h6

    The following example shows how to assign the tags to the Label widget.

    

/*Sample code to assign the span tag to the Label widget*/
    "accessibilityConfig": {
  "tagName": "span"
}
    		  
    Segment
    • ul(default)
    • ol
    • div
    • table
    • dl

    The following example uses the role and tagName attributes to modify the HTML tag of Segment widget.

    

/*Sample code to assign the div tag to the Segment widget*/
    "accessibilityConfig": {
  "a11yARIA": {
    "role": "grid"
  },
  "tagName": "div"
}
    • You can assign values to the role attribute inside the a11yARIA only when you modify the tag to div.
    • You can only assign the following values to the role attribute of a Segment widget: grid table and button.
    FlexContainer
    • div (default)
    • th
    • td
    • tr
    • dt
    • dd

    The following example uses the role and tagName attributes to modify the HTML tag of a FlexContainer widget.

    

/*Sample code to assign the td tag to a FlexContainer widget*/

    var flx = new kony.ui.FlexContainer({
    "accessibilityConfig": {
        "tagName": "td"
    }
});
    • This is a read-only property.

    • When you specify the value as tr for the tagName property of a FlexContainer widget, ensure that you use the Flex Horizontal Layout Type.
      The height of the FlexContainer widget is inherited from the height of the child widgets present inside it.
    FlexScrollContainer
    • div (default)
    • th
    • td
    • dt
    • dd

    The following example uses the role and tagName attributes to modify the HTML tag of a FlexScrollContainer widget.

    

/*Sample code to assign the td tag to a FlexScrollContainer widget*/

    var flx = new kony.ui.FlexScrollContainer({
    "accessibilityConfig": {
        "tagName": "td"
    }
});
    • This is a read-only property.

Example 1

This example uses the Login scenario to explain how to provide accessibility to the usernameText TextBox widget inside the frmLogin Form. The frmLogin form also contains the usernameLbl Label widget (with the text Username) and rulesLbl Label widget(that contains the username policies). 



//This is a generic property that is applicable for various widgets.
/*Here, we have shown how to use the accessibilityConfig Property for a TextBox widget.You need to make a corresponding use of the accessibilityConfig property for other applicable widgets.*/
frmLogin.usernameText.accessibilityConfig = {
  "a11yLabel": "Label",
  "a11yValue": "Value",
  "a11yHint": "Hint",
  "a11yARIA": {
    "tabindex" /* Integer with no floating/decimal numbers*/: 1,
    "role" /*Prescribed string value as per wcag guidelines*/: "main",
    "aria-labelledby": "usernameLbl"
    "aria-describedby": "rulesLbl"
  }
};

Example 2

This example creates a Label widget (lblSpan) inside the frmSample FlexForm. This sample code uses the tagName property to change the HTML tag of the lblSpan Label from label tag to span tag.



/*Here, we have shown how to use the accessibilityConfig Property for a Label widget. You need to make a corresponding use of the accessibilityConfig property for in Segment widget as well.*/
var lblspan = new kony.ui.Label({
  "accessibilityConfig": {
    "tagName": "span"
  },
  "id": "lblspan",
  "isVisible": true,
  "left": "460dp",
  "skin": "CopyslLabel0b3521e51e03b44",
  "text": "span tag",
  "top": "92dp",
  "width": kony.flex.USE_PREFFERED_SIZE,
  "zIndex": 1
}, {
  "contentAlignment": constants.CONTENT_ALIGN_MIDDLE_LEFT,
  "padding": [0, 0, 0, 0],
  "paddingInPixel": false
}, {});

frmSample.add(lblspan);

Example 3

This example uses the button widget to implement internationalization in accessibilityConfig property, but the principle remains the same for all widgets.



/*Sample code to implement internationalization in accessibilityConfig property in Native platform.*/

Form1.myButton.accessibilityConfig = {
    "a11yLabel": kony.i18n.getLocalizedString("key1")     
};
/*Sample code to implement internationalization in accessibilityConfig property in Desktop Web platform.*/

Form1.myButton.accessibilityConfig = {
    "a11yLabel": "kony.i18n.getLocalizedString(\"key3\")"
};

Platform Availability

  • Available in the IDE
  • iOS
  • Android
  • Desktop Web

Specifies the Icon to be displayed to visually indicate the type of alert.

Syntax

alertIcon

Type

String

Read/Write

No

Remarks

In Android platform, the alert icon can be either a string specifying a local resource, or an image object created using the API: kony.image.

In iOS platform, you can provide the alert icon only as a string. iOS platform does not support the use of the image object.

Examples

Using a local resource for the alert icon:

//Creating the alert with the alertIcon:"icon.png"
var alertBasic = {
    message: "Sample Alert",
    alertIcon: "icon.png"
};
//The icon.png should be available in resources folder.
var alertPSP = {};

var alert = kony.ui.Alert(alertBasic, alertPSP);

Using an image object:

//Creating the alert with an image object
imgObjRef = kony.image.createImage("local.png");
pspConfig = {};
var alert = kony.ui.Alert({
    "message": "Alert text",
    "alertType": constants.ALERT_TYPE_INFO,
    "alertTitle": "Alert Title",
    "yesLabel": "Yes",
    "noLabel": "",
    "alertIcon": imgObjRef,
    "alertHandler": null
}, pspConfig);

Platform Availability

  • Available in the IDE
  • iOS (does not support the image object)
  • Android

Specifies the Title of the alert.

Syntax

alertTitle

Type

String

Accessible from Code

No

Example

//Creating the alert with the alertTitle:"Confirmation"
var alertBasic = {
    message: "Sample Alert",
    alertTitle: "Confirmation"
};

var alertPSP = {};

var alert = kony.ui.Alert(alertBasic, alertPSP);

Accessible from IDE

Yes

Platform Availability

Available on all platforms

Specifies the Type of the alert window to be displayed. You can select one of the following:

  • Confirmation - This type is used when you want the user to verify or accept something. For example, In this type, the user has to click either "OK" or "Cancel" buttons to proceed or exit.
  • error - This type is used to display when user enters incorrect value. For example, username or password in a login screen.
  • info (Default)- This type is used to display some information to the user.

Use the below constants to display alert type using constructor:

  • ALERT_TYPE_CONFIRMATION
  • ALERT_TYPE_ERROR
  • ALERT_TYPE_INFO (Default)

Syntax

alertType

Type

Number

Accessible from Code

No

Example

//Creating the alert with the alertType:constants.ALERT_TYPE_CONFIRMATION
var alertBasic = {
    message: "Sample Alert",
    alertType: constants.ALERT_TYPE_CONFIRMATION
};

var alertPSP = {};

var alert = kony.ui.Alert(alertBasic, alertPSP);

Accessible from IDE

Yes

Platform Availability

Available on all platforms

In Desktop Web applications, when you hover the mouse over any widget, a mouse pointer appears. Using the cursorType property in Visualizer, you can specify the type of the mouse pointer.

Syntax

cursorType

Type

String.

You must provide valid CSS cursor value such as wait, grab, help, etc. to the cursorType property.

Read/Write

Read + Write

Remarks

To add the cursorType property using Quantum Visualizer in a Desktop Web application, follow these steps.

  1. In Quantum Visualizer, open the Desktop Web application. From the Project explorer, expand Responsive Web/ Desktop> Forms and select the form to which you need to make the changes.
  2. On the canvas, select the widget for which you want to specify the cursor type. For example, button.
  3. From the Properties panel, navigate to the Skin tab > Hover Skin tab.
    You will find that the details of the hover skin is not enabled here.
  4. Check the Enable option to add a hover skin to your widget.
    The details and configurations of the hover skin is enabled.
  5. Under the General section, for the Platform option, click the ellipsis icon.
    The Fork Skin window appears.
  6. In the Fork Skin window, for Desktop, check under HTML5 SPA.
  7. Click Ok. You have successfully forked your hover skin for Desktop Web application.
    You can see that the Cursor Type property has been added under the General section.
  8. Select a value from the drop-down list to set the Cursor Type for the widget.

Example

 

//This is a generic property and is applicable for many widgets.

/*The example provided is for the Button widget. Make the required changes in the example while using other widgets.*/

frmButton.myButton.cursorType = "wait";

Platform Availability

  • Available in IDE
  • Desktop Web

Specifies the message description of the alert to be displayed.

Syntax

message

Type

String

Accessible from Code

No

Example

//Creating the alert with the message:"Sample Alert"
var alertBasic = {
    message: "Sample Alert"
};

var alertPSP = {};

var alert = kony.ui.Alert(alertBasic, alertPSP);

Accessible from IDE

Yes

Platform Availability

Available on all platforms

Specifies the descriptive Text for the "No" label.

Syntax

noLabel

Type

String

Accessible from Code

No

Example

//Creating the alert with the noLabel:"No"
var alertBasic = {
    message: "Sample Alert",
    alertType: constants.ALERT_TYPE_CONFIRMATION,
    noLabel: "No"
};

var alertPSP = {};

Accessible from IDE

Yes

Platform Availability

Available on all platforms

This property is used to retain the content alignment property value, as it was defined.

NOTE: Locale-level configurations take priority when invalid values are given to this property, or if it is not defined.

The mirroring widget layout properties should be defined as follows.



function getIsFlexPositionalShouldMirror(widgetRetainFlexPositionPropertiesValue) {
    return (isI18nLayoutConfigEnabled &&
    localeLayoutConfig[defaultLocale]
    ["mirrorFlexPositionalProperties"] == true &&
    !widgetRetainFlexPositionPropertiesValue);
}

The following table illustrates how widgets consider Local flag and Widget flag values.

Properties Local Flag Value Widget Flag Value Action
Mirror/retain FlexPositionProperties true true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties true false Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties true not specified Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties false true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties false false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties false not specified Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties not specified false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified not specified Use the Design/Model-specific default layout.
 

Syntax

retainContentAlignment

Type

Boolean

Read/Write

No (only during widget-construction time)

Example



//This is a generic property that is applicable for various widgets.


//Here, we have shown how to use the retainContentAlignment property for Button widget.
/*You need to make a corresponding use of the 
retainContentAlignment property for other applicable widgets.*/
var btn = new kony.ui.Button({
    "focusSkin": "defBtnFocus",
    "height": "50dp",
    "id": "myButton",
    "isVisible": true,
    "left": "0dp",
    "skin": "defBtnNormal",
    "text": "text always from top left",
    "top": "0dp",
    "width": "260dp",
    "zIndex": 1
}, {
    "contentAlignment": constants.CONTENT_ALIGN_TOP_LEFT,
    "displayText": true,
    "padding": [0, 0, 0, 0],
    "paddingInPixel": false,
    "retainFlexPositionProperties": false,
    "retainContentAlignment": true
}, {});

Platform Availability

  • Available in IDE
  • iOS
  • Android

This property is used to retain flex positional property values as they were defined. The flex positional properties are left, right, and padding.

NOTE: Locale-level configurations take priority when invalid values are given to this property, or if it is not defined.

The mirroring widget layout properties should be defined as follows.



function getIsFlexPositionalShouldMirror(widgetRetainFlexPositionPropertiesValue) {
    return (isI18nLayoutConfigEnabled &&
    localeLayoutConfig[defaultLocale]
    ["mirrorFlexPositionalProperties"] == true &&
    !widgetRetainFlexPositionPropertiesValue);
}

The following table illustrates how widgets consider Local flag and Widget flag values.

Properties Local Flag Value Widget Flag Value Action
Mirror/retain FlexPositionProperties true true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties true false Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties true not specified Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties false true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties false false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties false not specified Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties not specified false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified not specified Use the Design/Model-specific default layout.
 

Syntax

retainFlexPositionProperties

Type

Boolean

Read/Write

No (only during widget-construction time)

Example



//This is a generic property that is applicable for various widgets.


//Here, we have shown how to use the retainFlexPositionProperties property for the Button widget.
/*You need to make a corresponding use of the 
retainFlexPositionProperties property for other applicable widgets.*/
var btn = new kony.ui.Button({
    "focusSkin": "defBtnFocus",
    "height": "50dp",
    "id": "myButton",
    "isVisible": true,
    "left": "0dp",
    "skin": "defBtnNormal",
    "text": "always left",
    "top": "0dp",
    "width": "260dp",
    "zIndex": 1
}, {
    "contentAlignment": constants.CONTENT_ALIGN_CENTER,
    "displayText": true,
    "padding": [0, 0, 0, 0],
    "paddingInPixel": false,
    "retainFlexPositionProperties": true,
    "retainContentAlignment": false
}, {});

Platform Availability

  • Available in IDE
  • iOS
  • Android

This property is used to convert Flow Horizontal Left to Flow Horizontal Right.

NOTE: Locale-level configurations take priority when invalid values are given to this property, or if it is not defined.

The mirroring widget layout properties should be defined as follows.



function getIsFlexPositionalShouldMirror(widgetRetainFlexPositionPropertiesValue){

    return (isI18nLayoutConfigEnabled &&
    localeLayoutConfig[defaultLocale]
    ["mirrorFlexPositionalProperties"] == true &&
    !widgetRetainFlexPositionPropertiesValue);
}

The following table illustrates how widgets consider Local flag and Widget flag values.

Properties Local Flag Value Widget Flag Value Action
Mirror/retain FlexPositionProperties true true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties true false Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties true not specified Use Mirror FlexPositionProperties since locale-level Mirror is true.
Mirror/retain FlexPositionProperties false true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties false false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties false not specified Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified true Use the designed layout from widget for all locales. Widget layout overrides everything else.
Mirror/retain FlexPositionProperties not specified false Use the Design/Model-specific default layout.
Mirror/retain FlexPositionProperties not specified not specified Use the Design/Model-specific default layout.
 

Syntax

retainFlowHorizontalAlignment

Type

Boolean

Read/Write

No (only during widget-construction time)

Example



//This is a generic property that is applicable for various widgets.


//Here, we have shown how to use the retainFlowHorizontalAlignment property for Button widget.
/*You need to make a corresponding use of the 
retainFlowHorizontalAlignment property for other applicable widgets. */
var btn = new kony.ui.Button({
 "focusSkin": "defBtnFocus",
 "height": "50dp",
 "id": "myButton",
 "isVisible": true,
 "left": "0dp",
 "skin": "defBtnNormal",
 "text": "always left",
 "top": "0dp",
 "width": "260dp",
 "zIndex": 1
}, {
 "contentAlignment": constants.CONTENT_ALIGN_CENTER,
 "displayText": true,
 "padding": [0, 0, 0, 0],
 "paddingInPixel": false,
 "retainFlexPositionProperties": true,
 "retainContentAlignment": false,
 "retainFlowHorizontalAlignment ": false
}, {});

Platform Availability

  • Available in IDE
  • iOS
  • Android

Specifies the descriptive Text for the "Yes" label.

Syntax

yesLabel

Type

String

Accessible from Code

No

Example

//Creating the alert with the yesLabel:"Yes"
var alertBasic = {
    message: "Sample Alert",
    yesLabel: "Yes"
};

var alertPSP = {};

var alert = kony.ui.Alert(alertBasic, alertPSP);

Accessible from IDE

Yes

Platform Availability

Available on all platforms