[Bug Report][3.7.3] Using objects with VSelect results in not very accessible values read by screen readers

[someguy20336]

Environment

Vuetify Version: 3.7.3
Vue Version: 3.5.12
Browsers: Chrome 129.0.0.0
OS: Windows 10

Steps to reproduce

• Set up a VSelect to use objects with a title and a value. The value may not be intended to be exposed to the user (for example, an ID of some sort)
• Turn on a screen reader
• Select a value in the VSelect
• Listen to what the screen reader reads for the value of the selection

Expected Behavior

I would expect the screen reader to read the title of the selection, as that is the useful part.

Actual Behavior

The screen reader reads out the value of the selection, which in this case is an ID and would mean nothing to the user that is using the screen reader.

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

I realize I can probably work around this, but that would mean I can't actually use objects with VSelect and I would need to maintain maybe some sort of two way mapping between titles and values. If I am doing something wrong or unexpected, definitely let me know.

I would think the fix would be that the input that gets focus should actually contain the title as the value. Perhaps there is another <input type='hidden' /> that captures the value as its value and might also be the one that participates in forms or something (gets the name attribute, if specified, for example). I have no idea what this might break, if anything, but let me know what you think. I might have some interest in submitting a PR if you agree with that approach and are looking for some help fixing it.