Oracle Accessibility Conformance Report

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:

• Bug 33351947: Report columns of type 'Display Image' have limited support for defining ALT text. 

Affecting Development Environment:

• Bug 33636441: 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.
• Bug 34133678: On the workspace home page, there is an unlabelled 'Success' icon under the 'Available Updates' section.
• Bug 34133596: In the footer, the username and workspace name are announced together (without any spacing), and are therefore difficult to understand with a screen reader.

Affecting Development Environment and Applications:

• Bug 34552693: Success and error message markup defined in the page templates of both the Universal Theme and theme used in our development environment, contain an unlabelled 'Close' icon button and unlabelled 'Success' or 'Error' icon.
• Bug 34668111: In the Interactive Grid region component, item types that don't fit in a cell (eg Textareas, Radio Groups) are rendered with an unlabelled close icon button.

The product and documentation were tested for:

• There is no pre-recorded audio only or video only content.

The product and documentation were tested for:

• No Pre-recorded video content is being used.

Exceptions:

Affecting Documentation:

• Bug 29370906: Videos on the Application Express YouTube channel are missing closed captions

The product and documentation were tested for:

• There is no pre-recorded video

The product and documentation were tested for:

• No live audio content in video is being used

The product and documentation were tested for:

• There is no pre-recorded video

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 Applications:

• Bug 34271178: In Universal Theme, many pages define a navigation landmark with the label 'Main Navigation'. This label should not include the text 'Navigation'.

Affecting Development Environment:

• Bug 25153940: The 'Quick Edit' and 'Live Template Options' features, available as a developer of an application via the developer toolbar, are inaccessible to screen reader users. 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.
• Bug 31972162: Search results pages for the Advisor, and for Application Search, are difficult to navigate with a screen reader.
• Bug 33925337: Some report pages are missing row headers.
• Bug 33637363: 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 difficult to navigate with a screen reader.

Affecting Development Environment and Applications:

• Bug 30375933: 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.
• Bug 31205979: LABEL elements for page items 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).
• Bug 32075361: 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.
• Bug 33270205: With the Color Picker item type, if Display As is set to 'Color-only Popup', the button rendered does not have a label.
• Bug 34152471: In Interactive Grid regions, the column, or columns defined with 'Value Identifies Row' set to on should be used as the row header, however they are not.
• Bug 34308481: In the Popup LOV item component, when 'Multiple Values' are on, it can be difficult to discern the item's label and value with a screen reader.
• Bug 34418403: In Interactive Grid regions, the dialog that opens when selecting a column header is missing a heading.
• Bug 34427572: Items can comprise of multiple distinct elements (for example the help button, inline help and 'Quick Pick' links). All elements associated with an item should be semantically grouped, however they are not.
• Bug 34456023: In the Date Picker item component, when navigating across the column headers of the calendar popup with a screen reader, the column header is always incorrectly prefixed with the column name of the currently selected date.
• Bug 34493281: In the Faceted Search region component, each facet should be rendered as a heading.

The product and documentation were tested for:

• The sequence of elements in the DOM matches a logical reading sequence

Exceptions:

Affecting Development Environment and Applications:

• Bug 34668049: In the Interactive Grid region component, after selecting 'Add Row', item types that don't fit in a cell (eg Textareas, Radio Groups) are rendered in the DOM at the end of the page, but visually positioned in the relevant grid cell, which can be confusing for screen reader users.

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

The product and documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

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.

The documentation was tested for:

• The documentation does not allow for input or changes to data.

Exceptions:

Affecting Development Environment and Applications:

• Bug 31978520: The autocomplete attribute is missing from pages that collect information about the user.

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:

• Bug 32463607: 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. 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.
• Bug 34099929: Chart regions provide no declarative way of defining a chart series pattern. As a workaround, it is possible to do this through customization, please see our Sample Chart > Pattern page for more information.

Affecting Development Environment and Applications:

• Bug 34184229: Interactive Grids and Reports provide the ability for an end user to define a highlight. This highlight can be either a row, or cell highlight. The user defines a background and a foreground color for the highlight, and some kind of data condition that controls when the highlight displays. Although we guide people into making good color combination choices by showing the luminosity ratio of the highlight text and background colors, the highlight itself is conveyed to the user by color alone.

The product and documentation were tested for:

• No automatically playing audio is used

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 Development Environment:

• Bug 34422388 In Page Designer, the contrast of items in Layout view is too low when running in Dark Mode.

Affecting Development Environment and Applications:

• Bug 34099910: In the Chart component, when a chart shows the label value next to the chart data, this can sometimes cause color contrast issues, where for example the text overlaps part of the chart data section, and the text color with the chart data color does not meet contrast requirements.

Affecting Documentation:

• Bug 29370357: The 'JavaScript API Reference' chapter of the documentation has text that does not meet the minimum contrast requirements.

The product and documentation were tested for:

• Text can be resized up to 200% without loss of content or functionality

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

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:

• Bug 31964090: Horizontal scroll is required throughout the development environment, when zoomed at 400%.

The product and documentation were tested for:

• Non-text items have a contrast ratio of at least 3:1

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

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:

• Bug 31888900: Tooltips used throughout the product fail the 'hoverable' test, because the tooltip disappears if you move the mouse over it.

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:

• Bug 32463573: 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).
• Bug 34455843: In the Application Search region, when focused on the pagination controls, if the user presses Shift+Tab, this can sometimes trigger pagination.

Affecting the Development Environment:

• Bug 30877825: 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. To workaround this issue, use Standard grid view, which does support selection and de-selection with the SPACE bar.

Affecting Development Environment and Applications:

• Bug 28293186: 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.
• Bug 30380719: 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.
• Bug 31971687: 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.
• Bug 33309025: Modal pages that submit and reload the modal page can lose focus.
• Bug 33824433: Markdown editor does not keep text selection when navigating to the toolbar by keyboard (for example to bold selected text).
• Bug 34200616: When an Interactive Grid region is loaded with no data, then a page event occurs that causes data to show, keyboard users cannot navigate the grid rows. To workaround this, keyboard users must refresh the page, where upon they will be able to navigate the displayed rows.
• Bug 34200659: In the Interactive Grid region, if a Dynamic Action is defined on a column that sets the value of another column, when keyboard users interact with the column, they can be taken to the next row unexpectedly.

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

The product and documentation were tested for:

• Single character keyboard shortcuts are only active when that component has focus.

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

The product and documentation were tested for:

• There is no moving, blinking or scrolling content

The product and documentation were tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

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:

• Bug 31972231: 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.
• Bug 32102597: In Universal Theme, page structure needs to be better identified with landmarks.
• Bugs 33172617 and 33098987: In Universal Theme, the Navigation Bar and Top Navigation Tabs list templates are missing a navigation landmark.

Affecting Development Environment:

• Bug 27782291: There are no 'Skip to Main Content' links implemented for the Development Environment.
• Bug 33847593: Complementary landmarks are not uniquely labelled on pages that have both a sidebar region, and a code editor.
• Bug 32930834: Breadcrumbs are defined just as links and are not contained within a navigation landmark.

Affecting Development Environment and Applications:

• Bug 32109673: Classic report regions need to better identify their contents with landmarks.
• Bug 34041752: Regions would benefit from landmarks to identify where items in the region are, and where any sub-regions in the region are.
• Bug 34552693: Success and error message markup defined in the page templates of both the Universal Theme and theme used in our development environment, are not wrapped in an appropriate landmark.

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

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:

• Bug 34017628: 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.
• Bug 33859795: 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.
• Bug 34071241: Item help can be displayed using Alt+F1, however this sometimes fails to load correctly with a screen reader. When this happens, screen reader users can workaround this by navigating to the end of the page, where the help dialog will be located.

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

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

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 Applications:

• Bug 34492904: Date Pickers with their Display As attribute set to Inline announce duplicate labels.

Affecting Development Environment:

• Bug 27782249: In Page Designer (where developers build and edit pages), the current heading structure needs improving to improve usability for users of Assistive Technology.
• Bug 20310474: One of the administration pages for the Attribute Dictionary contains a 'Check All' style checkbox in the report's column header, which is missing label text.
• Bug 33401741: In the App Builder, on the Static File Editor page, there is an empty H1 element.
• Bug 33566693: In the Create App wizard, there are headings to indicate the application type that could be improved by programmatically associating the description to the heading as well.
• Bug 31889333: Poor heading structure throughout the development environment.
• Bug 33575330: On the Create App page, the checkboxes in the Features section contains invalid labels.
• Bug 34130672: Help button labels that contain HTML are announced as unescaped HTML to screen reader users.
• Bug 34146997: On the Shared Component page, each shared component is listed with its name and also a count for the current application. For screen reader users, the name and count are not separated.
• Bug 34493156: On the 'Applications by Facets' page, the search facet has a landmark with the incorrect label 'New'.

Affecting Development Environment and Applications:

• Bug 25153552: In the Interactive Grid region component, some form fields rendered have either no label, or labels that require improvement.
• Bug 27810346: Native checkbox and radio group item types contain duplicate labels.
• Bug 32867611: In the Faceted Search region component, the facet chart button should not be part of the facet heading.
• Bug 34002311: 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. To workaround this in applications, define a custom Landmark Label in the region settings.
• Bug 33859790: In the Faceted Search region component, a facet's expand / collapse button has a duplicate label.
• Bug 33996908: Nested dialogs always use the same 'Close' button text, which can be confusing.
• Bug 34447053: In the Interactive Grid region component, when Single Row View is in view, there are two toolbars with the same label.
• Bug 34495581: When navigating the calendar of a date picker with a screen reader, the phrase 'Contains Controls' is incorrectly added to the announced day.

The product and documentation were tested for:

• Visual indication of the location of the focus

Exceptions:

Affecting Applications:

• Bug 30515581: 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.

Affecting Development Environment and Applications:

• Bug 25153460: In the Interactive Grid region component, some interactive controls do not show focus.

The product and documentation were tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality.

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

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.

The product and documentation were tested for:

• There are no functions that require motion of the device.

The product and documentation were tested for:

• Properly set lang attribute for each page

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

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

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 and Applications:

• Bug 33844689: In a Faceted Search region, focus is lost when closing a facet's chart dialog.
• Bug 34447426: In an Interactive Grid region, focus shifts to the top of the page when switching to Single Row View.

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

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

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:

• Bug 20697217: 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.
• Bug 31205839: When defining validations, 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). To workaround this issue, developers should select any location including the 'Notification' position.

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

Exceptions:

Affecting Development Environment and Applications:

• Bug 34469087: In the Interactive Grid region component, the row selector checkbox has no label.
• Bug 34684002: The Percent Graph column type, available with Classic Reports, Interactive Reports and Interactive Grid, is implemented as a 'Meter' widget, has no label.

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

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

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:

• Bug 33865529: Interactive Report regions defined with headings fixed to either 'Page' or 'Region' are rendered with duplicate IDs for the column header elements.

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 programmatically exposed name
• Frames have a meaningful title specified in the title attribute

Exceptions:

Affecting Applications:

• Bug 30515581: 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.
• Bug 32086482: In Universal Theme, when using 'Side' navigation, if the menu is in a collapsed state, the menu no longer works as expected. To workaround this issue, the menu can be expanded.
• Bug 33172617: In Universal Theme, all the current sublist entries in the Navigation Bar list template are missing aria-current.
• Bug 34275524: Breadcrumb entries are missing important information that would help a screen reader user (navigation landmark container and ARIA-CURRENT applied to the current breadcrumb).

Affecting Development Environment:

• Bug 32087719: 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).
• Bug 29283988: 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.
• Bug 20693603: In Page Designer, the splitter controls used to manage layout are poorly labelled and are missing ARIA-CONTROLS to point to relevant page area.
• Bug 31973124: 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.
• Bug 32103943: 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.
• Bug 32087187: Incorrect shortcut text conveyed to screen readers for accessing application search.
• Bugs 33161303 and 32929901: 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.
• Bug 32930834: 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.
• Bug 33856322: Code Editors when rendered in read-only mode appear editable to screen reader users, as they are mising the ARIA-READONLY attribute.
• Bug 33839482: In Page Designer, as tooltips are displayed a corresponding hidden DIV is added to the bottom of the DOM. These are not visible, however are perceivable with a screen reader and worsen the user experience.
• Bug 33638611: In Page Designer in the Link Builder, the Set Items property type uses an incorrect role.
• Bug 34401775 The email sent from the Purge Workspace notification has text that indicates the user should press a button to action the purge, although the action button looks like a button, it is actually a link, which is confusing to screen reader users.
• Bug 34133678: On the workspace home page in the 'Available Updates' section, the 'Success' icon is not coded as an image.

Affecting Development Environment and Applications:

• Bug 27941145: 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.
• Bug 32085649: Both Universal Theme, and the theme used in the development environment have label templates used for required fields. These label templates append the following visually hidden (but available to screen readers) text "(Value Required)" to the end of the label. Required state should instead be defined using the ARIA-REQUIRED attribute on the interactive element, and removed from the label.
• Bug 31964989: Row state information such as deleted, inserted or changed is conveyed visually, however this state information is not conveyed to screen reader users.
• Bug 30375933: 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.
• 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.
• Bug 30666675: When Modal Dialogs are used, the non-modal dialog content is not hidden to screen reader users.
• Bug 32138852: Where menus are used for page navigation, the menu item corresponding to the current page is missing the ARIA-CURRENT property.
• Bug 32284084: Interactive report regions can sometimes become unusable with screen readers, after the data has been dynamically refreshed.
• Bug 33882274: 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.
• Bug 33844482: 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.
• Bug 33571036: The following places have interactive elements that open dialog content, but where the ARIA-HASPOPUP attribute is missing:
  • Create application page contains links that open modal dialog regions
  • 'Cards' regions that expose action buttons that open modal dialog pages
  • Page buttons that redirect to modal dialog pages
  • Page buttons that open inline dialog regions
  • Report links that open modal pages
• Bugs 31200377, 34585616, 34556933, 34552301, 34550043, 34525007, 34518962, 34510276, 34305870: There are 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, a SPAN is rendered 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.
• Bug 34489941: The Popup LOV item renders its popup list of values in a dialog, however this dialog is not modal when used with a screen reader.
• Bug 34481324: The Checkbox item type renders an unlabelled element with no role, directly after the checkbox. When screen reader users encounter this element, they will hear nothing, which may cause confusion.
• Bug 34456004: Dialogs rendered by apex.message.showDialog (and used for example in the Date Picker item type to render the calendar popup) do not follow the WAI-ARIA dialog pattern.
• Bug 34447594: Single Row View of Interactive Grid regions renders non-editable fields that may be easily missed by users of Assistive Technology.
• Bug 34422373: The Tree widget (for example used in Page Designer, or by our native Tree region component) has no support for defining a label for the main tree root note.
• Bug 34413163: The Interactive Grid region has buttons on the column header that allow users to sort by that column. These buttons are not perceivable to screen reader users. To workaround this, screen reader users can sort via the Sort dialog.
• Bug 34258753: The Popup LOV item type implements the WAI-ARIA combobox pattern, however it is missing defining ARIA-CONTROLS on the combobox element pointing to the popup container element.
• Bug 34220104: The Interactive Report region has many configuration dialogs for defining things like visible columns, filters, and highlights. These dialogs display visually as modal dialogs, however they are not perceivable by screen reader users as modal.
• Bug 34184254: Interactive Grids and Reports provide the ability for an end user to define a highlight. This highlight can be either a row, or cell highlight. The user defines a background and a foreground color for the highlight, and a data condition that controls when the highlight displays. Screen reader users have no easy way of knowing which cells / rows are currently highlighted.
• Bug 34147034: The Switch item type is exposed to screen readers as a checkbox. It should be a switch.
• Bug 34146043: In the Faceted Search region, checkbox and radio facet types are incorrectly exposed as a listbox.
• Bug 34136334 and 34136083: The Tree widget (for example used in Page Designer, or by our native Tree region component) sometimes exposes incorrect child nodes and incorrect node levels to screen reader users.
• Bug 34130570: The first column of an Interactive Grid region is typically the row selection column. Cells in this column fail to expose any value to screen reader users.
• Bug 34552693: Success and error message markup defined in the page templates of both the Universal Theme and theme used in our development environment, contain a 'Close' icon button and 'Success' or 'Error icon that are not coded as an image.
• Bug 34668111: In the Interactive Grid region component, item types that don't fit in a cell (eg Textareas, Radio Groups) are rendered with a close icon button. This icon button is not coded as an image.

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 Applications:

• Bug 34455843: In the Application Search region, screen reader users are not notified when using pagination controls.

Affecting Development Environment:

• Bug 33651195: In Page Designer, success and error messages are not announced to screen readers.
• Bug 34026939: 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.

Affecting Development Environment and Applications;

• Bug 29348302: 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.
• Bug 30380762: The Faceted Search region component requires better notifications of partial page updates for screen reader users.

The product has no multimedia.

The product has no multimedia.

See WCAG Section

The product was tested for:

• File conversions preserve accessibility information

The product and documentation were tested for:

• PDF files conform to PDF/UA-1
• Components that support export to PDF respect either the APEX_PDF_ACCESSIBLE user preference, or the 'Include Accessibility Tags' option (where supported)

Exceptions:

Affecting Development Environment and Applications:

• Classic Report regions do not provide a direct way to allow an end user to select accessible PDF, although it is possible to export accessible PDFs from classic reports if the relevant user preference has been set. This issue is tracked with Oracle bug 31961351. There are four ways in which this user preference can be set, outlined below:
  • Interactive Report dialogs include an 'Include Accessibility Tags' option, which when checked will be saved as a preference for the current user.
  • Interactive Grid dialogs include an 'Include Accessibility Tags' option, which when checked will be saved as a preference for the current user.
  • The preference can be directly set by a developer, for example: APEX_UTIL.SET_PREFERENCE( 'APEX_PDF_ACCESSIBLE', 'Y', );
  • The API APEX_REGION.EXPORT_DATA is available, which allows for any component with a data source (which includes Classic Reports), to export supported PDF (where the parameter p_pdf_accessible is set to true). Once this API has been called with p_pdf_accessible set to true, the APEX_PDF_ACCESSIBLE preference will be set for the current user.

We mandate certain accessibility related attributes when building applications (for example page titles, region titles, and button labels). The developer is responsible for ensuring the text provided is appropriate and meaningful.

Oracle APEX includes a built-in tool called the Advisor, which can be run by developers as part of quality assurance of an application. To help with other non-mandatory attributes defined by a developer, the Advisor includes a set of accessibility checks to highlight possible common accessibility problems (for example page items with no labels, or page regions with no row headers defined). The developer should review and fix such problems as part of their ongoing development process. We recommend to fix issues identified by the Advisor before doing other accessibility testing, for example testing with Assistive Technologies.

Developers should use the default 'Universal Theme' when building applications. This theme contains templates for different component types, which have been accessibility tested. In addition, developers can select different 'Theme Styles' for styling their applications in different ways. Theme Styles are labelled as being 'Accessibility Tested' if they have undergone accessibility testing. The default 'Vita' is accessibility tested.

The product documentation describes:

• Accessibility Guide, dedicated to helping you both use Oracle APEX, and build Oracle APEX apps that meet accessibility guidelines.
• Special keystrokes needed to operate controls

Please visit the Oracle APEX documentation homepage and then select 'Accessibility'.

Product documentation is in electronic format.