30cc87a5__ications_and_Operating_Systems_on__scope_of_support_provided_
[Criteria] 1194.21(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. [Supporting Features] Product has been developed to meet this standard subject to the remarks on the right
The product was tested for: Reading of screen text Screen elements under magnification retain readibility and are recognizable AT product successfully tracks cursor focus Exceptions: Workspace main search fields have no associated label element or title attribute to signal to assistive technology the purpose of the field. It does however have a defaulted value which describes its purpose, (for example, Search Workspace, Search Application and so on). This issue is tracked with Oracle bugs 9733663, 9738655. Form fields in some multi-row edit pages have no associated label element or title attribute to signal to assistive technology the purpose of the field. Workaround: Use the single row view edit for the specific component. This issue is tracked with Oracle bug 8243270. Some form items do have a label tag, but it is empty. This only affects a minority of items in the Application Express development environment. This issue is tracked with Oracle bug 8243264. Some Form Elements in Interactive report region dialogs contain duplicate descriptive text. These contain many Ajax-based dialogs that are used to manage information about those components. Although all form elements have descriptive text (either a corresponding label tag or title attribute), some text is duplicated for similar elements in a few dialogs. This issue is tracked with Oracle bug 7027400.