[Libreoffice-ux-advise] [Bug 149013] Description of images, OLE objects and shapes is not exported to HTML

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Mon May 16 11:12:47 UTC 2022


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

--- Comment #13 from sdc.blanco at youmail.dk ---
(In reply to Christophe Strobbe from comment #12)

> Neither "Alternative Text" nor "Description" are primarily intended for
> tooltips.
Understood.  But BZ shows that people use or want to use the possibilities in
the software.

> 2. Sighted authors might start thinking that those attributes are intended
> for tooltips and begin use them for additional information instead of text
> alternatives.
IIUC, at present LO does not use those fields when hovering the mouse over
non-text objects. Michael was just pointing out that this possibility might be
attractive to some.

If this capability were added, then could we address your concern by using the
"help" page -- by pointing out that if this feature is being used to create
"accessible" documents, then "Text Alternative" should only be used to describe
the object.

This is an example of my point at the end of comment 10,
(a) do not tell the user what to do, but
(b) give adequate information so that they can make an informed decision about
how to use the feature.

> Is this too much detail 
Yes (in relation to help page) and No (in relation to giving a better idea of
what needs to be documented in help).


> HTML support (because I prefer to leave that out until we have fixed the
> issue of exporting long descriptions)
Assuming/hoping this will be resolved soon.  Will wait to update the help until
"the dust from construction settles".

Final question:
> Assistive technologies, such as screen readers used by blind people, should
> announce the presence of a long description to the user 
But how can these technologies know that a "long description" is present? 
Doesn't it depend on LO exporting this information to an HTML or PDF tag (or
internally to its own documents if this capability is added) in a form that
would likely to be recognized by these technologies? 

I ask because the online help has to document what happens, not what "should"
happen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Libreoffice-ux-advise mailing list