Screen reader is reading list from a vuetify v-select in random order #17123

ncsugrad94 · 2024-09-05T14:11:36Z

Steps to reproduce:

Go to any implementation of vue v-select like this one: https://vuetifyjs.com/en/components/selects/#density
Use the keyboard to navigate to the select menu and open it.

Actual behavior:

NVDA reads the items in the list in a random order.

output from speech viewer:
Select component — Vuetify - Google Chrome - Steven
Buzz
Fizz
Bar
Foo

Actual order of elements:
Foo
Bar
Fizz
Buzz

Expected behavior:

NVDA reads the items in the list in the order they are presented in the UI

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA Installed

NVDA version:

NVDA vs 2024.3 (2024.3.0.33433)

Windows version:

Windows 11

Name and version of other software in use when reproducing the issue:

Chrome Version 128.0.6613.120 (Official Build) (64-bit)

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

No

If NVDA add-ons are disabled, is your problem still occurring?

No add ons installed

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?\

Yes

Adriani90 · 2024-09-05T14:30:14Z

This is only reproducible in Chromium. In Firefox NVDA is always reading the same order.
I noticed however that if you press the down arrow key while focusing the multi combo box in focus mode, NVDA will report the presumably focused element first and then the remaining ones after the focused item, and then the ones before the focused item.
This happens only while the box is closed though. So it is not really random.

ncsugrad94 · 2024-09-06T01:56:51Z

Thanks for the feedback. Is it possible this will be fixed in a future release?

…

On Thu, Sep 5, 2024 at 10:30 AM Adriani90 ***@***.***> wrote: This is only reproducible in Chromium. In Firefox NVDA is always reading the same order. I noticed however that if you press the down arrow key while focusing the multi combo box in focus mode, NVDA will report the presumably focused element first and then the remaining ones after the selected item, and then the ones before the selected item. This happens only while the box is closed though. So it is not really random. — Reply to this email directly, view it on GitHub <#17123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLJSD2ATNF7FS62HT5VCDZVBTIZAVCNFSM6AAAAABNWS52NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZRHA2DGMRXHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

RyanSMS · 2024-09-06T02:53:36Z

This is only reproducible in Chromium. In Firefox NVDA is always reading the same order. I noticed however that if you press the down arrow key while focusing the multi combo box in focus mode, NVDA will report the presumably focused element first and then the remaining ones after the focused item, and then the ones before the focused item. This happens only while the box is closed though. So it is not really random.

"Random" because in each time the list is expanded, NVDA reads the list in different order. For example based on the one above:
At the first time, you may hear:
Buzz
Fizz
Bar
Foo

Maybe you will get at the second time of list expansion:
Fizz
Buzz
Foo
Bar

seanbudd · 2024-09-10T00:16:30Z

Welcome @ncsugrad94 ,

We are unable to process this issue as it stands.

To be able to reproduce this issue, we need a minimal code sample. Provide a minimal HTML sample using plain HTML/JS to reproduce this using codepen. It is not possible for us to debug the vuetify library.
This is very likely a problem with the implementation of the framework design, as a starting point please submit feedback to the authors to let them know about the problem.

Kind Regards,
NV Access Software Developers

thgcode · 2024-09-21T12:01:23Z

I tried to create a minimal example to try to understand the issue better and noticed that each time you close the browser and reopen the document again, NVDA reads the aria-live text with a different order:

<html>
	<head>
		<title>Aria-live reading order test</title>
	</head>
	<body>
		<script type="text/javascript">
		var pressed = false;

		function test() {
			let t1 = document.getElementById("t1");
			let t2 = document.getElementById("t2");
			let t3 = document.getElementById("t3");
			pressed = !pressed;

			if (pressed) {
				t1.textContent = "Aria 1";
				t2.textContent = "Aria 2";
				t3.textContent = "Aria 3";
			} else {
				t1.textContent = "";
				t2.textContent = "";
				t3.textContent = "";
			}
		}
		</script>
		<p aria-live="polite" id="t1"></p>
		<p aria-live="polite" id="t2"></p>
		<p aria-live="polite" id="t3"></p>
		<button onclick="test()">Press to change aria-live elements</button>
	</body>
</html>

I tested with Narrator and the events are read with the proper order each time. But I am not sure on how to debug further, is there some way I can find on which order aria-live events are arriving on NVDA's end, or if there is a difference on IAccessible 2 and UIA?

seanbudd · 2024-09-22T23:26:11Z

@thgcode - enabling "events" and "MSAA" logging in advanced preferences may help

thgcode · 2024-09-23T09:36:23Z

I tested with the event tracker addon and found something interesting:

IO - inputCore.InputManager.executeGesture (06:11:54.278) - winInputHook (3120):
Input: kb(laptop):space
DEBUG - external:globalPlugins.evtTracker.GlobalPlugin.evtDebugLogging (06:11:54.314) - MainThread (1180):
EvtTracker: object: <NVDAObjects.IAccessible.chromium.Document object at 0x08376750>
name: Aria-live reading order test
role: Role.DOCUMENT
event: loseFocus
app module: AppModule(appModuleHandler, appName='msedge', processID=7380)
window class name: Chrome_RenderWidgetHostHWND
IAccessible accName: 'Aria-live reading order test'
IAccessibleChildID: 0
DEBUG - external:globalPlugins.evtTracker.GlobalPlugin.evtDebugLogging (06:11:54.318) - MainThread (1180):
EvtTracker: object: <NVDAObjects.Dynamic_ButtonIa2WebIAccessible object at 0x083766D0>
name: Press to change aria-live elements
role: Role.BUTTON
event: gainFocus
app module: AppModule(appModuleHandler, appName='msedge', processID=7380)
window class name: Chrome_RenderWidgetHostHWND
IAccessible accName: 'Press to change aria-live elements'
IAccessibleChildID: 0
IO - speech.speech.speak (06:11:54.331) - MainThread (1180):
Speaking ['Aria 3 ']
IO - speech.speech.speak (06:11:54.332) - MainThread (1180):
Speaking ['Aria 2 ']
IO - speech.speech.speak (06:11:54.348) - MainThread (1180):
Speaking ['Aria 1 ']
DEBUG - external:globalPlugins.evtTracker.GlobalPlugin.evtDebugLogging (06:11:54.349) - MainThread (1180):
EvtTracker: object: <NVDAObjects.IAccessible.ia2Web.Ia2Web object at 0x08376610>
name: None
role: Role.PARAGRAPH
event: liveRegionChange
app module: AppModule(appModuleHandler, appName='msedge', processID=7380)
window class name: Chrome_RenderWidgetHostHWND
IAccessible accName: None
IAccessibleChildID: 0
DEBUG - external:globalPlugins.evtTracker.GlobalPlugin.evtDebugLogging (06:11:54.357) - MainThread (1180):
EvtTracker: object: <NVDAObjects.IAccessible.ia2Web.Ia2Web object at 0x083769D0>
name: None
role: Role.PARAGRAPH
event: liveRegionChange
app module: AppModule(appModuleHandler, appName='msedge', processID=7380)
window class name: Chrome_RenderWidgetHostHWND
IAccessible accName: None
IAccessibleChildID: 0
DEBUG - external:globalPlugins.evtTracker.GlobalPlugin.evtDebugLogging (06:11:54.361) - MainThread (1180):
EvtTracker: object: <NVDAObjects.IAccessible.ia2Web.Ia2Web object at 0x0842E2F0>
name: None
role: Role.PARAGRAPH
event: liveRegionChange
app module: AppModule(appModuleHandler, appName='msedge', processID=7380)
window class name: Chrome_RenderWidgetHostHWND
IAccessible accName: None
IAccessibleChildID: 0

Somehow, the aria-live event is being processed before it arrives to NVDA. I performed another test, I hardcoded a global list to save the processed aria-live events received by the event tracker addon and found that, even though NVDA spoke the aria-live events on a random order, surprisingly, event tracker received the events with the correct order all the time. Maybe, on NVDAHelper, some events arrive faster, changing the order, but I am not sure if this is the case.

seanbudd added blocked/needs-info The issue can not be progressed until more information is provided. blocked/needs-sample needs-triage labels Sep 10, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Screen reader is reading list from a vuetify v-select in random order #17123

Screen reader is reading list from a vuetify v-select in random order #17123

ncsugrad94 commented Sep 5, 2024

Adriani90 commented Sep 5, 2024 •

edited

Loading

ncsugrad94 commented Sep 6, 2024 via email

RyanSMS commented Sep 6, 2024

seanbudd commented Sep 10, 2024

thgcode commented Sep 21, 2024

seanbudd commented Sep 22, 2024

thgcode commented Sep 23, 2024

Screen reader is reading list from a vuetify v-select in random order #17123

Screen reader is reading list from a vuetify v-select in random order #17123

Comments

ncsugrad94 commented Sep 5, 2024

Steps to reproduce:

Actual behavior:

Expected behavior:

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA version:

Windows version:

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Have you tried any other versions of NVDA? If so, please report their behaviors.

If NVDA add-ons are disabled, is your problem still occurring?

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?\

Adriani90 commented Sep 5, 2024 • edited Loading

ncsugrad94 commented Sep 6, 2024 via email

RyanSMS commented Sep 6, 2024

seanbudd commented Sep 10, 2024

thgcode commented Sep 21, 2024

seanbudd commented Sep 22, 2024

thgcode commented Sep 23, 2024

Adriani90 commented Sep 5, 2024 •

edited

Loading