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 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.
• Bug 33351947: In Page Designer, there are trees for presenting information about Rendering, Dynamic Actions, Shared Components and Page Processing. If a node is a parent node, the arrow to the left of the text renders as an unlabelled span element, which is perceivable to screen reader users as an unlabelled object.

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: Interactive Grid region - Item types that do not fit in the 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 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.
• Bug 34975208: In Page Designer, the List of Values 'Static Values' dialog contains a table with an incorrect name.

Affecting Development Environment and Applications:

• Bug 30375933: Popup LOV item - 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 34308481: Popup LOV item - When 'Multiple Values' are on, it can be difficult to discern the item's label and value with a screen reader.
• Bug 35177965: Faceted Search region - The number of results for each facet value is difficult to understand for screen reader users.
• Bug 32075361: Interactive Grid region - 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 34989332: Interactive Grid region - The toolbar is labelled 'Toolbar' resulting in duplication with a screen reader.
• Bug 35166387: Interactive Grid region - If 'Load More' pagination is used (Pagination Type = Scroll, Show Total Row Count = No and pagination.loadMore = true in advanced JavaScript), the 'Load More Rows' button is difficult to find for screen reader users.
• 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 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).

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: Interactive Grid region - After selecting 'Add Row', item types that do not fit in the 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.

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: Map region - Polygon layers allows the user to visualize information with the fill color for the polygons on the map, providing a 'thematic map'. Polygons can be filled with different colors, but there is no ability 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 region - 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 Grid and Report regions 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: Chart region - 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. To workaround this, depending on the chart type and data, it may be possible to adjust the label settings, for example if 'Position' is set to 'Outside Bar Edge' (instead of the default 'Automatic'). In addition, if the chart displays a Tooltip including the value, this can be an alternative.

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: Map region - Spatial objects drawn on the map are currently not accessible with the keyboard. It is 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: 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.

• Bug 35194834: The following two places in the development environment allow users to select a color, and where the color name provided using the TITLE attribute, which displays to mouse users on hover, however keyboard users have no way of perceiving this text:

  • Create App Wizard > Choose Application Icon > Pick an Icon

  • Instance Admin > Define Environment Banner > Color

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 31971687: Region Display Selector region - This 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 region - Region does not keep text selection when navigating to the toolbar by keyboard (for example to bold selected text).
• Bug 34200659: 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 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 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 region - Region needs to better identify its 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.
• Bug 34960903: Regions defined to use landmarks will be missing their landmark information if the region also participates as a region controlled by a Region Display Selector on a page.
• Bug 35079324:  Page items can be co-located in a region with the region's other contents (for example a table of data). In this case, it can be difficult for screen reader users to quickly find the items, because there is no landmark around them.
• Bug 35079782: Region templates define custom 'Positions', within which different page components can position themselves. These positions are missing landmarks, making it potentially difficult for screen reader users to quickly locate these components.

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

• Bug 34271178: In Universal Theme, when collapsible side navigation is used, when expanding the side navigation focus should be set to the first item in the menu.

Affecting Development Environment:

• Bug 35222499: In Object Browser, APEX often displays the formatted SQL statement corresponding to the current operation. The element used to display the formatted SQL statement is navigable with keyboard, however it contains an unnecessary extra tab stop.

Affecting Development Environment and Applications:

• Bug 34017628: Interactive Grid region - 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 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

Exceptions:

Affecting Development Environment:

• Bug 34991575: In Instance Administration, although pages are fully inter-linked to each other, there is no search functionality.

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 Picker item - Duplicate label when Display As attribute set to Inline.
• Bug 34989214: In the Universal Theme, the region template 'Interactive Report' (used as the default template for both Interactive Report and Interactive Grid regions), is missing a heading. To workaround this issue, switch to using the 'Standard' region template, which does contain an H2 element. Note: Display settings can be adjusted via Template Options to visually hide the heading and remove borders, if desired.

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 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 35222938: In the Object Browser > Sample Queries Grid, the 'Copy' and 'Run' buttons are incorrectly labelled by the current grid cell's context.

Affecting Development Environment and Applications:

• Bug 27810346: Checkbox and Radio Group items - Duplicate labels.
• Bug 32867611: Faceted Search region - The facet chart button should not be part of the facet heading.
• Bug 33859790: Faceted Search region - Facet's expand / collapse button has a duplicate label.
• Bug 34447053: Interactive Grid region - When Single Row View is in view, there are two toolbars with the same label.
• Bug 34918506: Interactive Grid region - When a screen reader user is interacting with a data cell, context information is provided about the current column and row. The row information given is the current data row (not including the table header row), which can be confusing if the screen reader also announces the default table navigation row context (which includes the table header row).
• Bug 34980410: Interactive Grid region - When in Single Row View, the menu buttons for 'Change Menu' and 'Settings Menu' should include the word 'menu' in the label.
• Bug 35215504: Interactive Grid region - If the region title contains some HTML, this HTML will be exposed in the table's accessible name.
• Bug 35132319: When a page item uses help text, the label used for the help button is too long ('View help text for [item label]'). This forces a screen reader user to listen to 'View help text for' before the item label for every help button. To workaround this issue, define the Text Message 'APEX.ITEM.HELP_TEXT' with text 'Help for %0', to shorten the accessible name used for help buttons.

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: Interactive Grid region - 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

Exceptions:

Affecting Development Environment:

• Bug 34969961: On the workspace login page, if all languages are installed links will display below the 'Sign In' button allowing users to select their language. These links are missing the LANG attribute for the corresponding language.

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 34802394: Interactive Grid region - When duplicating a row, focus is moved unexpectedly away from the grid.

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 35222957: The recordView JavaScript widget (used by Object Browser to edit data, and Interactive Grid for Single Row View), presents inline validation messages for example when a field is required and null, however this information is not programmatically associated with the interactive element, making it difficult to perceive with a screen reader.

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: Interactive Grid region - The row selector checkbox has no label.
• Bug 34896075: Interactive Grid region - Advanced JavaScript configuration allows to display a sequence number as the first column in the grid. These sequence numbers are not perceivable to screen readers.

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 34659075: Interactive Report regions defined with headings fixed to either 'Page' or 'Region' are rendered with duplicate IDs for the column header elements. This has no impact on functionality.
• Bug 35120602: Rich Text Editor item (TinyMCE Library) - If there are more than one of these items on a page, they will have duplicate IDs. This has no impact on functionality.

Affecting Development Environment and Applications:

• Bug 35115041: Classic Report region - If more than one classic report is on a page, and if any of the columns of the different reports share the same column name, this will result in duplicate IDs on the page. This has no impact on functionality.

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 WAI-ARIA 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).
• Bug 34891616: Popup LOV item - When 'Manual Entry' is off, currently a readonly input element is rendered, however this gives the impression the field's value cannot be changed (which it can via the Popup).

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 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.
• 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 34859370: On the App Builder homepage, the report can optionally be rendered using 'Icon View'. In this view, for each application, a group of elements is displayed (link to the app, edit button, and run button) and these elements are not semantically grouped. To workaround this issue, please choose the 'Report View'.
• Bug 34969923: When signing up for a new workspace, on the Agreement page, the 'I accept the terms' checkbox uses a checkbox group, where it should just use a single checkbox.
• Bug 35074290: In Page Designer on the 'Search' tab, all elements in the tab panel have ARIA-CONTROLS pointing to an unlabelled element.
• Bug 35156073: In Page Designer, when using the layout option 'Two Pane Mode', the 'Rendering' tree becomes unusable with a screen reader. To workaround this issue, use 'Three Pane Mode'.
• Bug 35222919: The trees used in Page Designer, and Object Browser do not convey when a node is in an invalid state. In Page Designer, the invalid state is when the selected component has a property in an error state. In Object Browser the invalid state happens when a Database Object is invalid. The invalid information is available elsewhere on these pages, however it is missing from the tree node.

Affecting Development Environment and Applications:

• Bug 27941145: Calendar region - The List View uses DIVs with WAI-ARIA headings for the event list, however this should be implemented using more structured HTML.
• Bug 32085649: If a page item is a required field, developers can define this both using the 'Value Required' attribute on the item, and by defining one of the required label templates. If the 'Value Required' attribute is set, the rendered interactive element correctly uses the ARIA-REQUIRED attribute. However, if just the required label template is chosen, the interactive element is missing the ARIA-REQUIRED attribute, so users would not know the field is required at time of input.
• Bug 31964989: Interactive Grid region - 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: Popup LOV item - 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: Popup LOV item - 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 region - When displaying a very large set of data, these reports 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: Faceted Search region - Region uses a listbox implementation for the radio and checkbox style facets. This listbox implementation has some nesting and incorrect WAI-ARIA attribute issues.
• Bugs 33571036 and 35021433: 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
  • Main menu option 'SQL Developer Web' (available from the SQL Workshop menu, when there is an available SQL Developer Web environment)
• Bugs 31200377, 34585616, 34556933, 34552301, 34550043, 34525007, 34518962, 34510276, 34305870, 34836092, 34836385, 34836402: 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: 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 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 design pattern.
• Bug 34413163: Interactive Grid region - 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: Popup LOV item - Item implements the WAI-ARIA Combobox design pattern, however it is missing defining ARIA-CONTROLS on the combobox element pointing to the popup container element.
• Bug 34220104: Interactive Report region - 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 Grid and Report regions - Both 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: Switch item - Item is exposed to screen readers as a checkbox. It should be a switch.
• 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: Interactive Grid region - Item types that do not fit in a cell (eg Textareas, Radio Groups) are rendered with a close icon button. This icon button is not coded as an image.
• Bug 34910599: Interactive Grid region - If a Control Break is defined, in the grid the control break header is difficult to understand, and collapsed state is not conveyed to screen reader users.
• Bug 34970326: Interactive Grid region - Row states 'Inserted', 'Updated', 'Deleted' and 'Error' are not perceivable are not conveyed to screen reader users.
• Bugs 34987397 and 35038891: The iconList JavaScript widget used for example in the Interactive Grid Chart dialog and 'Icon View', is not coded to the WAI-ARIA Listbox design pattern, making them difficult to use with a screen reader.
• Bug 35112161: Modal dialog pages currently render an IFRAME inside the modal dialog element, however this should be with the IFRAME outside of the modal dialog element.
• Bug 35120596: Rich Text Editor item (TinyMCE Library) - Configuration dialogs contain menu buttons to define certain values (for example Insert / Edit Link dialog > Open Link in..) that should be select lists.
• Bug 35120615: Rich Text Editor item (TinyMCE Library) - In the Insert / Edit Link dialog, the URL combobox options are not perceivable with a screen reader.
• Bug 35120629: Rich Text Editor item (TinyMCE Library) - For Format mode 'HTML', it is possible to insert a table using the insert table functionality from the toolbar. If using keyboard to select the table dimensions, the selected state becomes difficult to distinguish from the focus state.
• Bug 35135038: Faceted search region - Facets are presented as a group of sections that can be expanded or collapsed, however they are not coded to the WAI-ARIA Accordion design pattern, making them difficult to use with a screen reader.

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.