https://bugs.documentfoundation.org/show_bug.cgi?id=172423
Bug ID: 172423
Summary: editing/a11y: Cursor navigation should land on images,
frames, OLEs, etc.
Product: LibreOffice
Version: 26.8.0.0 alpha0+ master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Created attachment 207417
--> https://bugs.documentfoundation.org/attachment.cgi?id=207417&action=edit
Simple document with text and image
Currently, images, frames and other non-textual objects are not reached by
keyboard caret movement while navigating a document.
This is a major issue for keyboard navigation and edition, which especially
impacts disabled people that cannot use the mouse and/or rely on screen
readers.
Actual behavior:
Currently, navigating a document moving the caret (using e.g. arrows) will
*not* reach embedded objects like images, frames, etc. They are essentially
on-existent for the purpose of caret navigation.
To reach them using the keyboard, one has to either use the Navigator window,
or the specific Shift+F4 shortcut. Both of these methods are mostly
disconnected from the object location inside the document (it's hard to tell
next to which paragraph the element is), and require actively looking for those
elements.
The primary impacts I see is that
1. for the visually impaired people, information is missing, and it's even hard
to *notice* that you missed some info. See also
https://bugs.documentfoundation.org/show_bug.cgi?id=77679#c16 and following.
2. keyboard editing is harder than it could: you cannot move the cursor to the
object/anchor and enter editing mode (e.g. by entries in the context menu). A
workaround is to use Shift+F4 *once you know you are close to the object you
want to edit*.
Expected behavior:
Navigating a document should allow reaching all content, without hiding some of
it away.
So what should happen (IMO) is that the caret land either *on* or *in* the
object. Care should be taken not to enter placement mode for those objects so
caret movements continue to behave as expected (e.g. not Shift+F4 followed by
caret movement behavior). If caret lands *inside* frames automatically, it
should also leave theme at the end. But just landing *on* the object (or its
anchor) and requiring an action to enter it is probably OK as well.
--
You are receiving this mail because:
You are the assignee for the bug.
