JAWS doesn't read aria-describedby label on a link if you use hot keys to navigate through types of elements

[yujiahuo]

Summary

If you have an element like a link that has an aria-describedby description, that description won't be read if you navigate to it with hotkeys. If you tab over to it in a form, it will read the description.

Expected result

The description would be read consistently regardless of how you navigate to the element.

Actual result

The description is not read if you use hotkeys.

Example

JAWS version and build number

2022.2211.7

Operating System and version

Windows 10

Browser and version:

Chrome 112.0.5615.138

[stevefaulkner]

Hi @yujiahuo can you provide a test case?

[stevefaulkner]

@yujiahuo I created a test case and can repoduce

@BrettLewisVispero JAWS 2023 announces the description when navigated to with the TAB key but not when arrowed to or U/V link navigation keys used. Is there a reason why this works this way?

[stevefaulkner]

Note: NVDA = Chrome behaviour: does not announce when using arrow keys. Does announce when using TAB or U/V link navigation keys.

[yujiahuo]

Hi @yujiahuo can you provide a test case?

Oops, sorry! Thanks for making this.

[36degrees]

We've just been looking into a very similar issue to try and understand the intended behaviour and found https://github.com/nvaccess/nvda/issues/9153#issuecomment-578381262 which suggests this might be working as designed (or at least was when the comment was posted back in 2020…).

[BrettLewisVispero]

I am not aware of any reason the description should only be announced on tab. Let me create an internal issue to investigate.

[BrettLewisVispero]

Imported into ADO as bug 17971