...
- The root container acts as a transparent container and since it is the root container, does not need a label. Therefore adding a transparent container under the root container only adds another layer of html, but does not make the application more accessible.
- This rule comes straight from the SAP Accessibility guidelines. The header4, header5 and header6 properties create semantic html, respectively <h2>,<h3> and <h4> tags.
- This rule comes straight from the SAP Accessibility guidelines. By giving each input a label, people using assistive technology will hear the input's label as a description.
- This rule allows SAP assistive code to associate a label with other UI elements or groups of elements.
- Not sure what this rule does.
- If an image does not have isDecorative set to true, WebDynpro will try to create an alt attribute that assistive technology will then read. Non informative images should not be announced with an alt tag.
- The tooltip property is what WebDynpro code uses to create the various alt and title tag content for assistive technology to read.
- If a tooltip repeats the label text, the code will be "read" twice by assistive technology and thereby annoy or confuse the user.
- Nested tables confuse assistive technology because assistive technology trys to gather semantic information (labels of table cells) from tables.
- Nesting grouping containers creates nested tables. See #9 for explanation of why this is bad.
- This rule is self-explanatory.
- This pattern essentially allows the developer to create two labels, one for a group of elements that includes an input, another for the input itself.
- The pageHeader UI element SHOULD create an <h1> tag, which is the topmost header tag on a page. It does not. If subsequent versions of WebDynpro pageHeader UI elements do create <h1> tags, this rules should be changed.
- This rule is self-explanatory.
- In the SAP GUI, tables have select buttons in the left column. When rendered by Webdynpro, these "buttons" consistently confuse non SAP-GUI users. Therefore the preferred method of making a row selectable is to make one of the first two table cells contain data with a link. Clicking on that link would allow the user to do something with that row.
- If the screen changes above the cursor, assistive technology may not "hear" the change and notify the user that a change occurred.
- The OTR tables allow for translations and the ability of non-programmers with GUI access to change text.
- The act of reading a drop-down "go menu" with assistive technology will fire the menu's Javascript and take the user away from the page before they have heard the other options (they will never be able to hear the other options).