On 2024-06-17 23:54, Jason J.G. White wrote:
After importing an OOXML (from MS-Word) document into LibreOffice Writer
24.2.4, using Orca as the screen reader I was unable to read the
alternative text associated with an image.
I don't think I can share the document, but I would be interested to
know whether anyone else here can reproduce the issue.
To reproduce, it should be sufficient to read a line containing an imge
that has alternative text associated with it.
Microsoft 365 was able to read it, establishing its presence. I don't
know whether the problem was with use of the accessibility API or the
conversion from OOXML format.
I just tried that. When setting an "Alt Text" in Word, that is shown as
"Description" in the "Properties" -> "Options" for the image after
opening the document in Writer, and (as can be seen in Accerciser) it's
used as the accessible description, too. There's also a "Text
Alternative" that can be set in Writer, which is used as the accessible
name, if set. (Word doesn't seem to distinguish between the two at all.)
So the import from OOXML seems to work fine.
I can reproduce that Orca doesn't announce an image when announcing a
line containing an image anchored as character, even if both of the
above attributes are set.
There is this existing bug report which sounds like it describes the
same issue:
https://bugs.documentfoundation.org/show_bug.cgi?id=77679
("[ACCESSIBILITY] Accessibility support for replaced objects is incomplete")
Orca does however announce the accessible *name* (not the description by
default, at least in my setup) when using the "To Next Frame" shortcut
Shift+F4 to select the image.
--
To unsubscribe e-mail to: accessibility+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/accessibility/
Privacy Policy: https://www.documentfoundation.org/privacy
