JAWS screen reader misreads "add" and "remove" buttons in composite field and in text field with unlimited allowed values

Problem

The JAWS screen reader does not distinguish between the "Add" and "Remove" buttons in the composite field or in the text field with unlimited values. Instead, it reads both controls as one composite control, which confuses users because they cannot determine which action is available.

Steps to reproduce

1. In the Webform, add a composite field or text field with unlimited values.
2. Use JAWS to navigate to the "Add" and "Remove" buttons.
3. Observe that JAWS reads both buttons together instead of individually.

Environment

• JAWS (Edge, Chrome, Firefox)

Observed behaviour:

1. NVDA: Able to read each button correctly.
2. JAWS on Edge and Chrome: Both buttons are read as "Add button, remove button. To activate press Enter", without differentiating between the buttons.
3. JAWS on Firefox: Both buttons are announced as "Blank. To activate press Space."
   JAWS fails to clearly indicate what the user is focused on and what to expect when using JAWS, as can be observed in the attached recording.
4. Markup validation errors: Following markup errors are appearing for the elements.

Error: Bad value image for attribute type on element button.

Error: Attribute src not allowed on element button at this point.

Error: Attribute alt not allowed on element button at this point.

Expected behaviour:

1. Each button should be read independently with its specific label (e.g., "Add new item after item 1"), so the user clearly understands which control is focused.
2. No markup validation errors should occur.

Possible fixes:

• After investigation and testing, it turns out that since both buttons are in the same table cell, JAWS is treating the cell as a single composite control rather than two separate buttons. This is causing it to read the hidden "sr-only" text from both buttons together.
• To fix the issue, I placed each button in its own