Reading order of aria-description on buttons

[code-dispenser]

Hi,
I would be grateful if anyone could confirm the reading order of both browse and focus modes for an aria-description attribute used on a button.

For example:

<button aria-disabled="true" aria-description="Nothing to copy">Copy notes</button>

This seems to be read as:

Focus mode (copied directly from speech viewer): Copy notes button unavailable Nothing to copy.

Browse mode using arrow keys (from speech viewer): button unavailable Nothing to copy. Copy notes

I am using NVDA Version 2024.4.1 (2024.4.1.34550) on Windows 11 using Edge Chromium, but got the same result in the latest version of Chrome and Firefox. Removing aria-disabled just removes 'unavailable' from the output.

Is the above how it should be read as the browse mode/arrow keys announcement seems a little odd?

If not can I correct this somehow so the text is announced the same for both Focus and Browse modes?

I did read issue #14559: 'aria-description read before accessible name in browse mode' Jan 17th 2023 but this appears to still be open?

Thank you for any assistance that can be provided.

Regards

Paul.

[seanbudd]

Yes, this is how these items are read. The issue is still open for fixing, and we've slightly bumped the priority

[code-dispenser]

@seanbudd Thank you for providing the clarification. As long as I know how things currently work I can code as necessary.

Regards

Paul