Criteria | Conformance Level | Remarks and Explanations |
|---|
| 1.1.1 Non-text Content (Level A) | Partially Supports | The product and documentation were 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
- Controls have an associated name
- Non-text characters are not used or have meaningful alternative text
Exceptions: Affecting Applications: - Report columns of type 'Display Image' have limited support for defining ALT text. This issue is tracked with Oracle bug 33351947.
Affecting Development Environment: - On the Shared Component page, there are images displayed next to the corresponding page sections. These images are unlabelled span elements in the markup, and are not perceivable to users of Assistive Technologies. This issue is tracked with Oracle bug 33636441.
- On the workspace home page, there is an unlabelled icon under the 'Available Updates' section. This issue is tracked with Oracle bug 33593212.
Affecting Applications and Development Environment: - Interactive Report and Interactive Grid report settings (used to display current report settings to the end user) contain unlabelled images. This issue is tracked with Oracle bug 33591098.
|
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Supports | The product and documentation were tested for: - There is no pre-recorded audio only or video only content.
|
| 1.2.2 Captions (Prerecorded) (Level A) | Partially Supports | The product and documentation were tested for: - No Pre-recorded video content is being used.
Exceptions: Affecting Documentation: - Videos on the Application Express YouTube channel are missing closed captions. This issue is tracked with Oracle bug 29370906.
|
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | The product and documentation were tested for: - There is no pre-recorded video
|
| 1.2.4 Captions (Live) (Level AA) | Supports | The product and documentation were tested for: - No live audio content in video is being used
|
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | The product and documentation were tested for: - There is no pre-recorded video
|
| 1.3.1 Info and Relationships (Level A) | Partially Supports | The product and documentation were tested for: - User interface component labels are associated with the fields they are labeling
- Headings are encoded with HTML heading tags
- List markup is used for marking up lists
- Table markup is used for marking up data tables, including row and column headers and table summaries where appropriate
- Data tables specify ARIA-LABEL or SUMMARY
- Layout tables use appropriate markup
- Groups of components are marked up with their description
- Style sheets are used only to change the layout and presentation on the screen
Exceptions: Affecting Development Environment: - The 'Quick Edit' and 'Live Template Options' features, available as a developer of an application via the developer toolbar, are inaccessible to screen readers user. You can use quick edit with keyboard-alone, where the cursor keys allow you to navigate through the runtime page and select the page component you wish to edit, however these components do not have any accessible label, meaning screen readers will not be able to identify them. Because Live Template Options is available via the Quick Edit feature, then this also means this is not accessible to screen reader users. Screen readers users will need to navigate to components to edit via the App Builder in the traditional way, so without the convenience of being able to go straight to a component to edit from the runtime. Also Template Options will need to be edited in the App Builder and saved, and then the page refreshed to see the effect of the change in the runtime, so without the convenience of the Live Template Option feature. This issue is tracked with Oracle bug 25153940.
- Summary style pages, typically shown at the end of wizards in APEX contain summary information that is difficult to understand with a screen reader. This issue is tracked with Oracle bug 31566352.
- Search results pages for the APEX Advisor, and for Application Search, are difficult to navigate with a screen reader. This issue is tracked with Oracle bug 31972162.
- In Page Designer, properties using the switch control type have duplicate labels. This issue is tracked with Oracle bug 33942967.
- Some report pages are missing row headers. This issue is tracked with Oracle bug 33925337.
- In the create list wizard on the page used to define list entries, the input elements are displayed in a grid format, however the markup used is not consistent with this, making it diffucult to navigate with a screen reader. This issue is tracked with Oracle bug 33637363.
Affecting Development Environment and Applications: - In the Popup LOV item component, when displaying multiple columns in the search results, although the results are announced as a data table, the table is missing an accessible label. This issue is tracked with Oracle bug 30375933.
- APEX provides two main ways in which page items can be rendered as non-editable, firstly the 'Display Only' item type, and secondly any item type whose 'Read-only' condition evaluates to true. For both of these scenarios, APEX renders a SPAN visually displaying the value of the item. Because this is not an HTML form element, this information could be missed by users of Assistive Technology. This issue is tracked with Oracle bug 31200377.
- LABEL elements for page items in APEX are always rendered, irrespective of which item type is used. This is fine for page items that use form elements such as text fields, select lists or textareas, however this is incorrect use of HTML for other item types (for example radio groups, checkboxes). This issue is tracked with Oracle bug 31205979.
- In Interactive Grid regions, inconsistent row counts are announced to screen readers when pagination type is 'Scroll', 'Show Total Row Count' is on, and there are more rows than initially displayed. This issue is tracked with Oracle bug 32075361.
- With the Color Picker item type, if Display As is set to 'Color-only Popup', the button rendered does not have a label. This issue is tracked with Oracle bug 33270205.
|
| 1.3.2 Meaningful Sequence(Level A) | Supports | The product and documentation were tested for: - The sequence of elements in the DOM matches a logical reading sequence
|
| 1.3.3 Sensory Characteristics(Level A) | Supports | The product and documentation were tested for: - Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
|
| 1.3.4 Orientation (Level AA) | Supports | The product and documentation were tested for: - Text is displayed in both device orientations without loss of functionality or visibility of the text.
|
| 1.3.5 Identify Input Purpose (Level AA) | Partially Supports | The product was tested for: - Text fields which collect information about the user contain the appropriate autocomplete content attribute.
- The autocomplete attribute is defined in the 'Custom Attributes' page item property in APEX.
The documentation was tested for: - The documentation does not allow for input or changes to data.
Exceptions: Affecting Development Environment and Applications: - The autocomplete attribute is missing from the pages in APEX that collect information about the user. This issue is tracked with Oracle bug 31978520.
|
| 1.4.1 Use of Color(Level A) | Partially Supports | The product and documentation were tested for: - Information conveyed by color is available in alternative formats, such as shape, text, font weight
- Information conveyed by color has a contrast ratio of at least 3:1
Exceptions: Affecting Applications: - For Polygon layers, the map region allows to visualize information with the fill color for the polygons on the map - which gives end users a 'thematic map'. Polygons can be filled with different colors, but there's no feature to have patterned fill, if color is not sufficient. This issue is tracked with Oracle bug 32463607. As a workaround, the 'Extruded Polygons' can be used instead of simple polygons. The map will become a 3D map, and the attribute is being visualized by the height of the extruded polygon - so color is not the only method to convey the information.
Affecting Development Environment: - Selection of environment banner color relies on color alone for selection. This issue is tracked with Oracle bug 33806174.
|
| 1.4.2 Audio Control(Level A) | Supports | The product and documentation were tested for: - No automatically playing audio is used
|
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | The product and documentation were tested for: - Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
- Other text and images of text have a contrast ratio of at least 4.5:1
Exceptions: Affecting Documentation: - The 'JavaScript API Reference' chapter of the documentation has text that does not meet the minimum contrast requirements. This issue is tracked with Oracle bug 29370357.
Affecting Applications and Development Environment: -
In the Chart component, when a chart shows the label value next to the chart data, this can sometimes cause colour contrast issues, where for example the text overlaps part of the chart data section, and the text colour with the chart data colour does not meet contrast requirements. This issue is tracked with Oracle bug 34099910. |
| 1.4.4 Resize text(Level AA) | Partially Supports | The product and documentation were tested for: - Text can be resized up to 200% without loss of content or functionality
Exceptions: Affecting Applications and Development Environment: - For a Popup LOV item with 'Multiple Values' on, when zoomed to 200% it becomes impossible to delete the selected value. This issue is tracked with Oracle bug 33494864. A keyboard user can workaround this issue by hitting the LEFT cursor key when the input has focus, then Backspace to delete the selected value.
|
| 1.4.5 Images of Text(Level AA) | Supports | The product and documentation were tested for: - Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
|
| 1.4.10 Reflow (Level AA) | Partially Supports | The product and documentation were tested for: - Text information reflows so that only one direction of scrolling is required while at 400% zoom.
- Content that requires two-dimensional layout only presents scroll bars in the component used
to present the two-dimensional content. Exceptions: Affecting Development Environment: - Horizontal scroll is required throughout the development environment, when zoomed at 400%. This issue is tracked with Oracle bug 31964090.
Affecting Applications: - Reflow issues with the Card region type, when the following attributes are defined: Template=Cards Container, Layout=Horizontal (Row), Title and Subtitle: Displayed, Badge Column: Selected. This issue is tracked with Oracle bug 33875869.
|
| 1.4.11 Non-text Contrast (Level AA) | Supports | The product and documentation were tested for: - Non-text items have a contrast ratio of at least 3:1
|
| 1.4.12 Text Spacing (Level AA) | Partially Supports | The product and documentation were tested for: - When the following attributes and no others are modified there is no loss in functionality or content:
- Line height (line spacing) to at least 1.5 times the font size
- Spacing following paragraphs to at least 2 times the font size
- Letter spacing (tracking) to at least 0.12 times the font size
- Word spacing to at least 0.16 times the font size
Exceptions: Affecting Development Environment: - Editing in our code editors becomes erratic (unexpected cursor insertion and code selection, misalignment of visual cursor and text inserted). This issue is tracked with Oracle bug 33855415.
|
| 1.4.13 Content on Hover or Focus (Level AA) | Partially Supports | The product and documentation were tested for: - Dismissable -The content can be dismissed without moving the pointer or keyboard focus
- Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
- Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: Affecting Development Environment and Applications: - Tooltips used throughout APEX fail the 'hoverable' test, because the tooltip disappears if you move the mouse over it. This issue is tracked with Oracle bug 31888900.
|
| 2.1.1 Keyboard(Level A) | Partially Supports | The product and documentation were tested for: - Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
- Proper operation of unique keystrokes and access keys, including those listed in the product documentation
- The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)
Exceptions: Affecting Applications: - When using the Universal Theme, a developer has two choices for the app's navigation menu system, 'Top', and 'Side'. When using 'Side' navigation, the app's navigation will appear in a tree structure on the side of the page. In addition, the end user has the option to expand or collapse the navigation menu, using a toggle button on the page. This expand / collapse functionality has two further developer options, 'Hidden' (the default) where the collapsed state actually hides the navigation menu completely, and 'Icon', where the navigation menu just collapses down to icons. When using the 'Icon' option, the icons cannot receive keyboard focus. This issue is tracked with Oracle bug 31112489. A keyboard user can workaround this by expanding the navigation menu, to be able to interact with it.
- In the Map region, spatial objects drawn on the map, are currently not accessible with the keyboard. It's possible to hover over these with the mouse and get more information about them, however this is not possible with the keyboard. The only workaround currently available to developers is to create alternative content on the page that conveys the same information, that is keyboard accessible (for example a report). This issue is tracked with Oracle bug 32463573.
Affecting the Development Environment: -
On the Team Development homepage, when the Issues Interactive Grid is in 'Card View', you can tab to a row and press the SPACE bar to select the row. However you are unable to de-select the row using the SPACE bar. This issue is tracked with Oracle bug 30877825. To workaround this issue, use Standard grid view, which does support selection and de-selection with the SPACE bar. Affecting Development Environment and Applications: - Although icon buttons used in our development environment and in Applications have an accessible name (using ARIA-LABEL), they also have a TITLE attribute which displays to mouse users on hover, however keyboard users have no way of perceiving this text. This issue is tracked with Oracle bug 28293186
- In the Faceted Search region component, users have no easy way to navigate with keyboard from the facet region to the results region, other than tabbing through all the facet controls. This issue is tracked with Oracle bug 30380719.
- The Region Display Selector region renders tabs based on the regions on a page. The keyboard interaction is not properly initialized immediately after page load, resulting in every tab being a tab stop for keyboard users. As soon as the user selects a tab using cursor keys, the correct keyboard interaction is added and the tabs function as a single tab stop, as expected. This issue is tracked with Oracle bug 31971687.
- Modal pages that submit and reload the modal page can lose focus. This issue is tracked with Oracle bug 33309025.
- Markdown editor does not keep text selection when navigating to the toolbar by keyboard (for example to bold selected text). This issue is tracked with Oracle bug 33824433.
|
| 2.1.2 No Keyboard Trap (Level A) | Supports | The product and documentation were tested for: - Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
|
| 2.1.4 Character Key Shortcuts (Level A) | Supports | The product and documentation were tested for: - Single character keyboard shortcuts are only active when that component has focus.
|
| 2.2.1 Timing Adjustable(Level A) | Supports | The product and documentation were tested for: - Time limits in the product can be turned off before they are encountered
- Time limits are not used within the documentation
|
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | The product and documentation were tested for: - There is no moving, blinking or scrolling content
|
| 2.3.1 Three Flashes or Below Threshold(Level A) | Supports | The product and documentation were tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
|
| 2.4.1 Bypass Blocks(Level A) | Partially Supports | The product and documentation were tested for: - A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
- Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
- WAI-ARIA Landmark elements are used outside of repetitive navigation links
Exceptions: Affecting Applications: - In Universal Theme, we make some use of landmark regions (for example for the main content, and page footer), however we do not make use of landmark regions in the native region templates. This issue is tracked with Oracle bug 31972231.
- In Universal Theme, page structure needs to be better identified with landmarks. This issue is tracked with Oracle bug 32102597.
- When creating a Faceted Search page from the wizard, the generated page can contain two regions with the same label 'Search'. This issue is tracked with Oracle bug 33385817. To workaround this issue, the Faceted Search region can be given a different title, for example 'Filters'.
- In Universal Theme, the Navigation Bar and Top Navigation Tabs list templates are missing a navigation landmark. This issue is tracked with Oracle bug 33172617 and 33098987.
Affecting Development Environment: - There are no 'Skip to Main Content' links implemented for the Development Environment. This issue is tracked with Oracle bug 27782291.
- Complementary landmarks are not uniquely labelled on pages that have both a sidebar region, and a code editor. This issue is tracked with Oracle bug 33847593.
- Breadcrumbs are defined just as links and are not contained within a navigation landmark. This issue is tracked with Oracle bug 32930834.
Affecting Development Environment and Applications: - Classic report regions need to better identify their contents with landmarks. This issue is tracked with Oracle bug 32109673.
- Regions would benefit from landmarks to identify where items in the region are, and where any sub-regions in the region are. This issue is tracked with Oracle bug 34041752.
|
| 2.4.2 Page Titled(Level A) | Supports | The product and documentation were tested for: - Pages have a meaningful title specified in the TITLE element
|
| 2.4.3 Focus Order(Level A) | Partially Supports | The product and documentation were tested for: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
Exceptions: Affecting Development Environment and Applications: - Interactive Grid focus issues when window loses focus while editing. If the user is editing a field with a popup (eg Popup LOV, Color Picker), if they navigate away from the page to another window, then switch back, focus is taken to a hidden element on the page and the page may also be scrolled down to near the end. This issue is tracked with Oracle bug 34017628.
- With a Faceted Search region, after hiding a facet focus goes to the More Filters button, which is not the most logical place to put focus. This issue is tracked with Oracle bug 33859795.
|
| 2.4.4 Link Purpose (In Context)(Level A) | Partially Supports | The product and documentation were tested for: - The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose
Exceptions: Affecting Applications: - Page Templates in Universal Theme can contain a 'Move to Top' link that takes the user back to the top of the page. This link is incorrectly labelled. This issue is tracked with Oracle bug 33592003.
Affecting the Development Environment: - The Gallery page contains links that open a new window, and no advance warning is given of this. This issue is tracked with Oracle bug 33416172.
- In Instance Administration on the Security page, the links in the 'Development Environment Authentication Schemes' report have no link text. This issue is tracked with Oracle bug 33845515.
|
| 2.4.5 Multiple Ways(Level AA) | Supports | The product was tested for: - Pages are fully inter-linked to each other
- Pages can be found using the provided "search" function
- Page contains controls that enable reaching all pages
The documentation was tested for: - Pages can be found using the provided "Search" function
- Pages are in a site table of contents
|
| 2.4.6 Headings and Labels(Level AA) | Partially Supports | The product and documentation were tested for: - Headers describe the topic or purpose of the content below them
- Labels describe the purpose of the associated field
Exceptions: Affecting Development Environment: - In Page Designer (where developers build and edit pages in APEX), the current heading structure needs improving to improve usability for users of Assistive Technology. This issue is tracked with Oracle bug 27782249.
- One of the administration pages for the Attribute Dictionary in APEX contains a 'Check All' style checkbox in the report's column header, which is missing label text. This issue is tracked with Oracle bug 20310474.
- In the App Builder, on the Static File Editor page, there is an empty H1 element. This issue is tracked with Oracle bug 33401741.
- In the Create App wizard, there are headings to indicate the application type that could be improved by programatically associating the description to the heading as well. This issue is tracked with Oracle bug 33566693.
- Poor heading structure throughout the development environment. This issue is tracked with Oracle bug 31889333.
Affecting Applications and Development Environment: - In the Interactive Grid region component, some form fields rendered have either no label, or labels that require improvement. This issue is tracked with Oracle bug 25153552.
- Native checkbox and radio group item types contain duplicate labelling. This issue is tracked with Oracle bug 27810346.
- In the Faceted Search region component, the facet chart button should not be part of the facet heading. This issue is tracked with Oracle bug 32867611.
- In APEX, region title text is sometimes used as the landmark label. If HTML is used in the region title, this can result in bad landmark region labels. This issue is tracked with Oracle bug 34002311. To workaround this in applications, avoid using markup in region titles.
- In the Faceted Search region component, a facet's expand / collapse button has a duplicate label. This issue is tracked with Oracle bug 33859790.
- Interactive Report and Interactive Grid report settings (used to display current report settings to the end user) contain poorly labelled controls. This issue is tracked with Oracle bug 33591098.
|
| 2.4.7 Focus Visible(Level AA) | Partially Supports | The product and documentation were tested for: - Visual indication of the location of the focus
Exceptions: Affecting Development Environment and Applications: - In the Interactive Grid region component, some interactive controls do not show focus. This issue is tracked with Oracle bug 25153460.
Affecting Applications: - The Tab Container region template which is used to render regions on a page as tabs, contains a 'tablist' element that does not show keyboard focus. This issue is tracked with Oracle bug 30515581.
|
| 2.5.1 Pointer Gestures (Level A) | Supports | The product and documentation were tested for: - Multipoint or path-based gesture actions can be completed using a different input modality.
|
| 2.5.2 Pointer Cancellation (Level A) | Supports | The product and documentation were tested for: - When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function
- When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion
- When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event
|
| 2.5.3 Label in Name (Level A) | Supports | The product and documentation were tested for: - User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.
|
| 2.5.4 Motion Actuation (Level A) | Supports | The product and documentation were tested for: - There are no functions that require motion of the device.
|
| 3.1.1 Language of Page(Level A) | Supports | The product and documentation were tested for: - Properly set lang attribute for each page
|
| 3.1.2 Language of Parts(Level AA) | Supports | The product and documentation were tested for: - Proper use of lang attribute for text passages that are in a different language than that of the page
|
| 3.2.1 On Focus(Level A) | Supports | The product and documentation were tested for: - When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
|
| 3.2.2 On Input(Level A) | Partially Supports | The product and documentation were tested for: - Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
- In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
Exceptions: Affecting Development Environment: Affecting Applications and Development Environment: - Menus have a toggle menu item type, allowing binary selection of a value. When activating such an item type with keyboard, focus is lost. This issue is tracked with Oracle bug 33859862.
- In a Faceted Search region, focus is lost when closing a facet's chart dialog. This issue is tracked with Oracle bug 33844689.
|
| 3.2.3 Consistent Navigation(Level AA) | Supports | The product and documentation were tested for: - Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time
|
| 3.2.4 Consistent Identification(Level AA) | Supports | The product and documentation were tested for: - Images and controls are used and identified consistently throughout the product
- Images and controls are used and identified consistently throughout the documentation
|
| 3.3.1 Error Identification(Level A) | Partially Supports | The product was tested for: - When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
The documentation was tested for: - The documentation does not allow for input or changes to data
Exceptions: Affecting Development Environment and Applications: - Errors displayed in Interactive Report dialogs (for example when attempting to save a Filter with an empty 'Expression' value) just display a red border around the field in error, with no text explaining what the error is. This issue is tracked with Oracle bug 20697217.
- When defining validations in APEX, the developer has the choice to define the 'Display Location' for the associated error message. This can either be 'Inline with Field and in Notification' (default), 'Inline with Field', 'Inline in Notification' or 'On Error Page'. When using the 'Inline with Field' location (where the error message will just appear next to the item with the error), a screen reader user is not notified that the error has occurred. So after submitting the form, the user would just stay on the same page, and would have to go back through the form fields and listen for details of any items with errors (which does with a screen reader because the error message is programmatically associated with the relevant page item). This issue is tracked with Oracle bug 31205839. To workaround this issue, developers should select any location including the 'Notification' position.
|
| 3.3.2 Labels or Instructions (Level A) | Supports | The product was tested for: - Labels or instructions are provided when the product requires user input
The documentation was tested for: - Content does not require user input
|
| 3.3.3 Error Suggestion (Level AA) | Supports | The product was tested for: - Where suggestions for fixing an input error are known, they are provided to the user
The documentation was tested for: - Content does not require user input
|
| 3.3.4 Error Prevention (Legal, Financial, Data)(Level AA) | Supports | The product was tested for: - Data is checked for input errors with an opportunity for the user to correct them
- When using the component creation wizards, data can be reviewed, corrected, and confirmed by the user before they are finalized
The documentation was tested for: - The documentation does not require user input that modifies user controllable data
|
| 4.1.1 Parsing(Level A) | Partially Supports | The product and documentation were tested for: - Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
Exceptions: Affecting Applications: - Interactive Report regions defined with headings fixed to either 'Page' or 'Region' are rendered with duplicate IDs for the column header elements. This issue is tracked with Oracle bug 33865529.
|
| 4.1.2 Name, Role, Value (Level A) | Partially Supports | The product and documentation were tested for: - HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’ or 'invalid'
- Custom controls have appropriate roles specified using the role attribute
- Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
- Custom controls have a meaningful programatically exposed name
- Frames have a meaningful title specified in the title attribute
Exceptions: Affecting Applications: - The Tab Container region template which is used to render regions on a page as tabs just renders as a standard HTML list, and does not follow the Tabs design pattern. This issue is tracked with Oracle bug 30515581.
- In Universal Theme, the 'Collapsible' region template does not clearly indicate its expanded state. This issue is tracked with Oracle bug 32532058.
- In Universal Theme, when using 'Side' navigation, if the menu is in a collapsed state, the menu no longer works as expected. This issue is tracked with Oracle bug 32086482. To workaround this issue, the menu can be expanded.
- In Universal Theme, all the current sublist entries in the Navigation Bar list template are missing aria-current. This issue is tracked with Oracle bug 33172617.
Affecting Development Environment: - Currently in the Property Editor, the display groups are marked up as DIV elements that are focusable with the keyboard. When focused, users can navigate between display groups with the Up and Down arrow keys, which aids keyboard support of the Property Editor. However, when the DIV is focused, screen readers can announce the display group title twice, and in addition can fail to announce the ARIA expanded state when the display group first gets focus (however, it is announced upon expand or collapse). This issue is tracked with Oracle bug 32087719.
- In Page Designer, it is possible to edit multiple components at the same time, however when using a screen reader, there is no indication that multiple items are selected. This issue is tracked with Oracle bug 29283988.
- In Page Designer, the splitter controls used to manage layout are poorly labelled and are missing ARIA-CONTROLS to point to relevant page area. This issue is tracked with Oracle bug 20693603.
- When using Spotlight search with JAWS, the search output can be confusing and sometimes duplicated. This issue is tracked with Oracle bug 31972027.
- The Wizard Selection plugin, used in our development environment in creation wizards (for example to select the page type in the create page wizard), is difficult to use with a screen reader. This issue is tracked with Oracle bug 31973124.
- In Page Designer, the tabs used to the different page elements (eg Rendering, Dynamic Actions, Processing etc) use aria-expanded, which is not valid for tabs. This issue is tracked with Oracle bug 32103943.
- Incorrect shortcut text conveyed to screen readers for accessing application search. This issue is tracked with Oracle bug 32087187.
- When navigating through our wizards that use chained modal pages, screen readers can sometimes break out of the dialog and access the underlying page content. This issue is tracked with Oracle bugs 33161303 and 32929901.
- The breadcrumbs used throughout the development environment are marked up as a list of links, but miss key markup that would make them easier to use with screen readers, for example a labelled navigation landmark and aria-current to show the current page. This issue is tracked with Oracle bug 32930834.
- Classic report region current column sort not pereivable with Assistive Technologies. This issue is tracked with Oracle bug 32079384.
- Success messages that are dynamically displayed (as opposed to when during a full page load), are announced twice. This issue is tracked with Oracle bug 33875951.
- In the Create Page wizard, when going through the 'Legacy Pages' path and on the 'Navigation Menu' page, there is a select list to define the 'Parent Navigation Meny Entry'. This select list can contain disabled options, which are not perceivable to screen reader users. This issue is tracked with Oracle bug 33997884.
- Code Editors when rendered in read-only mode appear editable to screen reader users. This issue is tracked with Oracle bug 33856322.
- In Page Designer, as tooltips are displayed a corresponding hidden DIV is added to the bottom of the DOM. This are not visible, however are perceivable with a screen reader and worsen the user experience. This issue is tracked with Oracle bug 33839482.
- In Page Designer in the Link Builder, the Set Items property type uses an incorrect role. This issue is tracked with Oracle bug 33638611.
- In the main menu bar, the current page is not programatically defined. This issue is tracked with Oracle bug 33571461.
- When deleting an application, which can take some time depending on the size of the application, a screen reader user is given no notification that anything is being processed. This issue is tracked with Oracle bug 34026939.
Affecting Development Environment and Applications: - When logging into a workspace, or an Application using an appropriate authentication scheme, if the instance is set to have a delay for failed login attempts (setting in Instance Admin > Security > General Settings > Delay after failed login attempts in Seconds), and the user enters incorrect login details, a notification displays that includes a count down of the number of seconds before they can attempt logging in again. This count down is not announced properly to screen reader users. This issue is tracked with Oracle bug 29348302.
- The List View of the native Calendar region type uses DIVs with WAI-ARIA headings for the event list, however this should be implemented using more structured HTML. This issue is tracked with Oracle bug 27941145.
- Some configurations of 'required' attributes produce inconsistent output by screen readers, and may confuse users of assistive technology. This can lead to inconsistencies in what is emitted, and possibly confuse a user of Assistive Technology. This issue is tracked with Oracle bug 32085649.
- Row state information such as deleted, inserted or changed is conveyed visually, however this state information is not conveyed to screen reader users. This issue is tracked with Oracle bug 31964989.
- The Faceted Search region component requires better notifications of partial page updates for screen reader users. This issue is tracked with Oracle bug 30380762.
- In the Popup LOV item component, search results visually highlight the searched text, however this causes screen readers to no longer read the searched word naturally, and instead the characters will be separated by the searched text and non-searched text. This issue is tracked with Oracle bug 30375933.
- In the Popup LOV item component, when displaying multiple columns in the search results, extra 'No results found' text will be incorrectly announced to screen readers. This issue is tracked with Oracle bug 30375933.
- When Modal Dialogs are used, the non-modal dialog content is not hidden to screen reader users. This issue is tracked with Oracle bug 30666675.
- Where menus are used for page navigation, the menu item corresponding to the current page is missing the ARIA-CURRENT property. This issue is tracked with Oracle bug 32138852.
- Interactive report regions contain a column header popup menu that allows fast column-centric operations such as filtering, sorting etc. by the user. This functionality is implemented in such a way that is confusing to screen reader users, becuase it is not clear that it is a popup, and also it is difficult to navigate between the column header, and the popup. This issue is tracked with Oracle bug 32080813.
- Interactive report regions can sometimes become unusable with screen readers, after the data has been dynamically refreshed. This issue is tracked with Oracle bug 32284084.
- With Modal Dialog pages, if the page setting 'Focus on first item' is used, a screen reader user will have difficulty in reaching the dialog 'Close' button and the modal dialog title. This issue is tracked with Oracle bug 33882274.
- The Faceted Search region component uses a listbox implementation for the radio and checkbox style facets. This listbox implementation has some nesting and incorrect ARIA attribute issues. This issue is tracked with Oracle bug 33844482.
- The Interactive Grid component uses a checkbox to implement its Edit button, this should be a toggle button. This issue is tracked with Oracle bug 33686901.
- Links and buttons that open modal dialogs are missing aria-haspopup. This issue is tracked with Oracle bug 33571036.
- Item help can be displayed using Alt+F1, however this sometimes fails to load correctly with the screen reader JAWS. This issue is tracked with Oracle bug 34071241. When this happes, a JAWS user can workaround this by navigating to the end of the page, where the help dialog will be located.
|
| 4.1.3 Status Messages (Level AA) | Partially Supports | The product was tested for: - Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus
The documentation was tested for: - There are no status messages
Exceptions: Affecting Development Environment: - In Page Designer, success and error messages are not announced to screen readers. This issue is tracked with Oracle bug 33651195.
Affecting Development Environment and Applications: - All success messages should use a role of 'status', not 'alert' as it is currently. This issue is tracked with Oracle bug 33368864.
|