Page History

Accessibility Rules

1. The top level of a page should be the ROOTUIELEMENTCONTAINER.
2. Each visible group of UI elements should be put in a Transparent Container. If the Transparent Container does NOT contain a Section Header, its "isLayoutContainer" must be set to TRUE. If instead a Section Header will be given to this group, it should be done as follows:
   1. Add a Section Header UI Element inside the Transparent Container. The Section Header's "Level" property should be set to "header4","header5", or "header6". Select the Transparent Container's property "LabeledBy" to be the ID of the Section Header. If a Transparent Container is labeled by a Section Header the property "isLayoutContainer" must be set to false.
3. All input fields must be given a "Label" and set the LabelFor property to the ID of the associated input.
4. All labels must be associated with a UI Element by setting the property "LabelFor."
5. Always create column headers for every visible column in a table.
6. All images that do NOT convey important information, such as horizontal rules, spacers, must have their "isDecorative" property set to True.
7. All images that DO convey important information must have short descriptive text in the ToolTip property.
8. Tooltips should never repeat Label text, they should only be used to add more information. See guidelines for alt text.
9. Never nest tables, for instance, never set a table popin's content to be another table.
10. Never nest trays, groups, or tabs, or other grouping containers, except Transparent Containers.
11. Periodically run the the automated "complete object" check as part of your development process to find and fix accessibility problems.
12. Melting Group pattern: use to remove input hints from the tab chain (see ZV_TEST, View V_CREATE_POS). ADD PICTURE.
13. Instead of using the PageHeader UI element, every page must have a page title made with a FormattedTextView, coded using the <h1> tag.
14. All Search Helps must be custom coded. The standard search help is neither accessible, nor usable, nor pretty.
15. The property "rowSelectable" of table UI elements should either have the value 'X' or it should be bound to the context. If you wish to ensure that the table cannot be selected or is to function merely as a display table, set the property "selectionMode" to the value "none" instead, which is preferred for usability reasons.
16. Screen changes: make all dynamic changes below the cursor, or move the cursor by changing the focused element, or announce that something has changed above the cursor.
17. Use the OTR to store all UI-related text.
18. Do not set actions to take a user off the page from a radio button or drop down elements without a go button.
19. To skip over Hint text, like (mm/dd/yy) after a date field, set the set the “design” property of the UI Element to “groupTitle”.

...

1. TextView versus InputField-ReadOnly
   • For text fields that will always be read-only, developers should use TextView (not InputField-ReadOnly).
   • For text fields that will sometimes be editable but under other conditions read-only (e.g. HSA Details screen), developers would prefer to use InputField-ReadOnly.
   • For screens that have a mix of field types, group things accordingly.   Keep TextView together or InputFields together for better visual user experience.  Try not to alternate or mix types.
2. For confirmation screens and button order, follow the SAP standard of ordering the buttons in order of "Yes/No".
3. For pop-ups that contain variable length texts ..... develop your own custom view.
4. For Search Helps, see rule Accessibility rule #14 above.
5. Layout choices:  Matrix, Flow, Grid, or Row....   Matrix and Grid seem to be the leade
6. UI Element formatting - details on formatting click here
7. When launched, WDA applications should launch in a new, chrome-less window.  Browsers' Back button has been disabled SAP.
   • Need to verify with SAP any plans to enable Back button
   • Need to re-visit when apps are incorporated into SAP Portal.
   • Replace the "Home" link at the top of each WDA application page.  Use the more accurate text "Close" rather than "Home".
     • The Close link should be positioned in upper right hand corner of the app, just after the Help link.

1. #* #** Separate Help and Close links by setting vGutter property in each to medium.
2. Tables and ALV handling (findings based on NW 7.02)
   • See Carolyn's notes on Automatically calculating totals, Javascript errors, multiple UI elements in single cell, focus within dropdown list.

...