...
- Incorrect number of columns is announced by screen reader for UI Element RowRepeater that uses complex layout such as nested TransparentContainers.
- UI Element table: in some cases screen reader announces the row as selectable even though it cannot be selected.
- UI Element ToggleButton anounced only as ""Button"" by screen reader.
- For HorizontalContextualPanel UI Element, no level information is announced for the 2nd level row.
- For some semantic colors of TextView UI Element there is no speech output defined.
- The disabled state is not announced for a UI Toolbar element.
- InputField UI Element with F4 Help is announced as ""combo box"" instead of ""Edit"".
- For a number of UI Elements, the screen reader either repeats element information twice or makes a second announcement that differs from the first (correct) announcement when the UI Element gets the keyboard focus:
- Groups: Sometimes ""Table"" is announced additionally at the begin of a Group and ""cell"" at the end.
- Images: Screen reader announces ""Graphic"" additionally.
- Radiobutton-Groups: ""0 Items"" is announced additionally even if the group has items.
- The ""Browse"" Button of a FileUpload UI Element is not announced at all.
- In some rare cases, instead of announcing the attributes of UI Element actually focused, the attributes of the UI Element container or the preceding UI Element are announced.
- When navigating to the items of the UI Element ItemListBox with MultiSelection via down arrow key the items sometimes are also automatically selected.
- Navigation to the first empty/blank entry in the dropdown of an Dropdown UI Element is not possible with the keyboard.
- While navigating to a different Tab within UI Element Tab Strip, visible focus gets lost.
- No visual indication for selected top level menu item.
- If Windows runs in High Contrast theme sometimes the focus is not visible when using the Web Dynpro High Contrast theme.
- Focus is not restored on Row Selectors in certain cases for UI Element Table when a selection is made. Instead, other elements are focused (e.g a UI Element Button below the Table)."
- The following UI Elements are rated as not accessible:
- Gantt
- Network
- BusinessGraphics
- GeoMap
Application Help
- <tbd>
Unit Testing Procedures
- A copy of JAWS screen reader software is being installer installed in the W92 QA test lab for use by WDA developers. This will allow basic unit testing of individual WDA components and screens. It is not a replacement for full Accessibility testing by the IS&T Accessibility team.
...
- Trays are strongly discouraged because they can confuse users. Programmatically hide elements instead.
- 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.
- For confirmation screens and button order, follow the SAP standard of ordering the buttons in order of "Yes/No".
- For pop-ups that contain variable length texts .....<tbd>
- For search helps ..... <tbd>