937 Build

9.3.7/ac_accessibility_features_for_designers.md

@@ -0,0 +1,55 @@
+# Accessibility features for application designers 
+
+HCL Leap contains accessibility features so users with disabilities can create forms and applications.
+
+To make designing forms and applications easier for users with disabilities, Leap has the following keyboard shortcuts:
+
+#### Adding items to your form
+
+To add items to your form from the Palette, set focus on the form item with the Tab key and press Enter. The item appears on the form where indicated by a blue line.
+
+#### Focus indicator
+
+When a form item has focus the background changes color, and the area that is occupied by the form item is defined by a colored line.
+
+#### Item triggers
+
+When an item has focus, you can trigger it by pressing the Enter key or space bar. The browser that you use determines whether you must press the Enter key or space bar.
+
+#### Tab key
+
+You can navigate to any visible form item, link, or menu by pressing the **Tab** key.
+
+#### Tab navigation
+
+The Properties side panel contains multiple tabs. To navigate between tabs, use the arrow keys.
+
+#### Tab order of form items
+
+When you place items on a form, the tab order is set based on item placement. If you insert a form item before existing items, the tab order is automatically reset. You do not have to manually configure tab order when you insert additional items into a form.
+
+#### Navigating between Palettes
+
+You can navigate between the Common, and Specialized palettes. When the focus is on one Palette use any arrow key to collapse the open Palette and expand another one. If you want to switch palettes while focus is on a form item, you must use the Tab key to move to the palette name, then navigate with the arrow keys. You cannot navigate between palettes when a form item has focus.
+
+#### Keyboard commands for common items
+
+Leap has three menu items: **Save**, **Preview**, and **Cancel**. The following keyboard commands are available so you do not have to navigate away from your form.
+
+  - Save: Ctrl+s
+  - Preview: Ctrl+e
+  - Cancel: Ctrl+q
+
+When designing forms the Properties side panel contains a box titled “Accessibility - Alternative text ID”. Use this box to provide a text description that is used by accessibility tools to describe the item.
+
+The following [WAI ARIA](http://www.w3.org/TR/wai-aria/) attributes are automatically added to form items when you design forms:
+
+-   aria-labelledby and Aria-label are added to fields to associate the correct label with each field.
+-   aria-describedby are added to fields where more description is needed to describe the function of a field.
+-   aria-required is added to inform a user that the field is mandatory.
+-   aria-invalid is added to fields when the value is not valid.
+-   aria-alert is used with Aria-invalid in error messages. Screen readers read the Aria-alert text to the user.
+-   aria-valuemin and aria-valuemax are used to denote if the file has an acceptable value range. If the value is outside the range, the aria-invalid attribute is set.
+
+**Parent topic: **[Accessibility overview](ac_experience_builder_accessibility.md)
+

9.3.7/ac_accessibility_features_for_users.md

@@ -0,0 +1,16 @@
+# Accessibility features for application users {#accessibilityfeaturesforapplicationusers .concept}
+
+When given the link to an HCL Leap application, a user is provided with many built in accessibility features.
+
+To make using forms and applications easier for users with disabilities, Leap has the following accessibility features and keyboard shortcuts:
+
+Screen reader compatibility
+:   Leap is compatible with screen readers that comply with WCAG 2.0 and WAI-ARIA. Some screen readers perform a read through of web pages from start to finish as the default.
+
+Tab key
+:   You can navigate to any visible form item, link, or menu by pressing the **Tab** key.
+
+<strong>Note:</strong>To move focus out of the Sample request or response body input area in a service description form, press <b>Esc</b>><b>Tab</b>.
+
+**Parent topic: **[Accessibility overview](ac_experience_builder_accessibility.md)
+

9.3.7/ac_creating_accessible_application.md

@@ -0,0 +1,21 @@
+# Creating an accessible application {#creatinganaccessibleapplication .concept}
+
+When you create a form or application, the following information helps you design an accessible form for users with disabilities.
+
+HCL Leap is designed to make building accessible forms easy. For example, the tab order of form items is set to start at the first item on the page, and work through consecutive items. You do not have to reset the tab order if you must add items to the beginning of a form. There are several things that you can do to make your forms more accessible to users with disabilities:
+
+-   During the creation of your application, accessibility standards, such as [WCAG 2.0](http://www.w3.org/TR/WCAG20/), should be considered with regards to layout and content. Leap does not prevent authors from creating non-accessible forms.
+-   When you add items to your form, give each form item a clear description or name. Screen readers read the name that is associated with a form item. You can also use a Text item as a data label instead of the field provided. For more information, see [Using a Text item as a label](ac_using_text_item_as_label.md).
+-   Add hints to each form item by modifying the **Add hint** field. The Hint provides more information when read to the user. For example, if your form has a **Name** field, the hint tells the user your preference for how to enter their given and surnames.
+-   Text blocks are not automatically part of the tab order. Screen readers do not put focus on text blocks, and your users might miss vital information. To ensure that text information is not omitted, select the text item, in the properties side panel, select the check box for **Add to tab order**. The text is added to the tab order, and is read by screen readers.
+-   If you add images or media items to your forms, open the Properties side panel and add descriptive text to the **Alternative text** property. A screen reader uses the alternative text to describe the image or media item to the user.
+-   You can add text items to your form and have them associate with other form items. You can use this technique to create formatted titles for your form items. However, you must link the text item and the form item together. For example, you have a Select One item on your form. You want its title to be rich text so it can have a color, background, and format different from the default title. You add the title with the Text form item, which gives the formatting you want. However, the text item is not read by the screen reader, and the user might not know what the choice list represents. To ensure that the **Text** field is read by a screen reader, go to the choice list Properties side panel. Insert the name of the **Text** field into the **Accessibility – Alternative label ID** field. A screen reader reads the appropriate text for the choice list.
+-   When using the new dynamic layout, it might be necessary to group items into Sections to convey the proper meaning to users. For example, when creating a custom label via the alternative text ID option.
+-   When using **Sections**, if a label exists, it provides a navigation landmark using WAI-ARIA that is available to assistive technologies. For more information, [WAI\_ARIA roles](http://www.w3.org/WAI/PF/aria/roles).
+
+-   **[Using a Text item as a label](ac_using_text_item_as_label.md)**  
+For accessibility ease of use, users might prefer to see the title of an entry field to the side of the field, rather than above the field.
+
+**Parent topic:** [Using the editor](cr_using_the_editor_toc.md)
+
+

9.3.7/ac_experience_builder_accessibility.md

@@ -0,0 +1,14 @@
+# Accessibility overview {#experiencebuilderaccessibility .concept}
+
+HCL Leap contains a number of built-in accessibility features to make applications easy to create and use by people with disabilities.
+
+Leap provides the best accessibility experience when used with the newest release of the browser and the newest release of the screen reader. For more information, see the following URLs:
+
+-   [Accessible Rich Internet Applications \(WAI-ARIA\) 1.0](http://www.w3.org/TR/wai-aria/)
+-   [Web Content Accessibility Guidelines \(WCAG\) 2.0](http://www.w3.org/TR/WCAG20/)
+
+-   **[Accessibility features for application designers](ac_accessibility_features_for_designers.md)**  
+HCL Leap contains accessibility features so users with disabilities can create forms and applications.
+-   **[Accessibility features for application users](ac_accessibility_features_for_users.md)**  
+When given the link to an HCL Leap application, a user is provided with many built in accessibility features.
+

9.3.7/ac_using_text_item_as_label.md

@@ -0,0 +1,27 @@
+# Using a Text item as a label {#settingatextitemasalabel .task}
+
+For accessibility ease of use, users might prefer to see the title of an entry field to the side of the field, rather than above the field.
+
+The following instructions describe how to set a text item as the title of a field. For this example, the title is displayed to the left of the field where the user will type information. You can also use these instructions inside a Section, which allows you to format the spacing between the Text item and the Entry Field without affecting the spacing of the rest of your form.
+
+1.  Add a **Text** item to the left column of the grid.
+
+    The Edit Text Properties side panel opens.
+
+2.  Type the title you want to display to users on the form.
+
+3.  Copy the information displayed in the **ID** field.
+
+    On a new form, where the text item is the first item on the form, the default name is F\_Text1. You can change this ID to be any name you want, however each form item must have a unique ID.
+
+4.  Add a **Single Line Entry**, or **Multi-Line Entry** to the right of the **Text** item.
+
+5.  In the properties side panel, delete the text from the **Title** field.
+
+6.  Go to **Data Label** and paste the unique ID you copied from the **Text** field.
+
+
+When you save and preview the form, the text item appears as the label for the entry field.
+
+**Parent topic:** [Creating an accessible application](ac_creating_accessible_application.md)
+

9.3.7/ad_managing_db2_database.md

@@ -0,0 +1,8 @@
+# Backing up and restoring the DB2 database {#managingyourdb2database .concept}
+
+Data for HCL Leap applications is stored within a database. Ensure that you have a backup and restore strategy in place to protect your data.
+
+Backing up and restoring data in DB2® is done using the **Backup** and **Restore** commands. If you plan to restore data from a server with a different bit order than the one currently storing the data, you must use the Data Movement Tool. For more information, see [Data Movement Tool](http://www.ibm.com/developerworks/data/library/techarticle/dm-0906datamovement/).
+
+**Parent topic: **[Administering Leap](administering_leap.md)
+

9.3.7/admin_application_dashboard.md

@@ -0,0 +1,19 @@
+# Admin Application Dashboard {#admin_application_dashboard .concept}
+
+The Admin Application Dashboard is a page that is available to members of the Admin or SuperAdmin groups.
+
+An **Admin** tab will appear in the top banner for users with permission. The page provides information about all the applications on the Leap server. To manage the load on the server, the details are gathered using a timer task that runs at a regular configurable interval \(see Application Statistics collection timer in [Configuration properties](co_configuration_properties.md)\).
+
+The dashboard shows the following:
+
+-   The total number of applications.
+-   A breakdown of the applications by status \(i.e. running, undeployed\).
+-   The total number of application records across all applications.
+-   A filterable table of all the applications. Clicking on a row in the table reveals additional details about the selected application.
+
+The data may be updated by clicking **Refresh**. The data may be exported to a spreadsheet by clicking **Export to spreadsheet**.
+
+For more information, see [Application statistics REST API](app_stats_restapi.md).
+
+**Parent topic: **[Administering Leap](administering_leap.md)
+