Bug 74255 - [Accessibility] When accessibility is on, automatically turn on cursor in read-only and Help documents
Summary: [Accessibility] When accessibility is on, automatically turn on cursor in rea...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version: 4.2.0.4 release
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 60251
  Show dependency tree / graph
 
Reported: 2014-01-31 05:16 UTC by Marco Zehe
Modified: 2014-03-03 05:29 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Marco Zehe 2014-01-31 05:16:33 UTC 
When bringing up the help and choosing a topic, the cursor is currently not able to move through the whole document. Same is true for read-only documents.

Suggestion: Turn on the ability to move through the whole document with the caret if accessibility is detected. This would remove the requirement to choose "text selection" from the help views's context menu  first. For those who are new to LibreOffice and don't know all the keystrokes and menus yet, it is not obvious how to get the help system in working condition with a screen reader.
Comment 1 V Stuart Foote 2014-03-02 19:08:54 UTC 
@Marco, *,

Actually this can be done from the Tools -> Options -> Accessibility: Miscellaneous options where the check-box for 'Use text selection cursor in read only text documents'

Still, would be a useful enhancement to enable this by default when an AT is detected in use, and perhaps change the panel option to selectively disable the feature.
Comment 2 James Teh 2014-03-03 05:29:39 UTC 
Is there a reason this isn't enabled by default for all users, even those not using an AT? I imagine it has something to do with these keys being used for scrolling or the like, but thought it was worth asking the question. :)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.