When creating accessible documents, images and other objects need a text alternative. This text alternative is used in text-to-speech (for example in screen readers) and when converting to other formats such as audio books and Braille. In Writer, a text alternative can be added after inserting a picture, but it would be more efficient to allow users to add the text alternative while inserting the picture.
The current process is:
1. Through the menus, go to Insert -> Picture -> From file...;
2. Browse to the image file and press Open.
3. In the Writer document, right-click on the picture, then either
3.a. select Picture from the context menu, go to the Options tab and fill in the field 'Alternative (Text only)', or
3.b. select Description from the context menu, and fill in Title (if the picture is so clomplex that it requires an elaborate description, also fill in Description).
The new process would be:
1. Through the menus, go to Insert -> Picture -> From file...;
2. Browse to the image file, fill in the field 'Alternative (Text only)' and press Open.
(When you then right-click on the picture, you should find the text alternative both on the Options tab of the Picture dialog and in the Title field of the Description dialog.)
Some WYSIWYG HTML editors have supported this for years (for example the Composer that is part of Mozilla Seamonkey, and previously Netscape Composer).
See also the current working draft of the W3C Authoring Tool Accessibility Guidelines (ATAG) 2.0 and the implementation guidance at http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/#sc_b222 .
This issue is currently linked to Writer, but it is also relevant to Impress.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Version info was previously unspecified. I confirm that this functionality request is still relevant to LibreOffice 3.5.0 RC1. Changing the status from NEEDINFO to NEW.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (220.127.116.11 or later): https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
Thank you for your help!
-- The LibreOffice QA Team
This NEW Message was generated on: 2015-02-19
Marking as enhancement and sending over to the design team to mull over.
Confirming still a valid a11y requirement, nothing more needed from UX-design.
Removing comma from Whiteboard (please use a space to delimit values in this field)
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
Just to confirm the need for this: people will always be lazy and not set a title, if they don't have a very easy way to do so. Currently, setting a title for the image is really not convenient, I didn't find it in the contextual menu, and was about to think that it wasn't available at all and give up tagging my presentations...
Actually, untitled pictures should have some sort of halo around them, to show that something is wrong, just like misspelled text are underlined in red. The halo could be blue for instance to represent accessibility. And then in the contextual menu, the very first item would allow to set the title for the image (or explicitly set an empty title, for pure decorations).
Yes and you'll note that in bug 101193 we've made more of a mess by removing the Description and Name actions from the context menu. At 5.2 they can be added back by customizing the context menus.
The title in the Description dialog becomes the Alt-text entry picked up by AT for images and other objects in documents, and should be included with HTML formatting. The description can be used by AT as alternative.
And we make it more difficult missing a context menu entry for Name. The field from the Name dialog is picked up as Name for objects in Navigator.
The Name and Description actions have been moved upward in the menu structure: on the Format menu in Writer, Impress. And on the Modify menu in Draw. But it remains on the Context Menu for objects inserted into a Calc sheet.
So, if these remain "suppressed" in the UI--agree it becomes more valid to nag folks to fully attribute an image or object while being created.
One option, atleast for images as its impossible for a11y users to insert shapes, would be to always show the Name dialog (.uno:NameGroup) after inserting the image. This could be done in 2 ways:
1) Have a checkbox in the insert image dialog which can be checked to auto open the dialog (in writer the uno command would likely have to be modified as it is currently disabled when selecting an image)
2) Have a checkbox in the Tools > Options dialog for accessibility mode, where it would automatically do a variety of different things that are beneficial to a11y users. (maybe this could automatically be enabled when LO detects that a screen reader is active)
(In reply to Yousuf Philips (jay) from comment #10)
> One option, atleast for images as its impossible for a11y users to insert
> shapes, would be to always show the Name dialog (.uno:NameGroup) after
> inserting the image. This could be done in 2 ways:
At the conference, Armin pointed out this:
Ctrl+Enter with keyboard focus (F6) on a drawing object icon on Tools bar: Inserts a drawing object of default size into the center of the current view.
(In reply to Buovjaga from comment #11)
> At the conference, Armin pointed out this:
> Ctrl+Enter with keyboard focus (F6) on a drawing object icon on Tools bar:
> Inserts a drawing object of default size into the center of the current view.
Texou mentioned this in irc as well a few days back, but the shortcut isnt easily discoverable and it doesnt help a11y users doing it through Insert > Shapes. :D