Accessibility Bug - Display text for item selected in hotbar does not hide on item USE on Touch Screen

The dynamic duration of items that have multiple enchantments/ lore details does not hide immediately upon USE on Android Touch Screen UI.

This is an accessibility issue that creates barriers to play when readying a weapon for combat. A heavily enchanted /Lore weapon or tool can stay on screen obscuring the player view for up to TEN SECONDS.

Unlike using a Bluetooth controller paired to an Android device, the dynamic display text for an item does NOT immediately clear from view upon item USE.

I performed a test on my mobile Android device and found that when using a paired controller, the dynamic overlay text for a heavily enchanted /Lore item clears immediately upon first use after selecting the item from the player hotbar.

The UI not doing exactly the same in Touch Screen UI indicates a great oversight that affects both playability and accessibility.

I suggest that this bug report be forwarded to the Accessibility Team for immediate review and remedy to be consistent with controller input.

Additionally, there should be an accessibility setting added to allow override of the dynamic duration of hotbar item selected text.

The test for this behavior is as follows:

1. Launch Minecraft on mobile touch screen device using a Bluetooth controller paired.

2. Load game world an equip a heavily enchanted / Lore tool or weapon to the hotbar.

3. Select the heavily enchanted /Lore tool or weapon, note the duration of the item details displayed on screen before the text disappears.

4. Select a different item. And then immediately back to the heavily enchanted /Lore item. Use the USE action for the item. Note that the item details displayed are hidden immediately upon use.

5. Perform the same above tests above using only the Touch Screen UI.

6. Results will show that the USE action on Touch Screen UI does NOT immediately clear item display details on the USE action. This is a clear accessibility and useability bug with the UI.

I will attempt to create a video displaying this behavior, but it is easily tested by anyone with the classic UI.