Page History

...

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 tooltips
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 funpretty.

Unit Testing Procedures

1. Check tab chain (explain).
2.  

...