Business Services/Create Objects : Informative images such as "Tick icon" and "X icon" is missing text alternative.

Issue Summary

The "Tick icon" and "X icon" image conveys information and is missing text alternative for assistive technology users.

Elements:

• Tick icon
• X icon

Location:
Present in the "Enter IQL (implicitly adds the current object type id)" field, it will appear on activating the "Advanced" link

Tested URL

https://instenv-21072-japp.instenv.internal.atlassian.com/secure/ObjectSchema.jspa?id=3&typeId=43&mode=object&objectId=201

Steps to Reproduce

1. Launch the URL
2. In the Insights menu, select any object schema.
3. In the Insights section, in the main content area, activate the "Advanced search" link
4. After the Advance search input field is available for Business services, navigate into the input field with the keyboard or screen reader on to interact with the "Tick" and "X" icons.

Actual Results

The "alt" text is missing in the source code for the icons such as "Tick" and "X" icon, which is present on activating the "Advanced search" link. After the Advance search input field is available for Business services, navigate into the input field with the  screen reader on to interact with the "Tick" and "X" icons, the screen reader does not announce any details regarding the icon. The functionality of the "Tick" and "X" icons is such that when we enter the correct input it stays as the "Tick" icon and when the wrong input has been entered it shows the "X" icon. So for the screen reader, it will create a problem while navigating through the input field.

Expected Results

Provide alternate text for all the images using the "alt" attribute. Ensure that the alternate text is descriptive of the image's purpose. If the image is informative, then give a descriptive alt text for the image icon such as alt="Accept" for "Tick" icon and alt="Error" for "X" icon.

Screenshot

Screen Recording

Screen Recording 2022-06-07 at 2.17.56 PM.mov

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available

Bug Ref: 749943

Bulldog Ref: JSMDC-12873