[Libreoffice-ux-advise] [Bug 135769] Accessibility Unnamed Button (for screenreaders)in hyphenation

[bugzilla-daemon at bugs.documentfoundation.org]

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

Michael Weghorn <m.weghorn at posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsUXEval
                 CC|                            |libreoffice-ux-advise at lists
                   |                            |.freedesktop.org,
                   |                            |m.weghorn at posteo.de
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=13
                   |                            |6025

--- Comment #5 from Michael Weghorn <m.weghorn at posteo.de> ---
(In reply to Matthias Doellert from comment #2)
> The bug could be reproduced.  Windows 10, Libre Office 7.0.0.3 (x64), NVDA
> 2020.2 and 2019.2.1
> If there is more than one possibility of hyphenation within a word, the
> shift arrows are not labeled.

Does anybody have a suggestion on what label to use for them? I can think of
simply "Previous" and "Next", but maybe there are better and more
self-explanatory suggestions.

And should these labels be visible on screen in the buttons or just set as
accessible names, which is what e.g. screen readers will use if present?

If they should be on the buttons, the can be set in the .ui file
(cui/uiconfig/ui/hyphenate.ui), otherwise accessible names can be set
explicitly in the C++ code in `SvxHyphenWordDialog::SvxHyphenWordDialog`
(cui/source/dialogs/hyphen.cxx), with sth like

        m_xLeftBtn->set_accessible_name("My accessible name");

(but using translatable strings of course).


Note that there's also  bug 136025 for the word/hyphenation not being announced
properly, so this ticket is only about the "arrow" buttons.

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