Issue Summary

The element is not accessible by keyboard alone and there is no conforming accessible version of the same functionality reachable from the non-conforming page.

Elements name:

• Select an object button i.e. 'Search' icon.
• create an object

Location of the elements: Buttons, in the "Affected Server:" edit section, just beside the "Affected Server:" text, in the "Details" heading section, in the main content.

Steps to reproduce:
1. Hover on the "oracledb-11g-prod" application section, just beside the "Affected Server:" text, in the "Details" heading section.
2. Then the "Edit" button will display. Click on the "Edit" button icon.
3. Then the above-mentioned buttons will display.

Tested URL

Steps to Reproduce

1. Step 1

Actual Results

Actual results

Expected Results

Fix Information
RULE :
For each user interface component that includes a visible text label, the accessible name MUST match (or include) the visible text in the label.

HOW TO FIX:
Fix this issue by ensuring that the accessible name - such as the aria-label - contains the text of the visible label in the same order in which it appears. While it is not necessary that the visible label and accessible name match exactly, it is a best practice to have the accessible name begin with the visible text.

REFERENCE:
WCAG Understanding document: https://www.w3.org/WAI/WCAG21/Understanding/label-in-name

BACKGROUND:
Speech input users can interact with a webpage by speaking the visible text labels of menus, links, and buttons that appear on the screen. It is confusing to speech input users when they say a visible text label they see, but the speech command does not work because the component's accessible (programmatic) name does not match the visible label. When a user interface component has a visible text label - whether it be real text or an image of text - that text must also be found in the component's accessible (programmatic) name. When the visible label and accessible (programmatic) name for interactive components are in sync, speech input users can effectively interact with those components.

Screenshot

Screen Recording

screen recording

Workaround

workaround

Bug Ref: 746202

Bulldog Ref: JSMDC-12597