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

--- Comment #4 from V Stuart Foote <vsfo...@libreoffice.org> ---
(In reply to Heiko Tietze from comment #3)
> Don't understand what UX can contribute but adding Michael as the a11y
> expert.

Question for UX/Design

There are a number of ways we could structure the viewport movements for use at
high magnification. An Assistive Technology tool, but also of utility for
general use.

A simple checkbox to enable the AT from Tools -> Options -> Accessibility would
of course be a minimum for the viewport to track the *text edit cursor*

What makes sense for controlling the view ports of the document canvas at zooms
sufficient to allow the edit cursor to pass out of the view port?

Centering the view port onto the results during a find or spell/grammar check
movement is an obvious requirement. As compared to current haphazard way canvas
is repositioned now and that can place the result--out of view--when using the
AT.

It is less clear exactly how to handle view port during text input--when to
pan? 2nd ICU word bound, 3rd?  Too soon and it becomes annoying, too late and
it is not effective AT as the cursor can pass out of view of the magnified
portion.

Also, how to adjust viewport relative to *drawing cursor* movements. Or
movements of entire drawing objects? Those would have the same issues with how
frequently to recenter, and what would trigger? 

Should the LO control of the viewport respond to the zoom factor the user
chooses for their os/DE magnification? Somehow dynamic, or require a value
entry when toggling the AT control?

And where else in the UI for general use?  Should it be provided globally on
the Tools menu, or from the affected dialogs/toolbars? 

Lots of potential input needed to guide any dev's effort, and not just the AT
facet. So, better to have the work (affected LO modules, viewport movements
over the canvas, triggers, and locations for the controls) scoped out under
UX-advise in advance.

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

Reply via email to