https://bugs.documentfoundation.org/show_bug.cgi?id=153918

--- Comment #3 from Michael Weghorn <[email protected]> ---
(In reply to Michael Weghorn from comment #2)
> This looks like a bug in the Windows a11y bridge (winaccessibility).
> 
> The character is shown just fine in the dialog, but the a11y
> object/description appears to be wrong: NVDA announces the wrong character
> code and this can also be seen in the Inspect tool's a11y tree, s.
> screenshot attachment 185723 [details].
> 
> It's just fine in Accerciser on Linux, though.

But then the a11y test uses the LO-internal a11y API, so the wina11y bridge
shouldn't be relevant at least for the CI issue where this was originally
observed...

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to