Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
1194.22(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images that convey information have meaningful alternative text using ALT.
- Images that are decorative are marked up using ALT=”” or CSS background images.
- Data shown in Flash based charts is also available in an alternative textual form (e.g. a data table) when running in Screen Reader Mode.
- Data tables specify SUMMARY.
- Titles for Pages are provided.
Exceptions: Affecting the Application Express Development Environment: - See remarks in 1194.21(d).
- 'Next' and 'Previous' style navigation buttons, used to allow navigation across related components in the development environment sometimes have button text of just '>' and '<'. This is insufficient in clearly describing the purpose of the button. This issue is tracked with Oracle bug 16322302.
|
1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Product has been developed to conform to this standard subject to the remarks on the right. | The product has no multimedia. |
1194.22(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Information conveyed by color or font styles is available in alternative formats, such as shape and text.
|
1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Style sheets are used only to change the layout and presentation of the screen
|
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. | Product has been developed to conform to this standard subject to the remarks on the right. | The product contains no server side image maps. |
1194.22(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | Product has been developed to conform to this standard subject to the remarks on the right. | The product contains no client side image maps. |
1194.22(g) Row and column headers shall be identified for data tables. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Table usage – only data tables, as opposed to layout tables, use table elements of TH and table attributes of SUMMARY, SCOPE and HEADERS.
- Each column of a data table is marked up with TH, and SCOPE=”COL” or uses ID and HEADERS associations
Exceptions: Affecting Custom Applications: - The Single Row View of Interactive Report Regions contains a table with no SUMMARY text, and no header / cell associations. This issue is tracked with Oracle bug 15864568.
Affecting Development Environment, Websheet Runtime and Custom Applications: - All native report regions of Application Express currently have no declarative way of defining row headers. This issue is tracked with Oracle bug 14198644.
|
1194.22(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Complex data tables, such as those used by Interactive Report Regions with a 'Control Break' defined where multiple headers are required, use the ID and HEADERS attributes.
|
1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Meaningful title on native components using FRAMEs and IFRAMEs
|
1194.22(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
|
1194.22(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. | Product has been developed to conform to this standard subject to the remarks on the right. | Text–only pages are not necessary because pages have been coded to meet other applicable standards, to the extent indicated. |
1194.22(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content generated by JavaScript has been coded to meet other applicable standards, to the extent indicated.
Exceptions: Affecting Development Environment, Websheet Runtime and Custom Applications: - The dialogs used in Interactive Report Regions for common interactions such as applying filters, saving reports, adding highlights etc., could be made more user friendly for a screen reader user. Please see the 'Accessing Interactive Reports Using JAWS' section of 'Appendix E, Accessibility in Oracle Application Express' in the Oracle Application Express User Guide for an example of how to interact with one of these dialogs. This issue is tracked with Oracle bug 12717028.
- The column headings in Interactive Report Regions used to sort, hide, filter, group or show help about data are not accessible for a screen reader user. This functionality, with the exception of showing help, is available via the interactive report 'Actions' menu. Please see the 'Accessibility in Oracle Application Express' appendix of the Oracle Application Express User Guide for details of how to access the 'Actions menu with keyboard only and JAWS'. This issue is tracked with Oracle bug 7655582.
|
1194.22(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Links are provided for downloading non-standard applets or plug-ins, such as the 'Flash' plug-in required by the Chart components in Application Express.
|
1194.22(n) When electronic forms are designed to be completed on-line, 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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL and TITLE.
Exceptions: - See the Remarks in 1194.21(l)
|
1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Structure and hierarchy is marked up with Header elements.
|
1194.22(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content that automatically updates, or time limits, can be adjusted by the user.
Exceptions: Affecting Development Environment and Websheet Runtime: - The Oracle Database Cloud Service has different time-outs in effect, that cannot be extended by an end-user. The Maximum Idle Time is 30 minutes and the Maximum Session Time is 480 minutes (8 hours). When either of these time-outs are reached, the session will silently expire and the next time the user tries to perform an action, they will be redirected to the login page and any unsaved changes may be lost. This issue is tracked with Oracle bug 14616880.
Affecting Development Environment, Websheet Runtime and Custom Applications: - Some Application Express authentication schemes (including authentication into the Application Express development environment itself), are designed to temporarily lock an account after a failed login attempt, for a period of time long enough to deter brute-force attacks. For the end user, this displays as an error notification in a Heading (H2) tag, stating 'Invalid Login Credentials. Please wait x seconds to login again.', where the 'x' will count down until the user is able to re-attempt login. This count down is the timed element, and a screen reader user is not notified when this count down concludes, so must currently keep checking the notification heading to see when it has completed. This issue is tracked with Oracle bug 14463181.
|